Overview
Landing page for DALP architecture fundamentals: design principles, quality attributes, deployment topology, and data domain ownership. Provides the conceptual foundation before exploring components and flows.
Purpose: Orient architects on the foundational decisions, quality commitments, and structural boundaries that shape the entire platform.
- Doc type: Reference
What you'll find here
- Design principles that guide every architectural decision, and explicit non-goals
- Quality attributes (security, reliability, performance, compliance) with documented tradeoffs
- Deployment topology across environments, runtime zones, and network boundaries
- Data domain ownership, sources of truth, and lifecycle governance
Architecture philosophy
DALP separates concerns into four distinct layers. The Asset Console provides the operator interface. The Unified API exposes every capability programmatically with OpenAPI documentation. The DALP Execution Engine orchestrates multi-step blockchain workflows with guaranteed delivery. The SMART Protocol enforces compliance at the smart-contract level through ERC-3643.
Each layer owns its boundaries, contracts, and failure modes. Layers communicate through stable interfaces -- never through shared internal state. This separation allows independent scaling, deployment, and evolution of each layer.
Sections
| Page | What it covers |
|---|---|
| Principles and non-goals | What we optimize for, what we deliberately exclude, and why |
| Quality attributes | Security, reliability, performance, and compliance commitments with tradeoffs |
| Deployment topology | Environments, runtime zones, network boundaries, and scaling constraints |
| Data domains | Sources of truth, data ownership, lifecycle stages, and governance model |
Related
- Component catalog for the full inventory of platform services
- Key flows for step-by-step operation sequences
- Security for threat model and controls mapping
- Start here for the architecture navigation map