#dusk I went back to the same section twice on Dusk's market-infrastructure page.
It lists six stages a regulated asset moves through: issuer setup, investor onboarding, transfer controls, trading, settlement, then servicing and disclosure. Nothing unusual there on its own.

What stopped me was one line right before that list.
Per Dusk's own documentation, the goal isn't to make every workflow private or every workflow public. The choice of what's visible, what's confidential, and what's disclosed to specific parties gets made per stage, not once for the whole application.

I'd been picturing privacy as a setting you choose for an entire product. This reframes it as something closer to a dial, reset at each step. Onboarding might stay confidential to protect an investor's identity, while settlement might need to stay visible enough for a regulator to trust it happened.

What I can't tell from the page alone is who actually makes that per-stage call in practice, the issuer designing the workflow, or something closer to a default the protocol nudges builders toward.

$DUSK @Dusk