Skip to main content
Spine Fabric is the heart of IntegrateWise’s moat. It is the shared contextual layer beneath SpineWorkspace where humans, the Contextual Twin, and every agent in the Spine Agent Network operate from the same live business picture. The fabric does not merely store data: it continuously ingests, resolves, assembles, and projects context so that every surface sees the same truth at the same time. Understanding the fabric is essential for anyone building on or supporting SpineWorkspace. This page covers what the fabric holds at a conceptual level, what it does, its five capability surfaces, and how it relates to the Spine Agent Network layered on top.

​
What the Fabric Holds

The fabric maintains four conceptual reservoirs that together form the single source of business truth.

Entities

Canonical representations of business objects: accounts, contacts, contracts, tickets, and any object modeled across connected systems. Each entity persists as a resolved, deduplicated record regardless of how many sources claim it.

Events

The ordered, append-only stream of meaningful changes: status transitions, communications, decisions, and system updates. Events thread discrete moments into coherent narratives that the fabric can recall on demand.

Evidence

Communications, documents, call transcripts, and other artifacts attached to entities and events. Evidence is the raw material that agents and Twin reason over when interpreting state or recommending action.

Memory

Durable organizational knowledge: prior decisions, outcomes, agent receipts, and learned patterns that persist beyond any single session or workflow. Memory prevents the organization from relearning what it already decided.
These four reservoirs are not silos. They are cross-referenced so that an entity carries its events, its evidence, and its memory as a unified whole whenever something asks about it.

​
What the Fabric Does

The fabric performs five continuous functions that turn raw intake into actionable context.
  1. Ingest from connectors. The fabric receives structured records, unstructured messages, and AI-derived signals through the connector layer, normalizing them into the canonical model regardless of source format.
  2. Resolve identity. Duplicate records across systems are recognized, linked, and collapsed into canonical entities so that no person or account exists in fragments.
  3. Unify context. Relationships, timelines, and overlays are woven together so that related objects travel as a coherent set.
  4. Assemble on demand. When a focus is selected, an agent is invoked, or a workflow advances, the fabric produces a fresh working picture drawn from entities, events, evidence, and memory.
  5. Project into domains. The same unified context is rendered into domain-specific views for support, sales, finance, or any workspace surface without duplicating storage.

​
The Five Capability Surfaces

Think of the fabric as exposing five surfaces that internal teams build against and operate.

Ingestion

The intake surface that accepts records, messages, and signals from every connector. Handles normalization, validation, and routing into the canonical stream.

Resolution

The identity surface that deduplicates and links records. Ensures that one real-world object maps to one canonical entity, even when sources disagree.

Assembly

The context surface that composes working pictures. Given a focus and a scope, it gathers neighbors, events, evidence, and memory into a single deliverable view.

Projection

The rendering surface that tailors assembled context for specific domains or surfaces. A support view and a finance view can read the same fabric and see different projections.

Memory

The persistence surface that records decisions, receipts, and learned outcomes so that workflows, agents, and Twin retain continuity across sessions.

​
Spine Fabric and the Spine Agent Network

The fabric is the shared substrate, but it is not the routing layer. The Spine Agent Network sits on top of the fabric and functions as the cognitive ESB (enterprise service bus) for SpineWorkspace.
Fabric provides the live business picture. Network decides who sees it, who acts on it, and how work continues.
The fabric holds the state. The network provides context-aware routing, capability discovery, governed handoff, and continuity across every agent and tool. When an agent needs to act, the network queries the fabric for assembled context, then routes the action to the right capability and records the receipt back into the fabric. The two layers are inseparable: the network is useless without the fabric’s picture, and the fabric’s picture is inert without the network’s orchestration.