Marketing
Review X and Reddit drafts with their sources, checks and open gaps. Live use is held while platform access and the two-channel pilot are checked.
Marketing
Coming soonGrow with social content is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.
This use case is held as coming soon. The local code supports evidence, drafts, exact review and saved outcomes. A seeded workflow does not prove current platform grants, writing quality or useful traffic.
Before live release, the operator must record current access, a spend cap, independent human scores and the two-channel pilot. X results cannot replace missing Reddit proof.
The artifact this use case produces, in the product view you would read it in.
Worked example
Not published yet
This workflow is not seeded yet, so there is no real output to show. We would rather leave this empty than print one we made up.
Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.
Workflow steps
Choose the brand ticket, reader and goal. Give public-use and model-use rights separately.
Use current evidence and saved opportunities. Weak evidence can produce no drafts.
Draft for each channel. Separate support and editorial checks can request at most two text repairs.
Review sources, text, target and media. Each public action needs its own current approval and platform access.
Confirmed links, schedules and unknown sends have distinct states. Missing metrics stay unknown.
The same job, on either side.
By hand
Keep facts in notes.
On Aestus
Keep approved facts linked to sources.
By hand
Copy text across channels.
On Aestus
Check the needs of each channel.
By hand
Lose the exact approved text.
On Aestus
Keep each saved version.
By hand
Guess if a failed send worked.
On Aestus
Keep an unknown send held for review.
By hand
Add numbers from different sources.
On Aestus
Keep metric windows and methods separate.
Every run is auditable after the fact, which is what makes handing the job over survivable.
Sources, claim spans, text versions and separate checks.
Exact approvals, confirmed receipts and unknown sends.
Small samples stay uncertain. Changes need owner review.
This use case reaches no system outside Aestus. It reads governed evidence and writes a document, so there is nothing to connect and no approval to wait on.
Brand-only drafts can use approved owner evidence. Account reads and public actions need current access.
No. Public actions require an exact native approval and current access checks.
No. Independent quality review and an eight-week two-channel pilot remain required before live release.
Sources