Pre-flight Maps
The five maps that prove we understand the problem before we build the Sui Tokenization capability.
| Map | Purpose | Key Finding |
|---|---|---|
| Outcome Map | What success looks like | The hardest part is off-chain/on-chain compliance sync, mitigated by Sui capabilities. |
| Value Stream | Where time dies | Onboarding and cap table reconciliation currently take weeks of wait time. |
| Dependencies | What blocks progress | KYC and fiat rail integrations are the only hard external dependencies. |
| Capabilities | What we can do | We have the Move expertise; we need to integrate fiat rails. |
| A&ID | How it orchestrates | Agents monitor compliance; Move capabilities enforce it structurally. |
Context
- PRD Index — Sui Real Estate Tokenization
- Prompt Deck — 5-card pitch
- Spec — Engineering depth
Questions
What is the most important visual missing from the sui real estate tokenization picture set — and why does it matter?
- Which relationship between elements in this diagram is most underspecified — and what would happen if it were wrong?
- If this picture were shown to a new engineer on day one, what would they misunderstand — and how should the picture be changed?
- What assumption does this visual make that should be made explicit in the spec?