Runbooks
Find the right DALP runbook for controlled platform, compliance, asset, and recovery operations.
DALP runbooks are controlled operating checklists for DALP state changes. Operators, compliance administrators, and developers use them when they need a named starting state, ordered steps, and a verification check.
Use this page to choose the right runbook before you start. If you need concepts, API fields, custody-provider policy, chain operations outside DALP, or an external incident-response plan, use the architecture, API, provider, or operations pages instead. Runbooks stay focused on DALP procedures with an accountable operator and a clear before-and-after state.
How to choose the next page
Start by naming the state you are about to change. Then pick the runbook group that matches the accountable operator. If the procedure you need is not listed here, use the nearest architecture or developer guide for context and keep the operational checklist with the owning team until a dedicated runbook exists.
Before you use a runbook
Make these checks before you begin:
- Confirm that you own the procedure or have the required DALP role for the page you are about to follow.
- Capture the current state first: participant, asset, provider, issuer, signer, workflow, or service status.
- Keep the verification step in view. A runbook is complete only when its final check proves the intended state change.
- Use the narrower guide when a page links to one. Do not turn a conceptual architecture page into an operating checklist.
Runbook groups
| Group | Owner for execution | Use it for | Current coverage |
|---|---|---|---|
| Operator runbooks | Identity Managers and platform operators | Admin and operations tasks completed in the DALP UI or across platform roles. | Actions work queue, User onboarding, and the user-facing Equity tokenization walkthrough. |
| Developer runbooks | Integrating developers and API operators | API, CLI, and integration procedures that create, mint, configure, or reconcile assets. | Developer runbooks, including token creation and collateral configuration walkthroughs. |
| Compliance runbooks | Compliance administrators and provider owners | Provider, issuer, signer, KYC, and compliance-control procedures that need a verifiable before-and-after state. | Rotate provider claim signer key and compliance configuration runbooks in the developer guides. |
| Recovery and incident runbooks | Service owners and incident operators | Restoring a DALP service, workflow, chain dependency, or operating state after a failure. | workflow engine recovery and architecture recovery pages until a dedicated incident runbook is needed. |
| Scenario walkthroughs | The role named in the walkthrough | End-to-end rehearsal flows for a named asset class or operating scenario. | The equity tokenization walkthroughs remain split by reader: the user guide covers UI operation, and the developer guide covers API execution. |
Available runbooks
| Runbook | Group | When to use it | Verification outcome |
|---|---|---|---|
| Actions work queue | Operator runbook | An operator needs to review pending, upcoming, completed, or expired DALP actions from the Actions page. | The operator can identify executable rows, act on supported pending actions, and verify the queue changed. |
| Rotate provider claim signer key | Compliance runbook | A compliance provider needs to replace the EOA used by its claim-issuer identity without changing the trusted issuer set. | The replacement key is active, the old key is removed, and DALP bookkeeping points at the replacement signer. |
| User onboarding | Operator runbook | An Identity Manager needs to register a participant and issue KYC verification through the DALP UI. | The participant has the required identity and verification state for the next operating step. |
| Equity tokenization in the console | Scenario walkthrough | An operator needs a UI-led rehearsal for an equity tokenization scenario. | The scenario reaches the documented post-tokenization state through platform screens. |
| Equity tokenization through APIs | Scenario walkthrough | A developer needs the same equity tokenization scenario through API calls. | The scenario reaches the documented post-tokenization state through API execution. |
| Create and mint bonds | Developer runbook | A developer needs to create debt instruments with coupon schedules and maturity dates. | The bond token exists with the documented minting state. |
| Create and mint deposits | Developer runbook | A developer needs to issue deposit certificates with interest accrual. | The deposit token exists with the documented minting state. |
| Create and mint equities | Developer runbook | A developer needs to deploy equity tokens with dividend distribution. | The equity token exists with the documented minting state. |
| Create and mint funds | Developer runbook | A developer needs to launch fund tokens with NAV tracking. | The fund token exists with the documented minting state. |
| Create and mint stablecoins | Developer runbook | A developer needs to create collateral-backed stablecoins. | The stablecoin exists with the documented minting state. |
| Configure equity collateral | Compliance runbook | A developer needs to add collateral requirements through the Compliance Module API. | The equity collateral requirement is configured for the documented asset. |
What to read next
- For the product architecture behind operational roles, read system context.
- For API-led asset operations, start with API integration.
- For UI-led operator tasks, start with user guides.
Actions work queue
Review upcoming, pending, completed, and expired DALP actions from the operator queue.
Rotate provider claim signer key
Operational runbook for rotating the autonomous EOA that signs claims on a compliance provider's claim-issuer identity. Rotation happens via addKey / removeKey on the identity and does not require any trusted issuers registry mutation.