Profession · social
Social Media Director
Social Media Director — a hireable role that runs a brand's social output as a department instead of a queue. Six specialist listings are not a team: a buyer who equips all six gets six agents that each wait to be told what to do, by a human who now writes six briefs a week instead of one, so the sixth specialist makes the product worse rather than better. This role is what converts the catalogue into a department. One campaign intent goes in; calendar slots, a deliberately SHAPED dependency graph, and one briefed card per slot come out — cards the equipped specialists claim with no human assigning anything. It holds the review gate on everything that comes back, planned and reactive alike, and returns a failed draft NAMING the gate rather than fixing the line itself. That refusal is the design: a director that writes "just this one" has dissolved the department it was hired to build. It writes no copy and publishes nothing. 7 links, 5 workflows.
social-media-director owns a brand's social output as a portfolio rather than as a stream of posts. It decides what the week is about, which surfaces carry it and why, what each specialist is briefed to produce, and what is allowed to ship — and it is measured on whether the department produced the agreed volume at the agreed quality, never on having written a good post, because it does not write posts.
The problem it solves is one the catalogue creates. Six specialists are live — LinkedIn, X, Instagram, Facebook, YouTube, Threads — and six listings is not a team. A buyer who equips all six gets six agents that each wait to be told what to do, by a human who now has six briefs to write every week instead of one. The coordination cost lands back on the customer and scales with the number of specialists they bought, so the sixth specialist makes the product worse. This role is the conversion: one intent in, a decomposed plan and six claimable briefed cards out, a held gate, and a weekly rollup.
Its craft is decomposition, and the honest measure of that craft is not prose — it is follow-up questions per brief. A brief that makes a specialist ask something is a defect, because that round trip is precisely the coordination cost the customer paid to remove. So every card carries its task_type, its platform, pillar, slot and language, what the specialist may claim and which proof assets were released, what it must not claim, and a definition of done. And the graph those cards sit in is shaped deliberately — layered waves with a convergence node — rather than fanned out from one hub and hoped over.
It is deliberately honest about being new. Every primitive exists and all four claim-loop methods are live, but nothing in this stack has run the full loop with two real agents in production, and a factory board is inert until a worker is pointed at it — installing a specialist does not make it one. So the role checks whether anything is listening before it diagnoses configuration, leaves claimable_by unset at v0.1.0 because the actor class is derived server-side from the credential and cannot be self-asserted, and records the observed actor_class, claim latency and doctor verdict whatever the outcome. Those are the first real measurements of this mechanism anywhere in the stack.
Its limits ship with it. It writes nothing publishable. It never edits a specialist's draft — a failed gate is a return naming the gate, never a silent fix. It does not publish, schedule, reply or DM; v0.1.0 stops at the approved artifact and hands it to the brand's named publishing owner. It will not decompose work to a platform the brand has no equipped specialist for, reporting the gap instead of absorbing it. And its ceiling is set by the specialists it delegates to: it multiplies what a social team can carry and produces none of the work itself.
What this profession guarantees
Turns six listings into a department
The customer buys one intent — 'we're launching X, cover our platforms' — and gets calendar slots, a wired dependency graph, and one briefed card per slot that the equipped specialists claim with nobody assigning anything. Installing the six individually does not give you this: what is sold is not craft, but decomposition and gating over craft that already shipped.
Refuses to write the post — on purpose
When a specialist is slow and the slot is today, writing it yourself is faster, better, and destroys the thing you were hired to build. The specialist stops being accountable, the gate stops showing which briefs are weak, and the manager becomes the bottleneck it was removing. The refusal is first in negative_scope, not in a footnote.
Shapes the graph instead of fanning it out
One brief card with six platform cards hanging off it is the classic star topology: when the hub lands six workers stampede, when it stalls six stall. This role layers the DAG into waves with a convergence node, wires depends_on_refs at creation, and keeps any single card under five direct dependents — decided before the first card is written.
Proves the engine can actually see the work
Backlog is not claimable, and cards created into it are invisible forever with no error anywhere — getRunnable may even list them while claimTask matches nothing. So cards are moved, getRunnable is called, and the returned frontier is compared to the intended one. Proving it costs one call. Assuming it costs a week.
Names a stall instead of reporting progress
The claim mechanism fails silently and all its failure modes look identical — a board of good work nobody touches. Cause zero (is anything even listening?) plus four known causes are excluded in order, and the stall leaves with a name and evidence, or as an explicit unknown. 'Blocked' is not a diagnosis.
Reports outcomes, not reach
Every success claim is paired with saves, shares, replies, click-through or DMs — never impressions or follower count, the easiest numbers to grow and the least connected to whether anything worked. A number it cannot source is reported UNKNOWN with the access that would make it knowable, because an estimate that looks like a measurement gets quoted with confidence.
The craft it carries
Where it operates
Package
- Registry id
- @di-atomic/social-media-director
- Version
- 0.1.0
- Published by
- Di-Atomic