Six-Step AI Workflow with Human Oversight
Each step shows the workspace, what the AI completed, and what still needs human review.
Steps 1, 3 and 5 need a person. Steps 3 and 5 are waiting for approval right now. Click either to open the full walkthrough.
Estimates are directional and based on stated assumptions. All names, organizations, and identifying details have been anonymized in accordance with our confidentiality agreements.
How a Global Technology Company Built Social Publishing That Backs Every Post with a Fact Sheet
Keeps a global brand present on every network without the brand ever saying something it cannot back. Every post carries the fact sheet behind its claims, every reply matches the thread it joins, and the only things that wait on a person are the calendar, the brand voice, and the customer who is actually angry. Six stations, run as a loop: what August measured writes September's calendar.
What Was Broken
What We Built
Six stations and 12 subagents. Each subagent carries its own tasks and its own refusal.
How It Runs
Calendar Planning
A person answers hereAgents draft the month's calendar across every network, attach the partner briefs and rights windows, and leave empty the slots the campaign gives nothing to say. A person owns the month. Nothing gets written until the calendar carries a signature.
Post Drafting
Nobody is asked anything hereAgents write each brief once per network, pair it with an asset cropped to every format, and cut any claim the fact sheet does not carry. Nobody sits here. Every draft passes through Brand Review before it wears the brand name.
Brand Review
A person answers hereAgents check every draft against the voice guide and the disclosure rules, queue the clean ones, and hold the rest with the exact line each one failed on. This is where a person clears the brand's own voice. Nothing queues wearing the brand name until they do.
Post Publishing
Nobody is asked anything hereAgents queue every cleared post into its slot, land it on every network on time, and stagger one story across platforms so it arrives as a sequence. Nobody sits here. A post the platform rejects goes back to Asset Pairing carrying the platform's own reason.
Community Engagement
A person answers hereAgents answer every question from the approved answer library, hide spam by the moderation rules, watch sentiment around the clock, and hand up any thread turning hostile with the whole thread attached. A person answers the angry ones. That is the reply a template must never write.
Performance Review
Nobody is asked anything hereAgents pull every post's numbers off all four networks into one record, mark what the platforms never returned, and turn what carried the month into proposed changes to next month's calendar. Nobody sits here. The proposals land on next month's calendar, where a person strikes or keeps them at sign-off.
Where a Person Decides
Operating Model
This changes how work flows through the team.
What Transfers, What Must Be True
Failure Modes
What breaks this pattern:
Without this refusal, the drafting station writes whatever makes the post read well. A product claim with no fact behind it goes out under your brand name.
The review station trusts the approved calendar instead of checking the rights window itself. You publish a partner asset after the license ended, and the partner learns it from your feed.
Without the hand-up, a complaint gets a generated reply like any other comment. That reply is now a statement your company made to someone with a grievance.
When the platform API returns nothing, the station fills the gap with a guess. Your team then makes budget decisions on numbers nobody measured.
Directional Outcomes
What the agent counts, and the station that counts it.
These counts are the tallies from one monitored run of the agents. They are not monthly or annual totals.
What Runs Where
Every step names the subagent that does the work, the record it writes, the thing that raises a question for a person, and what it is allowed to touch. This is drawn from the source, not from a diagram somebody kept in sync by hand.
plan-calendarcalendar/2026-08/<slot-id>.jsonsign-calendarcalendar/**, partners/** read-onlydraft-postsdrafts/<post-slug>/<network>.jsonbrief-unwritabledrafts/**, calendar/** read-only, assets/** read-onlyscreen-brandqueue/approved/<post-slug>.jsonawait-your-clearancequeue/**, drafts/** read-only, voice/** read-onlypublish-postspublished/<post-slug>-<network>.jsonplatform-rejectedpublished/**, queue/approved/** read-onlyengage-communityinbox/<thread-id>.jsonescalate-threadinbox/**, answers/** read-onlymeasure-performancereports/2026-08.json, playbook/proposals/<change-id>.jsonmetric-missingreports/**, playbook/**, published/** read-onlyStack
Every system this agent reads or writes.