Why institutional readers need multiple documentation lenses
An institutional diligence pass is rarely one question. It usually combines venue-model review, execution-risk review, integration review, governance review, and regulated-operating-context review. That is why the public docs spread this material across reference, how-to, and explanation routes that answer different diligence questions.Why market structure and compliance are documented together
For DerivaDEX, market structure is not separable from compliance posture. Public versus restricted APIs, explicit KYC boundaries, solvency controls, and governance-linked parameter changes all affect how an institution evaluates the venue. A reader who only studies latency or product specs without the operating-boundary pages will miss part of the real contract.Why market makers and integrators still need the same core truth
Market makers often come to the docs with a different first question than general integrators, but they still rely on the same underlying truth:- product constraints and price-band guards
- ordered-state and acknowledgement semantics
- funding, liquidation, and solvency behavior
- contract and governance upgrade boundaries
What the public diligence surface can answer
The public docs are meant to make the public contract legible. A diligence reader should be able to answer at least these questions from the public surface:- how orders are sequenced, matched, and bounded by public guardrails
- which APIs and operational routes are public versus restricted
- which governance mechanisms can change risk parameters or operating posture
- where support, escalation, and institutional follow-up begin
Where public diligence stops
The public surface is not a substitute for a private diligence room. It does not publish bespoke commercial terms, private runbooks, or jurisdiction-specific legal analysis as if those were stable public reference pages.How to read the public surface efficiently
Institutional readers usually get the best result by moving in this order:- platform and market-structure baseline
- execution and solvency controls
- integration and performance posture
- governance and token controls
- operating and escalation boundaries
Sources
- Institutional Resources for the current public institutional route map and publication boundary
- Institutional Diligence and Market-Maker Evaluation Reference for the structured artifact families and boundary limits
- Regulatory and Compliance Approach for the public explanation of governance, restricted surfaces, and regulated operating posture
- How DerivaDEX Works for the platform model and public exchange mechanics
- Price Formation, Risk Controls, and Solvency for the integrated view of risk controls and solvency behavior
- Performance Engineering for Strategy Builders for the latency-sensitive system-reading needed by institutional and market-making teams
- Digital Assets Supervision and Regulation in Bermuda for the statutory digital-asset regulatory framework already referenced elsewhere in the public docs