05 · tool · Social publishing desk
Social Os
Your accounts speak from seven places at once. Nobody reads the whole queue before it goes out, so you learn what your brand said at the same time as everyone else.
Everything your accounts are about to say sits in one queue, and nothing leaves it until you say yes.
- One queue for every account
- Approve, edit or reject in one click
- Off-voice drafts are held, not sent
The night shift proposes three subjects at most, and has never been allowed to publish.
01
What the tool does today
A console of workflows, not a stats page: each one drafts, and drops what it drafts into one queue before anything reaches an account. What you see here runs on fixed demo data, with no platform call; section 03 says what wiring it to real accounts takes.
The workflow console
Make it, send it, answer it, measure it: four kinds of work on one screen. Each workflow is on or paused, opens into its own rule, and runs on demand. You see what your accounts are doing without opening seven apps.
Every rule, three lines
When, then, guard. What sets it off, what it does next, what holds it back: three lines you can read without an engineer. Its conditions and its recent runs sit underneath, in plain words.
One draft, seven destinations
Write once. The composer checks each platform's character limit as you type, and a destination that overflows blocks the send. It never posts by itself: the draft lands in the approval queue with its voice score attached.
The approval queue
One screen holds every draft waiting: platform, target, text, and a voice score against a threshold of 80. Under 80 a draft is flagged and cannot ship as written. Approve, edit or reject, and the ledger updates as you click.
The agent, in plain terms
Its persona and objective are written out, and so are its rules for comments and for messages, in plain language. A median voice score, a median time to first reply, and a supervision tile reading on: nothing goes out without a human.
Honestly uneven
Seven platforms, and they do not offer the same things: what posts, replies, messages or hides changes from one to the next. The app is registered under your own name, wired in three steps, and your keys never leave your vault.
02
How it works
One path for everything the agent is about to say: trigger, draft, score, queue, ledger. No step skips the one before it.
- 01
Trigger
A comment, a message, a long video, a post beating its own median. Each workflow watches one signal.
- 02
Agent
Drafts the reply, the post, the clip or the message, against the rules and the voice you gave it.
- 03
Voice score
Scored against your account voice, threshold 80. Under it, the draft is held, not sent.
- 04
Queue
Approve, edit or reject, one click each. Nothing leaves before a human decides.
- 05
Ledger
Every verdict kept: who decided, when, and why, beside the draft it answers.
03
How it can grow
What you see today is the demo: the console, the composer, the governed queue, on fixed data, with zero platform call. V2 is the same system wired to real accounts.
V1 · the pitchable demo
The console, the composer with its live per-platform limits, the approval queue with its threshold and its ledger, the agent panel, the integrations map. One reconciled set of demo data, and not a single outbound call.
V2 · wired to real accounts
OAuth through an app you register yourself, one platform first. Real publishing and scheduling, webhooks for comments and messages, an analytics store instead of a snapshot, the voice score run by the real engine. A direct message becomes a lead in your pipeline.