Commitment · Foundational

The model is written in the standards its foundations name

adopted a build gate proves it

Answers Ontology · Topology · Derivation

On every build the model is written, from the verified graph and without a clock, in the standards its foundations name: the kinds as OWL classes and SKOS concept schemes, the relationships as object properties with domain, range and named inverse, the rows as individuals and concepts with their labels, definitions and alternate labels, the assertions as triples, the cardinalities and spines as SHACL shapes, the acyclic relationships as SHACL-SPARQL constraints, each declared question as a SPARQL property path, and the artifact's derivation from its ground in PROV. Every identifier is the one the site's structured data already publishes.

What goes wrong without it

A foundation that names a standard and is never written in it has named an aspiration. Written in the standard, the model can be proved by a validator that is not this build, and a declared question can be answered by a query engine that is not this build; two engines over one ground agreeing is a stronger fact than one engine agreeing with itself. It also makes the model portable: a graph store, a reasoner or an agent that speaks these standards reads it without reading this repository.

What proves it — 1

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.

ring:8the standards ring
A SHACL validator and a SPARQL engine that are not this build agree with it.

Derived from — 5

Where this model stands

public/standards/ holds the ontology, the individuals and assertions, the shapes and the queries, generated by the build and identical on every build from the same ground; the site publishes all four at /standards/, names them in llms.txt, and the site ring refuses a build that generated them and did not serve them.

scripts/standards_prove.py runs a SHACL validator over the shapes and every question's query over the triples, and holds each answer's size to the reach the build recorded. It runs outside the build, because it needs a validator the build does not carry, and the ship script runs it whenever the validator is present.

The proof is a gate on every push, where its validator is installed; locally it runs whenever rdflib and pyshacl are present, and the ship script says when it did not.

RUL-032