{"slug":"business/DEPLOYMENT_STATE","title":"DEPLOYMENT STATE","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/DEPLOYMENT_STATE.mdx","bytes":9810,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CURRENT\nScope: Observed deployed Cloudflare infrastructure and runtime readiness evidence\nCanonical Owner: Platform\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/operations/CF_WIRE_STATUS.md, docs/operations/ENDPOINT_MAP.md, docs/operations/DEPLOYMENT_RUNBOOK.md, docs/internal/runbooks/deployment-and-rollback.md, docs/archive/DEPLOYMENT_ANALYSIS_FULL.md, docs/archive/DEPLOYMENT_CLOUDFLARE.md, docs/archive/DEPLOYMENT_FIX.md, docs/archive/DEPLOYMENT_READY.md, docs/archive/DEPLOYMENT_STATUS.md, docs/archive/DEPLOYMENT_SUMMARY.md, docs/archive/VERCEL_DEPLOYMENT_STATUS.md, Option B divergence audit, wrangler manifests\nSupersedes: none\nSuperseded By: none\n\nDisclaimer: This document records observed deployment evidence and repository manifests only. Deployment success does not prove end-to-end operation. Do not classify as production ready without verification.\n\n---\n\n## 1. WHAT THIS DOCUMENT RECORDS\n\n- current repository service reality\n- target runtime topology\n- current Cloudflare deployment evidence\n- deployment summary claims and qualifying evidence\n- classified Worker inventory\n\nFull Worker inventory must be combined with:\n\n- Cloudflare runtime review\n- traffic/binding review\n- trigger review\n\n---\n\n## 2. CURRENT REPOSITORY DEPLOYABLE RUNTIME IDENTITIES\n\nFrom wrangler manifests across services/ and packages/:\n\n| Worker Name / Route    | Service                                   | Route                             | Observations                            |\n| ---------------------- | ----------------------------------------- | --------------------------------- | --------------------------------------- |\n| gateway                | services/gateway                          | gateway.dev.integratewise.ai      | production route documented             |\n| pipeline               | services/pipeline                         | pipeline.dev.integratewise.ai     | production route documented             |\n| intelligence           | services/intelligence                     | intelligence.dev.integratewise.ai | production route documented             |\n| twin-orchestrator      | services/twin-orchestrator                | twin.dev.integratewise.ai         | cron trigger + custom domain documented |\n| mcp-connector          | services/mcp-connector                    | mcp.integratewise.ai              | MCP route documented                    |\n| hub-controller-api     | packages/api                              | no explicit custom domain         | deployable package worker               |\n| iw-mcp-tool-connector  | packages/integratewise-mcp-tool-connector | no explicit custom domain         | deployable package worker               |\n| integratewise-webhooks | packages/webhooks                         | webhook route in manifest         | package worker                          |\n\nMany additional service manifests deploy without documented routes and are presumed to be accessible via internal service bindings from gateway or adjacent Workers.\n\n---\n\n## 3. OBSERVED DEPLOYMENT EVIDENCE\n\nDocumented deployment events:\n\n- Option B Wave 0 worker decoupling documented as cherry-pickable LOW risk\n- MCP OAuth 2.0 Worker reportedly deployed based on `docs/archive/DEPLOYMENT_ANALYSIS_FULL.md` and docs.internal/MCP_SETUP_COMPLETE.md\n- Twin agent runtime reportedly deployed\n- Wave 0 log documents operation day evidence as ca. July 2026 landing sheet claims\n\nVerified deployment evidence from manifest:\n\n- Worker names with wrangler.toml present: 30\n- Production custom domain route or documented route: gateway, pipeline, intelligence, iw-agent-runtime, mcp-connector, twin-orchestrator\n- Durable Objects: iw-agent-runtime (TWIN_AGENT, TENANT_BRAIN); folder-watcher DO\n- Queues: connector-sync, pipeline, webhook-ingress\n- Service bindings documented: continuity, webhook-ingress, agent-registry, iw-agent-runtime, gateway, connector\n- Secret store references: SUPABASE_URL in act, gove, tenants, billing, store; DATABASE_URL in admin; Secrets in mcp-connector and webhooks\n\nThese are runtime evidence of deployment configuration, not proof of active operational traffic.\n\n---\n\n## 4. DEPLOYED RUNTIME CLASSIFICATION\n\n| Worker Name       | Documented Classification            | Notes                                                                 |\n| ----------------- | ------------------------------------ | --------------------------------------------------------------------- |\n| gateway           | TARGET_RUNTIME                       | canonical ingress                                                     |\n| pipeline          | HISTORICAL_ACTIVE/TARGET             | actively deployed; legacy writer semantics may remain                 |\n| intelligence      | HISTORICAL_ACTIVE/TARGET             | active runtime; may have cognitive primitives already consolidated    |\n| iw-agent-runtime  | CURRENT/TARGET                       | active Twin runtime documented                                        |\n| mcp-connector     | CURRENT/TARGET                       | active MCP route documented                                           |\n| twin-orchestrator | CURRENT/TARGET or HISTORICAL_DORMANT | active cron route/call surface; migrations may shift responsibilities |\n| continuity        | CURRENT/TARGET                       | documented; routing evidence not explicitly surfaced here             |\n| hermes            | CURRENT/TARGET                       | documented                                                            |\n| knowledge         | CURRENT/TARGET                       | documented                                                            |\n| workflow          | CURRENT/TARGET                       | documented                                                            |\n| webhook-ingress   | CURRENT/TARGET                       | documented bindings                                                   |\n| normalizer        | CURRENT/TARGET                       | documented                                                            |\n| loader            | CURRENT/TARGET                       | documented                                                            |\n| admin             | CURRENT/TARGET                       | documented                                                            |\n| tenants           | CURRENT/TARGET                       | documented; still references SUPABASE_URL                             |\n| billing           | CURRENT/TARGET                       | documented; still references SUPABASE_URL                             |\n| govern            | HISTORICAL_ACTIVE/DORMANT/MIGRATING? | present; named differently than governance target                     |\n| act               | HISTORICAL_ACTIVE/DORMANT/MIGRATING? | present; may be retired; retires tech secret present                  |\n| think             | HISTORICAL_ACTIVE/DORMANT/MIGRATING? | present; no further runtime evidence here                             |\n| signals           | UNKNOWN                              | present; no opinion yet                                               |\n| l2                | UNKNOWN                              | present; no opinion yet                                               |\n| store             | CURRENT/HISTORICAL_ACTIVE            | still referencing SUPABASE_URL secret                                 |\n| telemetry         | CURRENT/TARGET                       | documented                                                            |\n| agent-registry    | HISTORICAL_ACTIVE/DORMANT/MIGRATING? | documented with pipeline binding                                      |\n| folder-watcher    | HISTORICAL_ACTIVE/DORMANT            | documented                                                            |\n| connector         | CURRENT/TARGET                       | documented; option-b attempted decoupled routing                      |\n\nThis table is conservative. Do not claim any current runtime is fully verified operational without end-to-end playback or traffic evidence.\n\n---\n\n## 5. CLOUDFLARE ACCOUNT CLAIMS\n\nReports indicate roughly 98 total deployed Workers exist across the Cloudflare account. The exact classification, canonical/runtime mapping, routing, and activation state are unknown in this document. A deduction beyond repository evidence would be unsupported.\n\nRecommended next evidence:\n\n- current Cloudflare account worker listing\n- current route/binding audit\n- traffic review\n- queue consumer review\n- durable object active provenance\n\n---\n\n## 6. DEPLOYMENT STATE SUMMARY\n\n- 27 repo-discovered workers deployed during July 2026 deployment session is a reported historical claim; evidence here documents configuration artifacts only.\n- Deployment success for those Worker sources is possible and supported by manifest presence, but not proven operational end-to-end through this document alone.\n- Current canonical runtime topology is MIGRATING at best.\n- Customer Zero runtime verification remains closed.\n\nDo not claim platform activation completion from deployment evidence alone.\n\n---\n\n## 7. DOCUMENTS THAT PRECEDE THIS\n\n- docs/operations/CF_WIRE_STATUS.md\n- docs/operations/ENDPOINT_MAP.md\n- docs/operations/DEPLOYMENT_RUNBOOK.md\n- docs/internal/runbooks/deployment-and-rollback.md\n- docs/archive/DEPLOYMENT_ANALYSIS_FULL.md\n- docs/archive/DEPLOYMENT_CLOUDFLARE.md\n- docs/archive/DEPLOYMENT_FIX.md\n- docs/archive/DEPLOYMENT_READY.md\n- docs/archive/DEPLOYMENT_STATUS.md\n- docs/archive/DEPLOYMENT_SUMMARY.md\n- docs/archive/VERCEL_DEPLOYMENT_STATUS.md\n- docs/internal/status/TWIN_DEPLOYMENT_STATUS.md\n- docs/internal/status/TWIN_ORCHESTRATOR_DEPLOYMENT.md\n- docs/internal/status/TWIN_AGENT_DEPLOYMENT_PLAN.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}