The day before an external review is the day you discover what is actually in your AI coding sessions. A real customer name buried in a tool input. A snippet of restricted code in a model response. A path that exposes more about your infrastructure than you wanted to share. The wrong answer is to clean it up by hand. By-hand redaction breaks integrity. The right answer is a redaction workflow that produces a sanitized derivative bundle with sentinels in place of the redacted content, a recorded reason on every change, and a verification step before sharing. This article walks Akmon's redact command end to end. The commands and the sentinel format are real Akmon v2.0.0 surface. Why "I will edit it by hand" does not survive Three reasons. First, the audit chain is cryptographic. If you change a byte without producing a new chain, the chain stops verifying. Your auditor opens the file, runs audit verify , gets a failure, and the conversation is over. Second, redaction without a reason is not auditable.…