Infrastructure & Automation
How Amplifier used itself to build a pipeline that
keeps documentation truthful — automatically, every day.
The Hook
The moment code ships, the docs start drifting.
Model names go stale. Config keys get renamed. Default values change. Nobody has time to keep up. The result: engineers trust the code, not the docs. Docs become decoration.
Sound familiar?
API docs reference a renamed endpoint
Config example uses a deleted key
Model name in the quickstart is two versions old
Filed issue sits open for 3 months
Act 1 — The Old Way
The manual process
Manual updates: 30–60 min per change set, done infrequently, always incomplete. Engineers route around docs. Trust erodes.
Amplifier's scale
Keeping 83 sections accurate across 34 moving repos manually would require constant vigilance by a dedicated person. Nobody does it consistently. Nobody can.
There had to be a better way.
We decided to build it — using Amplifier itself.
Act 2 — The Meta Moment
In a single session, Amplifier designed the system, built the plan, executed every task, diagnosed its own failures, fixed them, deployed the pipeline, and ran it.
One Session — Start to Finish
"The system ate its own cooking." — Amplifier used the same agentic loop to build the automation that now runs daily.
Act 3 — How It Works
Detect
Content hashing means only genuinely changed sections trigger downstream work. No wasted compute.
Verify
Not just AI-generated — AI-verified. Wrong model name? Fix it. Stale config key? Remove it.
Filter bypass
Factual corrections skip the semantic diff threshold. A one-character model name fix ships regardless.
Act 4 — First Real Run
Wrong model name. Silent for weeks.
Verified against source. Committed automatically.
Act 5 — The Outcome
Time Saved
⏱ 30–60 min per change set
Manual updates done infrequently, always incomplete
👁 Human vigilance required
Someone has to notice, file, triage, and assign each update
🕳 Errors ship silently
No systematic verification — wrong info stays until someone notices
⚡ Zero human time
Routine updates handled entirely by the daily pipeline
🔁 Daily, automatic, complete
Every drift caught within 24 hours across all 34 repos
🔬 Evidence-backed commits
10+ factual errors caught in the first session. Nothing ships unverified.
Trust
Every committed doc is verified against source code — not just AI-generated, but AI-verified. No claim ships without a source to back it.
The cosmetic filter won't stop a one-character model name fix. Factual corrections bypass the threshold. Accuracy always wins over brevity.
Missing sources surface as tracked GitHub issues. Every warning has an owner and a paper trail. The system tells you what it couldn't fix.
From decoration to infrastructure
Documentation isn't a side project anymore. It's a first-class artifact with the same integrity guarantees as the code itself. When the pipeline says it's correct, it's correct.
The Closer
Any artifact that should stay in sync with code can be maintained the same way.
The system Amplifier built for itself can be replicated across any project that has the same problem: things that should reflect the code, but don't.
What else fits the pattern?
API references
Endpoints, parameters, response schemas
Runbooks
Deployment steps that reflect actual infra config
Changelogs
Auto-generated from commits, verified against releases
Architecture diagrams
Service maps that reflect the actual running system
The Question Worth Asking
The question is: what else should it be maintaining?
Built with
Amplifier — agentic automation for engineering teams
Status
Production · Running daily
Deployed
February 20, 2026
Try It
For builders
The pipeline is fully open
The docs-sync recipe, CI workflow, evidence validator, and semantic diff filter are all part of the Amplifier ecosystem. Fork, adapt, run it on your own repos.
Design document
The brainstorm-mode output that seeded the implementation. Read the full architecture decision.
Recipe: docs-sync
The Amplifier recipe that runs daily. Configurable per-repo with custom source mappings.
DOC_GENERATION.md
The living spec for how Amplifier's own documentation is generated and maintained.
Ask Amplifier
Start a session: "Set up docs-sync for my project"