Temporal Authority Systems PBC today introduced OCUP, the One Chip Unified Protocol, a pre-production Runtime Authority evidence architecture being developed 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.
According to the company, OCUP addresses a different layer than existing systems focused on identity, access, monitoring, or cybersecurity. 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. OCUP is being developed to govern that authority through temporal boundaries, validator-mediated decisions, fail-closed behavior, and evidence-producing control events.
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. The current pre-production evidence harness is implemented in Rust to support deterministic execution, memory-safe systems development, reproducible benchmark testing, and tamper-evident audit generation.
As autonomous systems move into factories, roads, warehouses, financial networks, and human-shared environments, organizations face growing questions around liability, insurability, and regulatory accountability. 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, validator participation, and the reason for approval or denial. The objective is to create a clearer technical basis for underwriters, risk teams, engineers, regulators, auditors, and strategic partners.
At the center of the OCUP pilot program is the Self-Extension Denial Proof benchmark, which tests whether an autonomous system attempting to continue or enlarge its authority beyond an authorized temporal boundary is denied without relying on voluntary compliance. Additional benchmarks include lease expiration, validator-quorum loss, network partition, stale approval rejection, quarantine initiation, and gradual capability reduction under deteriorating conditions.
OCUP's paid pilots are structured as pre-production benchmark, audit, and technical due-diligence engagements. The program includes three commercial levels: a 90-day Reference Evidence Pilot providing a company-specific Runtime Authority Evidence Report; a 90- to 120-day Integration Evidence Pilot incorporating client-specific scenarios; and a 120- to 180-day Strategic Anchor Program for major industry participants. Each engagement converts tested autonomous-system authority behavior into a commercially usable evidence package.
For insurers, the immediate question is whether autonomous risk can be observed and priced with greater technical confidence. For robotics companies, the question is what authority remains during network loss or subsystem failure. For autonomous fleets, whether degraded conditions cause capabilities to narrow safely. For enterprise AI platforms, whether agents can be prevented from indefinitely renewing credentials. For financial institutions, whether high-risk digital actions can be contained. For defense and aerospace, whether machine execution remains subordinate to authenticated command authority.
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. "Human control cannot depend solely on whether an autonomous system chooses to obey," said Max Davis, Founder and CEO. "The boundary must exist outside the system's discretion. OCUP is being built to make that boundary time-bounded, validator-governed, fail-closed, and provable."
Organizations interested in evaluating OCUP's Runtime Authority Evidence Pilots can visit OCUP.ai, pilot.OCUP.ai, and evidence.OCUP.ai.
