What problem does it solve?
Turn potentially sensitive technical material (logs, configs, diagnostics, reports) into a shareable, reviewable, public-safe artifact while keeping the raw source separate and preserving the core lesson after redaction. This reduces the risk of leaking secrets, topology, or internal identifiers when material must be shared with a broader audience or published.
Core Features & Use Cases
- Structured Sanitization: Inspect input for tokens, private paths, topology, and internal identifiers, then remove, redact, or generalize sensitive details while preserving meaning.
- Source Separation & Placement: Keep raw material distinct from the sanitized surface and place the sanitized artifact in the project's canonical public-safe location for discoverability.
- Verification & Transparency: Record what was generalized or removed, name remaining uncertainty, and verify the sanitized output remains useful for the intended audience.
- Use Case: Convert an incident log or diagnostic output into a public incident summary that teaches the technical lesson without exposing secrets or internal topology.
Quick Start
Use aoa-sanitized-share to produce a public-safe version of the attached system log, place the sanitized artifact in the project's public-safe directory, and document the redactions and remaining uncertainties.
