What problem does it solve? Writing ranking-grade blog content for agency clients requires grounding in fresh client context, entity coverage matching top-10 SERP results, extractable answer blocks, and structured QA — a process that is slow and inconsistent when done manually. ## Core Features & Use Cases - End-to-end content job orchestration: Resolves the client, creates a blog content job via the AIOS API, waits for the pipeline to draft and self-QA, then fetches the draft, keywords, and Article JSON-LD schema. - 14-dimension QA gate: Evaluates entity coverage, snippet extractability, fact grounding, intent match, and information gain against an 85-point threshold with per-dimension minimums before any human approval. - Degradation and gap handling: Detects [NEEDS:] fact markers, stale context lag, and degraded mode when SERPER/ANTHROPIC keys are missing, routing everything to a human review gate instead of auto-publishing. - Use Case: An operator says "write a blog post for Acme Plumbing on how tankless water heaters save money" and receives the draft, QA scorecard, and JSON-LD for lead approval. ## Quick Start Ask the assistant to write a blog post for a specific client on a specific topic, for example: write a blog post for Acme Plumbing on how tankless water heaters save money.
