Redact for Public Disclosure

Split a reverse-engineering research repo into a private source-of-truth and a public-disclosure subset using a redaction checker, pattern deny-lists, and an orphan-commit publish pattern. Methodology travels; specific findings stay private.

When to Use

• Publishing methodology findings about a closed-source CLI harness you integrate with
• Preparing an upstream proposal or bug report to a project you do not own
• Archiving a private research repo as a public reference
• Promoting investigation notes (Phase 1-4 artifacts) into a public guide
• Establishing a publish pipeline before findings accumulate so leak risk does not back up
• Cleaning up after a near-miss where a draft almost shipped a sensitive identifier

Inputs