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 artifactsituational-applicability-map.json
- 02Evidence artifactdoctrine-glossary.json
situational-applicability-map.json
/situational-applicability-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.
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.
Declaration vs Qualification
Declaring a canonical intent does not automatically qualify a user request.
The registry says: this token exists, here is its scope, its possible CCL/SAL links, its exclusions and expected packs. It does not say: this request belongs to this token.
Qualification remains an external operation. It may be performed by an agent, evaluation protocol or human, but it must not be inferred by the runtime itself.
This distinction protects the SAL doctrine: declared applicability does not mean recommendation, necessity, guarantee or measured fit.