SYS.31 / CONSTITUTION
The Constitution
The rulebook anything working on this project must respect — derived from the project rather than from a template, and editable.
What it is
The written half of what a new contributor would have to be told.
Every project has rules that are true and written down nowhere: the layer that owns writes, the transform one package must use, the environment variable whose relative path resolves to two different directories. A new engineer learns them by breaking one. An agent never learns them at all.
The Constitution is that set, written from the intelligence and the deterministic facts beneath it, in a form an agent loads alongside its Skills.
The half that can be measured
Constraints are run. The rest is judged.
CONSTITUTION what the project is, and what anything working on it must respect (judged) CONSTRAINTS the part of that which can be measured (run)
A rule like "the API is the only writer of authoritative rows" is real and is not a number. A rule like "critical findings do not increase" is a ratchet with a measurement behind it. The second kind lives in the Constraints Engine; the first stays here, where it is read rather than evaluated.
Editing it
It is yours, and the record of it changing is kept.
The generated Constitution is a first draft with evidence attached, not a verdict. Edits are versioned rather than overwritten, so a rule that changed leaves a record of having changed — which matters when a Skill written under the old version is still on somebody’s disk.
pskl pull writes the current Constitution into your repository alongside the Skills. See The CLI.