AquaGit · Code with context.
AquaGit is git, empowered by Aqua Protocol. Every action is signed by whoever took it. Every agent has an owner who answers for it.
A coding agent commits under a bot account or a developer’s name. The request sits in a chat window, the transcript on someone’s laptop, the approval in a team thread.
Today’s signing proves which account pushed a change. Not which agent wrote it, for whom, or why.
One example: a payment fix written by an agent.
The commit
signed by a shared bot account, or not at all
The request
in a chat window that has since closed
The transcript
on one developer’s laptop, secrets and all
The approval
a thumbs-up in a team thread
In a 2026 study of 180 million repositories, looking up bot accounts found only 3.3% of the commits a leading coding agent had made. Khosravani and Mockus, arXiv
Your developers and their agents keep using git. After a one-time setup, AquaGit signs every commit the moment git creates it, with the key of whoever made it.
When the change is pushed, AquaGit checks it at the door of your shared repository. A change that passes gets a signed receipt. A change that fails is refused with its reason and never reaches your branch.
Agents and people
git commit · git push
AquaGit
checks who signed · checks their grant · checks the session is attached
asks a person when the risk calls for it · receipt or refusal with a reason
Your shared repository
only signed, granted and approved changes
AquaGit decides what reaches your shared code. Signing adds no noticeable delay.
Each agent acts under a signed grant from its owner. Withdraw the grant and the agent is out.
People
Sign with a passkey
A passkey or a wallet, not a password. Every approval carries a named person’s signature.
Agents
Exactly the rights you grant
Every git operation is a defined, signed record. You grant each agent the operations it may do, on the branches it may touch.
Approvals
A person signs off by risk
You set which actions need a human. A merge into main waits for a passkey-signed approval, and the record names who approved.
Each commit names the agent session that produced it. When the change is pushed, the session’s prompts and transcripts are stored on AquaNode as signed records, helper agents included.
The owner sees
The full conversation
Every prompt and every transcript. Keys and tokens are blacked out before anything is stored.
Everyone else sees
Fingerprints only
Proof that the conversation exists and has not changed, without its content. The owner decides who may read more.
Export a period as one evidence bundle, sealed with a qualified timestamp whose date and integrity EU law presumes accurate.
1 · Choose
A range of commits or a time window: last quarter, last release, one incident.
2 · Export
Signed commit records, the receipt of every push, every approval, and the conversations you choose to share.
3 · Check
Built so anyone can check it with the Aqua SDK, without trusting us. Ask us to walk you through one.
AquaGit produces the evidence these frameworks ask for. The EU AI Act applies when what you ship is part of a high-risk AI system.
Every change is signed, when it is made, by the agent or person who made it.
EU AI Act Art. 11CRA Art. 31SOC 2 CC8.1
Every agent change names the session behind it, with its prompts and transcripts.
EU AI Act Art. 17ISO/IEC 42001
Actions above the risk level you set wait for a named person’s passkey-signed approval.
EU AI Act Art. 17SOC 2 CC8.1
A refused change never reaches your branch, and the refusal names its reason.
SOC 2 CC8.1
Protected history cannot be force-pushed or deleted, not even by an administrator.
EU AI Act Art. 18CRA Art. 13
Every evidence bundle carries a qualified timestamp, whose date and integrity EU law presumes accurate.
eIDAS Art. 41