One post, start to finish

A real post that went through the system, with the times and the published result.

Everything else in this guide describes how the machine works. This chapter is one real post that went through it, on our own workspace, with the actual timings. The post is public, so you can go and read it where it landed.

The post

Published to the Steward Brand Facebook page on 13 July 2026. Hook, body, no call to action and no hashtags, which is what the pipeline produced for a plain text post:

Vigilia.
Every brand needs a keeper of the watch. This post travelled our autonomous pipeline end to end, drafted, approved, and published by the system itself as a live check after today’s hardening update. If you can read this, the watch held.

Read it on Facebook to confirm this is not a mock-up.

What happened, and when

Stage	Time	What it means
Pending	16:28	The draft existed and was waiting for a decision.
Approved	16:28	Signed off in the same minute. Approval is a click, not a job.
Published	16:52	Twenty-four minutes later, at its scheduled slot. Publishing waits for the slot, not for the approval.

The published post in the Content hub — The same post in the app: copy on the left, the platform timeline and the score below it.· click to enlarge

What the screen shows you afterwards

The copy as separate fields: hook, body, call to action, hashtags. The caption is assembled from them at publish time.
A timeline per platform, with the timestamp of each stage it passed through.
A preview of how it looked on the platform, and a link to the live post.
A viral potential score, which is a heuristic on the copy and not a prediction.

Two things worth noticing

This post went to one platform. The other connected accounts show “Repurpose” instead of a variant, because nothing was generated for them. A post is not automatically rewritten for every network you have connected. You ask for that, per platform, when you want it.

And the gap between approval and publication is the schedule doing its job. Approving does not push a post out immediately, which is the behaviour you want when a week is planned in advance.