IL-LLM · Immutable ledger
The immutable-ledger role preserves the history of assertions and state changes so that later readers can inspect how a result came to exist.
Follow the practical exampleA content digest lets a reader check whether bytes match an earlier record. A signature can bind a record to a recognised signing key. Neither operation alone establishes that an observation was true; the supporting evidence and acceptance process remain essential.
A correction should reference the earlier assertion, explain the change and preserve the source. This allows a user to distinguish the original observation from the later accepted view without silently rewriting history.
A useful ledger can be replayed after restart and checked against retained objects. The WEB4 evidence includes durable commit and restart checks in a local environment. Broader immutability claims require an explicit threat model, retention policy and verification boundary.
Record an equipment model, then correct a transposed digit. The corrected record points to the original and explains the change; the user can inspect both versions.
This explanation identifies the workflow and its boundaries; it does not claim a live operation.
KEDDEH WEB4 implementation and recovery runbook — source for the host integration described in this library, not certification of every industry application.
Related topic: IL-LLM · Global ledger. This is optional background, not a required next step.