{"slug":"architecture/RUNTIME_TOPOLOGY","title":"RUNTIME TOPOLOGY","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/RUNTIME_TOPOLOGY.mdx","bytes":12960,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CURRENT\nScope: Current and target runtime identities, app/package service boundaries, cloudflare worker boundaries\nCanonical Owner: Platform\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/FINAL_E2E_SYSTEM.md, docs/platform-specs/15-deployment-architecture.md, docs/operations/ENDPOINT_MAP.md, Option B branch divergence audit, wrangler manifests across services/ and packages/\nSupersedes: none\nSuperseded By: none\n\n---\n\n## 1. RUNTIME TOPOLOGY REALISM\n\n```text\nSERVICE FOLDER\n≠\nCANONICAL SERVICE\n≠\nDEPLOYED WORKER\n≠\nACTIVE RUNTIME\n```\n\nDocumentation must never conflate these four concepts.\n\n- Service folder: repository artifact indicating intended implementation boundary\n- Canonical service: approved target runtime identity\n- Deployed Worker: manifest identity with deployed Cloudflare evidence\n- Active runtime: manifest, routing, binding, triggers, observability, and runtime traffic evidence combined\n\nPresence in the repository is evidence only. Deployment, routing, binding, and traffic evidence are required before CURRENT classification.\n\n---\n\n## 2. CURRENT REPOSITORY RUNTIME IDENTITIES\n\nFrom wrangler manifests in current branch, runtime identities observed:\n\n| Folder | Worker Name | Has Route | Has Service Bindings | Has Durable Objects | Queues | Has Secrets | Observed Retired-Tech Secrets |\n| ----------------------------------------- | ----------------------------- | --------------------------------- | -------------------- | ------------------- | ------ | ----------- | ----------------------------- |\n| services/act | integratewise-act | no | no | no | no | yes | SUPABASE_URL |\n| services/admin | integratewise-admin | no | no | no | no | yes | DATABASE_URL |\n| services/agent-registry | integratewise-agent-registry | no | no | no | no | no | no |\n| services/billing | integratewise-billing | no | no | no | no | yes | SUPABASE_URL |\n| services/connector | connector | ves | yes | no | yes | no | no |\n| services/connector-sync | integratewise-connector-sync | no | yes | no | yes | no | no |\n| services/continuity | continuity | no | yes | no | no | no | no |\n| services/folder-watcher | integratewise-folder-watcher | no | no | yes | no | no | no |\n| services/gateway | gateway | gateway.dev.integratewise.ai | yes | no | no | no | no |\n| services/govern | integratewise-govern | no | no | no | no | yes | SUPABASE_URL |\n| services/hermes | integratewise-hermes | no | no | no | no | no | no |\n| services/intelligence | intelligence | intelligence.dev.integratewise.ai | yes | no | no | no | no |\n| services/iw-agent-runtime | iw-agent-runtime | no | yes | yes | no | no | no |\n| services/knowledge | knowledge | no | no | no | no | no | no |\n| services/l2 | l2 | no | no | no | no | no | no |\n| services/loader | integratewise-loader | no | no | no | no | no | no |\n| services/mcp-connector | integratewise-mcp-connector | mcp.integratewise.ai | yes | no | no | yes | no |\n| services/normalizer | integratewise-normalizer | no | no | no | no | no | no |\n| services/pipeline | integratewise-pipeline | pipeline.dev.integratewise.ai | no | no | no | no | no |\n| services/signals | integratewise-signals | no | no | no | no | no | no |\n| services/store | integratewise-store | no | no | no | no | yes | SUPABASE_URL |\n| services/telemetry | integratewise-telemetry | no | no | no | no | no | no |\n| services/tenants | integratewise-tenants | no | no | no | no | yes | SUPABASE_URL |\n| services/think | integratewise-think | no | no | no | no | no | no |\n| services/twin-orchestrator | twin-orchestrator | twin.dev.integratewise.ai | no | no | no | no | no |\n| services/webhook-ingress | integratewise-webhook-ingress | no | yes | no | no | no | no |\n| services/workflow | workflow | no | no | no | no | no | no |\n| packages/api | hub-controller-api | no | no | no | no | no | no |\n| packages/integratewise-mcp-tool-connector | integratewise-mcp-connector | no | no | no | no | yes | no |\n| packages/webhooks | integratewise-webhooks | no | no | no | no | no | no |\n\n---\n\n## 3. TARGET RUNTIME TOPOLOGY\n\nCanonical target topology expected:\n\n| Target Identity | Repository Evidence | Status |\n| --------------------- | -------------------- | ---------------- |\n| gateway | YES | CURRENT/TARGET |\n| loader | YES | CURRENT/TARGET |\n| normalizer | YES | CURRENT |\n| spine-writer | NO | TARGET/UNKNOWN |\n| schema-synthesis | UNKNOWN | UNKNOWN |\n| continuity | YES | CURRENT |\n| governance | NO, govern exists | TARGET/MIGRATING |\n| hermes | YES, runtime present | CURRENT |\n| knowledge | YES | CURRENT |\n| store | YES | CURRENT |\n| workflow | YES | CURRENT |\n| webhook-ingress | YES | CURRENT |\n| mcp-connector | YES | CURRENT |\n| telemetry | YES | CURRENT |\n| huggingface-inference | UNKNOWN | TARGET/UNKNOWN |\n| admin | YES | CURRENT |\n| tenants | YES | CURRENT |\n| billing | YES | CURRENT |\n\n---\n\n## 4. CURRENT ROUTING AND SERVICE BINDING EVIDENCE\n\nOption B Wave 0 evidence records intended bindings:\n\n- gateway WANTS: ADMIN, BILLING, TENANTS\n- connector WANTS: LOADER, MCP, STORE\n\nThese are not yet canonical branched. Cherry-pick/approval status:\n\n- Approved for canonical branch: NO\n- Approved for worktree: evidence supported\n- Applied in runtime manifests on current branch: evidence-supported divergence audit only\n\nCurrent documented routing traffic evidence is UNKNOWN until Cloudflare runtime review\n\n---\n\n## 5. DEPLOYED VS. ACTIVE CLASSIFICATION\n\nClassification guidance:\n\n| Classification | Meaning |\n| ------------------ | ----------------------------------------------------------------------------------------- |\n| TARGET_RUNTIME | Approved target service identity not yet proven deployed from current branch manifests |\n| HISTORICAL_ACTIVE | Existing router with retained runtime and traffic surface; no longer canonical |\n| HISTORICAL_DORMANT | Existing router with manifest but no observed/traffic evidence supporting operational use |\n| DUPLICATE_RUNTIME | Multiple runtime identities intended for same url/role |\n| UNKNOWN | Insufficient evidence to classify |\n\nA large Cloudflare account reportedly contains about 98 deployed workers. Exact runtime classification cannot be made here without runtime inventory evidence, and must be treated as UNKNOWN.\n\n---\n\n## 6. APPS AND PACKAGE RUNTIME BOUNDARIES\n\nRuntime app boundaries:\n\n| App | Evidence | Target Role | Notes |\n| -------------- | ---------------------------------------------- | ------------------------ | -------------------------------------------------------------- |\n| apps/web | Present; docs target this as Vite/React target | TARGET | verify host/runtime assumptions |\n| apps/workspace | Present | CURRENT/CURRENT_EVIDENCE | may hold corpus evidence; not canonical target unless verified |\n| apps/desktop | Present; wrapper | HISTORICAL | desktop wrapper only |\n| apps/mobile | Present; placeholder | HISTORICAL | placeholder only |\n| apps/docs | Present | UNKNOWN | docs-only app mission |\n\nPackage boundary documentation requires separate verification of publish boundaries, module exports, and cross-package invocation. Backup packages such as packages/config-backup-_, packages/lib-backup-_, packages/types-backup-\\* must be classified strictly and not left alive as duplicate sources of truth.\n\n---\n\n## 7. DOCUMENTS THAT PRECEDE THIS\n\n- docs/platform-specs/15-deployment-architecture.md\n- docs/operations/CF_WIRE_STATUS.md\n- docs/operations/ENDPOINT_MAP.md\n- docs/internal/operations/OPERATIONAL_STATE.md\n- OPTION_B_BRANCH_DIVERGENCE_AUDIT.md\n- OPTION_B_WAVE0_LOG.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}