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 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?
OCUP's current commercial offering is a paid benchmark, audit, and technical due-diligence program. It is not yet a production safety controller, live distributed validator network, hardware-enforced deployment, insurance approval, or third-party certification. Temporal Authority Systems PBC is initially opening paid pilot participation to insurers, technical underwriting teams, robotics manufacturers, autonomous fleet operators, and strategic evaluators.
Most existing systems focus on identity, access, monitoring, cybersecurity, model behavior, or post-incident logging. OCUP addresses a different layer: Runtime Authority. 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; and autonomous systems cannot approve their own indefinite continuation.
At the center of the OCUP pilot program is a benchmark designed to test Self-Extension Denial Proof. The test generates 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.
OCUP's paid pilots are structured as pre-production benchmark, audit, and technical due-diligence engagements. They are not production safety certifications, insurance approvals, or live autonomous control deployments. The program currently includes three commercial levels: Reference Evidence Pilot (90-day engagement), Integration Evidence Pilot (90-120 days), and Strategic Anchor Program (120-180 days). Each engagement is designed to convert tested autonomous-system authority behavior into a commercially usable evidence package.
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 enterprise AI platforms, the question is whether agents can be prevented from indefinitely renewing credentials, permissions, or operational scope. OCUP is built around the proposition that these are manifestations of the same missing infrastructure layer: Runtime Authority.
"Human control cannot depend solely on whether an autonomous system chooses to obey," said Max Davis, Founder and CEO of Temporal Authority Systems PBC. "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."
OCUP's current paid offering is intentionally pre-production. The immediate goal is to establish benchmark evidence, client-specific findings, technical credibility, and commercial records across realistic operating scenarios. The longer-term path includes HSM-backed key custody, secure elements and hardware enforcement, distributed validator networks, and sector-specific Runtime Authority standards. Organizations interested in evaluating OCUP's Runtime Authority Evidence Pilots can visit OCUP.ai, pilot.OCUP.ai, and evidence.OCUP.ai.
