Show your auditor what every agent changed.
gitta records who started each agent, what it changed, what was checked and who merged it. Every record links to the one before it, so any edit to the record shows.
The questions auditors ask, and the answers.
When agents write code, your auditor wants the same chain of evidence as for any other change, and to know which changes came from an agent.
Which changes came from an AI agent, and who started it?
Every agent is recorded with the person, the machine and the tool. Each change that reaches main shows which of its commits name an AI coauthor in their trailers.
Was the change tested before it reached production code?
Each merge records every check and its result, with your own tests run on the combined work.
Were tests or checks weakened?
Every removed test and weakened check is recorded with the exact findings and the person who ran the merge.
Can we trust the record?
One command checks the whole chain. With gitta Enterprise, the team servers keep a copy that nobody on a machine can rewrite.
Evidence for the frameworks you report on.
gitta maps each feature to the controls your auditor checks, so you can fill in a security questionnaire from one page.
- Change management, access and loggingSOC 2
- Secure development, testing and loggingISO 27001
- Secure development of products sold in the EUCyber Resilience Act
- Change control at banks and insurersDORA
- A record of how AI took part in developmentEU AI Act
From first agent to audit file.
- 01Recorded from day one
The trail starts the moment you set up gitta. There is nothing extra to turn on.
- 02Checked in one step
One command confirms that every event is still linked to the one before it.
- 03Exported for your auditor
A spreadsheet for your auditor, or event lines for your log system.
What the record holds
Paths, names, commits and results. Your source code stays out of it.
Make AI agents part of your next audit.
Tell us which frameworks you report on, and we will walk you through the evidence gitta gives you.
