CURRENT
A typed validity state available to claims, receipts and restoration logic.
Invalidation
Correct the dependent system, not only the source line.
A material correction must reach claims, decisions, receipts, caches, simulations, human pages and machine endpoints while preserving the prior record.
v0.18.0Repository-local evidenceUnknowns preserved
Answer first
What happens when a proof, source or receipt becomes invalid?
Its validity state changes and known dependents are marked for review, invalidation or supersession. The prior record and provenance remain preserved, and affected mandatory obligations must pass again before restoration.
Truth boundary: v0.18 reports exact repository-owned bytes, deterministic local checks, schemas and analytical definitions. It does not report a fresh external capture, live shared interoperability, a production partition or restoration, adoption, legal recognition, safety certification or independent certification.
IV01–IV20
Triggers that require review or revalidation
| ID | Category | Trigger | Signal | Candidate scope | Propagation targets |
|---|---|---|---|---|---|
| IV01 | identity | Artifact identity mismatch | identity or successor relation changes | artifact, baseline, comparison, receipt | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV02 | integrity | Raw digest mismatch | exact repository/captured bytes differ | artifact, run, receipt | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV03 | integrity | Selected-field digest mismatch | canonical selected fields differ | baseline, comparison, dependent claims | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV04 | schema | Capture-scope change | fields added, removed, renamed, or retyped | comparison, materiality review | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV05 | authority | Authority expiry | validity interval ends under declared clock basis | authority receipt, restoration state | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV06 | authority | Authority revocation | valid revocation becomes known | cached permission, action authorization, restoration state | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV07 | rights | Stay or suspension discovered | valid stay, injunction, hold, or suspension becomes known | action, receipt, downstream decisions | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV08 | authority | Jurisdiction mismatch | subject, matter, territory, or institution falls outside scope | authority, decision, restoration | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV09 | authority | Purpose mismatch | proposed use falls outside authorized purpose | authority, data use, decision | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV10 | source | Source correction or supersession | publisher or authorized custodian issues corrected/successor record | artifact, claim, decision, cache | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV11 | history | Contradictory partition history | material conflicting history is discovered | reconciliation, authority, restoration | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV12 | baseline | Software/configuration drift | code, configuration, dependency, or control state differs | attestation, run, restoration | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV13 | baseline | Data/evidence drift | input data, evidence set, provenance, or contradiction state differs | run, decision, receipt | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV14 | baseline | Model/policy drift | model, policy, approval, or evaluation version differs | run, decision, restoration | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV15 | time | Clock uncertainty | clock source, offset, ordering, or expiry confidence becomes insufficient | authority freshness, history ordering | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV16 | review | Reviewer conflict or withdrawal | required independence fails or reviewer authority is withdrawn | review, release receipt | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV17 | availability | Required archive/identity service unavailable | mandatory source cannot be checked | history completeness, authority, restoration | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV18 | correction | Correction propagation failure | known dependent record remains stale or unacknowledged | claim graph, decision register, cache, receipt | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV19 | legibility | Human/machine parity failure | human explanation omits or contradicts a material machine state | legibility result, receipt, release | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
| IV20 | recovery | Rollback/residual-risk change | rollback target becomes unavailable or residual risk materially changes | restoration profile, release authority | claims, decisions, receipts, caches, simulations, human pages, machine endpoints |
Validity states
Correction is state change, not deletion
REVIEW_REQUIRED
A typed validity state available to claims, receipts and restoration logic.
INVALIDATED
A typed validity state available to claims, receipts and restoration logic.
SUPERSEDED
A typed validity state available to claims, receipts and restoration logic.
UNKNOWN
A typed validity state available to claims, receipts and restoration logic.
RESTORED_AFTER_REVALIDATION
A typed validity state available to claims, receipts and restoration logic.
Propagation rule
Known dependents cannot remain silently current
Invalidation changes validity state but does not erase the prior record or its provenance.
Every trigger requires the prior record to remain available, the affected scope to be marked, dependent targets to be identified, the safest allowed restoration state to be selected, and mandatory obligations to pass again before reuse.
Claim → evidence
Follow the exact support boundary
Repository implementation and local execution remain local evidence classes. They do not establish external adoption, production behavior, legal recognition or independent certification.
CLM084 · CONCRESCA IMPLEMENTATION STATE
The invalidation register defines twenty triggers with dependency propagation, history preservation, and revalidation requirements.
Evidence owner: exact Concresca repository registries and, only where stated, the deterministic local run record.
Repository-local design or execution evidence only; it does not establish external adoption, live shared interoperability, production restoration, legal recognition, or independent certification.Judgment-free total cognitive freedom
NO JUDGMENT WHATSOEVER. Concresca coordinates without assigning moral worth, character, guilt, danger, trustworthiness, loyalty, purity, normality, or social standing. Questions, thoughts, identities, messages, content, and conduct are not objects of Concresca judgment.