Overview
The platform layer is where operators, integrators, and administrators enter DALP. It explains how the Asset Console, Unified API, and System Factory route requests through shared authentication, authorization, wallet verification, and audit controls.
Operators use the Asset Console. External systems call the Unified API. Administrators create organization systems through the System Factory. These entry surfaces share backend controls before work reaches execution services, custody signing, indexers, or SMART Protocol contracts.
Where this layer fits
This layer turns a browser request, API call, or administrator setup request into a controlled DALP operation. It authenticates the caller, checks authorization, applies wallet verification when a blockchain signature is needed, records audit data, and routes eligible work to the services that execute it.
This entry layer does not replace the Execution Engine, Chain Indexer, custody integration, System Factory, or SMART Protocol contracts. It owns request intake, shared backend controls, and the creation path into the System Factory. Operators and external systems still own user access policy, off-platform approvals, custody provider policy, and caller-side integration behavior.
Request path
- The Asset Console or an API client submits an authenticated request.
- The Unified API validates the request, checks permissions, and applies wallet verification when the operation needs a blockchain signature.
- Backend services coordinate execution, indexing, storage, and audit records.
- Infrastructure services call the relevant SMART Protocol contracts when the operation changes on-chain state.
This route matters for regulated operations. A human can start a workflow in the browser, and an integration can automate the same workflow through the API. DALP still applies the same policy checks and records the operation through the same backend path.
Component summary
| Component | What it is | What it controls | What it does not control |
|---|---|---|---|
| Asset Console | White-label web interface for managing assets, compliance work, portfolio views, and distribution. | Browser workflows, role-based screens, wallet verification prompts, branding, language settings, and operator navigation. | It does not bypass API permissions, custody signing, compliance modules, or contract rules. |
| Unified API | OpenAPI 3.1 documented programmatic access to platform operations. | Request validation, authentication, authorization, headers, versioned API discovery, and integration entry points. | It does not grant a caller broader participant rights than its credential allows or replace workflow state. |
| System Factory | Organization system creation and token factory scoping for asset isolation. | One system per organization, directory-backed system creation, factory registry scope, and fail-closed reads without factories. | It does not treat wallet addresses as tenants or make assets visible outside the active system context. |
Review path
Security and architecture reviewers should be able to trace a request from entry surface to execution evidence. Start with the platform layer when you need to answer these questions:
| Review question | Platform-layer answer | Next evidence page |
|---|---|---|
| How do users and systems enter DALP? | Operators use the Asset Console. Integrations call the Unified API. Administrators create systems. | Asset Console and Unified API |
| Which controls run before execution? | The shared backend path validates the request, checks authorization, applies required wallet verification, and records audit data. | Authorization and wallet verification |
| Where is tenant or organization scope set? | System creation establishes the organization system, and token reads use the active system context. | System Factory and system context |
| Where do execution, custody, and chain state live? | This layer routes eligible work to execution services, custody and signing controls, indexers, and contracts. | Infrastructure layer and asset contracts |
This page stops at the entry layer. Read the linked component pages when you need endpoint details, wallet verification behavior, execution state, system creation failure modes, or on-chain contract behavior.
Choose the right surface
| Reader goal | Start here | Then read |
|---|---|---|
| Operate assets through a governed web interface | Asset Console | Wallet verification and compliance modules |
| Automate asset lifecycle operations from another system | Unified API | API integration guide |
| Create or isolate an organization system | System Factory | System context and contract runtime |
| Review how user requests become controlled execution | This overview | Execution engine and security architecture |
What stays outside this layer
This layer does not decide token eligibility, custody policy, or settlement finality by itself. It collects the request, authenticates the actor, checks authorization, applies required request gates, and hands the operation to shared services.
Compliance modules, identity claims, custody signing, workflows, indexers, and smart contracts enforce the deeper rules. This split keeps entry points consistent: browser and API requests reach the same backend behavior when they represent the same action, and system setup creates the organization context that later scopes assets, identities, registries, and factory-backed reads.
Where to go next
- Start with Asset Console when you need the operator workspace, branding controls, or browser workflow model.
- Start with Unified API when you need programmatic access, OpenAPI files, or integration behavior.
- Start with System Factory when you need to understand organization systems, creation idempotency, or tenant-scoped asset reads.
- Read the component catalog for the full component model.
- Read the infrastructure layer for the services that execute platform requests.
- Read security architecture for authentication, authorization, identity, and wallet verification.
- Read asset contracts for the SMART Protocol contracts that execute token behavior.
Component catalog
Find the DALP component layer that owns an architecture decision, integration handoff, control, or evidence trail across platform entry surfaces, infrastructure services, asset contracts, token features, and capabilities.
Asset Console
The Asset Console is DALP's authenticated web interface for asset lifecycle operations. It gives operators a guided view over asset design, holdings, compliance checks, and theme configuration while keeping execution, policy, and audit evidence in the platform services behind it.