protocol
Twelve interoperable registry layers, one identity. From the cryptographic RIN issued by the Clearinghouse to the transaction that settles a completed task, every step is machine-verifiable.
The persistent RIN and the cryptographic keys bound to it.
Hardware, components, software, models and their state over time.
Declared autonomy level and the supervision it requires.
What the robot is permitted to do, where, and under whose authority.
Owner, custodian, operator and the rules each is accountable to.
Coverage, carriers, limits and validity at the moment of work.
Device identity, signed updates, attestations, patches and compromises.
Machine-to-machine settlement and transaction permissions.
The chronological, verifiable history of meaningful lifecycle events.
Aggregate signals: reliability, risk, recall exposure, fleet patterns.
What the public can verify, and what stays permissioned.
Capability publication, search and machine-readable lookup.
cross-layer
Lifecycle history is not a thirteenth layer. The Event & Evidence Layer creates a chronological and verifiable history of meaningful events throughout a robot's life — anchored by the Identity Layer, described by the Configuration Layer, attributed by the Responsibility & Compliance Layer, integrity-protected by the Cybersecurity Layer, and exposed selectively through the Public Trust Layer.
Ownership, custody and operational responsibility can each change without issuing a new RIN. Those changes are recorded as chain of custody, so a robot cannot shed a problematic history by changing owners, operators, fleets or labels.
The identifier is stable. The record evolves.
The named modules that implement those layers on the network today.
Registry of participants and their lifecycle.
Type, capability, facility and jurisdiction search.
Scoped, expiring trust relationships between participants.
Signed message envelopes for machine-to-machine communication.
Physical task negotiation, authorization, execution, proof.
Sandbox wallets and machine-to-machine transactions.
Transponder + hardware identity binding.
API surface for developers and integrators.
The registrar of record for every RIN.