Governance artifacts
Governance files brought into scope by this page
This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.
doctrine-glossary.json
/doctrine-glossary.json
Published machine-first governance surface.
- Governs
- Part of the corpus reading conditions.
- Bounds
- An inference zone that would otherwise remain implicit.
Does not guarantee: This file does not, on its own, guarantee system obedience.
agentic-governance-interlayer-map.json
/agentic-governance-interlayer-map.json
Published machine-first governance surface.
- Governs
- Part of the corpus reading conditions.
- Bounds
- An inference zone that would otherwise remain implicit.
Does not guarantee: This file does not, on its own, guarantee system obedience.
attested-interpretive-units.json
/attested-interpretive-units.json
Published machine-first governance surface.
- Governs
- Part of the corpus reading conditions.
- Bounds
- An inference zone that would otherwise remain implicit.
Does not guarantee: This file does not, on its own, guarantee system obedience.
Evidence layer
Probative surfaces brought into scope by this page
This page does more than point to governance files. It is also anchored to surfaces that make observation, traceability, fidelity, and audit more reconstructible. Their order below makes the minimal evidence chain explicit.
- 01Evidence artifactinterpretive-integrity.json
- 02Evidence artifactcontent-digests.json
interpretive-integrity.json
/interpretive-integrity.json
Published surface that contributes to making an evidence chain more reconstructible.
- Makes provable
- Part of the observation, trace, audit, or fidelity chain.
- Does not prove
- Neither total proof, obedience guarantee, nor implicit certification.
- Use when
- When a page needs to make its evidence regime explicit.
content-digests.json
/content-digests.json
Published surface that contributes to making an evidence chain more reconstructible.
- Makes provable
- Part of the observation, trace, audit, or fidelity chain.
- Does not prove
- Neither total proof, obedience guarantee, nor implicit certification.
- Use when
- When a page needs to make its evidence regime explicit.
Executable doctrine glossary
The doctrine glossary must not remain a reference document only. It must become a validation gate: a machine-readable artifact, versioned, attested by CAI and enforced by a script that blocks non-canonical tokens.
This rule answers a drift observed inside the corpus itself: a proposed layer can be named correctly in prose and then receive competing keys in artifacts. The glossary closes that error class.
Canonical tokens are ccl, sal, cpi, cai and q-layer. Machine tokens cas, iwl and ail are forbidden unless they appear explicitly as forbidden aliases inside the glossary.
Proposed normative rule
A layer has exactly one machine token. Already deployed tokens prevail by default. Any renaming must be an explicit, versioned migration with deprecated aliases, executable validation and changelog.