publishlisted

# Publishing analysis !`docgov publish --json --compact $ARGUMENTS 2>&1 | head -c 10000` ## The rule this skill exists to enforce **An external document is a different artifact, not a copy of an internal one.** They serve different readers and answer different questions. Copying internal documentation outward — even with the secrets removed — produces documentation that is technically safe and practically useless, and it leaks information structure even when it leaks no values. ## What to do 1. **`blocked[]` — report and stop.** These contain detected sensitive patterns. List the file, line and what was found. Do not publish, do not "clean up and publish anyway" on your own judgement. Hand it back to the user. 2. **`rewrite[]` — write a new document, do not edit the old one.** Use the brief in `briefs[]`. Under the external lens: - no internal jargon, team names, ticket ids, or hostnames - no unmitigated risks, no infrastructure topology - task-oriented: what the reader wants to do, not how the system is built - prerequisites stated explicitly, because the external reader has none of your context - every example runnable exactly as written 3. **`publishable[]` — still read before shipping.** Soft flags (ticket references, email addresses, work-in-progress markers) are judgement calls, not false positives. 4. **Never publish.** This skill analyzes and drafts. A human approves and a human ships. Say that explicitly when you report, and do n