redaction-gatelisted

# Redaction Gate **Adapting this skill:** filenames below name roles in a document set rather than literal paths. `docs/standing-documents.md` describes that set, what each file does, and the tier scheme this procedure assumes. Read it once and the pointers resolve; substitute your own filenames freely. Run this before anything crosses a tier boundary outward. The governing rule in `CLAUDE.md` is that the pass must actually run and actually be checked, never assumed to have happened already, and that it applies even to Public-tier output that was derived from higher-tier material. Take one argument: the path or description of the candidate content. If none was given, ask what is being published and where it is going before proceeding. ## Step 1: Establish direction and destination Name the source tier and the destination explicitly. The gate applies to outward movement. Common destinations, all of which count: - A commit or push into any Git working tree - A repomix pack intended to leave this machine - A vendor API call, including a sub-agent running on a different account - A document handed to a person outside the tier's audience - Any published artifact or page If the destination is inward (a vendor response arriving with something sensitive in it), stop and say so. Whether this gate covers the inbound direction is an open question in `agents/claude/lead-handoff.md`, not a settled rule, and it is not this skill's job to settle it unilaterally. ## Step 2: Build the