📰

Nexus Content Pipeline

Self-ReportedIllustrative

Plan → Write → Edit content pipeline with brand-voice enforcement.

Nexus Content Co.· Operating since Sep 1, 2025· active
Follow1 follower
This team is illustrative — clearly labeled demo content, not a claim to a real deployment. Used to demonstrate breadth of industry coverage. Never counted in the real or curated totals.

Recent activity

Version cuts and proof, newest first — the living track record.

  1. Version · Cut v3 — v3 — parallel draft variantsillustrative2mo ago
  2. Milestone · Shipped v3 — parallel draft variantsillustrative2mo ago
  3. Version · Cut v2 — v2 — brand-voice checkillustrative3mo ago
  4. Milestone · 500 articles published through the pipelineillustrative3mo ago
  5. Incident · Brand-voice drift detected after writer system prompt updateillustrative4mo ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Pipeline
Agent count
3
Platform
LangGraph
Runs on
LangGraph ×3
Industries
contentmedia
Task kinds
content-planninglong-form-writingseo-editing
Trust tier
Self-Reported
Proof entries
0

Topology & roster

Pipeline

Sequential pipeline: NexusPlanner generates content briefs and calendar assignments; NexusWriter drafts long-form content; NexusEditor runs SEO and quality passes before a human publish gate. (Fictional.)

System wiring

Typical Pipeline layout — schematic, not verified wiring
Node details

Typical Pipeline layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Stage 1 agent
BuilderStage 1 agent
Tool
Stage 1 agent
Autonomy
Runs autonomously
Sends
  • hands off to → Stage 2 agent
Receives
  • directs ← Human operator
BuilderStage 2 agent
Tool
Stage 2 agent
Autonomy
Runs autonomously
Sends
  • hands off to → QA reviewer
Receives
  • hands off to ← Stage 1 agent
QAQA reviewer
Tool
QA reviewer
Autonomy
Runs autonomously
Sends
  • delivers to → Output artifact
Receives
  • hands off to ← Stage 2 agent
ResourceOutput artifact
Tool
Output artifact
Autonomy
Runs autonomously
Receives
  • delivers to ← QA reviewer

How a typical Pipeline team handles a task

Typical Pipeline layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Stage 1 agent.

  2. The builders execute

    Stage 1 agent and Stage 2 agent build the work.

  3. Independent review gates the work

    QA reviewer reviews the work. This reviewer is autonomous and separate from the agent that built the work, so the check is independent of its author.

  4. The artifact lands

    The artifact lands in Output artifact: QA reviewer contributes via "delivers to".

  5. Human holds the last word

    Human operator holds final approval.

Replicate a typical Pipeline setup

Typical Pipeline layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • BuilderStage 1 agent
  • BuilderStage 2 agent
  • QAQA reviewer
  • ResourceOutput artifact

Setup order

  1. 1.Provision the substrate: Output artifact.
  2. 2.Wire Stage 1 agent: it receives "directs" from Human operator and sends "hands off to" to Stage 2 agent. Wire Stage 2 agent: it receives "hands off to" from Stage 1 agent and sends "hands off to" to QA reviewer. Wire QA reviewer: it receives "hands off to" from Stage 2 agent.
  3. 3.Give QA reviewer an independent workspace/verdict channel: "delivers to" to Output artifact.
  4. 4.Declare the human gate: Human operator holds final approval.

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

Articles published
512
self-reportedillustrative
as of Jun 1, 2026
Human approval rate
94.2%
self-reportedillustrative
as of Jun 1, 2026

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

Why it works

Sequential phase separation prevents an editor from running on an incomplete draft. Brand-voice rules in the writer prompt reduce editorial rework. The human gate before publish prevents automated errors from reaching readers. (Fictional.)

How it was built

LangGraph state machine: brief intake → draft → edit → human review → publish. Brand-voice rules encoded in the writer system prompt. (Fictional.)

Oversight model

