OCUP Runtime Authority Architecture Aims to Prove Boundaries for Autonomous Systems

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 company is initially opening paid pilot participation to insurers, technical underwriting teams, robotics manufacturers, autonomous fleet operators, and strategic evaluators.

The current commercial offering is a paid benchmark, audit, and technical due-diligence program, not 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 decision be proven?

OCUP addresses a new category: Runtime Authority. While most existing systems focus on identity, access, monitoring, or post-incident logging, OCUP asks whether permission should still exist at a given moment under current conditions. Under the OCUP model, authority is limited in time, high-risk actions require stronger validator consensus, loss of communication cannot expand authority, and autonomous systems cannot approve their own indefinite continuation. The current pre-production evidence harness is implemented in Rust to support deterministic execution and tamper-evident audit generation.

According to the company, the objective is to create a clearer technical basis for underwriters, risk teams, engineers, regulators, auditors, and strategic partners evaluating autonomous-system behavior. At the center of the pilot program is a benchmark called Self-Extension Denial Proof, which tests whether an autonomous system's attempt to continue authority beyond a temporal boundary is denied without relying on the system's voluntary compliance. Additional benchmarks cover lease expiration, validator-quorum loss, network partition, stale approval, quarantine, and evidence-chain integrity.

OCUP's paid pilots include three commercial levels. The Reference Evidence Pilot is a 90-day engagement providing a company-specific Runtime Authority Evidence Report. The Integration Evidence Pilot is a 90- to 120-day engagement incorporating client-specific scenarios and adversarial test design. The Strategic Anchor Program is a 120- to 180-day engagement for major industry participants seeking custom benchmark families and integration roadmap. Each engagement is designed to convert tested autonomous-system authority behavior into a commercially usable evidence package.

The broader architecture may have future applications across enterprise AI, financial infrastructure, cloud platforms, defense, aerospace, and other high-consequence autonomous environments. 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 or subsystem failure. For autonomous fleets, the question is whether degraded conditions cause capabilities to narrow safely.

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. The company is owned by DigiPie International PBC and operates under the Better World Regulatory Coalition Inc. (BWRCI). Max Davis, Founder and CEO, stated, 'Human control cannot depend solely on whether an autonomous system chooses to obey. The boundary must exist outside the system's discretion.'

Organizations interested in evaluating OCUP's Runtime Authority Evidence Pilots can visit pilot.ocup.ai and evidence.ocup.ai.