Dependency Map | Dreamineering

DEPENDENCY MAP
════════════════════════════════════════════════════════════

                    ┌─────────┐
                    │  START   │
                    └────┬────┘
                         │
          ┌──────────────┼──────────────┐
          │              │              │
          ▼              ▼              ▼
     ┌─────────┐   ┌─────────┐   ┌─────────┐
     │ KYC API │   │  FIAT   │   │ MOVE/SUI│
     │(SumSub) │   │ (Stripe)│   │(Internal)│
     └────┬────┘   └────┬────┘   └────┬────┘
          │        ═════╪══════       │
          │              │            │
          └──────────────┼────────────┘
                         │
                         ▼
                    ┌─────────┐
                    │ SUI MVP │
                    └────┬────┘
                         │
                         ▼
                    ┌─────────┐
                    │  DONE   │
                    └─────────┘

  ─────── = Soft (can proceed with mocks)
  ═══════ = HARD (cannot proceed without functional fiat flow for actual value transfer)

════════════════════════════════════════════════════════════

Dependency Notes:
- KYC APIs (SumSub/Blockpass) can be soft-mocked during initial development.
- Move smart contract architecture is completely internal and parallelized.
- Fiat Rail is a HARD external dependency because issuers won't use the platform without automated dividend distributions and funding rails.

Questions

Which dependency in the sui real estate tokenization map represents the highest systemic risk — and is there a path to eliminating it?

If the most critical dependency failed, which capabilities would cascade and which could operate independently?
Are any dependencies in this map bidirectional — and does that create circular risk that should be decomposed?
Which dependency was added because of a constraint that no longer exists?

Questions​

Questions