collect_sources
Loads the sealed source manifest and its independent source records. Direct inputs and the exact selected brand-library snapshot remain distinguishable, and a failed source pauses atawaiting_source_resolution instead of being discarded.
extract_sources
Normalizes every ready source behind one typed artifact contract. Amazon Transcribe creates timed spoken segments for authorized audio and video; Nova visual analysis supplies separately labelled observations; deterministic extractors normalize documents, web pages, and pasted text. Each segment carries a source ID, digest, and typed locator. A replacement or exclusion seals a new manifest revision before execution resumes.understand
Nimi receives the typed source package and returnsSourceAnalysis. Deterministic validation checks
source identity, evidence bounds, provenance, confidence, and analysis-only authority before persisting
the complete object and canonical digest. Ryan receives that exact persisted analysis. See
Nimi for its method and agent contracts for the handoff.
strategize
Ryan turns the persisted analysis and bounded operator, performance, and eligible AgentCore Memory context into one four-weekContentStrategy with grounded briefs. Application code validates its evidence
lineage and authority, then persists the proposal, version, and canonical digest. See
Ryan for the strategy method.
awaiting_strategy_approval
An authenticated human decision must match the current strategy digest. One rejection with required operator feedback permits strategy version 2; a second rejection terminates the job. Temi cannot run for a missing, rejected, expired, or mismatched approval. Dashboard, chat, and allow-listed Telegram decisions use the same tenant-scoped transaction.plan
Application code persists one immutable planning snapshot containing capabilities, commitments, capacity, cadence policy, posting-window observations, assets, dependencies, and calendar projection. Temi receives its exact ID and digest alongside the unchanged approved strategy and Nimi analysis. After validating and persisting Temi’s plan, deterministic code selects one eligible item for production. Temi never mutates an external calendar. See Temi.draft (typed artifact production)
Noni receives only the selected editorial item, exact Ryan brief, and referenced Nimi evidence. Dara reviews every requested typed artifact against immutable input. Deterministic code permits at most one issue-bound Noni revision, validates the complete batch, and prepares effect proposals from accepted content. See Noni and Dara; the full skills and tools inventory is here. Every action lands withrequiresApproval, risk level, and its own idempotency key material.
optional media production plan
Accepted content can be expanded into a versioned production plan for clips, reels, generated b-roll, soundtrack, captions, and deterministic composition. The plan binds every scene to authorized source excerpts or approved conditioning artifacts, records exact estimated and maximum cost, and remains inert until the operator seals and approves the current revision. Revision, explanation, status, approval confirmation, and cost-free rerender requests are available through the same conversational surface. Paid provider operations are isolated behind the production outbox and immutable mandate. Provider operation identities, submitted source digests, generated artifacts, and failures are persisted independently. A cost-free rerender may reuse verified provider artifacts but cannot create another paid operation or alter publication authority.awaiting_approval
Hard gate for X and LinkedIn publishing, image generation, and paid Nova Reel/ElevenLabs generation. Approvals arrive through the dashboard queue, chat confirmation, or a Telegram inline-button callback — all through the same decision engine. Conversational intent can locate and explain a decision, but cannot manufacture approval. Content-pack exports and ffmpeg rendering require approval. Internal draft artifacts can be stored without granting publication authority.publish
Executes policy-authorized actions in dependency order, checking effect claims and receipts first for idempotency. Dependencies are part of the immutable command digest and are rechecked transactionally before claim ownership is granted. Approval-required actions must carry the exact matching decision; internal artifact actions execute under their deterministic safe-action mandate:
Failures are classified: permanent errors stop the job visibly, transient errors nack for redelivery.