● Competency 04 — Automation Systems
Automation Systems
One run token moves through trigger, context, creation, review, approval and delivery — and leaves a receipt.
Business job: Move recurring work between systems without losing approval or accountability.
Scroll: the run branches to a second destination draft and rejoins the track.
Trigger — A real event starts the run
Flagship film · 26 s · work that moves
- 00–12 a trigger becomes context and content
- 12–20 a destination branch is approved, not assumed
- 20–26 delivery is recorded as a receipt
Systems in operation
Working structures behind the competency.
- 01
Editorial autopilot
Confidence routes the work
Sources → AI validation → human review or queue → publish → history
- 02
Multi-channel publishing
Approval-bound delivery
Content → approval → durable outbox → provider → reconciliation
- 03
Campaign distribution
Idempotent scheduled runs
Variants → languages → groups → schedule → retry → readback
- 04
Sales operations
AI does not control money
Classify → price → verify payment → activate → monitor → renew
What keeps a run straight
- 01
Approval is an explicit state between creation and delivery.
- 02
A run can branch for a second destination and rejoin the main track.
- 03
Every run ends with a receipt naming its destinations and outcome.
Technical details
- Each run carries one token, so a branch can be followed back to the point it left the track.
- Approval sits between creation and delivery, with the approving step visible.
- Delivery is reported per destination, with the run identifier attached.
Surfaces shown: website-native SVG, Canvas and native-ratio campaign media.
Have work that should move on its own?
Build