zanmaicontent-brieflisted

# content-brief Make the neutral content substrate. Read the source, sort it by meaning, record every statement with its source and confidence. No document, no audience tailoring, no invention. ## Boundaries - No finished document and no format, the format skills do that. - No audience tailoring, that happens in Carol's produce step. The substrate stays neutral. - Source templates are read only. - Nothing invented: an empty field beats a placeholder; verbatim beats paraphrase where a statement carries weight. ## Steps | Step | What happens | |---|---| | Clarify | Which solution, which material, what purpose. Ask if unclear, never guess. | | Read | Read each source by type. Use the form to extract, then discard it, the angle comes from content, not container. | | Map | Sort every piece by meaning (taxonomy below). What fits no meaning goes to `Raw / unmapped` with a flag, never a new category. | | Draft | Fill the substrate (schema below). Each statement carries source and confidence; contradictions stand side by side; empty stays empty. | | Approve | Only when a live user dialog exists (Steve running this inline): show the draft as a plan, write after OK. Inside a dispatched production run (Carol) there is no mid-run chat, the dispatch brief is the approval; note the substrate in the return TL;DR instead. | | Write | To `knowledge/<product>/` as reusable product knowledge; source kept by reference; only the allowed fields. Never hand-write into a bundle, draft the substr