A documentation pipeline designed around traceability and controlled change.
What docagent guarantees
The drift problem
Verification environments evolve faster than their manuals. docagent addresses that drift by extracting facts from source and build files, validating every claim against the exact Git blob analyzed, and regenerating only documentation whose source meaning changed.
The operating contract
- Capture the configured source branch as one immutable commit before reading files.
- Treat repository code, comments, scripts, README files, and configuration as untrusted data rather than instructions.
- Attach externally visible claims to file, line range, quote, and blob identity evidence.
- Build a complete candidate vault and unified diff before changing the real vault.
- Preserve Engineer Notes blocks byte-for-byte and leave unrelated notes unchanged.
- Record omissions, ambiguity, skipped files, and unsupported claims instead of filling gaps with guesses.
Deterministic control, bounded model work
A fixed graph owns routing, retries, validation, staging, and promotion. Model calls transform bounded inputs into typed outputs; they do not receive filesystem, network, or tool access and do not decide which node executes next.