A commitment says whether the build proves it

Answers Epistemology · Deontics

A commitment is an agreement to use these shapes coherently, not a preference and not an industry standard. Each one therefore declares whether it is enforced, meaning a named build check tests it on every run, or guidance, meaning it is a commitment no check can test. Only an enforced commitment may name a check, an enforced one must name at least one, and a proposed one may never be enforced. A foundation derives its checks from the commitments it holds. Following minimal ontological commitment, the model states the weakest theory that still does the work: what it has not committed to stays visibly uncommitted rather than being asserted for completeness.

What goes wrong without it

A stated rule and an enforced rule look identical on a page, and the difference is the whole of the value: one is an intention, the other a guarantee. Declaring which is which stops a model claiming verification it does not have, and leaves what it has not committed to visibly open rather than quietly filled in.

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.

• foundation integritygovernance classification
  Every rule declares whether a build check proves it; only an enforced rule names a check, every check is claimed by one, and no commitment or foundation states a count the model does not currently have.
• Every gate is claimed, and every claim resolvesGate coverage
  Every gate a commitment names is a check, a ring or an eval the law catalogs; and every gate the law catalogs is claimed by an enforced commitment, or says itself why nothing here can claim it.

Derived from — 3

• Thomas R. GruberToward Principles for the Design of Ontologies Used for Knowledge Sharing
• W3CShapes Constraint Language (SHACL)
• Dublin Core Metadata InitiativeThe Singapore Framework for Dublin Core Application Profiles

Where this model stands

Every commitment declares whether a check proves it. Guidance names no check, an enforced commitment names at least one, and a proposed commitment is never enforced.

Every build check is claimed by at least one enforced commitment, so no check enforces something never committed to.

Every deferred boundary stays visibly open rather than filled in for completeness.

Each build issues one conformance report — whether the graph conforms, when it was verified and how many checks ran — the receipt a validation is expected to yield.

RUL-016