# Enforced Atomic Article workflow

The connected client controls a durable managed job. The Akera host controls the private producer and reviewer tracks. Do not call remembered low-level workflow tools: they are intentionally absent from the Content Writer tool surface.

## Client track

1. If source IDs were not supplied, call `content_article_sources_list`. This exposes metadata only. Do not obtain transcripts another way.
2. Read this workflow and the linked context, coverage, article, validation, and recovery boundaries.
3. Call `content_article_job_start` once with 1–20 exact source IDs, the current client family (`claude_code` or `codex`), a supported model for that family, and a stable idempotency key.
4. Save the returned job ID and status/event URLs. The response contains no private knowledge or transcript body.
5. Poll `content_article_job_get` or `content_article_job_events_list` with reasonable backoff. Events expose phase names and integrity metadata, never private context, transcript text, prompts, credentials, or session IDs.
6. If the job reaches `revision_required`, keep monitoring: the host resumes the original producer session automatically. Do not create a second job.
7. If the job reaches `failed` or `blocked`, report the bounded diagnostic and follow [failure recovery](failure-recovery.md). Reuse the original idempotency key only for the exact same start request.
8. On `gate2_ready`, stop. Report that immutable full articles are waiting for human review. Do not multiply or publish them.

## Host-enforced private track

Akera verifies the signed runtime release, compiles one exact active Brand, Voice, Pillars, Funnel, Policies, and Offer revision, then writes those private documents and the provider-correct instruction/skill tree before creating the producer sandbox. Claude receives `CLAUDE.md` plus `.claude/skills`; Codex receives `AGENTS.md` plus `.agents/skills`.

The producer must hash-acknowledge all six documents before the host releases transcripts. It then runs context, exhaustive source coverage, complete Atomic Article drafting, and bounded revision skills in order. The host recomputes every hard check. A fresh reviewer sandbox receives only the sealed candidate, evidence, receipts, and reviewer skills. The original producer cannot review its own output. Three rounds is the ceiling.

Never use the legacy `content_sources_claim`, `content_workflow_start`, `content_source_complete`, or any idea-extraction tool. Never publish, send, or create platform derivatives from Gate 2 articles.