A0 decides; A6 executes
Autopost is deterministic execution after release approval, not a separate autonomous social-posting agent.
Operational previewLive, durable, planning and unavailable states must remain visually distinct.
Canonical master → A0 approval → platform-native renditions
Phase 3 · RELEASEDistribution
Head of Content approves what may enter autopost. A6/adapters execute independent publication intents, immutable rendition checksums, isolated retries and status reconciliation.
A0 release/autopost gate
No queue entry without approved lineage
Golden Short master QA, final checksum, platform rendition QA, audience/policy state, authorization, schedule slot, idempotency identity and reconciliation route are required before Head of Content can approve publication.
Adapters
not live yetDestination readiness
Instagram / Facebook · Meta publication adapter
pendingYouTube · Shorts + long-form, made-for-kids/synthetic-media metadata
pendingTikTok · Direct Post or draft fallback after account/app approval
pendingHiggsfield connectors · Optional adapter only when capability/reconciliation is sufficient
optionalReconcile ambiguity first
Unknown submission state must be checked before retry to prevent duplicate posts.
Preserve lineage
Join every result to canonical content, hook, cover, mascot, environment, model, prompt, rendition and time slot.