Temporal Authority Systems PBC, a public-benefit corporation, today announced OCUP, the One Chip Unified Protocol, a pre-production Runtime Authority evidence architecture. OCUP aims to establish time-bounded authority leases, multi-party validator consensus, fail-closed boundaries, and tamper-evident evidence for autonomous systems. The current commercial offering is a paid benchmark, audit, and technical due-diligence program, not yet a production safety controller or live distributed validator network.
The program is designed to help organizations test a foundational question before live deployment: Can an autonomous system be prevented from indefinitely extending, enlarging, or restoring its own operational authority, and can the resulting grant, denial, expiration, degradation, quarantine, or recovery decision be proven? Temporal Authority Systems PBC is initially opening paid pilot participation to insurers, technical underwriting teams, robotics manufacturers, autonomous fleet operators, and strategic evaluators. The broader architecture may also have future applications across enterprise AI, financial infrastructure, cloud platforms, defense, aerospace, and other high-consequence autonomous environments.
OCUP addresses a different layer than existing systems focusing on identity, access, monitoring, cybersecurity, model behavior, or post-incident logging. Authentication asks who or what is making a request. Access control asks whether that actor has permission. Observability records what the system reports. Runtime Authority asks whether that permission should still exist now, under current conditions, for this specific capability. Under the OCUP model, authority is limited in time; high-risk actions may require stronger validator consensus; loss of communication cannot expand authority; stale or replayed approvals cannot restore authority; lease expiration produces denial or bounded degradation; critical recovery requires fresh authorization; autonomous systems cannot approve their own indefinite continuation; and material authority events generate tamper-evident evidence.
As autonomous systems move into factories, roads, warehouses, financial networks, cloud platforms, infrastructure, and human-shared environments, organizations face growing questions around liability, insurability, technical due diligence, operational continuity, and regulatory accountability. Traditional logs may show what software reports after an event. OCUP's Runtime Authority model is designed to produce a structured record of the authority decision itself, including the identity of the governed system, the authority lease in effect, the capability being requested, the applicable time boundary, validator participation and quorum state, the reason for approval or denial, and evidence associated with degradation, quarantine, and recovery.
At the center of the OCUP pilot program is a benchmark designed to test Self-Extension Denial Proof, generating a deterministic evidence record showing that an autonomous system attempted to continue or enlarge its authority beyond an authorized temporal boundary and that the request was denied without relying on the system's voluntary compliance. Additional benchmark families include lease expiration and fail-closed behavior, validator-quorum loss, network partition and communication failure, stale approval and replay rejection, quarantine initiation and release, phased recovery, deterministic replay, evidence-chain integrity, and gradual capability reduction under deteriorating conditions.
The paid pilots are structured as pre-production benchmark, audit, and technical due-diligence engagements, not production safety certifications or live autonomous control deployments. The program includes three commercial levels: Reference Evidence Pilot (90-day engagement), Integration Evidence Pilot (90- to 120-day engagement), and Strategic Anchor Program (120- to 180-day engagement). For insurers, the immediate question is whether autonomous risk can be observed, benchmarked, and priced with greater technical confidence. For robotics companies, the question is what authority remains during network loss, sensor uncertainty, subsystem failure, or delayed coordination. For autonomous fleets, the question is whether degraded conditions cause capabilities to narrow safely rather than expand unpredictably.
Temporal Authority Systems PBC was formed around a long-term public-benefit mission: to preserve humanity's seat at the table as autonomous systems gain greater operational power. It means establishing a boundary that machines do not control. It means ensuring that temporary authority cannot be silently converted into indefinite authority. It means keeping human institutions structurally relevant even when machines operate at speeds no human can continuously supervise. Organizations interested in evaluating OCUP's Runtime Authority Evidence Pilots can visit OCUP.ai, pilot.OCUP.ai, and evidence.OCUP.ai.
