> For the complete documentation index, see [llms.txt](https://worldxc.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://worldxc.gitbook.io/docs/start-here/mvp-scope-and-sequencing.md). # MVP Scope and Sequencing Exchanges fail when complexity outpaces control. WorldX follows a sequencing rule:
Foundations → Proof → Liquidity → Scale #### MVP Scope MVP is complete when: **A) The wallet System is Correct and Controlled** * Deposits and withdrawals work reliably * Balance states are explicit and consistent * Suspicious withdrawals trigger containment pathways * Reconciliation runs continuously, and exceptions are handled **B) Spot Trading is Stable and Transparent** * Order placement and fills are consistent * Fees are clearly disclosed * The trade history is accurate and exportable * Basic market integrity monitoring is operating **C) Trust Hub v1 is Live** * PoR/PoL/custody/execution/listing/incident modules exist * Each module includes scope, method, cadence, limitations, and changelog * The incident log is permanent (not deleted after recovery) **D) Operational readiness exists** * Monitoring and alerting are in place * Incident response playbooks exist * Change-control discipline exists (no silent rule changes) #### Post-MVP Expansion WorldX expands only after: * Trust Hub cadence is stable (not “one-off reports”) * Custody controls and incident readiness are validated in real operation * Market integrity controls operate effectively under stress * Compliance posture supports expansion regions and features This is how WorldX avoids becoming “wide but fragile.”