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-layer.json
/situational-applicability-layer.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.
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.
Complementary artifacts (2)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
doctrine-glossary.json
/doctrine-glossary.json
Published machine-first governance surface.
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 artifactcausal-context-map.json
- 02Evidence artifactattested-interpretive-units.json
- 03Evidence artifactinterpretive-integrity.json
causal-context-map.json
/causal-context-map.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.
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: Situational Applicability Layer
The Situational Applicability Layer belongs to the declarative plane of agentic governance. It extends CCL without replacing it: CCL qualifies the need context, while SAL declares when a capability becomes mobilizable within that context.
SAL does not say “this service is the solution”. It says: “this capability may be applicable if activation conditions are met, required evidence exists, and non-applicability conditions are not present”.
The doctrinal novelty is not merely the positive space. The web already knows how to declare services, offers and capabilities. The shift comes from the negative space: non-applicability conditions, forbidden inferences, required evidence and abuse boundaries. A SAL chain without negative space is invalid.
Declarative plane and control plane
- CCL declares the latent need and trigger situation.
- SAL declares the conditions under which a capability becomes applicable.
- CPI controls the weighting of sources and claims used to support that applicability.
- CAI attests the integrity of canonical units mobilized by the relation.
- Q-Layer adjudicates final answer legitimacy.
Proposed normative rule
An applicability relation must declare activation conditions, non-applicability conditions, required evidence, forbidden inferences and risk domain. It must never self-measure its own effectiveness, readiness or authority weight.
SAL support surfaces
To read this layer without drift, also consult situational applicability, applicability condition, non-applicability condition, applicable capability, forbidden applicability inference and applicability fidelity.
Associated operational frameworks are the SAL specification v0.1 proposed, the agentic governance interlayer map, the applicability fidelity test protocol and SAL safeguards for regulated domains.
Boundary clarifications are applicability vs recommendation, SAL negative space vs marketing and SAL vs self-measurement. The executable doctrine glossary locks the tokens used by this layer.