Documentation agents

Agent-written docs, under change control.

READMEs, API references, ADRs, and runbooks change in the same pull request as the code. Reviewed and recorded like any other change.

PR merge evidence digest · sample from a demo workspace

markdown
## 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…9b2f

The same evidence as code changes.

01Controls evidenced

Docs change like code. Evidence them like code.

A generated runbook is a change to a controlled system. Same evidence as the code beside it.

  1. FFIEC.SDLC-02Verifiable artifact

    Change attribution

    Development, Acquisition, and Maintenance booklet: change management

    How the session record supports it

    Pull request evidence links available agent sessions, commit hashes, and policy decisions.

    PR evidence / Check Run

    Catalog entry
  2. SOC2.CC8-03Verifiable artifact

    Change evidence integrity

    Trust Services Criteria CC8: change management

    How the session record supports it

    Evidence manifests bind exported records to hashes that local verification checks.

    Evidence package / Verifier result

    Catalog entry

02The 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 doc in the PR; the decision is recorded.
Template-aware generation
Docs follow your existing templates.

03Artifacts

What the agents keep current

READMEs and onboarding

Install steps and workflows update in the PR that changed them.

API references

Update when schemas or routes change.

ADRs, release notes, runbooks

Capture rationale while the diff context is still fresh.

Session replay

Illustrative · demo data

Verification portal sessions view showing replayable agent runs.

Doc changes stay tied to the session, findings, and approval.

Put docs under the same change control

Reviewed in the pull request, recorded in the same audit trail. Start with one repository.