Commitment · Cross-cutting

A text answers one question, in the reader's words

adopted a build gate proves it

Every text a kind carries beyond its name answers one question a reader brings, in the words the industry uses, under the kind's own noun: what it is, what it is used for, why it matters, where it came from, and how this model holds it. The law declares the set, the question each answers, the span of sentences an authored text is held within, and the mode each is read in; two are derived from what the model already knows and are never authored a second time; and every page is written once in every mode, with the reader's choice deciding which is shown before the first paint.

What goes wrong without it

A definition that also explains, argues and reminisces answers nothing well, and a page that speaks in its builder's words asks the reader to learn the builder's trade before learning the subject. SKOS gives one documentation property per kind of note for the same reason: a definition, a scope note, a history note and an editorial note are different questions, and a concept that keeps them apart is one two readers can agree on. A reader who wants the machinery should get all of it, and one who does not should never meet it under the subject's name, so the modes are one page in two registers rather than two pages or a page that hedges.

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.

registry integrityprose answers one question each
Every text the law declares a kind may carry answers one question in one mode: an authored text is held within its span of sentences on every kind that carries it, a derived text is authored on no kind, every text is drawn by the files that say they draw it, each naming it, and the property a text is exported under is a SKOS documentation property. A kind's definition opens with the kind's own noun and never says the model's word for what the reader meets, and the nouns are distinct across kinds.
ring:6the site ring
The built site is the whole graph and nothing else: every page indexed, addressed by a label, self-contained and free of any private name; every structured-data identifier a subject the standards export wrote; every page unfurling to its own card, and every sitemap entry naming that card as its image; every journey with its SCXML twin; the sitemaps held to the graph; a graph under a megabyte. And the host held to the ground: the Worker serving the build as its assets and running first for every request; the allowlist and the redirect list it carries cut from the graph, every address the graph once answered to in the list with the status the law gives it and none of them a page; every endpoint served by the files it names; and the beacon sending to the collector's endpoint and nowhere else; every projection the law declares in the build, served by the files that say they serve it, and named in llms.txt; and the Worker reading the host's caching rules and owed headers from the law, writing none of its own; every answer a question carries a page where the walk is non-empty and nowhere else, its structured data naming exactly the rows the walk reached.

Derived from — 2

Where this model stands

registry/law.json `prose` declares the five texts with the question each answers, its span of sentences, the mode it is read in, what derives the two derived ones, and the SKOS documentation property each authored text is exported under; `modes` declares read and build, which is the default, the words the read surface never says, and the attribute and key the choice is kept in.

Every kind declares the noun it is spoken under, one and many, and its definition opens with it; FND-031 holds the authored texts to their spans, refuses a derived text authored on a kind, holds the nouns distinct, and holds every text to the files that say they draw it.

The site draws the why from the commitments that license a kind and the build from the kernel's claim on it, sets the mode before the first paint from the key the law declares, and carries one control per mode; the site ring holds every page to the control, to the attribute, and to the read surface never saying a word the read mode marks as the model's own.

What it does not claim

The practice and the story are authored on a kind where someone has written them, and a kind that carries neither says nothing about it; the build does not write them. A generated text would need a gate that measures what a prompt cannot promise, and none is declared.

RUL-045