K07 · evidence-bundled critical-infrastructure assurance

Evidence Supersession

Direct answer

Evidence supersession preserves the historical receipt, requires an explicit signed transition to a later receipt, and forces dependent assurance claims to be re-evaluated.

Stable record: K07-EVIDENCE-SUPERSESSION
Claim status: PROJECT TECHNICAL PROPOSAL
Last reviewed: 2026-08-16
Research cutoff: 2026-08-16
Source type: GOVERNED PROJECT KNOWLEDGE
Currentness: Current for release 2.1.0; external sources require periodic revalidation.
Correction state: No unresolved public correction recorded for this release.
Machine record: Static JSON record

Authority and evidence boundary. K07 publishes knowledge architecture, bounded reference records, procurement structures, local validation tools, signed synthetic fixtures, and point-in-time source review. It does not certify a facility, award a contract, authorize an operation, prove truth, establish deployment, or claim current operation.

Supersession lifecycle

Prior receipt

The historical receipt remains addressable and is marked SUPERSEDED.

Successor receipt

A later sequence names the prior receipt and carries the current artifact state.

Signed transition

A separate signed supersession record binds prior, successor, reason, authority, and effective time.

Graph propagation

Dependent assurance claims are recalculated; they do not silently retain the prior state.

Correction and revocation

Supersession does not erase history. Revocation, correction, staleness, incident response, repair, retest, and currentness transitions remain explicit records with accountable authority and evidence.

Inspect the supersession schema.