In short.
Git and live co-editing keep working the way people already know them. Aqua adds proof at chosen moments, called seals: points where the current state is signed, so anyone can later check what was sealed, by whom and when.
Git: what a repository inherits.
Working today in our own git server, built and tested end to end. Production use and outside time-stamps come next.
- Same tools, nothing new to learn. Developers keep using standard git commands and tools; Aqua works alongside them at the server.
- Every published change carries a signature. Each push is signed by a named identity, and the server checks and countersigns it before the shared history moves on.
- History stays on record. When someone overwrites a branch, the earlier version is kept and the overwrite is recorded, so a rewrite of shared history is visible, not silent.
- Checkable from a plain copy. The signed record travels inside the repository, so anyone holding a copy can check it offline, without asking us.
Live documents: what a shared document inherits.
Designed and backed by experiments. We are building a first pilot.
Live co-editing lets several people type in one document at once, even offline. The technique behind it is called a CRDT.
- Live editing stays live. People keep typing together in real time and offline edits still merge by themselves, because Aqua stays out of the typing path.
- One fingerprint for the whole document. Each sealed state gets one content fingerprint, so anyone can tell whether two copies hold exactly the same document.
- Signed snapshots. The editing service signs each snapshot, and a person who saves adds their own signature to that exact state. Approval is recorded separately.
- AI agents sign their own edits. An agent’s change is recorded under the agent’s own identity, and the person who accepts or rejects it signs that decision.
- Where the seal sits. In git, the seal is a published push; in a shared document, it is a snapshot. Aqua’s proofs cover each seal. Drafts and keystrokes between two seals are recorded by the service that runs the seal.
- Who decides. Each repository, document or folder lives in a space: a domain its owners control and govern. Who may change, merge or seal is that space’s policy. Aqua records which rules each seal was checked under, and the owners’ own systems act on it.
What the full comparison will cover.
- git: what a repository inherits when its history is sealed on Aqua.
- CRDTs: what a shared, live document inherits when its states are sealed.
- Where the seal sits, and what lies between two seals.
Who may change, merge or seal is the policy of each space, decided by its owners. What we report, and what we don’t.
Want it sooner?
Tell us what you need to know, and we start there.