Capability docs matrix
Map DALP capabilities to the public documentation pages that explain the architecture, operator workflow, API integration path, and review notes for each capability.
DALP capabilities are documented across architecture explanations, operator guides, developer guides, and runbooks. Use this matrix when a review names a capability and the evidence sits across several docs sections.
Pick the row that matches the question. The Start with link gives the mental model. The Then read links point to operator steps, API details, or readiness evidence. The matrix is a routing aid, not a product checklist; read the linked pages for the exact flow, API surface, constraints, and responsibilities.
Capability coverage
| Capability area | Start with | Then read | What the docs cover |
|---|---|---|---|
| Platform architecture and ownership | System context | Architecture one-pager, Components | How the Asset Console, Unified API, execution services, SMART Protocol contracts, feeds, custody providers, compliance providers, and operator systems fit together. |
| Asset setup and issuance | Tokenization modeling | Asset issuance, Create an asset, Token lifecycle API | How an asset definition becomes a configured tokenised instrument, which lifecycle controls apply, and where operator and API workflows continue. |
| Asset servicing after issuance | Lifecycle after issuance | Asset detail workspace, Mint assets, Asset economics | Where minting, redemption, conversion, fixed-income servicing, pricing, and fee concepts sit after the asset is live. |
| Identity, claims, and compliance controls | Identity and compliance | Compliance modules, Configure trusted issuers, Compliance provider subjects | How identity claims, trusted issuers, configured compliance modules, and provider-driven subject records participate in transfer and issuance controls. |
| Asset policy and transfer controls | Asset policy | Policy-based transfer controls, Asset policy compliance, Compliance templates | How configured asset policy, compliance modules, and transfer-control checks decide whether a regulated mint, transfer, or burn may execute; deployment-specific policy choices stay with the operator. |
| Custody, signing, and wallet verification | Custody providers | Signing flow, Wallet verification, Account security | How DALP prepares transactions, hands signing to the selected custody or wallet path, verifies wallets, and separates platform workflow from custody-provider policy. |
| Replay, idempotency, and mint controls | Replay, idempotency, and mint controls | Source verification and auditability, Mint assets | Where duplicate-request protection, deterministic operation keys, configured mint authority, and audit evidence belong in the operating model. |
| Settlement and cross-chain positioning | XvP settlement | XvP operator guides, Bridge and cross-chain position, Supported networks | How settlement workflows are represented in DALP, which EVM network assumptions apply, and which bridge or external-chain responsibilities stay outside DALP. |
| Market data and feeds | Market data infrastructure | Feeds overview, Create feeds, Feeds update flow | How feed registration, signed updates, adapter reads, and indexed price data support configured asset or workflow needs. |
| Event evidence, auditability, and monitoring | Source verification and auditability | Events, Operability, Observability | Which records and event streams help reviewers trace platform actions, monitor operations, and reconcile workflow outcomes. |
| Vendor governance and outsourcing review | Vendor governance responsibility model | Deployment topology, High availability, Operational integration patterns | How DALP supplies controls, evidence, and integration points while DORA, outsourcing governance, incident reporting, regulatory permissions, and legal responsibility stay with the operator unless the deployment contract assigns them. |
| Network and RPC resilience | EVM RPC Node | Chain Gateway, Supported networks, Failure modes | How DALP reaches configured EVM RPC upstreams through the gateway, what routing and failover responsibilities sit in DALP, and what node, provider, rate-limit, method-support, and independent-verification evidence stays with the operator. |
| Production deployment and recovery | High availability | Deployment topology, Backup and recovery, Failure modes | How to read the deployment, availability, RTO/RPO, backup, and incident-response pages during an operational readiness review. |
| Public-chain privacy and reserve evidence | Stablecoin lifecycle | Public-chain privacy, Supply cap and collateral, Source verification and auditability, Chain Indexer, Collateral developer guide, Stablecoin responsibilities, Precious metals use case | How DALP frames token-side backing checks, collateral metrics, public EVM visibility, indexed event evidence, and the split between platform collateral state and external reserve attestations. |
How to use the matrix
- Match the review question to one capability row.
- Open the Start with page first so every reader uses the same mental model.
- Use Then read for the next evidence path: operator workflow, API integration, architecture detail, or readiness review.
- Stop when the linked page answers the question. Do not treat nearby capability rows as automatic product commitments.
If a topic touches several areas, keep the sequence narrow. For example, a custody review usually starts with custody providers and signing flow. Then move to wallet verification and account security. Add the full asset issuance path only when the review also covers issuance authority or minting.
For implementation work, move from this page into the relevant developer guide. For product and risk review, start with the architecture and executive overview sections, then use security and operability pages where the question needs them.
Architecture one-pager
A buyer-safe DALP architecture one-pager for RFP, security, and integration reviews: user surfaces, API, execution engine, contracts, indexer, database, chain gateway, custody, and deployment responsibilities.
Institutional asset tokenization architecture
See how DALP structures institutional asset tokenization across asset templates, SMART Protocol contracts, identity, compliance controls, custody routing, settlement, monitoring, and APIs.