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.
situational-applicability-map.json
/situational-applicability-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.
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.
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.
Complementary artifacts (1)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
applicability-fidelity-test-protocol.json
/applicability-fidelity-test-protocol.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 artifactinterpretive-integrity.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.
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.
SAL specification v0.1 proposed
This specification proposes the minimum fields of a situational applicability chain. It does not yet stabilize an external standard and publishes no effectiveness score.
A valid SAL chain must declare: linkedCausalContextId, applicableCapability, activationConditions, nonApplicabilityConditions, requiredEvidence, forbiddenInferences, applicabilityAbuseBoundaries, riskClass and domain.
Negative fields are not decorative. A valid non-applicability condition must describe a plausible domain scenario where the capability should not be mobilized. A valid forbidden inference must be specific to the chain.
No self-measurement
The site may declare conditions. It must not publish its own applicabilityFit, agenticUseReadiness, authorityWeight or modelCompliance scores. Those measurements belong to InferensLab or another external auditor.