# Capability docs matrix

Source: https://docs.settlemint.com/docs/architecture/start-here/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. Architects, reviewers, and integration teams can use this matrix to find the right page before detailed implementation or review work.

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-coverage]

| Capability area                              | Start with                                                                                             | Then read                                                                                                                                                                                                                                             | What the docs cover                                                                                                                                                   |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Platform architecture and ownership          | [System context](/docs/architecture/start-here/system-context)                                         | [Architecture one-pager](/docs/architecture/start-here/architecture-one-pager), [Components](/docs/architecture/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](/docs/architecture/concepts/tokenization-modeling)                             | [Asset issuance](/docs/architecture/flows/asset-issuance), [Create an asset](/docs/user-guides/asset-creation/create-asset), [Token lifecycle API](/docs/developer-guides/api-integration/token-lifecycle)                                            | 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](/docs/architecture/start-here/lifecycle-after-issuance)                     | [Asset detail workspace](/docs/user-guides/asset-servicing/asset-detail-workspace), [Mint assets](/docs/user-guides/asset-servicing/mint-assets), [Asset economics](/docs/architecture/concepts/tokenization-modeling#where-asset-economics-fit)      | 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](/docs/architecture/security/identity-compliance)                             | [Compliance modules](/docs/architecture/security/compliance), [Configure trusted issuers](/docs/user-guides/compliance/configure-trusted-issuers), [Compliance provider subjects](/docs/developer-guides/compliance/compliance-provider-subjects)     | How identity claims, trusted issuers, configured compliance modules, and provider-driven subject records participate in transfer and issuance controls.               |
| Custody, signing, and wallet verification    | [Custody providers](/docs/architecture/integrations/custody-providers)                                 | [Signing flow](/docs/architecture/flows/signing-flow), [Wallet verification](/docs/architecture/security/wallet-verification), [Account security](/docs/user-guides/user-management/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](/docs/architecture/security/replay-idempotency-mint-controls) | [Source verification and auditability](/docs/architecture/security/source-verification-auditability), [Mint assets](/docs/developer-guides/asset-servicing/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](/docs/architecture/flows/xvp-settlement)                                              | [XvP operator guides](/docs/user-guides/system-addons/xvp-settlement/overview), [Bridge and cross-chain position](/docs/architecture/security/bridge-cross-chain), [Supported networks](/docs/architecture/integrations/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](/docs/executive-overview/market-data-infrastructure)                      | [Feeds overview](/docs/developer-guides/feeds/overview), [Create feeds](/docs/developer-guides/feeds/create-feeds), [Feeds update flow](/docs/architecture/flows/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](/docs/architecture/security/source-verification-auditability)   | [Events](/docs/events), [Operability](/docs/architecture/operability), [Observability](/docs/architecture/operability/observability)                                                                                                                  | Which records and event streams help reviewers trace platform actions, monitor operations, and reconcile workflow outcomes.                                           |
| Production deployment and recovery           | [High availability](/docs/architecture/self-hosting/high-availability)                                 | [Deployment topology](/docs/architecture/overview/deployment-topology), [Backup and recovery](/docs/architecture/self-hosting/high-availability/backup-recovery), [Failure modes](/docs/architecture/operability/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    | [Public-chain privacy](/docs/architecture/security/public-chain-privacy)                               | [Supply cap and collateral](/docs/architecture/security/compliance/supply-cap-collateral), [Precious metals use case](/docs/executive-overview/use-cases/precious-metals), [Tokenization modeling](/docs/architecture/concepts/tokenization-modeling) | How DALP frames public EVM visibility, configured supply or collateral controls, and external reserve or backing evidence responsibilities.                           |

## How to use the matrix [#how-to-use-the-matrix]

Start with the capability area that matches the review question. Use the first link for the mental model, then use the follow-up links for operator steps, API details, or review evidence.

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, use the architecture, security, operability, and executive overview sections first.