{"slug":"architecture/ARCHITECTURE_END_STATE","title":"End-State Architecture","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/ARCHITECTURE_END_STATE.mdx","bytes":16085,"description":"The complete SpineWorkspace architecture — one workspace, all connected software, shared context, human + AI working together","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n**One Workspace. All Connected Software. Shared Context. Human + AI Working Together.**\n\n\nThis is the canonical end-to-end architecture reference. Every other architecture doc is a deep-dive into one section of this page.\n\n\n## The Flow\n\nEvery piece of work in SpineWorkspace follows one continuous loop:\n\n```\nBusiness Context → Work → Communication → Decisions → Execution → Reconciliation → Memory → Next Work\n```\n\nNothing is isolated. Every action feeds back into organizational memory. Every decision is traceable. Every outcome creates the context for the next cycle.\n\n---\n\n## Architecture Layers\n\nThe architecture is composed of 10 interconnected layers, organized into three horizontal bands:\n\n### Top Band — User Surfaces\n\n| Layer | Purpose | Docs |\n|-------|---------|------|\n| **Users & Roles** | Who uses the system | [Roles & Agents](/architecture/ROLES_AND_AGENTS) |\n| **Human Workbench** | One workspace for all human work | [Human Workbench](/architecture/HUMAN_WORKBENCH) |\n| **Communications Layer** | All conversations in one place | [Communications](/architecture/COMMUNICATIONS_LAYER) |\n| **Twin Workbench** | AI workspace for reasoning, planning and execution | [Twin Workbench](/architecture/TWIN_WORKBENCH) |\n\n### Middle Band — Platform Core\n\n| Layer | Purpose | Docs |\n|-------|---------|------|\n| **Source Systems** | External applications and tools | [Bridge Layer](/architecture/BRIDGE_LAYER) |\n| **Bridge Layer** | Connectivity and integration | [Bridge Layer](/architecture/BRIDGE_LAYER) |\n| **Spine Fabric** | Canonical business memory and operational continuity | [Spine Schema](/architecture/SPINE_SCHEMA) |\n| **ADX Orchestrator** | Agent runtime and orchestration | [ADX Orchestrator](/architecture/ADX_ORCHESTRATOR) |\n| **Governance Layer** | Policy, authorization, approval | [Governance](/architecture/GOVERNANCE) |\n| **Execution Fabric** | How work gets done | [Execution Fabric](/architecture/EXECUTION_FABRIC_v2) |\n| **Target Systems** | External systems being acted upon | [Bridge Layer](/architecture/BRIDGE_LAYER) |\n\n### Bottom Band — Continuity\n\n| Layer | Purpose | Docs |\n|-------|---------|------|\n| **Reconciliation & Continuity Pipeline** | Closes the loop on every action | [Reconciliation Pipeline](/architecture/RECONCILIATION_PIPELINE) |\n| **Data Governance & Security** | Cross-cutting concerns across all stores | [Data Governance](/architecture/DATA_GOVERNANCE_SECURITY) |\n\n---\n\n## Users & Roles\n\nSpineWorkspace serves every role in the organization. Each role gets a domain-specific projection of the workbench.\n\n### Human Roles\n\n| Role | Primary Focus |\n|------|---------------|\n| Executive Leader | Strategic KPIs, organizational health, decisions |\n| Sales Manager | Pipeline, opportunities, forecasts |\n| Account Manager | Customer health, renewals, expansion |\n| Finance Analyst | Revenue, billing, collections |\n| Support Lead | Tickets, SLAs, escalations |\n| Any Role / Customer | Role-specific work surfaces |\n\n### AI Agents\n\n| Agent Type | Scope | Behavior |\n|------------|-------|----------|\n| **AI Twin** | Per-user, role-scoped | Reasons, plans, suggests — never acts without approval |\n| **AI Coworker** | Context companion | Observes active work, gathers context, supports communication |\n| **Domain Agents** | Sales, Finance, Support... | Specialized reasoning within a business domain |\n| **Specialist Agents** | Research, Analysis... | Deep-dive capabilities triggered on demand |\n| **System Agents** | Platform Services | Infrastructure, scheduling, monitoring |\n\nSee [Roles & Agents](/architecture/ROLES_AND_AGENTS) for full definitions.\n\n---\n\n## Human Workbench\n\n**One Workspace for All Human Work.**\n\nThe Human Workbench is the single surface where every person does their job. No context switching. No app juggling.\n\n### Navigation\n\n| Section | Purpose |\n|---------|---------|\n| **My Work** | Personal work items and priorities |\n| **My Queue** | Ordered work waiting for attention |\n| **Today** | Today's focus and timeline |\n| **Alerts** | Notifications requiring attention |\n| **Approvals** | Items awaiting human approval |\n| **Decisions** | Decisions requiring human judgment |\n| **Reports & KPIs** | Analytics and performance metrics |\n| **Settings** | Configuration and preferences |\n\n### Work Surface Tabs\n\n| Tab | Purpose |\n|-----|---------|\n| **Orientation** | Context and situational awareness |\n| **Work** | Active work items and tasks |\n| **Communications** | All conversations and messages |\n| **Organizations** | Company and relationship context |\n| **Knowledge / Memory** | Organizational knowledge base |\n| **Domain Work Surfaces** | Role-specific deep-dive views |\n\n### Domain Work Surfaces\n\nEach role gets a tailored view of the work surface:\n\n| Domain | Focus |\n|--------|-------|\n| **Sales** | Pipeline, Opportunities, Forecasts |\n| **Account Success** | Health, Renewals, Expansion |\n| **Finance** | Revenue, Billing, Collections |\n| **Support** | Tickets, SLAs, Escalations |\n| **Operations** | Projects, Tasks, Workflows |\n| **Custom Views** | Role / Domain Specific Projections |\n\n### Business KPI / Health Overview\n\nThe workbench surface key metrics at a glance:\n\n| Metric | Value | Trend |\n|--------|-------|-------|\n| Revenue | $8.4M | +12% |\n| Pipeline | $27.6M | +8% |\n| Revenue at Risk | $1.2M | +15% |\n| Customer Health | 76 | +4 pts |\n| Open Work | 128 | +2 |\n| SLA Risk | 5 | View all KPIs → |\n\nSee [Human Workbench](/architecture/HUMAN_WORKBENCH) for complete specification.\n\n---\n\n## Twin Workbench\n\n**AI Workspace for Reasoning, Planning and Execution.**\n\nThe Twin Workbench is the AI counterpart to the Human Workbench. It reasons about work, proposes actions, and executes under governance.\n\n### Tabs\n\n| Tab | Purpose |\n|-----|---------|\n| **My Twin View** | Twin's current understanding and state |\n| **Active Work** | Work items the Twin is reasoning about |\n| **Reasoning & Plan** | The Twin's analysis and proposed plan |\n| **Tools & Capabilities** | Available AI tools and integrations |\n| **Memory** | What the Twin knows and remembers |\n\n### Context & Understanding\n\nThe Twin maintains a continuous understanding of the current situation:\n\n- **Current State** — What is happening right now\n- **Relevant Context** — Related information from the Spine\n- **Evidence** — Data supporting or contradicting actions\n- **Related Work** — Connected work items and dependencies\n- **Risks & Drivers** — What could go wrong, what matters most\n\n### Suggested Actions (OODA Grammar)\n\nThe Twin follows the OODA loop for every work item:\n\n1. **Understand Context** → Orient to the situation\n2. **Collect Evidence** → Gather supporting data\n3. **Analyze** → Reason about options\n4. **Recommend** → Propose a course of action\n5. **Plan** → Detail the execution steps\n6. **Awaiting Approval** → Human decides\n7. **Execute** → Act on the approved plan\n8. **Reconcile** → Verify the outcome\n9. **Complete** → Close the loop\n\n### AI Tools & Capabilities\n\n| Tool | Purpose |\n|------|---------|\n| **Research** | Deep investigation and information gathering |\n| **Data Analysis** | Quantitative analysis and pattern detection |\n| **Prediction** | Forecasting and trend analysis |\n| **Drafting** | Content creation and communication |\n| **Workflow** | Automated process execution |\n| **Automation** | Rule-based task completion |\n| **Integration** | External system interaction |\n\n### Coworker (Context Companion)\n\nThe Coworker is a lighter-weight AI participant that:\n\n- **Observes** active work without interfering\n- **Gathers** relevant context from the Spine\n- **Retrieves** information on demand\n- **Supports** communication between humans and the Twin\n\n**Focus Areas:** Active Work Context, Relevant Information, Communication Support, Context Alignment.\n\nSee [Twin Workbench](/architecture/TWIN_WORKBENCH) for complete specification.\n\n---\n\n## Communications Layer\n\n**All Conversations in One Place.**\n\nThe Communications Layer unifies every channel of communication into a single surface:\n\n| Channel | Description |\n|---------|-------------|\n| **Team Chat** | Internal team messaging |\n| **Customer Communications** | External customer-facing messages |\n| **Internal Updates** | Status updates and announcements |\n| **Email** | Email integration and management |\n| **Meetings** | Meeting notes, action items, follow-ups |\n| **Announcements** | Organization-wide communications |\n| **AI / Human Hand-offs** | Transitions between AI and human actors |\n\nThe Communications Layer feeds directly into the Spine as events and evidence. Every communication is searchable, traceable, and linked to the work it relates to.\n\nSee [Communications Layer](/architecture/COMMUNICATIONS_LAYER) for complete specification.\n\n---\n\n## Spine Fabric\n\n**Canonical Business Memory & Operational Continuity.**\n\nThe Spine Fabric is the heart of SpineWorkspace — the single source of truth that all other layers read from and write to.\n\n### Core Domains\n\n| Domain | Purpose |\n|--------|---------|\n| **Business Context** | Goals, Objectives, Needs, Standards |\n| **Work Graph** | Work, Tasks, Activities, Dependencies |\n| **Entities** | Accounts, People, Products, Assets... |\n| **Events & Evidence** | Activities, Changes, Interactions, Signals |\n| **Decisions** | Choices, Rationales, Approvals |\n| **State & Status** | Current, History, Attribution |\n| **Provenance** | Source, Time, Attribution |\n| **Organizational Memory** | Knowledge, Insights, Learnings |\n\n### Spine Stores\n\nThe Spine operates across three storage tiers, each with distinct governance:\n\n| Store | Technology | Contents |\n|-------|-----------|----------|\n| **Canonical Spine** | Neon / Postgres | Authoritative truth, long-term memory, governed writes |\n| **Operational Spine / Context Store** | D1 / Durable Objects / Cache | Working context, real-time state, short-term working sets |\n| **Edge / Session State** | Workers / Cache | Ephemeral state, per-session / per-device, fast access |\n\nSee [Spine Schema](/architecture/SPINE_SCHEMA) for complete data model.\n\n---\n\n## Bridge Layer\n\n**Connectivity & Integration.**\n\nThe Bridge Layer connects SpineWorkspace to every external system:\n\n### Source Systems\n\nSalesforce, HubSpot, Dynamics 365, NetSuite, QuickBooks, ServiceNow, Zendesk, Slack / Teams, Google Workspace, Microsoft 365, Databases / APIs, Files / Events / Webhooks, Any System.\n\n### Bridge Components\n\n| Component | Purpose |\n|-----------|---------|\n| **Connectors** | Pre-built system integrations |\n| **Adapters** | Protocol and format translation |\n| **APIs** | Direct API connections |\n| **Webhooks** | Event-driven ingestion |\n| **Event Streaming** | Real-time data feeds |\n| **File / DB Sync** | Batch and incremental synchronization |\n| **Transformers** | Data normalization and enrichment |\n| **Protocol Handlers** | Protocol-specific implementations |\n\n### Target Systems\n\nThe same systems listed as sources can also be targets — the Bridge Layer is bidirectional.\n\nSee [Bridge Layer](/architecture/BRIDGE_LAYER) for complete specification.\n\n---\n\n## ADX Orchestrator & Agent Runtime\n\n**Orchestration Engine + Agent Runtime + Workflow Engine.**\n\nThe ADX Orchestrator is the brain that coordinates all agent activity:\n\n| Component | Purpose |\n|-----------|---------|\n| **Orchestration Engine** | Coordinates multi-step agent workflows |\n| **Agent Runtime** | Executes individual agent actions |\n| **Workflow Engine** | Manages complex business processes |\n| **Task Decomposition** | Breaks work into executable units |\n| **Context Assembly** | Builds the context window for agents |\n| **Agent Hand-off (A2CP)** | Transfers work between agents |\n| **State Management** | Tracks workflow and agent state |\n| **Scheduling** | Time-based and event-based triggers |\n| **Retries** | Automatic retry on failure |\n| **Monitoring** | Observability and alerting |\n\nSee [ADX Orchestrator](/architecture/ADX_ORCHESTRATOR) for complete specification.\n\n---\n\n## Governance Layer\n\n**May This Be Done?**\n\nThe Governance Layer is a hard gate between intent and execution. Nothing executes without passing through governance.\n\n| Component | Purpose |\n|-----------|---------|\n| **Policy Evaluation** | Checks against organizational policies |\n| **Authorization** | Verifies permissions and roles |\n| **Approval Workflow** | Routes to human approvers when required |\n| **Limits & Guardrails** | Enforces spending, rate, and scope limits |\n| **Risk & Compliance** | Assesses risk and compliance requirements |\n| **Audit & Accountability** | Records who did what, when, and why |\n\n### Governance Rules\n\n- No execution token = no execution\n- Every action is auditable\n- Human approval required for high-risk actions\n- Twin never acts without explicit approval\n\nSee [Governance](/architecture/GOVERNANCE) for complete specification.\n\n---\n\n## Execution Fabric\n\n**How It Gets Done.**\n\nThe Execution Fabric is the set of capabilities that actually perform work:\n\n| Component | Purpose |\n|-----------|---------|\n| **APIs & Services** | Direct API calls to external systems |\n| **MCP / Tools** | Model Context Protocol tool invocations |\n| **Workflows** | Multi-step process execution |\n| **Hermes** | Execution service for complex actions |\n| **Functions / Workers** | Serverless compute execution |\n| **External Integrations** | Third-party service calls |\n\nSee [Execution Fabric](/architecture/EXECUTION_FABRIC_v2) for complete specification.\n\n---\n\n## Reconciliation & Continuity Pipeline\n\n**Closes the Loop on Every Action.**\n\nThe Reconciliation Pipeline ensures every action is verified and feeds back into memory:\n\n```\nExecution Receipt → Re-ingestion → Normalization & Entity Resolution → State Update → Reconciliation → Discrepancy Handling → Memory Promotion → Next Work\n```\n\n| Step | Purpose |\n|------|---------|\n| **Execution Receipt** | Confirm Acknowledgement |\n| **Re-ingestion** | New Data / Events |\n| **Normalization & Entity Resolution** | Resolve entities across stores |\n| **State Update** | Spine Update |\n| **Reconciliation** | Intended vs. Actual |\n| **Discrepancy Handling** | Retry / Compensate |\n| **Memory Promotion** | Knowledge / Learning |\n| **Next Work** | Created / Updated |\n\n### Loop State (Stored in Spine)\n\nEvery work item progresses through these states:\n\n```\nIdentified → Contextualizing → Defined → Allocated → Deciding → Governing → Executing → Observing → Re-ingesting → Reconciling → Resolved → Learning → Continuing → Next Work\n```\n\nSee [Reconciliation Pipeline](/architecture/RECONCILIATION_PIPELINE) for complete specification.\n\n---\n\n## Data Governance & Security\n\n**Across All Spine Stores.**\n\nCross-cutting concerns that apply to every layer:\n\n| Concern | Scope |\n|---------|-------|\n| **Tenants** | Multi-tenant isolation |\n| **Identity** | Authentication and identity |\n| **Roles** | Role-based access control |\n| **Permissions** | Fine-grained permission model |\n| **Policies** | Organizational policy enforcement |\n| **Purpose** | Purpose limitation for data use |\n| **Consent** | Consent management |\n| **Data Classification** | Sensitivity and handling labels |\n| **Audit** | Immutable audit trail |\n| **Retention** | Data lifecycle management |\n\nSee [Data Governance & Security](/architecture/DATA_GOVERNANCE_SECURITY) for complete specification.\n\n---\n\n## Outcomes\n\nSpineWorkspace delivers:\n\n- **Faster execution** — Work moves from intent to outcome without friction\n- **Lower risk** — Every action is governed, audited, and reversible\n- **Higher quality decisions** — AI reasoning backed by complete context\n- **Audit ready** — Full traceability from decision to outcome\n- **Connected teams** — One surface, no silos, shared context\n- **Organizational intelligence** — Every cycle builds institutional knowledge\n"}