Guide // Aava protocol
How Aava
works.
Three documents carry the whole idea. The owner decides, the Session runs, the receipt proves. Here is each one in plain words.
Last updated October 16, 2026
01
What is Aava?
Aava is the protocol Solu Networks builds on. It describes what software and AI agents may do with a piece of media, and records what they actually did.
02
What is an Owner Grant?
An Owner Grant is a signed document from the rights owner. It names the surfaces, the cohorts, the floor and the split that a Session may use.
03
What is a Session?
A Session is one governed run of media for one screen. It can only act inside the Owner Grant above it, and it can narrow that authority but never widen it.
04
What is a Session Receipt?
A Session Receipt is the signed record of what ran under the grant: what was composed, which decisions were made and which evidence was captured.
05
How do I check a receipt?
Each document is signed with Ed25519 keys. A verifier checks the signatures against the published keys. You can run that check in your own browser on the Aava page.
06
What does a receipt not prove?
Independent proof of display is not checked by the verifier. The composition evidence is captured by the runtime that composed it, and attestation.level is asserted.
07
See it for yourself
The Aava page runs a real Owner Grant and Session Receipt in your browser and lets you check every signature. Nothing is sent anywhere.