What we report, and what we don’t.
We report
What Aqua’s software proves.
Which evidence Aqua’s protocol and SDK produce and check, at a named version.
We name
What your system must add.
Some duties need the system built around Aqua: acting on a decision at runtime, deployment, hardware. We say where they sit and do not rate them.
Stays with you
What your organisation decides.
Whether a law or a standard is met is decided by the organisation that runs the system and the people who answer for it. Aqua supports that work and never replaces it.
Five ways to look at Aqua.
Open standard
Proof of Control
An open standard for proving what AI agents did. How far Aqua’s evidence goes, item by item.
Weekly Tier 2 · self-assessed
Regulation
EU AI Act
Europe’s AI law. Which record-keeping, transparency and oversight duties Aqua’s technology can support, and which stay with you.
Weekly In preparation
RFC · NIST · W3C
Internet and cryptography standards
The open standards Aqua is built on, and the new ones we are assessing.
Tracked Tracked
C2PA · Sigstore
Other trust tools
How Aqua relates to content credentials and to software signing: where they overlap, complement and differ.
Reference In preparation
git · CRDT
Aqua as a base layer
How code history and live collaboration can run on Aqua, and what they inherit from it.
Reference In preparation
Where we are, and how to try it.
Today anyone can inspect aqua-rs-sdk-core, a published snapshot of Aqua’s core under the Apache-2.0 licence. The full SDK, the version every assessment here is made against, is in pre-release.
Today
A public snapshot, and the full SDK for pilots.
Anyone can read and run aqua-rs-sdk-core, the published snapshot of Aqua’s core. Pilot partners work with the full SDK before its release.
When the viewer is published
Anyone can check Aqua evidence themselves.
A free verification tool, published as a binary, checks evidence without an account, a contract or our help.
When the SDK is published
The verification code is open to inspect.
The full SDK, at the version each claim names. This is what the highest tiers of Proof of Control ask for.
How the five fit together.
- 01 Proof of Control asks what evidence an AI system must produce so that others can check it.
- 02 The EU AI Act asks organisations for records and oversight that such evidence can support.
- 03 Internet and cryptography standards are the building blocks both rest on: hashing, signatures, timestamps, transparency logs.
- 04 C2PA and Sigstore solve neighbouring problems, for media and for software, with different trust models.
- 05 git and CRDTs show Aqua underneath tools people already use.
This week.
18 October 2026
First edition. Proof of Control is assessed against Working Draft v0.1 and the current SDK. The EU AI Act, the trust tools and the base layer follow.
How we assess.
- Self-assessed by inblock.io, against the full SDK.
- Every result names the version of the standard and the SDK it was made at.
- Prepared with AI assistance and reviewed by people.
- Not legal advice and not a conformity statement.
Questions about an assessment?
Ask us how a result was reached, or how Aqua would fit the rules you work under.