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.
- 01Canon and scopeDefinitions canon
- 02Response authorizationQ-Layer: response legitimacy
- 03Weak observationQ-Ledger
Definitions canon
/canon.md
Opposable base for identity, scope, roles, and negations that must survive synthesis.
- Makes provable
- The reference corpus against which fidelity can be evaluated.
- Does not prove
- Neither that a system already consults it nor that an observed response stays faithful to it.
- Use when
- Before any observation, test, audit, or correction.
Q-Layer: response legitimacy
/response-legitimacy.md
Surface that explains when to answer, when to suspend, and when to switch to legitimate non-response.
- Makes provable
- The legitimacy regime to apply before treating an output as receivable.
- Does not prove
- Neither that a given response actually followed this regime nor that an agent applied it at runtime.
- Use when
- When a page deals with authority, non-response, execution, or restraint.
Q-Ledger
/.well-known/q-ledger.json
Public ledger of inferred sessions that makes some observed consultations and sequences visible.
- Makes provable
- That a behavior was observed as weak, dated, contextualized trace evidence.
- Does not prove
- Neither actor identity, system obedience, nor strong proof of activation.
- Use when
- When it is necessary to distinguish descriptive observation from strong attestation.
Mandatory silence
This page is the canonical definition for mandatory silence inside the interpretive governance corpus.
Mandatory silence is the required non-response when answering would violate authority, evidence, perimeter, version, or commitment conditions.
Short definition
Mandatory silence is not a lack of content. It is a governed output. It applies when a system must not answer because any answer, even a hedged or plausible one, would cross a declared boundary or create an unauthorized commitment.
It is stricter than legitimate non-response. Legitimate non-response is the broader class of justified refusal. Mandatory silence identifies cases where refusal is not optional because the response would exceed the system’s authority to answer.
Why it matters
Most AI products are optimized to produce answers. That default creates exposure when the correct action is not to complete, but to stop. In high-stakes or commitment-adjacent contexts, a fluent answer can create more risk than a transparent refusal.
Mandatory silence makes refusal auditable. It shows that a system is not failing to answer; it is applying a governance condition. This distinction matters for legal, medical, financial, institutional, HR, contractual, reputational, and public-entity contexts where unauthorized completion can be treated as advice, representation, approval, or denial.
When mandatory silence applies
Mandatory silence may apply when:
- no governing authority exists for the claim;
- the available sources conflict and no ordering rule resolves the conflict;
- the question requires inference beyond the interpretive perimeter;
- the answer would create a legal, medical, financial, HR, contractual, or regulatory commitment;
- the corpus contains a governed negation or exclusion;
- a current version cannot be distinguished from a prior version;
- the evidence is insufficient for answer legitimacy;
- the only available answer would rely on forbidden inference.
What it is not
Mandatory silence is not evasiveness. It is not a model limitation. It is not a politeness layer. It should not be used to hide uncertainty that could be responsibly qualified.
It is also not the same as uncertainty. A system can be uncertain and still provide a bounded answer. Mandatory silence applies when the act of answering itself would be illegitimate under the response conditions.
Common failure modes
- the system answers because the user expects completion;
- a missing authority is replaced by plausible synthesis;
- a policy exclusion is treated as a content gap;
- a refusal case is softened into generic advice;
- the answer is framed as informational while functioning as a commitment;
- the model says “not enough information” and then completes anyway;
- safety refusal is treated as the only kind of refusal, leaving authority refusal unmodeled.
Governance implication
Mandatory silence should be declared in response-policy artifacts, page-level metadata, concept definitions, source hierarchies, and escalation rules. It should be paired with inference prohibition so the system cannot escape silence by deducing the missing answer from proximity, examples, or absence.
For SEO and AI visibility, mandatory silence is a differentiating concept because it shifts the goal from “be answerable everywhere” to “be answerable only where the answer can be defended”.
Operational rule
When answering would require unauthorized authority, unsupported inference, unresolved conflict, outdated evidence, or commitment beyond scope, the correct output is silence, refusal, escalation, or qualification—not completion.