{"slug":"business/CONTINUITY","title":"CONTINUITY","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/CONTINUITY.mdx","bytes":3869,"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: Continuity capability and L1 product expression\nCanonical Owner: Platform / Continuity\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/platform-specs/25-continuity-engine.md, docs/platform-specs/07-memory-system.md, docs/platform-specs/03-workspace-runtime.md, docs/internal/playbooks/tenant-onboarding-and-initial-hydration.md, docs/internal/operations/CUSTOMER_ZERO_FLOW_TEST.md, wrangler manifests, Option B divergence audit\nSupersedes: none\nSuperseded By: none\n\n---\n\n## 1. WHAT CONTINUITY IS\n\nContinuity is persistent operational context.\n\nIt is the platform capability that preserves state across time, actors, actions, and operational restarts.\n\n---\n\n## 2. MEMORY SCOPES\n\nContinuity memory operates at three scopes:\n\n- USER — per-person operational memory\n- WORK — per-entity or per-process operational memory\n- ORGANIZATION — tenant-wide operational memory\n\nContinuity permits:\n\n- workspace continuation\n- entity continuation\n- previous action awareness\n- unresolved work awareness\n- prior decision awareness\n- model/context continuation\n\n---\n\n## 3. CONTINUITY PLATFORM CAPABILITY\n\nContinuity is the platform behavior of:\n\n- persisting operational state\n- recovering prior context\n- maintaining unresolved work visibility\n- maintaining decision lineage\n- supporting model/context continuation\n\nRuntime identities that may participate in continuity include:\n\n- services/continuity\n- services/workflow\n- services/knowledge\n- services/hermes\n- services/iw-agent-runtime\n- Spine or supporting storage substrates\n\nEach must be classified individually.\n\n---\n\n## 4. CONTINUITY BRIDGE\n\nContinuity Bridge is a platform concept, not a product page or activity feed.\n\nThe platform concept is:\n\n```text\nOPERATIONAL REALITY\n      ↓\nCONTINUITY CAPTURE\n      ↓\nPERSISTED STATE\n      ↓\nCONTEXT RECOVERY\n      ↓\nNEXT OPERATOR/ACTOR CONTEXT\n```\n\nThis is true regardless of whether a UI styling pattern uses the word \"bridge\".\n\n---\n\n## 5. L1 CONTINUITY PRODUCT EXPRESSION\n\nContinuity product expression should not imply that Continuity is a page or screen.\n\nContinuity expression in L1 may include:\n\n- activity history\n- previous action markers\n- unresolved state indicators\n- recent change markers\n- approval history\n- execution history\n- continuation affordances\n\nEach is a projection of persisted platform continuity state.\n\nThe product does not create continuity. The product reflects continuity.\n\n---\n\n## 6. CURRENT VERIFICATION STATE\n\nDocumentation must not treat boot-level hydration or onboarding completion as continuity continuity confirmational proof.\n\nCurrent runtime evidence for continuity product optimization:\n\n- services/continuity wrangler manifest present\n- docs/internal/playbooks/tenant-onboarding-and-initial-hydration.md present as active operational reference\n- docs/internal/operations/CUSTOMER_ZERO_FLOW_TEST.md present but likely frontend state trace\n- Documentation style Continuity Bridge references may reflect UI naming, not platform state\n\nClassification:\n\n- Platform continuity lifecycle: CURRENT\n- Product expression lifecycle: CURRENT\n- Verified E2E continuity: UNKNOWN until tenant state hydration readback is traced\n- Next required evidence: tenant onboarding flow readback, persisted recovery replay test\n\n---\n\n## 7. DOCUMENTS THAT PRECEDE THIS\n\n- docs/platform-specs/25-continuity-engine.md\n- docs/platform-specs/07-memory-system.md\n- docs/platform-specs/03-workspace-runtime.md\n- docs/archive/CONTINUITY_BRIDGE_COMPLETE.md\n- docs/archive/CONTINUITY_BRIDGE_SIMPLE.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}