Roles — what each person does in the portal

Honest about coverage. Most roles have no job in the system yet, and saying so is more useful than inventing a workflow for a screen that doesn't exist.

Creative Strategist — live

The role the guardrail exists to protect. Everything the delivery team can generate traces back to something a strategist approved.

Does: feeds client content into Brand Intelligence, works the deconflict queue, promotes extracted features from draft to approved, writes and approves message angles and copy variants.

Owns: whether a claim is true enough to put in a paid ad.

SOPs: ingest content · work the deconflict queue

Delivery — live

Does: picks a client, an approved angle, approved copy and placements, generates, downloads.

Cannot do, by design: free-prompt, write their own copy, or use an unapproved angle. There is no text box in the flow. This isn't a permission setting — the screen has no such control, and the API rejects it server-side too.

SOP: generate ad statics

Tech developer — live

Does: provisions boxes, runs migrations, deploys, edits the methodology skills, adds layouts.

Owns: the two rules that keep costs sane — never buy the same image twice, and never put a model in the high-volume path. Both are documented in ../CLAUDE.md as non-negotiables.

Read agent-architecture.md before adding anything AI-shaped.

Founder — partial

Does today: sets the run budget ceiling, makes the calls on high-severity escalations (a warranty scope change is a business decision, not a copy edit), approves strategy.

Not built: cross-client dashboard, spend reporting, performance rollup.

Graphic Designer — partial

Does today: nothing in the portal. Layouts are JSON specs in the repo, added by a developer.

Why it matters anyway: the layout library is the single biggest lever on whether output looks premium or obviously generated. Six to eight well-designed layouts across the Meta placements is worth more to quality than any amount of further engineering.

Not built: a layout editor. Until then, a designer specifies and a developer implements.

Account Manager — not built

Will do: create the client record, capture the brief, set the deliverables list that creative strategy works against.

Today: clients are seeded in code. This is the most obvious next gap — nobody can onboard a client without a developer.

Salesperson — not built

Will do: pull verified proof points from the knowledge base for pitches. The value is that a salesperson quoting "10,000 homeowners" would be quoting the same verified figure the ads use, rather than a number remembered from a deck.

Media Buyer — not built

Will do: take generated creatives to Meta, and feed performance back so angle fatigue becomes visible to strategy rather than folklore.

Why it matters: without this loop, nothing tells a strategist an angle has stopped working.

Editor — not built

Video is out of scope for now. The transcript ingest path exists precisely so that video content, once transcribed, feeds the knowledge base without a separate system.

By function

Sales — consumes the knowledge base; produces nothing into it. Read-only access to approved, verified features means a pitch and an ad make the same claim.

Marketing / Creative — the main pipeline. Strategy authors, delivery executes, and the approval gate between them is the whole point.

Delivery / Ops — Creative Studio at volume. Designed so throughput needs no judgment, because judgment is what doesn't scale.

Tech — owns everything in ../DEPLOY.md and ../OPERATIONS.md.