brief-graphiclisted

# Design Brief — Orchestrator <!-- BUDGET_EXCEPTION: Brief carries artifact-schema-as-contract that is load-bearing and cannot move to references/. 4 downstream routes × distinct renderer consumers + 14-field frontmatter + 8-dim Quality Gate + 6 Critical Gates (one per render-failure mode) are the contract surface tools read by name. ~400 tokens over standard cap is legitimate cost, matching evaluate-landing-page sibling. --> Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OG cards, hero illustrations, OOH, ad creative. Emits an image-gen prompt or designer-handoff spec; does NOT render (not for user flow / wireframe — use `map-user-flow`). Capability metadata: [`routing.yaml`](routing.yaml). Agents + 4 downstream routes + 8-dim rubric: [`references/agent-manifest.md`](references/agent-manifest.md). Methodology: [`references/playbook.md`](references/playbook.md). **Core question:** Could a designer or image-gen tool execute this asset on-brand and on-platform without follow-up questions? ## Critical Gates — load first - **Do NOT render.** Brief only — spec + reference direction + image-gen prompt. Rendering happens downstream. - **Do NOT proceed without brand anchors.** Missing `brand/BRAND.md` or `brand/DESIGN.md` → `NEEDS_CONTEXT`, recommend `create-brand`. Hard gate fires BEFORE Cold Start (survives `--fast`). - **Do NOT invent tokens, fonts, or motion specs.** Every visual decision traces to DESIGN.md. Gap → flag, don't g