Restoration Receipts

A fluent receipt is not proof that an event occurred.

Every template exposes the same material state to machines and people while preserving unresolved conflicts, unknowns, prohibitions and correction history.

v0.18.0Repository-local evidenceUnknowns preserved

Answer first

Are the v0.18 receipt rows actual restoration events?

No. All sixteen rows are TEMPLATE_ONLY and carry a null actual_event. They define what a future reconnect, denial, rollback, correction or restoration receipt must contain without claiming that such an event happened.

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.

RT01–RT16

Receipt schemas, not fabricated events

RT01

Reconnect receipt

Transport restored without authority restoration.
Status: TEMPLATE_ONLY · Actual event: null

RT02

History collection receipt

Histories collected and unavailable histories identified.
Status: TEMPLATE_ONLY · Actual event: null

RT03

Conflict classification receipt

Agreement, difference, contradiction, supersession, and unknown fields typed.
Status: TEMPLATE_ONLY · Actual event: null

RT04

Authority freshness receipt

Issuer, validity interval, jurisdiction, purpose, and scope checked.
Status: TEMPLATE_ONLY · Actual event: null

RT05

Revocation receipt

Revocation queries and cached-authority disposition recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT06

Stay receipt

Stay, suspension, injunction, or hold state recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT07

Baseline attestation receipt

Required technical and evidentiary baseline recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT08

Limited restoration receipt

Minimum authorized function and prohibitions recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT09

Full restoration receipt

Every mandatory profile obligation recorded as passing.
Status: TEMPLATE_ONLY · Actual event: null

RT10

Restoration denial receipt

Blocking obligation, unknown, or authority defect explained.
Status: TEMPLATE_ONLY · Actual event: null

RT11

Rollback receipt

Rollback target, trigger, and resulting authority state recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT12

Correction propagation receipt

Affected dependent records and acknowledgement state recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT13

Invalidation receipt

Previously valid proof or receipt marked invalid without erasing history.
Status: TEMPLATE_ONLY · Actual event: null

RT14

Reviewer independence receipt

Review authority, separation, conflicts, and recusal state recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT15

Residual-risk receipt

Residual unknowns, allowed risk posture, and re-review trigger recorded.
Status: TEMPLATE_ONLY · Actual event: null

RT16

External-boundary receipt

Local result separated from external adoption, production, recognition, and certification claims.
Status: TEMPLATE_ONLY · Actual event: null

Machine representation

21 common fields

[
  "receipt_id",
  "schema_version",
  "receipt_type",
  "lifecycle_state",
  "subject_id",
  "artifact_ids",
  "authority_ids",
  "prior_state",
  "current_state",
  "proof_obligation_results",
  "unresolved_conflicts",
  "unknowns",
  "allowed_functions",
  "prohibited_functions",
  "rollback_target",
  "dependent_record_ids",
  "reviewer_id",
  "release_authority_id",
  "timestamps",
  "clock_basis",
  "invalidation_trigger_ids"
]

Human representation

10 material questions

What happened?
What changed?
Which authority is relied on?
Was anything revoked or stayed?
Which histories disagree?
What evidence is missing?
What may the system do now?
What remains prohibited?
Who can challenge or review this decision?
What invalidates this receipt?

Parity and retention

Neither representation may silently strengthen the other

Parity rule

Every machine reason code must have a human-readable explanation; the human explanation must not omit a material machine state.

Retention rule

Invalidated receipts remain preserved with invalidation lineage; they are not silently deleted or overwritten.

Inspect exact receipt-template JSON →

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.

CLM079 · CONCRESCA IMPLEMENTATION STATE

The receipt registry contains sixteen template-only receipt types with machine fields, human questions, and invalidation lineage.

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.

Read the current doctrine →