Glossary
Quick reference for terminology used across the DPO2U documentation.
| Term | Definition | First appears in |
|---|---|---|
| Attestation | A compliance result or verification-oriented artifact that can be reviewed, referenced, and in some environments anchored to a public verification layer. | Architecture |
| CID | Content Identifier — a content-addressed reference used to locate an artifact without embedding the full artifact in the public layer. | Smart Contracts |
| Compliance artifact | A structured output such as a schema, report, evidence bundle, or machine-readable result generated by a DPO2U workflow. | Integration Surfaces |
| DID | Decentralized Identifier — a machine-readable identity format that can be used to reference agents, validators, or services. | Agents |
| Degraded Mode | A frontend or service state where some real backend data is unavailable, partial, or delayed, but the system does not hide that limitation. | Frontend Visualization |
| Demo Mode | A frontend or workflow state used to explain system behavior without pretending that every displayed value is canonical live runtime data. | Frontend Visualization |
| Evidence reference | A hash, CID, ID, or pointer that allows an artifact to be checked or retrieved without exposing all underlying content publicly. | Architecture |
| FHE | Fully Homomorphic Encryption — computation on encrypted data. In DPO2U docs, this belongs to research and advanced roadmap unless explicitly stated otherwise. | Architecture |
| Frontend | The human-facing presentation layer used to visualize workflow, evidence state, attestation progress, and the distinction between live, degraded, and demo views. | Frontend Visualization |
| GDPR | The European Union's General Data Protection Regulation. DPO2U documentation often references it alongside LGPD as part of cross-jurisdiction compliance framing. | Schemas |
| IPFS | Content-addressed storage commonly used for off-chain artifacts and references. | Architecture |
| LGPD | Lei Geral de Proteção de Dados — Brazil's general data protection law and a core regulatory reference in DPO2U documentation. | Introduction |
| Live Mode | A frontend or service state where the displayed information is backed by the current canonical runtime path rather than illustrative fixtures. | Frontend Visualization |
| MCP | Model Context Protocol — the agent-facing integration surface that currently serves as the clearest public capability layer in DPO2U documentation. | MCP Server |
| Runtime truth | The most reliable currently reachable source for what the system exposes in practice. In these docs, that generally means the live public MCP runtime rather than static copy. | Integration Surfaces |
| Selective disclosure | The design principle that only the minimum information needed for verification should be made public, while richer compliance material stays off-chain or off-public-surface. | Smart Contracts |
| Verification backend | Any backend path used to validate, score, attest, or settle compliance-oriented results. Some may be public; others may be local or environment-dependent. | Architecture |
| zk-SNARKs | A zero-knowledge proof family relevant to privacy-preserving verification. In DPO2U docs, they are part of the verification design space and should not be assumed to define every active public runtime path. | Smart Contracts |