A record of how AI took part in your development.
As the EU AI Act lands, teams are being asked a plain question about their own software: where did AI touch this code, and can you show it. gitta answers it as a matter of record. It marks which changes came from an agent, keeps who directed each one and what was checked, and holds all of it in an immutable, tamper-evident trail.
- Author
- anna@acme
- Co-authored-by
- Claude Code <agent>
- Checked
- tests pass, 1 security flag resolved
- Merged by
- ben@acme
What a record of AI in development has to show.
Not a policy document, but the trail itself: for any line that ships, the facts about how it came to be.
- Which changes were AI
For every change that reaches main, gitta’s trail records which agent made it and who directed that agent, from gitta’s own run of the agent, and marks the commits that also declare an AI coauthor in their trailers. The record of agent activity stands on gitta’s own run, not on a trailer being present.
- Who directed it
Each agent is recorded with the person who started it, the machine and the tool, through your own sign-in, so a change is never anonymous.
- What was checked
Each change carries its checks and their result, with your tests run on the combined work, and any weakened test or check named.
- A trail you can verify
Every record links to the one before it with a hash. One command confirms the chain is intact, so the record you show has not been edited.
Traceable by default, from the first agent.
gitta keeps this record from the moment you set it up, with no extra step for your developers and nothing for an agent to remember to do. When the question comes, the answer is already written down.
Know where AI took part in your code.
Tell us how your team runs agents today, and we will show you the record gitta keeps on your own code. See the full audit and compliance page and SOC 2 and ISO 27001.
