> ## 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.

# The System Path: From Event Intake to State Update

> Walk the System Path end to end: how SpineWorkspace processes intake, resolves identity, assembles context, routes decisions, executes capabilities, and.

The System Path is the complete operational pipeline through which SpineWorkspace processes external and internal events from the moment of intake to the moment of state update and continuation. It is the invisible machinery that turns a raw signal into a changed business reality. Every event, record, message, or agent action travels this path, and the path itself is what feeds Spine Fabric so that the Spine Agent Network can operate from a live, unified picture.

This page walks the full arc in stages, showing how each step contributes to the fabric and how the fabric, in turn, enables the next cycle.

## The Pipeline

<Steps>
  <Step title="Intake">
    Signals arrive through connectors: structured records from CRM or support platforms, unstructured emails and documents, AI-derived classifications and summaries, and explicit identity assertions. Everything enters through the ingestion surface of Spine Fabric.
  </Step>

  <Step title="Load">
    Raw payloads are normalized into the canonical model. Format differences, encoding quirks, and source-specific conventions are reconciled so that downstream stages see consistent representations regardless of origin.
  </Step>

  <Step title="Normalize">
    Semantic normalization ensures that similar concepts from different sources are treated uniformly. A "customer" in one system and an "account" in another are brought into the same conceptual frame without field-level mapping tables.
  </Step>

  <Step title="Resolve Identity">
    Duplicate and related records are linked to canonical entities. Identity resolution collapses fragments so that a single person, account, or contract exists as one coherent object in the fabric, even when source systems disagree on identifiers.
  </Step>

  <Step title="Thread Events">
    Normalized and resolved events are placed onto ordered timelines associated with their canonical entities. Events are threaded so that causality and sequence are preserved: what happened, to whom, and in what order.
  </Step>

  <Step title="Assemble Context">
    For any focus that requires action or review, the contextual layer produces a working picture. It gathers the focus entity, its neighbors, recent events, evidence, prior decisions, and relevant memory into a scoped, coherent view.
  </Step>

  <Step title="Project into Domains">
    The assembled context is tailored for the consuming surface. A support projection emphasizes ticket history and SLA posture. A finance projection emphasizes contract terms and billing status. The same fabric powers all views.
  </Step>

  <Step title="OODA">
    Observe, orient, decide, act. Twin and agents consume the projected context, assess the situation, select a course of action, and prepare to execute. The decision loop runs within the Spine Agent Network, drawing on the fabric for orientation.
  </Step>

  <Step title="Governance">
    Before any action is taken against a source system, policy checks are applied. Authorization boundaries, data handling rules, and business constraints are enforced here so that execution is always compliant.
  </Step>

  <Step title="Capability Execution">
    Approved actions are routed through the capability layer to the appropriate connector. Writes, updates, messages, and other side effects are executed against source systems, with the Spine Agent Network handling routing and handoff.
  </Step>

  <Step title="State Update">
    Outcomes from execution are reflected back into Spine Fabric. Canonical entities are updated, new events are recorded, and the fabric's picture of truth advances.
  </Step>

  <Step title="Receipt and Continuation">
    Agent actions and system writes generate receipts that enter memory. These receipts inform future context assembly, enable audit, and allow workflows to continue from known state rather than guessing.
  </Step>
</Steps>

## How the System Path Feeds the Fabric and Network

The System Path is not a one-way street. It is a loop.

<Note>
  Every completed cycle updates Spine Fabric, which updates the picture available to the Spine Agent Network, which enables the next cycle of context assembly, OODA, and execution.
</Note>

Intake loads data into the fabric. Resolution and event threading enrich the fabric's entity and event reservoirs. Assembly and projection consume the fabric to build working pictures. OODA and execution occur within the Spine Agent Network, which relies on those pictures. State update and receipt write outcomes back into the fabric, closing the loop.

This tight coupling between path, fabric, and network is why SpineWorkspace maintains coherent state across human and agent actions. The fabric is the shared substrate. The network is the cognitive EBS that moves work across agents. The System Path is the circulatory system that keeps both alive.

## Related

* [User Path](/internal-docs/two-paths/user-path)
* [Spine Fabric Overview](/internal-docs/spine-fabric/overview)
* [Contextual Layer](/internal-docs/spine-fabric/contextual-layer)
* [Product Topology](/internal-docs/product/product-topology)