Machine identity
Durable CPID, accountable sponsor, hardware identifier, issuer, assurance level and lifecycle status.
IDENTIFYCompute Passport™ for Robots
Identity infrastructure for autonomous machines.
Extend Compute Passport™ from AI agents into robotics: one persistent machine identity that can bind accountable ownership, hardware, approved AI software, operating context, policy state and evidence across the robot lifecycle.
THE IDENTITY GAP
Robots are becoming software-defined actors.
A humanoid can carry models, tools, credentials and delegated authority while moving between sites and operating roles. Traditional asset inventory tells you what was purchased. Compute Passport is designed to help establish what the machine is, what software it is expected to run, who is accountable for it and whether its current state remains trusted.
WHOPersistent identityOne CPID across software and lifecycle events.
WHATAuthorized stateBind approved software, claims and operating context.
PROVEEvidence historyPreserve issuance, change, access and status events.
Identity contract
A passport is more than a serial number.
The identity object is designed to connect the physical asset to the software and governance state that makes the machine operationally meaningful.
Software authority
Approved models, agents, runtime packages, versions and cryptographic digests attached to the robot object.
BINDOperating context
Site, zone, GPS context, environment constraints and time-bound operating claims available to policy systems.
CONTEXTTrust state
Active, suspended, quarantined or retired status with credential posture and assurance evidence.
CONTROLRuntime evidence
Desired-versus-reported software state, telemetry, verification events and policy outcomes linked back to identity.
OBSERVELifecycle proof
Hash-linked and signed events can preserve issuance, rotation, deployment, revocation and review history.
PROVECompute Passport Access Protocol™
Identity becomes useful when it participates in a decision.
CPAP is the interoperability path between the passport object and relying systems. In the current architecture it carries identity, status, software and evidence signals that policy engines can evaluate before an autonomous system is trusted with access or action.
01ISSUERegister machine + sponsor
→02BINDHardware + software claims
→03VERIFYSignature + status + context
→04DECIDEAllow / deny / restrict
→05RECORDEvidence event
Reference architecture
One identity across five control planes.
The design complements existing IAM, asset management, robot middleware and safety systems instead of attempting to replace them.
Enterprise policy & assurance
IAM, Zero Trust, GRC, SIEM/SOC, approvals and audit.
Compute Passport / CPAP
CPID, signed claims, status, assurance, verification and evidence.
Robot software management
Models, agents, perception stack, runtime packages and desired state.
Edge & robot middleware
ROS 2 / DDS, edge gateway, telemetry, device credentials and OEM APIs.
Physical machine & safety controller
Hardware root, sensors, actuators and safety-rated motion functions.
Machine-readable identity
Designed to be consumed by systems—not only viewed by humans.
A relying system should be able to ask whether the passport is valid, who issued it, what state it is in, which software is approved and what obligations apply before granting access.
{
"cpid": "urn:cpid:v1:solarion:robot:sr-h01",
"issuer": "Solarion AI Systems",
"subject_type": "humanoid_robot",
"assurance": "CPAL-3",
"status": "active",
"software_state": "verified",
"policy": "robot-prod-v3",
"evidence_head": "sha256:91ab…"
}Use cases
Where a persistent robot identity becomes valuable.
Zone-bound autonomy
Verify machine identity, approved navigation/perception stack and assigned facility context before operational access.
Controlled software change
Bind a robot to an approved model/runtime manifest and preserve who authorized a deployment or rollback.
Third-party robot fleets
Issue time-bound trust to vendor-operated autonomous systems without relying on a shared long-lived credential.
Quarantine by identity
Change the passport state to quarantine and make that status available to relying systems and operators.
Identity-bound telemetry
Associate health, GPS and software reports with the specific registered machine that produced them.
Evidence reconstruction
Reconstruct identity, software and policy state around a historical machine event without depending on one dashboard view.
Network evolution
From signed identity to a verifiable network.
Compute Passport does not require a cryptocurrency or public blockchain. The credible path is to add decentralization only where independent verification creates real value.
- 2026Signed passport objects
Issuer signatures, status, software digests and verification APIs.
- NEXTHash-linked evidence
Ordered identity and lifecycle events with tamper-evident history.
- THENTransparency & witnesses
Merkle commitments and independent observers reduce reliance on one operator.
- FUTUREFederated trust network
Multiple issuers and verifiers establish interoperable machine identity across organizations.
Working MVP
Open Robot Control ↗See identity, software state and evidence in one robot control plane.
The current MVP demonstrates the management model. Production deployments require hardened key management, external verification services, OEM/edge adapters and environment-specific safety/security engineering.