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.
governed-context-runtime.json
/governed-context-runtime.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.
governed-context-runtime.json
/.well-known/governed-context-runtime.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.
intent-registry.json
/intent-registry.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.
Complementary artifacts (1)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
intent-registry.json
/.well-known/intent-registry.json
Published machine-first governance surface.
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 artifactattested-interpretive-units.json
- 02Evidence artifactcontent-digests.json
- 03Evidence artifactdoctrine-glossary.json
attested-interpretive-units.json
/attested-interpretive-units.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.
doctrine-glossary.json
/doctrine-glossary.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.
Governed Context Runtime
The Governed Context Runtime is proposed infrastructure, not a doctrinal layer. It serves a precompiled artifact for a canonical intent token already selected by an external agent.
The runtime does not select intent from a free request. It does not generate an answer, recommend a service, measure output fidelity or modify the published governance package.
The intended sequence is closed: the site declares intents, CI precompiles packs, CAI attests units, then an isolated runtime serves the exact requested pack.
v0 boundary
v0 composes nothing at request time. Admissible inputs are closed identifiers such as intentToken, lang, version, packId, unitId and digest.
Prompts, conversations, answers, personal identities, raw IPs and cookies are out of scope. Any future ledger must measure only technical distribution events.
Relation to doctrinal layers
CCL and SAL declare context and applicability. CPI and CAI control source weighting and integrity. Q-Layer adjudicates response legitimacy. The runtime replaces none of these layers: it only distributes a precompiled view of the governed corpus.
See also the canonical intent registry, governed context packs and runtime vs generative agent.