dsh-mutation-receipt

Every time an AI agent creates, updates, or deletes a file on the host, the act vanishes the moment the session ends. Backups can restore bytes but cannot prove a touch happened; verbose logs often embed file contents that auditors may never be permitted to read.

dsh-mutation-receipt closes that gap with a single design constraint: record which file was touched, what happened to it, and the sha256 before and after — and stop there. Each mutation is appended as one JSONL line; no snippet, no diff, no preview, and no byte of content is ever stored. Path handling is strict: absolute paths outside the configured workspaceRoot are refused, and symlink-parent traversal is blocked via realpath resolution. The receipt lives entirely on local disk with zero network calls, and can be inspected through the mutation_receipt tool or the mutation-receipt CLI, both supporting session-filtered and limit-bounded queries.

It is built for engineers and managers who need to hand a compliance team, a hiring reviewer, or a security auditor a citable, append-only record of what the agent touched — a record the recipient can read even when the files it describes are off-limits, and one that is worthless if stolen because it carries no file contents.