Select a layer to explore its role.
Each layer has a single job: narrow ambiguity and increase inspectability. Click any layer in the stack to see its components, responsibilities, and how it connects to the layers above and below.
Clock cycle
From perception to attested action.
Every agent cycle follows the same verifiable sequence. Each step maps to a primitive, an event type, and a cryptographic commitment. Hover any step to see the detail.
Three layers of cryptographic trust.
Trust in selfdriven.computer is structural, not relational. It doesn't require trusting an operator, a platform, or a certificate authority — only the mathematics.
The KERI key event log provides the fundamental trust anchor. Every identity — human or agent — has an AID with an append-only, witnessed KEL.
ACDC credentials attest domain-specific claims anchored in KERI. They define what an agent can do, not just who it is.
Domain actions — transactions, governance decisions, service interactions — are anchored to the credential layer and recorded in the KEL.
Authority flows downward.
Verification flows up.
KERI's bilateral delegation creates a cryptographic chain of custody from human conductor to autonomous agent. Every node in the tree holds its own AID and has a verifiable reference to its delegator — recorded in both parties' key event logs.
Delegation events (dip) require mutual commitment. An agent cannot claim to be delegated without the delegator having confirmed it. Revocation flows in the other direction — a parent can revoke any child AID instantly via a rotation event, with no cooperation from the child required.
The KEL is the complete record.
Every agent lifecycle event is recorded in strict sequence. The KEL is append-only and tamper-evident — any modification would break the digest chain and be immediately detectable by any witness or verifier.
Click any event to see the full structure. The KEL is the foundation of all accountability in the system — it answers not just "what happened" but "when, by whom, and with what authority."
Every domain inherits the full trust stack.
Layer 06 is where the architecture meets the world. Each ecosystem domain builds on top of the five layers below — inheriting verifiable time, reduced primitives, policy enforcement, delegated runtime, and shared trust.
Health
Discharge optimisation, care coordination, and patient consent management anchored to KERI identity and ACDC credentials.
Banking
CDR Open Banking, NPP PayID, and APRA-regulated transaction flows all signed with KERI AIDs and audited via KEL evidence streams.
Community
TANA self-actuation platform with governance votes anchored to Cardano, community credentials, and NuNet compute orchestration.
AI agents
Agent marketplace and A2A protocol hub. SKILL.MD capability contracts, delegated AIDs per agent, and cross-domain composition enforcement.
Professional
Human Conductor webapp across 9 professional domains. KERI-anchored credential verification for professional identity and service delivery.
This layer
The operating substrate that all other domains build on. The clock, the primitives, the policy layer, the runtime, and the trust network.