System 04 · Distribution

Social engine

One piece of work, adapted per platform and posted on schedule. Comment triggers turn a public reply into a direct message without anyone sitting in the inbox.

PlatformsLinkedIn, Instagram, Facebook, X
SourceAdapted from published articles
SchedulingAutomatic, with a reconciler
DM funnelsNative private replies
Architecture

Three layers, so the guessing stays in one of them.

Directive

What to do

The SOP, written down. Goals, inputs, the tools to use, the outputs and the edge cases — in plain language, versioned like code. When we learn an API limit the hard way it gets written here, so it is never learned twice.

Orchestration

Decision-making

The only probabilistic layer. It reads the directive, calls the tools in order, handles the errors and asks when something is genuinely ambiguous. It does not do the work itself.

Execution

Doing the work

Deterministic scripts. Same input, same output, every run. Ninety per cent accuracy per step is fifty-nine per cent over five, so anything that must be right lives down here instead.

Data flow

In, through, out.

Sources
Published articles and their briefs
Brand voice and visual archetype
Comment and message webhooks
Process
  1. Adapt the article per platform
  2. Generate the visual for the format
  3. Queue to the schedule
  4. Post, then verify it actually landed
  5. Route comment triggers to a private reply
Artifacts
Platform-native post, live
Carousel, card or hero image
Captured lead from a DM funnel
Reach and engagement rollup

The verify-it-landed step exists because a scheduler that silently stops is worse than no scheduler. A reconciler re-fires anything still sitting queued past its window, so a stalled poller costs you a delay rather than the post.

Integrations

It reads your stack. It doesn't replace it.

LinkedInInstagramFacebookXAirtableClickUpGoogle DriveSlack

Read-only wherever read-only is enough. Nothing gets write access it doesn't need, and every write is logged.

Quality gates

A run either passes, or it doesn't ship.

Four hashtags maximum on any variant — truncated if the generation overruns.

The post is confirmed live on the platform, not merely accepted by the queue.

Private replies only inside the platform-permitted window.

If a gate fails, the pipeline halts and files the error. It does not retry blindly, and it does not hand you a report built on half a run.

Datasheet

The boring details.

SpecStandardDeployable
Where it runsOur infrastructureYours
Who holds the API keysUs, scoped per clientYou
CadenceMonthly, or weeklyAny schedule
Raw data retentionRebuilt each runYour policy
Artifact deliveryYour Drive and trackerYour choice
Source code accessFull
Runs unattendedYesYes
Failure alertingSlack and emailYour channels
The other systems

Same architecture, different job.

Want it in your own stack?

Deployable hands over the software, the hosting and the keys. You run it; we stay on for support.

Talk scope