# V3 migration roadmap by release wave

The ledger is complete as an inventory, not as a port. Most dispositions remain
blocked because completion must be evidence-backed and owner-authorized.

## Wave 0 — Authority reconciliation and freeze

**Scope:** 36 V2 contract identities, 134 deployed addresses, 36 ABIs, 134
runtime hashes, 132 source routes, 97 x402 network offerings, 15 Solana
programs, and all discovered repository surfaces.

**Exit gates**

- Canonical counts and checksums reproduce exactly.
- V2 ABI and runtime checks pass without writes or network access.
- The nine aggregate-only Solana x402 offerings are replaced by exact
  method/path/network identities from the live-service authority.
- Owners are assigned to every blocked ledger item.

## Wave 1 — Mission/privacy and forbidden-control firewall

**Scope:** behavioral, flourishing, reputation, loyalty, belief, biometric,
profiling, and surveillance-derived signals.

**Exit gates**

- None of those signals controls custody, access, eligibility, pricing,
  slashing, settlement, or disputes.
- Every high-impact decision uses objective, consented, auditable inputs.
- Negative policy tests prove direct, indirect, wrapper, SDK, API, and metadata
  paths fail closed.
- Privacy classifications and retention/disclosure behavior are reviewed.

## Wave 2 — Core contracts, chain surfaces, and governance

**Scope:** Base first, then Avalanche, Arbitrum, Polygon; contract mappings;
roles, multisig/timelock, pause, recovery, and incident controls.

**Exit gates**

- Per-contract port/wrapper/retirement decisions have concrete V3 targets.
- Contract, invariant, and arithmetic suites pass for the exact candidate.
- Assets/liabilities, caps, deadlines, dispute paths, and role transitions are
  covered by regression and invariant evidence.
- No deployment occurs through this roadmap; deployment requires a separate,
  authorized human gate.

## Wave 3 — SDK and API compatibility

**Scope:** every exported SDK symbol and every one of the 132 V2 source routes.

**Exit gates**

- Export snapshots and typed import compatibility pass.
- Request/response/error/idempotency contracts have explicit dispositions.
- The generated V2/V3 compatibility discovery artifact is current.
- SDK and API builds/tests run from a clean exact-candidate environment.

## Wave 4 — x402 discovery, Bazaar, and Solana

**Scope:** 88 exact Base endpoint entries, nine currently aggregate-only Solana
entries, discovery/Bazaar metadata, 15 Solana programs, unpaid-402 and receipt
behavior.

**Exit gates**

- All 97 endpoint identities are exact and source-linked.
- Discovery count, schemas, prices, payees, networks, and version claims agree.
- Unpaid requests return the specified 402 challenge without side effects.
- Receipt verification, replay resistance, idempotency, and settlement safety
  pass; no prohibited signals gate payment or disputes.
- Solana builds/IDLs/artifacts reproduce in the clean room.

## Wave 5 — Site, navigation, docs, operations, and partner claims

**Scope:** all inventoried pages/nav/docs, schemas/manifests, monitoring,
incident/recovery controls, and readiness-claim lines.

**Exit gates**

- V2 and V3 addresses/actions are visibly isolated.
- Links, version labels, schemas, manifests, and generated files are current.
- Monitoring, incident, rollback, and recovery drills have evidence.
- Every partner-facing readiness claim links to exact-candidate proof or states
  its unresolved blocker plainly.

## Wave 6 — Pre-push clean-room release candidate

**Exit gates**

- Fresh local clone/worktree of the exact commit/tree; no dirty or local
  untracked dependency.
- Complete ledger and checksum verification.
- Full contract/invariant/arithmetic, SDK/API/site, Solana, and x402 matrix.
- Frozen V2 compatibility proof.
- Final-scope review has zero active critical/high/medium/low findings.
- All external blockers are truthfulness-reviewed and none is release-blocking.

## Wave 7 — GitLawb main publication verification

**Exit gates**

- Authorized publisher pushes; this package does not.
- Fresh post-push clone of GitLawb `main` resolves to the exact candidate
  commit/tree.
- The complete Wave 6 matrix passes again without local dependencies, stale
  generated artifacts, or unverifiable counts.
- `publication_gate.py --stage final` passes.
