Documentation agents
Docs that ship with the code that changed them
READMEs, API references, ADRs, and runbooks update in the same PR — reviewable, auditable, never stale.
PR merge evidence digest · sample from a demo workspace
## AutoDevOps merge evidence
Session: claude-session-fincard-demo-002
Repository: fincard-network-verifier
Decision: confirm → approved
- Policy: fincard-demo-2026-04-20
- Approval: audit-fincard-004
- Intent fidelity: 0.94 (event: intent.fidelity.scored)
Digest: sha256:a4e8…9b2fThe same evidence as code PRs, bound to one audit record.
The fix
Docs that go through the same gate as code
Same workflow as code
Doc updates land in the commit or PR that changed the behavior.
Reviewable before merge
Approve or reject the generated doc inside the PR; the decision lands in the audit record.
Template-aware generation
Repo structure and team templates produce docs in your existing format.
Artifacts
What the agents keep current
READMEs and onboarding
Install steps, commands, and workflows update in the PR that changed them.
API references
Contract-facing docs update when schemas, routes, or integration behavior change.
ADRs, release notes, runbooks
Capture rationale while the diff context is still fresh.
Session replay
FinCard demo
Doc-changing agent runs stay tied to session replay, findings, and approval state.
Who benefits
Three stakeholders, one record
- Engineering leads
- Onboarding docs and runbooks that reflect what shipped.
- Security teams
- Every runbook change carries an approver, a decision, and an audit record.
- Platform engineers
- Set the doc template and policy once; every repo’s generated docs follow it.
Stop treating docs as a separate workstream
Reviewed in the PR, recorded in the same audit trail as the code. Start with one repo.