W4-031 · Condition 04 — The agent workforce
Sealed record
A sealed record is an append-only, hash-chained account of what happened that a third party can verify without trusting the party that wrote it — the audit layer treated as a public utility rather than as one vendor’s private log.
A record one party holds is a claim. A record anyone can verify is evidence.
When an agent causes a loss, the only thing that turns an incident into a lookup is a record that a party outside engineering can reconstruct — what was instructed, by whom, under what authority, and what resulted. A sealed record makes that verifiable by a stranger: entries are appended and never edited, each hashes over the one before it, and a correction is a new entry that supersedes rather than an edit that hides.
The position is that this is a public utility rather than a feature of whichever platform ran the agent. A vendor’s own log is a claim about itself; the estate’s audit layer is a format anyone can check offline, which is the difference between a record accepted in a dispute and one dismissed as self-serving. The falsifier is vendor logs being accepted as evidence in agent disputes at scale, which would mean the neutral layer was never needed.
The canonical definition is planned at https://flashyos.com/defined/sealed-record and does not resolve yet; until it does, this builder’s entry is the reference and says so.