A record of the models, versions, and datasets used to generate or test software (3.6.f), review of AI generated code like manually written code (3.6.c(1)), and human review and approval for AI generated changes to security or safety critical functionality (3.6.a(2)). Attestia records the model per session, a named reviewer per agent authored commit, and required review on protected paths. The export is evidence toward the software evidence package the instruction describes.

Which agent, model, and version made each change, which person reviewed it, and that the record has not been altered since the night it was written. It is evidence for controls in the AU, CM, SA, SR, and IA families; the control map says exactly which and what would make it insufficient. We never say compliant.

No. It never adds an approval step. The review that counts is the peer review your team already does; Attestia records it. Only three things are ever blocked, a banned model or tool, a commit with no session identity, and an agent approving its own work, and each has a logged break glass.

The record lives in your git. The hosted board reads it through the GitHub App. The only thing that leaves is a hash of each day, sent to a public transparency log, and an enterprise can point that at its own log instead.

In your repository, as JSON files under a tracker folder, plus GitHub issues for tasks, notes, and questions. Attestia stores accounts and an audit log, nothing else. Git history is the audit trail and you can leave with everything at any time.

Claude Code today. Other agents follow as they add session start and end hooks, and custom and platform agents through the SDK, coming next.

Yes, a template is planned, including air gapped installs with your own anchor. The hosted board is the same app, so nothing about the record or the scripts changes between the two.

No. Hours come from a clock the engineer controls and can turn off, every figure has timestamps behind it, and any correction is signed. The point is a record the team owns, not a manager watching. Teams that do not want hours switch them off with one setting. DoWI 8430.01 says the same of delivery metrics: they inform team level improvement and are not appropriate to compare beyond the team context (3.3.c(2)).

No. Sign in is by email. A product owner opens the board, leaves notes, asks questions, and answers decisions without ever seeing GitHub.

The nightly close finalizes every day for everyone at five past midnight. An interval left open by a crashed session is closed at the last commit after it started, so it never claims time it cannot prove.