Launch Copy — Orchestrator

3 agents (launch-copywriter → guard-checker → critic) emit a launch channel's complete native copy bundle from its launch-channel playbook pack, with the pack's §4 hard guards enforced. Capability: routing.yaml. Agents + dispatch + rubric: references/agent-manifest.md. Methodology: references/playbook.md.

Core question: Does this bundle earn the launch — every native copy piece the channel needs, clearing every §2 cap and §4 hard guard, engineered to earn first-window velocity (never beg)? A launch is a bundle, not a post — the reason this is a separate emitter from write-social.

Critical Gates — load first

Full detail: references/procedures/critical-gates.md.

1. Single-channel per artifact — multi-channel = re-invoke per channel (the launch chain fans out).
2. Pack-bound or transparent degrade — load the channel's launch-channel pack and narrate it (legibility). No pack → general principles only, stated as such; never fake channel tailoring.
3. Brand mode required (founder / company) — no silent default.
4. Hard guards are publish-blocking — the pack's §4 guards (PH: no vote-ask anywhere; Reddit: founder disclosure + 9:1 + sub-rule/flair fit) are non-negotiable. A breach unresolved in 1 guard-check revision = GUARD_FAIL → status: blocked, critic NOT dispatched.

Before Starting

Apply references/_shared/before-starting-check.md. Then: