Introduction
DPO2U is a Compliance as a Protocol project: public technical infrastructure for verifiable compliance, not a reactive privacy consultancy wrapped in APIs.
DPO2U documentation distinguishes between runtime surfaces that are live today, components being hardened, and roadmap material.
During VPS validation for this docs refresh, the most reliable public surface was the MCP layer at https://mcp.dpo2u.com, with live capability discovery available through /tools and /openapi.json.
The central goal is to turn compliance assertions into verifiable artifacts, where:
- companies can prove specific compliance properties without exposing sensitive records
- AI agents can check permissions and attestations programmatically
- evidence is durable, queryable, and reducible to explicit trust assumptions
The problem we solve
Auditing the privacy posture of suppliers and partners is still largely manual, expensive, and slow. In practice, many organizations exchange PDFs, spreadsheets, and legal narratives when what they need is a narrow answer to a narrow question: is this counterparty allowed to do this, under this rule, right now?
DPO2U aims to reduce that question to a programmatic verification step, with cryptographic evidence where appropriate and plain operational status where cryptography is not yet the bottleneck.
If you're integrating DPO2U into an application or agent workflow, start with Getting Started.
The philosophical foundation
DPO2U is not only a technical stack. It is grounded in Teoria Protópica (Protopic Theory), a working framework that connects repeated games, incremental progress, and adaptive resilience.
Verifiability creates an infinite shadow of the future
Robert Axelrod's The Evolution of Cooperation (1984) showed that cooperation emerges in iterated settings when actors expect future interaction — when there is a shadow of the future. On-chain attestations create exactly that: a durable compliance memory. When counterparties know that verification outcomes can be revisited, dishonesty stops being a one-shot optimization and becomes a repeated-game liability.
From cooperation to evolutionary stability
Axelrod explains why cooperation can emerge. John Maynard Smith's work on evolutionarily stable strategies (ESS) explains when it persists. This matters for DPO2U because the protocol is not only about proving statements; it is about shaping incentives so that honest attestation remains stable even when dishonest agents exist.
In DPO2U terms, the relevant question is not just "is honest behavior rational once?" but:
under what reward, penalty, and verification conditions does honest attestation resist invasion by defectors?
That is the research spine for the protocol's incentive layer and the reason the docs treat ESS as a first-class concept rather than a side note. See Research and Incentive stability (ESS).
Protopia, not utopia
Kevin Kelly's concept of protopia (The Inevitable, 2016) rejects the fantasy of a perfect end-state in favor of steady, compounding improvement. DPO2U follows that posture: each schema revision, operational hardening step, and better attestation interface is a small gain. The project does not promise perfect compliance; it tries to make the compliance surface more legible and more verifiable over time.
Adaptive fitness over prediction
Following Nassim Taleb's antifragility framework, DPO2U is designed less to predict every regulatory shock and more to shorten recovery after one. Immutable evidence does not eliminate incidents, but it can reduce time spent reconstructing what happened.
How this materializes in DPO2U
| Philosophical concept | Protocol implementation |
|---|---|
| Shadow of the future (Axelrod) | Attestations create durable compliance memory |
| Evolutionary stability (Maynard Smith) | Incentive design asks when honest attestation resists defection |
| Protopia (Kelly) | Incremental schema, agent, and integration improvements |
| Antifragility (Taleb) | Durable evidence shortens post-incident reconstruction |
| Verifiability reduces narrative noise | Zero-knowledge proofs and explicit trust boundaries replace unsupported claims |
| Cooperation emerges from machine-readable trust | MCP-facing interfaces let software consume compliance state directly |
DPO2U does not claim novelty where the field has already converged. "ZK for compliance" is now a recognized frontier with multiple entrants. The distinctive claims live elsewhere: compliance as protocol, multi-jurisdiction composition, agent-native consumption, and incentive stability under repeated interaction. Those claims are developed in Research.
What's in this documentation
| Section | Description |
|---|---|
| Architecture | System layers, trust boundaries, and current deployment status |
| Research | Thesis, related work, formal model, ESS, routing, and open problems |
| Tokenomics | Dual-token economy and the ESS framing of incentives |
| Smart Contracts | Verification and settlement patterns described conservatively |
| Agents | Agent identity, validation, and relationship to emerging standards |
| Integration Surfaces | When to use MCP vs SDK vs frontend |
| MCP Server | AI-native integration via Model Context Protocol |
| Frontend Visualization | Live Mode vs Demo Mode and the product presentation model |
| Schemas | The dpo2u/lgpd/v1 schema and storage flow |
| About | Thesis, lifecycle, and protocol positioning |
| Style Guide | Documentation standards for contributors |
What's next
Start with Architecture for the operational stack as it exists today, or jump to Research if you want the formal thesis, related work, and open questions behind the protocol.