Docs
Documentation
Everything a lab engineer or compliance architect needs to evaluate, integrate, and verify the Akaeon Registry.
What it is
A cryptographic opt-out registry for AI training. Publishers register intent. Labs query a single API. Anyone verifies independently.
Read the spec →What it’s for
Audit-defensible evidence at training-data ingestion. Records that survive their issuer.
See a concrete example →How to integrate
One HTTPS GET per domain. Standard-library Node.js to verify — three checks, no SDK. One to three engineer-days.
Read the runbook →All documents
Technical specification
Cryptographic primitives, message schemas, audit-defensibility properties, and governance for the Akaeon Registry.
Publisher integration runbook
Step-by-step guide for a publisher registering a domain opt-out. One ops engineer, half a day. DNS-based proof of authority, no new infrastructure.
Lab integration runbook
Step-by-step guide to integrating the Akaeon Registry at training-data ingestion. One engineer, one to three days.
Architecture
How Stelais, the Akaeon Registry, the core packages, and Arweave fit together — and what to omit from the diagram on purpose.
Concrete example: a publisher opt-out, end to end
Walk one specific scenario from submission to lab-side acknowledgment, so a technical evaluator can see exactly what code paths run, what artifacts each step produces, and what's verifiable independently.
Standalone verifier
Copy-paste-ready Node.js verifier for Akaeon Registry records. No SDK. Standard library only. No Akaeon code in the verify path.
Changelog
Versioned record of changes to the Akaeon Registry specification and API.