# Integration Roadmap

The authoritative sequence is Gates A–G in [BACKSTOP-MASTER-DEVELOPMENT-PLAN.md](../BACKSTOP-MASTER-DEVELOPMENT-PLAN.md). The labels below describe scope, not a promise or release date.

| Gate | Scope | Evidence required before acceptance |
|---|---|---|
| A | Engineering foundation | Local Git/CI baseline, reproducible verification, secrets handling and documented current state; hosted CI is separate external evidence |
| B | Website, Developer Docs and sandbox/Web3 application | Accurate product/docs surfaces; functional API-backed local journey; responsive, keyboard and accessibility review; no wallet or chain claim without implementation |
| C | Persistent blockchain/backend integration | Durable transaction journal, idempotent retry/restart behavior, event cursor, confirmations and reorg-safe reconciliation across the backend/EVM boundary |
| D | Base Sepolia testnet product | Explicitly approved test-only deployment, verified chain/addresses/source, test asset provenance and transaction/receipt evidence; no mainnet |
| E | Financial security, risk and operations | Independent security work, authorization/solvency evidence, monitoring, recovery and incident procedures |
| F | Provider network and bounded pilot | Named provider, approved operational/legal roles, tested credentials and failure/reconciliation procedures |
| G | Ecosystem expansion | Each module independently scoped, threat-modeled, tested and approved; no capability is implied by roadmap listing |

## Current dependencies and non-goals

Gate B's default browser sandbox stays simulated. The opt-in Gate C fixture connects the durable HTTP API/SQLite/outbox to the local vault for the full protection lifecycle, with verified receipts, restart/reorg handling, read-only reconciliation and signed operator recovery. [Gate C acceptance](../BACKSTOP-GATE-C-ACCEPTANCE.md) records the final local evidence. Gate D wallet/testnet integration follows separately and deployment requires explicit approval. A local contract build is not testnet verification.

Wallets, exchanges, payment providers, Recover expansion, multi-chain adapters and AI/Prevent modules are not available just because they appear in future product concepts. The website labels them planned or unavailable until concrete implementation evidence exists. No autonomous financial correction is part of reconciliation.