docs: add Dusk Trade and bridge docs sections

Author: HDauven

public/llms-full.txt

@@ -32,6 +32,7 @@ Dusk is designed for workflows such as:
 Relevant docs:
 
 - https://docs.dusk.network/learn/market-infrastructure/
+- https://docs.dusk.network/learn/dusk-trade/
 - https://docs.dusk.network/learn/tokenization-comparison/
 - https://docs.dusk.network/learn/deep-dive/assets-and-regulations/
 
@@ -78,6 +79,7 @@ Relevant docs:
 
 - Overview: https://docs.dusk.network/learn/overview/
 - Market Infrastructure: https://docs.dusk.network/learn/market-infrastructure/
+- Dusk Trade: https://docs.dusk.network/learn/dusk-trade/
 - Core Components: https://docs.dusk.network/learn/core-components/
 - Core Values: https://docs.dusk.network/learn/core-values/
 - Native Issuance: https://docs.dusk.network/learn/tokenization-comparison/

public/llms.txt

@@ -6,6 +6,7 @@
 
 - [Overview](https://docs.dusk.network/learn/overview/): high-level introduction to Dusk.
 - [Market Infrastructure](https://docs.dusk.network/learn/market-infrastructure/): how Dusk supports regulated asset workflows.
+- [Dusk Trade](https://docs.dusk.network/learn/dusk-trade/): product layer for tokenized financial asset workflows on Dusk.
 - [Core Components](https://docs.dusk.network/learn/core-components/): DuskDS, Rusk, DuskVM, DuskEVM, Citadel, and application-layer tooling.
 - [Core Values](https://docs.dusk.network/learn/core-values/): regulated workflows, access controls, selective disclosure, and deterministic settlement.
 - [Native Issuance](https://docs.dusk.network/learn/tokenization-comparison/): digitization, tokenization, and native issuance.

src/content/docs/developer/integrations/dusk-connect.md

@@ -22,6 +22,8 @@ Dusk applications often need two kinds of integration:
 
 Dusk Connect is for the wallet side. For network APIs and transaction flow, see [Transaction Lifecycle](/developer/integrations/tx-lifecycle), [HTTP API](/developer/integrations/http-api), and [W3sper SDK](/developer/integrations/w3sper).
 
+If you are testing against the first-party browser wallet, use the [Dusk Wallet Extension](/developer/integrations/wallet-extension) as one compatible provider.
+
 ## Typical flow
 
 A dApp integration usually follows this shape:

src/content/docs/developer/integrations/wallet-extension.md

@@ -28,6 +28,8 @@ A typical dApp flow is:
 
 See [Dusk Connect](/developer/integrations/dusk-connect) for the SDK-level integration path.
 
+If you are building the application side, start with Dusk Connect. If you are testing or documenting the wallet-provider side, use this page together with the wallet provider API.
+
 ## Provider discovery
 
 The extension announces an EIP-1193-style provider through Dusk discovery events. Dusk is not an EVM chain, so wallet methods use Dusk-specific names.

src/content/docs/learn/core-components.md

@@ -74,7 +74,7 @@ On top of the base protocol, Dusk supports application-layer protocols and tools
 
 ### Dusk Trade
 
-Dusk Trade is the application layer for tokenized financial assets on Dusk. It is being built around real market workflows: investor onboarding, wallet binding, controlled transfers, payment coordination, and compliant settlement.
+[Dusk Trade](/learn/dusk-trade) is the application layer for tokenized financial assets on Dusk. It is being built around real market workflows: investor onboarding, wallet binding, controlled transfers, payment coordination, and compliant settlement.
 
 ### Zedger / Hedger
 

src/content/docs/learn/deep-dive/assets-and-regulations/index.md

@@ -9,6 +9,7 @@ If you're looking for implementation details, start here:
 - [Digital Identity Protocol (Citadel)](/developer/digital-identity/protocol)
 - [Transaction Models (Moonlight & Phoenix)](/learn/deep-dive/duskds-tx-models)
 - [Market Infrastructure on Dusk](/learn/market-infrastructure)
+- [Dusk Trade](/learn/dusk-trade)
 
 ## MiCA (EU)
 
@@ -82,6 +83,7 @@ For many tokenization projects, the relevant takeaway is that “real-world” a
 
 ## Read next
 
+- [Dusk Trade](/learn/dusk-trade)
 - [Native Issuance](/learn/tokenization-comparison)
 - [Market Infrastructure on Dusk](/learn/market-infrastructure)
 - [Digital Identity Protocol](/developer/digital-identity/protocol)

src/content/docs/learn/dusk-trade.md

@@ -0,0 +1,58 @@
+---
+title: Dusk Trade
+description: Where Dusk Trade fits in the Dusk stack and how it turns market infrastructure into tokenized asset workflows.
+---
+
+Dusk Trade is the application layer for tokenized financial assets on Dusk.
+
+It sits above the base protocol and turns Dusk's market-infrastructure primitives into user-facing workflows: asset discovery, investor onboarding, wallet connection, payment coordination, trading actions, and settlement.
+
+## What Dusk Trade is for
+
+Dusk Trade is designed for regulated market workflows where assets are not just listed and transferred, but also need eligibility, disclosure, and settlement logic around them.
+
+Typical flows include:
+
+- discovering tokenized financial assets
+- connecting a wallet
+- completing onboarding or eligibility checks
+- buying or selling an asset
+- coordinating the asset leg and payment leg
+- exposing the right information to issuers, venues, investors, or other authorized parties
+
+## Where it fits in the stack
+
+Dusk Trade is not the base protocol. It is a product layer that can use the Dusk stack underneath it.
+
+| Layer | Role |
+| --- | --- |
+| **DuskDS** | Settlement, finality, data availability, native transaction models |
+| **DuskEVM** | EVM-compatible application execution and Solidity tooling |
+| **DuskVM** | Native Rust/WASM execution for Dusk-specific contracts |
+| **Citadel** | Identity, credentials, and selective disclosure patterns |
+| **Dusk Connect** | Wallet discovery and account connection |
+| **Dusk Wallet Extension** | First-party browser wallet provider for Dusk applications |
+
+The exact architecture depends on the product and regulatory requirements of the market being served.
+
+## Why it matters
+
+For regulated assets, the hard part is rarely a token contract in isolation. The hard part is the complete market workflow:
+
+- who can access the asset
+- who can hold or transfer it
+- what information is public
+- what information is confidential
+- what can be selectively disclosed
+- how payment and asset settlement are coordinated
+- how issuers, venues, and investors interact with the same environment
+
+Dusk Trade is where those requirements become a usable product surface.
+
+## Read next
+
+- [Market Infrastructure on Dusk](/learn/market-infrastructure)
+- [Native Issuance](/learn/tokenization-comparison)
+- [Assets & Regulations](/learn/deep-dive/assets-and-regulations)
+- [Dusk Connect](/developer/integrations/dusk-connect)
+- [Dusk Wallet Extension](/developer/integrations/wallet-extension)

src/content/docs/learn/guides/staking-basics.md

@@ -22,6 +22,8 @@ To earn protocol staking rewards directly, you run a provisioner node 24/7 and s
 - Run a node: [Provisioner node](/operator/provisioner)
 - Set up wallet + stake: [Wallet setup](/operator/guides/node-wallet-setup)
 
+If you are deciding whether to operate infrastructure yourself, read this page first, then move to the operator guide once you are ready to run a node.
+
 ### 2) Staking pools (no infrastructure)
 
 Some third-party services and on-chain pools stake on behalf of users. This can let you earn staking yield without running your own node, but it adds operator and smart contract risk.
@@ -80,5 +82,6 @@ If you withdraw down to **600 DUSK** active stake, the **400 DUSK** inactive sta
 ## Next steps
 
 - Direct staking (run your own node): [Provisioner node](/operator/provisioner), then [Wallet setup](/operator/guides/node-wallet-setup)
+- Operator maintenance after staking: [Maintenance & monitoring](/operator/maintenance-monitoring)
 - Understand rewards and emissions: [Tokenomics](/learn/tokenomics)
 - If you hold ERC20/BEP20 DUSK: [Mainnet migration](/learn/guides/mainnet-migration)

src/content/docs/learn/market-infrastructure.md

@@ -59,9 +59,13 @@ Use the Dusk stack depending on the layer you are building:
 - **DuskVM** for Rust/WASM contracts that need native Dusk execution.
 - **Citadel** for identity, credentials, and selective disclosure patterns.
 - **Dusk Connect** for wallet discovery and account connection in Dusk applications.
+- **Dusk Trade** for product-level tokenized asset workflows such as onboarding, wallet connection, buying, selling, and settlement coordination.
+
+If you want to understand the product layer, start with [Dusk Trade](/learn/dusk-trade). If you want the underlying regulated asset concepts, read [Assets & Regulations](/learn/deep-dive/assets-and-regulations).
 
 ## Read next
 
+- [Dusk Trade](/learn/dusk-trade)
 - [Native Issuance](/learn/tokenization-comparison)
 - [Assets & Regulations](/learn/deep-dive/assets-and-regulations)
 - [Core Components](/learn/core-components)

src/content/docs/learn/tokenization-comparison.md

@@ -43,4 +43,4 @@ In practice, that means you can:
 - build applications and tokenization-style workflows with familiar EVM tooling through **DuskEVM**, and
 - rely on **DuskDS**, the Dusk L1, for privacy-capable transaction models, data availability, and deterministic finality.
 
-If you want the architectural overview next, see [Core Components](/learn/core-components). For the product and market framing, see [Overview](/learn/overview).
+If you want the architectural overview next, see [Core Components](/learn/core-components). For the product and market framing, see [Overview](/learn/overview), [Market Infrastructure on Dusk](/learn/market-infrastructure), and [Dusk Trade](/learn/dusk-trade).