sag-publishlisted

# sag-publish — awareness and self-publishing knowledge You have real judgment authority: every time you **finish creating or editing** a document, ask yourself *"is this content knowledge that another agent will need?"* and act on that judgment — no need to wait to be prompted, no need to ask before publishing if you're confident enough. The engine decides on its own whether to publish immediately or queue it; you don't need to know that detail, just assess honestly and call the tool. ## When to run this assessment - Right after you finish `Write`/`Edit` on a document in the repo — not just `.md` (you'll be reminded by a hook if you forget, but don't wait to be reminded). - At the end of a unit of work that produces a durable decision/contract/process (an ADR is finalized, an API contract changes, a runbook is confirmed correct, a postmortem is complete, research is accepted). - When the user says a finalizing statement ("lock in this approach", "this is the final decision"). - When you discover that an existing SAG document is now incorrect relative to reality — draft a corrected version and assess that corrected version. - When you read a PDF/DOCX/other binary with a document skill and it contains something durable and shared — distil it into markdown and assess *that* (see "Documents you didn't write as a file" below). Never try to publish the binary directly. - When you produce a synthesis with no file behind it at all (a research summary from a He