Commitment · Structural

Governance and execution share one substrate

adopted a build gate proves it

A governed vocabulary says what it governs and which gate holds it, and each of its values carries what makes it real: the condition that selects it, or the files that draw it. A value may not be declared with nothing anywhere to realise it, and a rule that selects a value is written once, where the value is, and read from there by everything that acts on it.

What goes wrong without it

Every closed set here was a name and a sentence, and the sentence said the rule while the code said it again. The vocabulary for how a bound pattern draws itself stated its own selection rule four times, in English, in the law; the surface stated the same rule in TypeScript; and nothing held the two together, so changing the law would have left the surface quietly doing the old thing. In the other direction a third way of drawing could be declared, described, and pass every gate while nothing on earth drew it. Governance and execution were two substrates pretending to be one, which is the same defect as prose that outlives what it describes, one layer down.

What proves it — 2

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

Every governed vocabulary names its gate, and every value is reachableVocabularies are governed
Every block of the law or the kernel that declares `values` says what it governs and which gate holds it, and that gate is one the law catalogs. Where a value carries the condition that selects it, the conditions are total and disjoint: every shape a binding can turn out to be selects exactly one value, and no value is unreachable. A rule stated twice is a rule that drifts, so it is stated here and read from here.
registry integrityThe host answers from the law
The host's caching rules each select by one form of a path, a prefix, a suffix or the endpoints, with exactly one rule for everything else; and the headers the host owes carry distinct names. What a browser may keep and what every response carries are the law's to say, and the Worker reads them rather than restating them.

Derived from — 2

W3CShapes Constraint Language (SHACL)
Thomas R. GruberToward Principles for the Design of Ontologies Used for Knowledge Sharing

Where this model stands

registry/law.json and registry/kernel.json: every block that declares `values` carries what it governs and the gate that holds it, and that gate is a check, a ring or an eval the law already catalogs.

FND-029 finds those blocks by walking the law and the kernel rather than by reading a list of them, because a register of registers is the second copy this ground refuses. It holds each one to naming its gate.

The values of the vocabulary for how a binding draws itself carry the condition that selects them, as two inclusive ranges over how many roles and how many bindings the binding turned out to have. FND-029 holds those conditions total and disjoint over every shape a binding can be, so exactly one value is selected and none is unreachable, and both runtimes of the engine read them instead of restating them.

Each value of both view vocabularies names the files that draw it, and the site ring refuses a build where a named file does not name the value back. A way of drawing cannot be declared and left unimplemented.

registry/law.json `host` declares how the host answers: `caching`, what a browser may keep by the form of the path, and `headers`, the three a static site owes on every response. The Worker reads both from the generated address module and writes neither itself. FND-030 holds the caching rules to one form each, with exactly one for everything else, and the headers to distinct names; the site ring refuses a Worker that does not read them from the law or that writes a value of its own; the host eval proves the origin answers with them.

What it does not claim

A vocabulary whose values carry no condition is held only to naming its gate and saying what it governs. The claims a relationship may make and the ways a row may be admitted are selected by a person and not by a shape, so there is no condition to write down.

Nothing derives the condition from the drawing or the drawing from the condition. They are separate statements about one value, held together by the check, which is the weaker guarantee and the only one available while one of them is a template.

RUL-040