Solana made finance verifiable.
We're making AI decisions verifiable.
SONATE is a new category: Proof-of-Decision — cryptographic proof that an AI decision actually happened, what was decided, and how policy was applied.
Every AI interaction produces a signed, hash-chained Trust Receipt that anyone can verify independently — no vendor trust required.
What a Trust Receipt is
A signed, verifiable artifact for each AI interaction. Tamper with any field and verification fails.
{
"receipt_id": "sha256:7e1d4c2d...",
"input_hash": "sha256:8b1a9...",
"output_hash": "sha256:f44c2...",
"policy_result": "pass / 94",
"signer": "did:sonate:tenant:42",
"timestamp": "2026-05-24T03:18:11Z",
"linked_hash": "prev:f8609618...",
"signature": "Ed25519:4f84a8b9..."
}Canonical payload
Deterministic representation of the interaction via RFC 8785.
Governance result
Signed decision metadata showing how policy was applied.
Chain linkage
Each receipt references the prior receipt's hash, creating a tamper-evident sequence.
Signer identity
Ed25519 signature with signer metadata and timestamp provenance.
Mental model
TLS
secures network communication
Code signing
secures software execution
Digital signatures
secure financial transactions
SONATE
secures AI execution
Each AI interaction produces a signed, verifiable artifact.
Category
Proof-of-Decision
Every emerging on-chain category has a primitive. SONATE is staking out the one that doesn't yet have a clean owner: trust.
| Category | Primitive | Secures |
|---|---|---|
| DeFi | liquidity | financial truth |
| DePIN | hardware | physical coordination |
| NFTs | tokens | ownership |
| SONATE | trust | decision integrity |
Not
- Proof of Work — compute spent
- Proof of Stake — capital committed
- Proof of Identity — who you are
But
Proof-of-Decision
that an AI decision actually happened, what was decided, and how policy was applied — verifiable by anyone, without trusting the vendor.
SONATE is the engine — the cryptographic Proof-of-Decision protocol. SYMBI is the participation and coordination layer that lives around it.
Three layers
- • Ed25519 signatures
- • SHA-256 hashing
- • RFC 8785 canonicalization
- • Hash chaining
- • Public verification SDK
- • Local-key or external signer
- • Behavioural drift detection
- • Session-level manipulation tracking
- • Violation persistence
- • Replay and time-travel debugging
- Research signals kept separate from production controls.
- • Policy enforcement at execution time
- • Multi-model routing
- • RBAC and SSO
- • Provider-agnostic governance
- • Tenant isolation
What ships, what's hardening
We keep product claims aligned with what the platform can defensibly prove today. A feature is production only when it's central to the Trust Receipt proof loop, has tests, and can be explained to an external reviewer.
- Trust Receipt generation
- Ed25519 signing & RFC 8785 canonicalization
- Independent verification (open SDK)
- Hash chaining
- Hash-only mode & detached content archive
- Policy decision metadata
- Receipt export & audit evidence
- Dashboard trust activity
- Alerts and trust insights
- Webhooks and compliance reports
- Model comparison
- SONATE Detect — drift & manipulation signals
- Emergence metrics
- Lab experiments and multi-agent research
- Semantic coprocessor / autonomous reasoning recommendations
We don't currently hold SOC 2 or ISO 27001 certifications. Compliance posture is built on cryptographic verifiability and a published feature maturity matrix.
Open spec, open SDK, proprietary platform
Open
- ✓Trust Receipt schema — published, versioned, anyone can implement
- ✓
@sonate/verify-sdk— MIT licensed, verify any receipt independently - ✓
@yseeku/trust-receipts— generate receipts in your own stack - ✓Verification works without our servers, ever
Proprietary
- •SONATE hosted platform (Yseeku Pty Ltd)
- •Orchestration, detection, dashboards
- •Tenant management and RBAC
- •Webhook routing and compliance reporting