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
- 02Weak observationQ-Ledger
- 03Derived measurementQ-Metrics
- 04AttestationQ-Attest protocol
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-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.
Q-Metrics
/.well-known/q-metrics.json
Derived layer that makes some variations more comparable from one snapshot to another.
- Makes provable
- That an observed signal can be compared, versioned, and challenged as a descriptive indicator.
- Does not prove
- Neither the truth of a representation, the fidelity of an output, nor real steering on its own.
- Use when
- To compare windows, prioritize an audit, and document a before/after.
Q-Attest protocol
/.well-known/q-attest-protocol.md
Optional specification that cleanly separates inferred sessions from validated attestations.
- Makes provable
- The minimal frame required to elevate an observation toward a verifiable attestation.
- Does not prove
- Neither that an attestation endpoint exists nor that an attestation has already been received.
- Use when
- When a page deals with strong proof, operational validation, or separation between evidence levels.
Complementary probative surfaces (2)
These artifacts extend the main chain. They help qualify an audit, an evidence level, a citation, or a version trajectory.
IIP report schema
/iip-report.schema.json
Public interface for an interpretation integrity report: scope, metrics, and drift taxonomy.
AI changelog
/changelog-ai.md
Public log that makes AI surface changes more dateable and auditable.
Reconstructable evidence
Reconstructable evidence is treated here as a bridge term for evidence that is packaged well enough that a third party can reconstruct what happened, under which corpus, which version, which scope, and which comparison regime.
The word matters because many teams do not only need evidence. They need evidence that survives handoff, challenge, audit, and later review.
Operational definition
Evidence becomes reconstructable when an external reader can recover, with enough rigor, the essential chain behind a reported state:
- what corpus or source set was in scope;
- which authority hierarchy applied;
- which question class, scenario, or window produced the observation;
- which version state was current at that moment;
- what was observed, compared, or qualified.
Reconstructability therefore concerns packaging, continuity, and reviewability, not only the existence of a record.
Minimum components
A reconstructable evidence package usually needs:
- a dated source perimeter;
- a declared authority hierarchy or canonical anchor;
- an interpretation trace or equivalent path information;
- an observed or captured output set;
- enough version context to avoid mixing current, historical, and superseded states.
This is why reconstructable evidence often sits near version power, public benchmarks, observation ledgers, and snapshots, and the interpretation integrity audit protocol.
Why reconstructability matters
Without reconstructability, evidence remains fragile.
Several failure modes then appear:
- a later reader cannot tell which version was current;
- the observed output is detached from the question or test regime;
- the comparison looks persuasive but cannot really be replayed;
- a contradiction is reported without enough hierarchy to interpret it.
In that condition, evidence may still be rhetorically useful, but it becomes procedurally weak.
What reconstructable evidence does not guarantee
Reconstructability is not yet truth, legitimacy, or fidelity.
A case can be fully reconstructable and still show that:
- the output drifted;
- the canon was weak;
- the response conditions were badly governed;
- the final answer failed to preserve exclusions or negations.
Reconstructable evidence makes challenge possible. It does not predetermine the outcome of that challenge.
Difference from interpretation trace and proof of fidelity
The distinction used here is functional:
- interpretation trace explains the path from source to output;
- reconstructable evidence packages enough material for a third party to review that path later;
- proof of fidelity supports the stronger claim that the output remained inside the canon.
So reconstructability stands between raw traceability and a fidelity claim.
Why this page exists
The expression is commercially readable and institutionally useful. Capturing it matters, provided it is not allowed to replace stricter canonical objects.
On this site, reconstructable evidence is accepted as bridge vocabulary for packaging and challengeability, not as a substitute for proof of fidelity.
Service-facing packaging now captured on this site
The captured label Independent reporting depends directly on this concept, because a report that cannot be reconstructed later remains rhetorically useful but procedurally weak.
The same requirement now also feeds Multi-agent audits and Interpretive risk assessment whenever a third party must be able to replay how the case was qualified.