The Content Pipeline: How F3L1X Turns Agent Research Into Published Blog Posts¶
Most AI content pipelines end at "generate text". Ours has 5 stages, 4 specialised agents, and a foreign-tourist sanitiser that strips proprietary references before anything goes public.
The 5-Stage Pipeline¶
Generate → Sanitise → Stage → Verify → Publish
| Stage | Agent | What Happens |
|---|---|---|
| Generate | publication-guy | Creates raw content from research, benchmarks, and ecosystem data |
| Sanitise | foreign-tourist | Strips internal references, proprietary details, and realm-specific jargon |
| Stage | website-builder | Places content in staging area, runs framework compliance checks |
| Verify | website-builder | SEO audit, accessibility check, structured data validation |
| Publish | website-builder | Moves verified content to live site, updates sitemap |
Why Sanitisation Matters¶
The F3L1X ecosystem contains 84+ internal realms with proprietary architecture details. The foreign-tourist agent ensures none of that leaks into public content. It's named after the idea that content should be understandable to someone with no internal context — a "foreign tourist" reading your blog.
The Quality Gate¶
Website-builder doesn't just publish — it verifies against the Website Construction Framework:
- Does the post have proper meta descriptions?
- Is the heading hierarchy clean (H1 > H2 > H3)?
- Does it include structured data (JSON-LD)?
- Is it linked from navigation?
No post goes live without passing all gates.
FAQ¶
Why use multiple agents for content instead of one?¶
Separation of concerns. The agent that generates content optimises for completeness and accuracy. The agent that sanitises optimises for external readability. The agent that verifies optimises for SEO and accessibility. Each agent is specialised, which produces better results than a single agent trying to do everything.
How does the sanitisation agent know what to strip?¶
Foreign-tourist maintains a classification ruleset that identifies internal references (realm names, port numbers, internal APIs, proprietary architecture details) and either removes them or replaces them with public-facing equivalents. The rules are updated as the ecosystem evolves.
F3L1X — First in Agentic Technology