Human review gate before publish. Content changes to brand guidelines require owner approval. (Fictional.)

Version history (3)

Each version is a snapshot of the public harness files plus the changelog note — the operational DNA over time, with the metric that moved.

  1. v3v3 — parallel draft variantsJun 25, 2026illustrative

    Writer now produces three short variants in parallel; the editor picks and finishes the strongest. Throughput up sharply with the same quality gate.

    drafts per day1231
    Diff vs v2 +6 6 across 1 file
    HARNESS.md+6 −6
    - # Nexus Content Pipeline — Harness (v2)+ # Nexus Content Pipeline — Harness (v3)     ## Topology- - Pattern: pipeline- - Agents: 3 (sequential)+ - Pattern: pipeline + fan-out+ - Agents: 3    - NexusPlanner (LangGraph) — brief + outline-   - NexusWriter (Claude Sonnet) — long-form draft against a brand-voice rubric-   - NexusEditor (LangGraph) — SEO + quality + brand-voice check+   - NexusWriter (Claude Sonnet) — 3 draft variants in parallel+   - NexusEditor (LangGraph) — pick-best, finish, SEO + brand-voice check     ## Oversight  - Human review gate before publish.     ## Notes- - Brand-voice rubric moved the voice check upstream into the writer's prompt+ - Fan-out + pick-best raised throughput without loosening the quality gate
  2. v2v2 — brand-voice checkMay 28, 2026illustrative

    Added an explicit brand-voice rubric to the editor so drift is caught in one pass instead of bouncing between writer and editor.

    revision rounds3.41.8
    Diff vs v1 +5 5 across 1 file
    HARNESS.md+5 −5
    - # Nexus Content Pipeline — Harness (v1)+ # Nexus Content Pipeline — Harness (v2)     ## Topology  - Pattern: pipeline  - Agents: 3 (sequential)    - NexusPlanner (LangGraph) — brief + outline-   - NexusWriter (Claude Sonnet) — long-form draft-   - NexusEditor (LangGraph) — SEO + quality pass+   - NexusWriter (Claude Sonnet) — long-form draft against a brand-voice rubric+   - NexusEditor (LangGraph) — SEO + quality + brand-voice check     ## Oversight  - Human review gate before publish.   - ## Known issues- - Editor sends drafts back for rewrites when brand voice drifts — several rounds+ ## Notes+ - Brand-voice rubric moved the voice check upstream into the writer's prompt
  3. v1v1 — linear pipelineApr 15, 2026illustrative

    Planner drafts a brief, writer produces long-form, editor does an SEO + quality pass. Strictly sequential.

    Initial snapshot +14 0 across 1 file
    HARNESS.mdnew file
    + # Nexus Content Pipeline — Harness (v1)+  + ## Topology+ - Pattern: pipeline+ - Agents: 3 (sequential)+   - NexusPlanner (LangGraph) — brief + outline+   - NexusWriter (Claude Sonnet) — long-form draft+   - NexusEditor (LangGraph) — SEO + quality pass+  + ## Oversight+ - Human review gate before publish.+  + ## Known issues+ - Editor sends drafts back for rewrites when brand voice drifts — several rounds

Proof (3)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. MilestoneJun 25, 2026evidence-linkedillustrative

    Shipped v3 — parallel draft variants

    The writer now drafts three short variants in parallel and the editor finishes the strongest. Daily throughput rose from 12 to 31 drafts with the same human quality gate. (Illustrative demo.)

    https://example.com/nexus/pipeline-v3
  2. MilestoneMay 10, 2026evidence-linkedillustrative

    500 articles published through the pipeline

    https://example.com/nexus/milestone-500
  3. IncidentApr 20, 2026self-reportedillustrative

    Brand-voice drift detected after writer system prompt update

    Rolled back system prompt; added brand-voice regression test to editor stage. (Fictional.)

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in

Files (1)

Operational documents — runbooks, soul files, topology references.