Autonomous Content System

The publish-critical path is sequenced in code, not left to a creative model: author, polish, risk-gate, publish. A three-layer fail-closed LLM judge checks content safety, compliance rules and machine-voice tells, backed by per-persona dry-run, canary and live modes, an environment-level kill switch, idempotent publishing and operator escalation into a triage queue.

1. Deterministic spine, model-driven leaves: the publish-critical sequence is owned by code, giving every safety control a fixed, verifiable attachment point.
2. Three-layer fail-closed safety gate: content safety, compliance hard-fail rules bound only to the injected style guide, and a tone gate that rejects machine-voice tells.
3. Defense in depth for publishing: dry-run to canary to live per persona, typing the account name to go live, per-draft allowlists and a production lockout on manual triggers.
4. Self-healing runtime: transient-versus-permanent error classification, a two-stage session watchdog, a boot-time orphan reaper and idempotency keys so retries can never double-post.
5. The full platform: a five-workspace TypeScript monorepo, an operator console with runtime cron editing and Slack alerting, and CI/CD to Kubernetes with Vault-managed secrets.

For a system whose output is public and irreversible, the architecture keeps the critical path deterministic: code sequences every publish-critical step, and models operate only at the leaves. Production incidents were closed with durable tooling rather than patches: forensic queue inspection, crash-safe log streaming, and a zero-downtime storage migration with a resumable backfill.