> ## Documentation Index > Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt > Use this file to discover all available pages before exploring further. # SpineWorkspace Product Topology: Five Layers > The topology of SpineWorkspace as an IntegrateWise product: five layers from human and AI workbench surfaces down through the Spine Agent Network, Spine. SpineWorkspace is not a single application. It is a vertically integrated system with five distinct layers, each with its own responsibilities, contracts, and interfaces. Understanding this topology is essential for internal teams because it defines ownership boundaries, communication patterns, and the flow of every request from a human click or agent trigger to a source-system write. The topology reinforces the IntegrateWise brand architecture: SpineWorkspace is the product, Spine Fabric is the contextual moat, and the Spine Agent Network is the cognitive ESB that makes both surfaces and automation intelligent. ## The Five Layers The surfaces where users interact with SpineWorkspace. The Human Workbench provides entity pages, timelines, and action panels for operators and analysts. The AI Workbench provides conversational and assisted interfaces for querying, steering, and delegating work to Twin and agents. Both benches consume assembled context from Spine Fabric through the same projection surface. The cognitive ESB layered on top of Spine Fabric. It provides context-aware routing so tasks reach the right agent or capability, capability discovery so agents know what tools are available, governed handoff so work passes between agents cleanly, and continuity so sessions and workflows retain state across steps. The network consumes assembled context from the fabric and routes outcomes back through the fabric. The contextual layer and IntegrateWise moat. It holds canonical entities, ordered events, evidence, and organizational memory. It ingests from connectors, resolves identity, assembles context on demand, and projects into domain views. The fabric is the shared substrate: every layer above it reads from and writes into the same live picture. The read and write surface to external systems. Connectors ingest data into Spine Fabric. Capabilities execute actions against source systems on behalf of the Spine Agent Network. This layer translates between Spine's canonical model and the formats, protocols, and constraints of each external system. The external systems of record: CRM, support platforms, documentation repositories, email and communication tools, billing systems, and any other system that holds or receives business data. These systems are not replaced by SpineWorkspace. They are integrated, unified, and acted upon through the layers above. ## How Each Layer Talks to the Next Communication flows strictly through adjacent layers. No layer skips its neighbor. | Direction | Flow | What Travels | | --------- | --------------------------- | ----------------------------------------------------------- | | Downward | Workbench → Agent Network | User intent, queries, commands, delegations | | Downward | Agent Network → Fabric | Context requests, agent action receipts, memory writes | | Downward | Fabric → Connectors | Read requests, sync triggers, capability execution commands | | Downward | Connectors → Source Systems | API calls, queries, writes, updates | | Upward | Source Systems → Connectors | Records, events, responses, status | | Upward | Connectors → Fabric | Normalized entities, events, evidence, confirmations | | Upward | Fabric → Agent Network | Assembled context, state updates, memory | | Upward | Agent Network → Workbench | Results, suggestions, status, continuations | This bidirectional stack ensures that the Human Workbench and AI Workbench never speak directly to a source system. They speak to the Spine Agent Network, which consults Spine Fabric, which reaches through connectors. The abstraction is what makes the product maintainable and what makes the fabric authoritative. ## The Role of the Cognitive ESB The Spine Agent Network sits at the critical intersection between the user-facing workbenches and the authoritative fabric. As a cognitive ESB, it does more than route messages. It understands the context of a request because it reads from Spine Fabric. It discovers which agent or capability can fulfill a request because it maintains capability metadata. It governs handoffs because it records receipts into fabric memory. And it ensures continuity because each step inherits the assembled context and receipts of the steps before. Without the Spine Agent Network, the workbenches would be dashboards and the fabric would be a data store. With the network, they become an intelligent operating system for business operations. ## Related * [Product Definition](/internal-docs/product/product-definition) * [User Path](/internal-docs/two-paths/user-path) * [System Path](/internal-docs/two-paths/system-path) * [Spine Fabric Overview](/internal-docs/spine-fabric/overview) * [Contextual Twin](/how-it-works/contextual-twin)