About DPO2U
DPO2U is a technical project for verifiable compliance.
It sits at the intersection of:
- machine-readable regulatory schemas
- agent-native tooling
- evidence-oriented workflows
- cryptographic verification patterns
- public or backend attestation rails where they add real value
The operating thesis is simple:
compliance should behave more like infrastructure and less like unstructured document exchange.
What DPO2U is
DPO2U is best understood as a stack for turning compliance claims into:
- typed artifacts
- replayable or reviewable workflows
- validation-oriented outputs
- progressively more verifiable results
That stack can include:
- schema-driven compliance packages
- auditor and expert agent roles
- MCP-facing integration surfaces
- off-chain evidence references
- optional verification and settlement backends
What DPO2U is not
The project should be equally explicit about what it is not:
- not a claim that regulation collapses into one score
- not a claim that cryptography removes institutional judgment
- not a generic blockchain wrapper around legal consulting
- not a statement that every part of the stack is fully public and production-complete today
Where DPO2U is differentiated
DPO2U is differentiated mainly by composition:
- Compliance as protocol rather than consultancy software
- Schema-first outputs designed for machine consumption from the start
- Agent-facing integration surfaces through MCP and explicit validation boundaries
- Incentive stability as a design problem, not just proof generation as a cryptography problem
- Cross-jurisdiction extensibility, starting from LGPD and expanding outward
Current posture
Today, the clearest public-facing DPO2U surface is the MCP runtime.
That matters because it gives the docs a reliable way to talk about capability truth without pretending every backend is equally public or equally hardened.
The documentation should therefore distinguish:
- public runtime truth
- environment-dependent backend paths
- conceptual architecture
- research and roadmap
That is not a weakness to hide. It is the correct operating posture.
Research orientation
DPO2U still treats several topics as active research rather than finished claims:
- formal attestation models
- incentive stability under adversarial populations
- routing across trust and jurisdiction layers
- the long-term relationship between credential systems and privacy-preserving verification
See Research for the deeper thesis and open problems.
Why this matters
The important shift is not "put compliance on a chain."
The important shift is:
- structure the evidence
- make the workflow inspectable
- preserve privacy boundaries
- strengthen verification over time
That is the real DPO2U claim.
What's next
- Introduction — conceptual starting point
- Architecture — runtime surfaces and trust boundaries
- Integration Surfaces — MCP vs SDK vs frontend
- Research — formal models and open questions