Commitment · Cross-cutting

Prose names only what the registry holds

adopted a build gate proves it

A text may name another governed thing, a kind by its name or anything else by its identifier, in one declared form; the build resolves every such reference to the thing's address and label, refuses one that resolves to nothing, to two things or to the text's own subject, draws it as a link, and lists on the thing named where it is named. A reference is a name and never an assertion: prose may name, only the registry relates, and a pair the prose joins that the registry does not is listed as proposed and written nowhere.

What goes wrong without it

A thing in this model is composed in part of its relationships to other things, and the prose about it names them whether or not anything checks. A name that resolves to nothing is a dead reference that reads as knowledge; a name typed by hand in a sentence is the second copy of an identifier the rename law says must exist once; and a link that is really a relationship, asserted in a paragraph and nowhere else, is a relationship the model does not know it has. Naming by identifier keeps the reference through a rename, resolving it on every build keeps it true, and refusing to let it assert anything keeps the registry the one place the model relates.

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 integrityreferences resolve
Every reference in prose resolves to exactly one governed thing, a kind by its name or anything else by its identifier, and never to the text's own subject; the texts references are read from are fields the schema and the ledger declare. A reference is a name, never an assertion: the build draws it as a link and lists it on the target, and a pair of rows a text joins that the registry does not is listed as proposed and written nowhere.
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

Berners-Lee, W3C, 1998Cool URIs don't change
Thomas R. GruberToward Principles for the Design of Ontologies Used for Knowledge Sharing

Where this model stands

registry/law.json `references` declares the form a reference takes, what it may name and the registry each resolves in, and the texts references are read from, each a string field the schema or the ledger declares.

FND-032 holds every reference to resolving to exactly one thing that is not the text's own subject; scripts/ground/graph.py resolves each once into a mention on the text's owner and a naming on the target, and lists as proposed every pair of rows a text joins whose kinds may relate and between which nothing is asserted.

The site draws a reference as a link, reads the text back as words wherever words leave the page - a description, a card, structured data, llms.txt, the standards export - and every page names where it is named; the site ring refuses a page carrying an unresolved reference, a reference not drawn as a link, or a target that does not say where it is named.

What it does not claim

A proposed pair is a note for the model's author, not a relationship: asserting one is a decision made in the registry, with the verb the grammar allows, and never by the build.

RUL-046