History should survive the system that displays it.
A verifiable audit trail carries inspectable evidence of accepted changes. Receiz preserves that continuity in the proof object: an authorized append verifies the predecessor and advances the same object to a successor history head while preserving its identity, source and earlier admitted history.
Verify the predecessor
Start from the complete accepted proof object and its carried history.
Admit the addition
The existing append primitive checks the actor and permitted change against that predecessor.
Carry the successor
Preserve stable object identity and prior history in the complete successor.
Review how the record advanced without reconstructing it from disconnected logs.
A service record gains an authorized inspection addition. The successor carries the earlier history and the new evidence. A reviewer can inspect that continuity from the complete original rather than treating the latest dashboard row as the only account of what happened.
Append history without replacing the original basis.
An authorized append advances the same proof object. The successor can have new bytes and a new artifact digest while retaining stable object identity. Earlier accepted history remains carried truth. A later display, server acknowledgement or mutable database record cannot erase the predecessor or manufacture a valid transition.
Sequence is carried proof structure.
Receiz history uses its carried Kai coordinates and predecessor relationships. Human-readable dates help people understand the record; sorting timestamp labels is not a substitute for verifying causal continuity. Inspect the actual sequence and applicable authority through the existing verifier and history surfaces.
Use the record across service, acceptance and investigation.
Asset service evidence, milestone acceptance and investigation handoffs all benefit when the next reviewer can inspect the earlier basis. Keep the complete original and authorized additions available to the people who need them. A valid held history proves its supported continuity; completeness against undiscovered later activity is a separate question.
Carry the original. Check it yourself.
Use a public demonstration proof object to test independent verification. Download the complete sealed example and the offline verifier. Open the verifier locally, select the held file and inspect its result. Once both files are prepared, repeat with the network disconnected. This tests the held original; it does not discover later additions elsewhere.
Questions that matter.
Is every activity log a verifiable audit trail?
No. A displayed activity list needs evidence for the claims it makes. Receiz history binds accepted additions to the predecessor proof object instead of treating display order as authority.
Does a verified trail prove compliance?
It establishes the claims supported by its proof. An organization still evaluates its applicable obligations, the scope of the record and whether the required evidence is present.
Can a correction silently rewrite an earlier event?
An admitted correction must preserve prior accepted history through the applicable authorized append. The earlier basis remains inspectable; a replacement row cannot stand in for that continuity.