Docs that ship with the code that changed them
READMEs, API references, ADRs, and runbooks update in the same PR — reviewable, auditable, and never silently stale.
PR merge evidence digest
## 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 (internal build)
- Intent fidelity: 0.94 (event: intent.fidelity.scored)
Digest: sha256:a4e8…9b2fReviewers see session refs, approval state, and intent fidelity in the PR they already read — bound to the same audit record.
Stale docs are a slow-motion incident
Same workflow as code
Doc updates land in the commit or PR that changed the behavior.
Reviewable before merge
Generated docs go through the same approval flow as code changes.
Template-aware generation
Repo structure and team templates produce docs in your existing format.
The docs your team actually depends on
READMEs and onboarding
Setup guides and workflow docs that stay current with actual project behavior.
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 — not weeks later.
Session replay
FinCard demo
Doc-changing agent runs stay tied to session replay, findings, and approval state — not a separate wiki workflow.
Three stakeholders, one record
Engineering leads
Onboarding docs and runbooks that reflect what actually shipped.
Security teams
Runbooks under the same review flow as code — no ad-hoc wiki edits.
Platform engineers
Templates and policy-enforced workflows that match your artifact format.
Stop treating docs as a separate workstream
Same approval, telemetry, and deployment controls as the rest of your engineering workflow.