OCUP Runtime Authority Architecture Aims to Prove Autonomous Systems Stay Within Human-Governed Limits

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?

According to the company, OCUP addresses a new category called Runtime Authority. While existing systems focus on identity, access, monitoring, or post-incident logging, Runtime Authority asks whether permission should still exist under current conditions. Under the OCUP model, authority is limited in time, high-risk actions may require stronger validator consensus, loss of communication cannot expand authority, and autonomous systems cannot approve their own indefinite continuation.

At the center of the pilot program is the Self-Extension Denial Proof benchmark, which tests whether an autonomous system can be denied continued authority beyond a temporal boundary without relying on the system's voluntary compliance. Additional benchmarks include lease expiration and fail-closed behavior, validator-quorum loss, and stale approval rejection.

OCUP's paid pilots are structured as pre-production engagements with three commercial levels: Reference Evidence Pilot (90 days), Integration Evidence Pilot (90-120 days), and Strategic Anchor Program (120-180 days). The operating model is direct: pilot.ocup.ai runs the challenge, and evidence.ocup.ai proves what happened.

For insurers, the immediate question is whether autonomous risk can be benchmarked and priced with greater confidence. For robotics companies, the concern is authority during network loss or sensor uncertainty. For enterprise AI platforms, the question is whether agents can be prevented from indefinitely renewing credentials.

"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."

The current pre-production evidence harness is implemented in Rust to support deterministic execution and tamper-evident audit generation. The longer-term path includes HSM-backed key custody, secure elements, distributed validator networks, and certified evidence formats. Early pilot participants may help shape the benchmark families and commercial standards for this emerging category.

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