THE CONTENT PIPELINE — eight operating stages
The content pipeline is the operating layer's stage sequence instantiated for SEO: a committed strategy directive enters as a brief and leaves as published pages plus typed, attested outcome records. Teardown is staffed disjoint from reconstruction (Law 2); the last two gates before the world are deliberately the dumbest things in the system. ↳ system/seo/PIPELINE.md:12
The stage sequence
↳ system/seo/PIPELINE.md:28 (§2 — the stage sequence)
Stage detail
Stage 1 Brief / framing
A committed strategy directive (itself gated upstream — strategy consensus is not this document's subject) is translated into briefs: target concept, angle, beat assignment, audience question being answered. The brief is a mini mission frame.
workers:framer
Enforcement notes
- The brief is a mini mission frame.
- Two pages targeting the same query cannibalize each other's ranking and split the audience's answer across two half-pages — a defect against both pillars of the mission (SYSTEM.md §0). The check is an independent orienter, not self-administered by the brief's author: the framer generates candidate briefs, a separate dumb check kills collisions against the content registry.
↳ system/seo/PIPELINE.md:37
Stage 2 Evidence
The draft is grounded before it is written. Inputs:
workers:(no named workers extracted for this stage — see source)
Enforcement notes
- Admissible as evidence and prioritization — what is worth covering, what the audience is being underserved on — never as the acceptance standard (V1 enforcement point 2). - Keyword data: volume, difficulty, adjacent queries.
↳ system/seo/PIPELINE.md:53
Stage 3 Draft production
Beat writers produce drafts from brief + beat directive + voice references. Production is deliberately elastic — many writers, one per beat/job, each a durable unit with its own directive and earned reference (corpus/COMMISSIONING.md).
workers:beat writers contributing writers lead writer sensor
↳ system/seo/PIPELINE.md:70
Stage 4 Elimination stages
The teardown block. Staffed separately from production (teardown ≠ reconstruction); none of these workers composes new content except as rework against a specific flag.
workers:fact-checker scanner fixer researcher
Enforcement notes
- A claim that cannot be traced to committed evidence does not ship (V2, V5: never publish uncommitted claims).
- 4a. Fact-check against the evidence pool.
- 4b. Voice 3D scan/fix pairs.
- 4c. Injection scan/fix pair.
↳ system/seo/PIPELINE.md:86
Stage 5 Compression / assembly
The lead writer composes surviving materials into the final page: on-page work (keyword placement, internal links within silo rules, semantic coverage), rich-media integration, schema. Compression is generation and gets its own elimination: assembly output passes a fidelity check — did any contributor's surviving, fact-checked point get dropped or mutated in composition? Compression may lose resolution, never survivorship.
workers:lead writer
↳ system/seo/PIPELINE.md:129
Stage 6 The mechanical gatekeeper
The last gate before release, and deliberately the dumbest thing in the pipeline: mechanical checks only. Frontmatter and schema validity, link integrity, required fields, staging completeness — everything recomputable by anyone, arguable by no one.
workers:gatekeeper
Enforcement notes
- - No single worker's output reaches the live site without passing here (V5). The gatekeeper is inside every publish path with no exceptions and no smart fallback.
↳ system/seo/PIPELINE.md:147
Stage 7 The drip publisher (pull-only release gate)
The single actor with publish access (seo/SECURITY.md §6 blast-radius doctrine).
workers:publisher gatekeeper
↳ system/seo/PIPELINE.md:162
Stage 8 Post-publication outcome observation
Publication is not the end of the loop; it is where ground truth starts.
workers:(no named workers extracted for this stage — see source)
↳ system/seo/PIPELINE.md:176
VALUEMAXX enforcement points
Mission machinery, structural — four points where the mission is enforced by the pipeline itself, not by the values gate. The headline rule: SEO data admissible as evidence, inadmissible as acceptance standard.
- SEO data is admissible as evidence, inadmissible as an acceptance standard. SEO data is admissible as evidence and prioritization input — inadmissible as an acceptance standard. SERP and keyword data shape briefs (stage 1) and inform meta work (stage 3). No gate anywhere in stages 4–6 passes an artifact because it targets a keyword well, and no elimination stage reads ranking data at all. ↳ system/seo/PIPELINE.md:194
- "Publishes thin, derivative, or valueless content" sits at the top of the consequence dial — graded there because it forks both pillars at once. The block comes from the pipeline's acceptance standards and the gatekeeper's stage-stamp requirements — mission machinery, not the values gate (quality is not a refusal; it is the standard of the work). ↳ system/seo/PIPELINE.md:194
- Velocity is defensible only through quality-adherence at volume. The pipeline is what makes the flood non-slop; if quality canaries degrade, the valves close on the publisher and admission queues, never on the elimination stages. ↳ system/seo/PIPELINE.md:194
- A ranking-motivated action that degrades audience value fails its acceptance standard — at every stage. The audience's needs are the acceptance standard. ↳ system/seo/PIPELINE.md:194
What changed from v1
| Prototype (v1) | v2 |
|---|---|
| 13 named stages, prose-ordered | Operating stages: framing → evidence → production → elimination → compression → commit/delivery → outcome observation |
| Rich Media Taste Gate: single smart LLM judge | Abolished. Dumb checklist + consequence-scaled corroboration; taste lives upstream in libraries and dials |
| Gatekeeper: voice violations warn, don't block | Every listed gatekeeper criterion blocks; non-blocking criteria are removed from the gate |
| Publisher: push-on-schedule | Pull-only release gate with currency re-check |
| Analytics as untyped dumps | Typed, attested outcome records in the ledger |
| Cannibalization check self-administered by Content Director | Independent dumb check against the content registry |
| Fixed per-gate thresholds | One consequence dial (specs/CONSEQUENCE.md) |
| No injection stage | Injection scan/fix pair before assembly |
↳ system/seo/PIPELINE.md:213 (§4 — what changed from the prototype)