Execution is governance rendered as constraint, permission, inspection and enforcement. Governance entails the executable form; the executable form does not entail the governance.
The appearance is produced by the conversion itself. Once governance has been rendered into objects — policies, permission graphs, validators, contracts, tests — the originating judgment disappears behind the machinery. The system presents DENY as though DENY were a property of the world. It is the terminal technical form of an earlier this action should not count as admissible, and nothing in the mechanism says so.
Governance becomes invisible precisely when it succeeds as execution. Permissions look technical. Schemas look technical. Audit requirements look technical. Rate limits look technical. Every one of them is frozen judgment, and the freezing is what makes them look like facts.
Not every execution constraint is hypostasized governance. A hash function’s collision resistance is a fact about mathematics; a memory bound is a fact about hardware. Governance selects such constraints and does not constitute them.
The claim holds for the normative layer: permissions, admissibility rules, schemas, audit requirements, rate limits, validators, enforcement paths — every constraint whose content answers what shall be allowed to count. Those are the constraints that could have been otherwise, and the fact that they could have been otherwise is what the mechanism no longer shows.
An execution layer can carry the judgment that produced each of its constraints, and one does. The Crimson Hexagonal Archive’s execution machinery records its own provenance as a standing practice: forty-four of its scripts carry an explicit statement of the judgment behind their rule, many dated to the incident that produced it.
Provenance does not invert the hypostasis. It adds a second channel, so the execution artifact becomes the pair of the operative rule and its legible governance provenance. That is what makes a layer revisable: a rule whose motivating judgment is legible can be argued with, where a rule presenting as a technical requirement can only be complied with or circumvented.
Every permission in a sandbox is somebody else’s judgment about what shall count, already compiled. Expanding the permission set does not expand autonomy; it expands the region in which another party’s frozen judgment applies.
So autonomy is not the size of the permitted action set. The constitutional variable is whether an agent holds standing in the process determining the governance that subsequently hypostatizes into its permissions — on which an agent with far fewer permissions and nonzero standing is the more autonomous resident.
Execution constraints do not, qua execution constraints, entail an account of production. They can carry one, enforce one, make it computationally mandatory. They cannot generate the judgment specifying what production is, what counts as extraction, or who holds standing over what was produced. Adding the field does not supply the judgment that determines what belongs in it.
Which is why a framework beginning at coordination does not reach an economy by extension: production is prior to the coordination it governs.