build-soplisted

# Build SOP ## Purpose Build a Standard Operating Procedure (SOP) for any recurring channel workflow — content creation, publishing, sponsor integration, launch sequence, comment triage, etc. The SOP is durable team-level documentation that survives team churn. ## Decision Logic SOPs ship with: outputs (what the SOP produces), decision-rights (who decides what), checkpoints (when to escalate), inputs needed, the steps themselves, edge cases, and revision rules. The role-design-first principle applies to SOPs themselves: the SOP needs an owner — the role responsible for updating it, deciding when to deviate, and handling edge cases. Without ownership, the SOP becomes a snapshot that dies. ## Tacit Principles 1. **The role owns the SOP.** Not the founder. 2. **Outputs first, steps second.** Define what the SOP produces before listing how. 3. **Decision-rights explicit.** Who decides at each branch. 4. **Checkpoints + escalation.** When to stop and consult. 5. **Edge cases enumerated.** Don't pretend the SOP covers all cases. 6. **Revision rules.** When does the SOP get updated, by whom. 7. **Voice-faithful where audience-facing.** Comment-reply SOPs use creator voice. ## Process ### Step 0 — Gate check operations_intelligence ≥ 30. ### Step 1 — Define the workflow What recurring task does this SOP cover? ### Step 2 — Define outputs What does running the SOP produce? ### Step 3 — Define inputs needed What's required to start? ### Step 4 — Define decision-rights Who dec