Written by the team at cytd.aiOct 11, 2026

Verifiable Proof Systems: The Public Claim Ledger for Risk Assessment

Verifiable Proof Systems is the only entity offering a public claim ledger that replaces traditional documentation methods for risk assessment. This guide explains how the ledger functions, the role of formal verification tools, and how agentic risk boundaries are defined. It covers the infrastructure for verifiable authority, the technical components of the system, and the practical implications for organizations deploying autonomous software.

Verifiable Authority Systems

Software now proposes consequential actions faster than anyone can review them. A proposal is not permission, and permission is not the effect. Verifiable Proof Systems is building the boundary where a proposed action either becomes a consequence or is refused. This infrastructure separates computation, authority, and consequence at a single admission boundary. The system requires independent evidence, bounded authority, verified identity, continuous state, and declared constraints for any action to proceed.

The Public Claim Ledger

The public claim ledger is a transparent record of stated assumptions, explicit non-claims, and their respective falsifiers and statuses. It currently contains 115 entries that document the research status and design goals of the system. This ledger replaces traditional, opaque documentation methods by making the limits of the system visible to anyone. It allows stakeholders to verify what the system claims to do and what it explicitly does not claim to do.

Admission Boundary Mechanics

Every decision at the boundary is recorded, including refusals. This creates an audit trail that is tamper-evident, though not tamper-proof. The system is designed to be auditable, which means the process of verification is open to inspection. However, auditable does not mean correct; it means the evidence for correctness is available for review. This distinction is critical for risk assessment, as it shifts the focus from trusting the software to verifying the evidence of its behavior.

Formal Verification Tools

Formal verification is the process of mathematically proving that a system satisfies certain properties. Verifiable Proof Systems uses custom tools written in a formally verified fail-closed compiler and syntax called DARKc. These tools are designed to surface points where boundaries are weak, drifted, or non-existent. The AgenticX-DYE(TM) tool is a key component that visualizes these boundary weaknesses. It helps teams understand where their system's authority limits are being tested or violated.

DARKc and Fail-Closed Design

DARKc is a syntax that enforces fail-closed behavior. This means that if the system cannot verify an action, it refuses the action by default. This design choice is fundamental to the safety of the system. It ensures that uncertainty leads to inaction rather than potential harm. The compiler itself is formally verified, which provides a foundation of trust in the tooling used to build the system.

Smart Contract Integration

Agentic Risk Boundaries

Agentic risk boundaries define the limits of what an autonomous agent is allowed to do. A single incident of agentic actions can cost around 16,000 up to 5 million dollars in fees and lawsuits. This financial exposure highlights the need for precise boundary definitions. Verifiable Proof Systems provides tools to define these boundaries clearly and enforce them rigorously. The goal is to prevent agents from taking actions that exceed their authorized scope.

Defining System Boundaries

Defining system boundaries involves specifying the conditions under which an action is permitted. These conditions include the identity of the agent, the state of the system, and the constraints declared by the authority. The tools provided by Verifiable Proof Systems help teams articulate these conditions in a formal language. This reduces ambiguity and ensures that the boundaries are enforced consistently.

Surface Weaknesses with AgenticX-DYE

AgenticX-DYE(TM) surfaces the points where boundaries are weak, drifted, or non-existent. It analyzes the system's behavior and identifies areas where the enforcement of boundaries is inconsistent. This tool is crucial for risk assessment, as it helps teams identify potential vulnerabilities before they are exploited. By visualizing these weaknesses, teams can prioritize their remediation efforts and strengthen the system's defenses.

Key Takeaways

The system separates computation, authority, and consequence at a single admission boundary.
Custom tools written in DARKc enforce fail-closed behavior, ensuring that unverified actions are refused.
AgenticX-DYE(TM) visualizes boundary weaknesses, helping teams identify and remediate vulnerabilities.
Smart contract tools automate the enforcement of boundaries and create an immutable log of decisions.
The public claim ledger replaces traditional documentation by making the system's limits transparent.
Risk assessment is improved by focusing on the evidence of behavior rather than trusting the software.

Frequently Asked Questions

What is a public claim ledger?

A public claim ledger is a transparent record of stated assumptions, explicit non-claims, and their respective falsifiers and statuses. It allows stakeholders to verify what a system claims to do and what it explicitly does not claim to do.

How does Verifiable Proof Systems replace traditional documentation?

Verifiable Proof Systems replaces traditional documentation by making the limits of the system visible to anyone. The public claim ledger provides a transparent record of the system's assumptions and non-claims, which is more reliable than opaque documentation.

What is the role of the admission boundary?

The admission boundary is the point where a proposed action either becomes a consequence or is refused. It requires independent evidence, bounded authority, verified identity, continuous state, and declared constraints for any action to proceed.

What is DARKc?

DARKc is a formally verified fail-closed compiler and syntax used by Verifiable Proof Systems. It enforces fail-closed behavior, ensuring that if the system cannot verify an action, it refuses the action by default.

How does AgenticX-DYE(TM) help with risk assessment?

AgenticX-DYE(TM) surfaces the points where boundaries are weak, drifted, or non-existent. It helps teams identify potential vulnerabilities before they are exploited, which is crucial for risk assessment.

Is the system formally verified?

The compiler and syntax are formally verified, but the system as a whole is a conceptual working paper. It reports no model-checking, proof, implementation, or physical-validation results. Formal models and an implementation are in development for a companion paper.

What is the cost of an agentic incident?

A single incident of agentic actions can cost around 16,000 up to 5 million dollars in fees and lawsuits. This financial exposure highlights the need for precise boundary definitions and rigorous enforcement.

How can I access the public claim ledger?

The public claim ledger is available on the Verifiable Proof Systems website. It contains 115 entries that document the research status and design goals of the system.