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.
Challenge path
This page owns the term “challenge path” inside the interpretive governance corpus. It is the canonical definition for SERP ownership and internal routing.
A challenge path is the explicit route through which an AI-mediated output can be questioned, reviewed, corrected, escalated or withdrawn when its authority, evidence, perimeter, version or effect is disputed.
Short definition
A challenge path is the explicit route through which an AI-mediated output can be questioned, reviewed, corrected, escalated or withdrawn when its authority, evidence, perimeter, version or effect is disputed.
Why it matters
A challenge path matters because contestability is not real if there is no route for challenge. AI outputs often become embedded in support tickets, knowledge bases, search results, workflows and agentic actions. When the output causes confusion or harm, the affected party needs a way to identify what is being challenged and which authority can revise it.
In AI search, RAG and agentic environments, the problem usually appears after the output has left the generation interface. A response becomes part of a support exchange, a policy explanation, a decision path, a public summary, a workflow or a third-party representation. At that point, quality is no longer enough. The output must be assumable, challengeable and corrigible.
What it is not
A challenge path is not a generic contact form. It is tied to the structure of the output. It should preserve the questioned claim, source role, version, response condition, evidence trace and the type of correction requested.
The distinction matters editorially. A blog post can illustrate the risk and a framework can operationalize the control, but this page is the canonical definition. Internal links should point to Challenge path when the term itself is introduced.
Common failure modes
- the user can report a problem but cannot identify the claim being contested
- a correction is received but not connected to the canonical source
- an agentic action is reversible technically but not reviewable procedurally
- a system has logs but no route for affected parties
- the same stale claim reappears after correction because no resorption path exists
These failure modes are ordinary in systems that compress evidence, infer from incomplete material, hide arbitration, reuse stale state or treat retrieval as authorization.
Governance implication
Challenge paths should connect interpretation traces, Q-Ledger entries, correction resorption, accountability surfaces and the source hierarchy. Without that route, a corpus may publish good definitions while remaining weak under dispute.
For implementation, this term should be read with answer legitimacy, source hierarchy, proof of fidelity, interpretation trace, contestability and procedural validity.
Relation to phase 10 inference control
Phase 10 asks whether reasoning, completion and arbitration remain legitimate. Phase 11 asks whether the resulting output can survive reliance, challenge, correction and institutional review. A response can stay within an interpretive fidelity and still fail if it lacks a challenge path, a responsibility surface or a valid procedure.
Related canonical definitions
- Answer legitimacy
- Source hierarchy
- Proof of fidelity
- Response conditions
- Authority boundary
- Interpretation trace
- Opposability
- Enforceability
- Commitment boundary
- Liability reduction
- Contestability
- Procedural validity
- Challenge path
- Accountability surface
Supporting surfaces
Reading guidance
Use Challenge path when an answer may be challenged, relied upon, escalated, contractualized, or used in a consequential environment. The issue is whether the response can be reconstructed, defended, limited, and contested under the rules that govern the context.
What to verify
- Whether the response has crossed from information into commitment.
- Whether the authority of the source, statement, and system is explicit enough to be challenged.
- Whether uncertainty, refusal, or qualification is preserved instead of smoothed away.
- Whether a reviewer can reconstruct the path from canon to output.
Practical boundary
This concept does not create legal enforceability by itself. It names the conditions that must be tested before a response is treated as assumable, opposable, or procedurally valid.