{"slug":"business/MIGRATION_STATE","title":"MIGRATION STATE","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/MIGRATION_STATE.mdx","bytes":5865,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Tier C — Historical.** This document is a point-in-time snapshot preserved for reference. For current architecture, see [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md).\n\nStatus: CURRENT\nScope: Option B migration state, product reconciliation, Supabase removal, auth mission state\nCanonical Owner: Platform\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/migrations/DE_SUPABASE_MIGRATION.md, docs/architecture/l1-reality-check.md, OPTION_B_BRANCH_DIVERGENCE_AUDIT.md, OPTION_B_WAVE0_LOG.md, wrangler manifests, README.md, Option B worktree evidence, customer-zero evidence\nSupersedes: none\nSuperseded By: none\n\nDisclaimer: This document reports migration state based on documented and manifest evidence, not inferred operational facts. Deployment, runtime, and end-to-end completion remain separately verified.\n\n---\n\n## 1. MIGRATION TARGET OVERVIEW\n\nCurrent enterprise direction: Option B product reconciliation.\n\nOption B collapses or repositions historical runtime identities into canonical platform boundaries and Platform/Product boundaries. Target runtime topology is expected to converge around:\n\n- gateway\n- loader\n- normalizer\n- schema-synthesis\n- spine-writer\n- continuity\n- governance\n- hermes\n- knowledge\n- store\n- workflow\n- webhook-ingress\n- mcp-connector\n- telemetry\n- huggingface-inference\n- admin\n- tenants\n- billing\n\nHistorical or deprecated runtime identities expected to migrate:\n\n- act\n- agent-registry\n- connector\n- folder-watcher\n- govern\n- intelligence\n- iw-agent-runtime\n- l2\n- pipeline\n- signals\n- think\n- twin-orchestrator\n\nMigration completion criteria:\n\n- customer-zero activation end-to-end on canonical topology\n- one-auth enforcement on production runtime\n- Supabase removal complete in product runtime\n- package topology stabilized\n- frontend corpus consolidated into L1 target app\n\nCurrent state is not complete. Classification for each migration thread is below.\n\n---\n\n## 2. SUPABASE REMOVAL\n\nTarget: Supabase removed from product plane.\n\nEvidence of current partial state:\n\n- Supposedly still ~71 code references to Supabase in repo\n- WRANGLER manifests for services/act, services/govern, services/tenants, services/billing, services/store reference SUPABASE_URL secrets\n- docs/migrations/DE_SUPABASE_MIGRATION.md treats removal as in progress\n- docs/architecture/l1-reality-check.md documents Supabase entanglement\n\nClassification:\n\n- Removed: UNKNOWN\n- In progress: CURRENT\n- Complete: NO\n\nDo not document as complete.\n\n---\n\n## 3. ONE-AUTH ENFORCEMENT\n\nTarget: one-auth enforcement on production runtime.\n\nEvidence:\n\n- docs/FINAL_E2E_SYSTEM.md and docs/CANON.md cite DECISION 22 combined with auth rationalization plans\n- docs/architecture/l1-reality-check.md documents Auth model still using Supabase Auth earlier than target JWT Gateway auth in some corpus\n- Option B does not conclude auth migration as complete\n\nClassification: CURRENT in migration, UNKNOWN whether enabled in production runtime.\n\n---\n\n## 4. FRONTEND CORPUS MIGRATION\n\nTarget: single L1 Workbench app substantially replacing historical Next.js Vercel multi-page corpus.\n\nOptions documented under migration history include:\n\n- dual-repo strategy\n- Vite + Cloudflare Pages canonical surface\n- legacy Next.js surface retained temporarily as Customer Zero consumer\n\nCurrent evidence:\n\n- apps directories present: apps/web, apps/workspace, apps/desktop, apps/mobile, apps/docs\n- docs/architecture/l1-reality-check.md documents Next.js entanglement\n- canonical target remains apps/web unless evidence shifts\n\nClassification: MIGRATING\n\n---\n\n## 5. PACKAGE TOPOLOGY STABILIZATION\n\nTarget package publication surface:\n\n- contracts\n- canonical\n- auth-sdk\n- tenant-sdk\n- spine-sdk\n- continuity-sdk\n- governance-sdk\n- capability-sdk\n- integration-sdk\n\nCurrent evidence:\n\n- packages/types and other existing packages exist in manifest notation\n- many packages present but not necessarily matching canonical target\n- backup packages named config-backup-_ and types-backup-_ suggest recent consolidation without yet settled publication truth\n\nClassification: MIGRATING\n\nAll backup packages must be classified:\n\n- KEEP\n- MERGE\n- REPOSITION\n- ARCHIVE\n- UNKNOWN\n\nDo not assume stabilization is complete until package filesystem and package metadata prove it.\n\n---\n\n## 6. OPTION B WAVE 0 EVIDENCE\n\nOPTION_B_BRANCH_DIVERGENCE_AUDIT.md evidences a clean cherry-pick feasibility for Wave 0 gateway/connector decoupling.\n\nWave 0 artifacts include:\n\n- services/gateway/wrangler.toml bindings for ADMIN, BILLING, TENANTS\n- services/connector/wrangler.toml bindings for LOADER, MCP, STORE\n- services/loader/lib/nango.ts and token-refresh.ts\n- services/mcp-connector/lib/oauth-jwt.ts\n- connector and OAuth tests\n\nClassification:\n\n- Work merged onto local worktree: YES\n- Approved for canonical branch: NO, pending\n- Cherry-pickable with LOW risk: evidence supported\n\n---\n\n## 7. WORKSPACE LAYER CONSOLIDATION\n\nTarget platforms/experience separation rules:\n\n- Platform = services/packages/runtimes\n- Experience = apps/UIs\n- Workbench reserved for primary end user experience only\n\nCurrent state:\n\n- services/wrangler manifests show extensive runtime coverage\n- apps corpora show multiple app surface candidates\n- doc legacy shows Workbench Doctrine spanning multiple workbench types\n\nClassification: MIGRATION IN PROGRESS, platform/experience boundary documents need finalization.\n\n---\n\n## 8. MIGRATION COMPLETION CRITERIA\n\nDo not declare migration complete without evidence for each of:\n\n- Supabase removal verified\n- One-auth enforced\n- Package topology matches target publish boundary\n- Frontend corpus evaluated against apps/web canonical mission\n- Runtime topology matches target service identities\n- Customer Zero activation end-to-end verified\n- Documentation lifecycle labels accurate across corpus\n"}