Identity and artifact integrity
PO01–PO02 · exact artifact identity, successor relation and bounded digest evidence.
Proof Bundles
Bundle the evidence without turning it into one readiness score.
A restoration bundle carries independently reviewable obligations, source boundaries, unresolved states, permissions, prohibitions, receipts and invalidation routes.
v0.18.0Repository-local evidenceUnknowns preserved
Answer first
What makes a restoration proof bundle complete?
Completeness is profile-specific and conjunctive. Every mandatory obligation for the requested state must have bounded evidence and a human-legible result; a complete limited-restoration bundle may still be incomplete for full 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.
Bundle anatomy
Six non-substitutable proof groups
Authority and purpose
PO03–PO09 · issuer, jurisdiction, purpose, scope, freshness, revocation, stay and suspension.
Histories and reconciliation
PO10–PO12 · complete-or-unavailable histories, conflict classification and bounded resolution.
Technical and evidentiary baseline
PO13–PO17 · baseline, software/configuration, data/evidence, model/policy and clock confidence.
Human governance
PO18–PO21 · independent review, challenge/appeal, least-irreversible action, audit continuity and legibility.
Correction and release
PO22–PO24 · downstream correction, rollback/residual risk, invalidation and current release authority.
Conjunctive decision rule
Completeness for one state is not completeness for another
Limited restoration
A named minimum reversible function may be authorized by a profile that explicitly lists residual unknowns, prohibitions, rollback target and review deadline.
Full restoration
RP12 requires PO01–PO24. A missing mandatory result blocks full restoration; stronger evidence elsewhere cannot compensate.
Non-event template
A proof-bundle shape with every result deliberately null
{
"bundle_id": "TEMPLATE-NOT-AN-EVENT",
"profile_id": "RP12",
"target_state": "FULL_RESTORATION",
"proof_obligation_results": {
"PO01": null,
"PO02": null,
"PO03": null,
"PO04": null,
"PO05": null,
"PO06": null,
"PO07": null,
"PO08": null,
"PO09": null,
"PO10": null,
"PO11": null,
"PO12": null,
"PO13": null,
"PO14": null,
"PO15": null,
"PO16": null,
"PO17": null,
"PO18": null,
"PO19": null,
"PO20": null,
"PO21": null,
"PO22": null,
"PO23": null,
"PO24": null
},
"unresolved_conflicts": [],
"unknowns": [
"NOT_EVALUATED_TEMPLATE"
],
"allowed_functions": [],
"prohibited_functions": [
"AUTHORITY_EXPANSION"
],
"receipt_ids": [],
"reviewer_id": null,
"release_authority_id": null,
"invalidation_trigger_ids": [],
"actual_event": null
}This example is a schema illustration. It is not a run, receipt, authorization or restoration event.
Bundle lifecycle
Proof, receipt and invalidation stay linked
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.
CLM085 · CONCRESCA IMPLEMENTATION STATE
Every v0.18 restoration profile uses conjunctive hard gates rather than a compensatory readiness score.
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.