- AI Article Pipeline
AI Article Pipeline
Understand the 8-agent pipeline that powers Alfa article generation.
Alfa’s AI Article Pipeline
Alfa runs article generation as a multi-stage pipeline instead of a single monolithic prompt. This makes the system easier to recover, inspect, and improve over time.
The Eight Stages
1. Content Architect
Frames the piece around the keyword, audience, brand context, and search opportunity.
2. Outline Writer
Builds the article structure and section hierarchy.
3. Deep Researcher
Collects source material, factual support, and competitive context.
4. Writer
Produces the first article draft.
5. Fact-Checker
Reviews article claims against the available research payload.
6. Sub-Editor
Tightens the draft, improves clarity, and removes rough edges.
7. Art Director
Adds visual context such as hero or section image data when the run includes it.
8. SEO Optimizer
Finalizes SEO-facing polish such as metadata and article readiness.
Why the Pipeline Is Structured This Way
The pipeline model gives Alfa a few advantages over a one-shot generator:
- clearer progress tracking
- recoverable failed states
- better separation between research, writing, and polish
- easier export of structured article payloads
Inputs That Matter
The article pipeline works best when three inputs are solid:
Brand Context
The saved brand profile influences voice, product framing, internal links, and audience assumptions.
Article Intent
Alfa normalizes freeform requests into a more explicit keyword and content shape, which helps the pipeline treat a request as a real article job rather than a vague prompt.
Target Length and Format
The writing flow uses target word count and article category to shape the output. In the current UI, this includes formats such as listicles, topic guides, comparisons, alternatives guides, how-to guides, and reviews.
Progress, Recovery, and Retry
Alfa persists article runs and supports status tracking rather than relying on a single request lifecycle.
That enables:
- active run monitoring
- stale run detection
- retry for failed runs
- reopening completed runs later
This recovery model is present in both the app and the CLI.
What You Get at the End
A completed run can include:
- final article content
- editor blocks
- title
- word count
- metadata such as slug and meta description
- citations
- verification score when available
- hero or section image data when present
From there you can continue in the review workspace, export to files, or publish to WordPress.