Redaction
Removing a committed item's claims and tags while preserving every hash (claims hash, witness hashes, item hash) and the item code, so the inclusion proof stays valid - restoring requires claims that hash to the preserved claims hash, and only a system administrator undoes a compliance redaction.
Overview
Redaction removes a committed item’s content (its claims) and its tags while keeping every hash intact: the claims hash, the witness hashes and the item hash are all preserved, and so is the item code, so the item’s Merkle inclusion proof remains valid and the proof still shows that something was submitted in that window even though the content is withheld. Only a committed item can be redacted, moving it to the redacted state; this supports privacy and right-to-be-forgotten needs without breaking the cryptographic record. Truestamp records who redacted the item and the right they used: the item’s owner, an admin or owner of the team that owns it, or a system administrator, whose redaction is a compliance redaction. No proof can be generated for a redacted item until it is restored. A redacted item can be restored to committed only by supplying claims that canonicalize (via JCS) and hash to exactly the preserved claims hash, so unredaction is verifiable rather than a blind overwrite; the tags are not restored, and only a system administrator can undo a compliance redaction. The claims can come from the item’s proof file downloaded before the redaction, which carries them, or be pasted as JSON, in any formatting, on the item’s page; restoring is also on the APIs (JSON:API, GraphQL and MCP), with the claims as a JSON text. Redaction is not deletion; the surrounding item states and permissions are covered in the item lifecycle and the fingerprint construction in the item’s composite fingerprint.