02 · Spine Fabric

The central fabric. Not merely a database.

Spine Fabric is the single source of truth that all other layers read from and write to. It maintains canonical business memory and operational continuity. It is what makes the loop continuous rather than episodic.

                    SPINE FABRIC


 ┌────────────────────────────────────────────────────┐
 │                                                    │
 │                 BUSINESS CONTEXT                   │
 │                                                    │
 │ Goals          Needs           Objectives          │
 │ Entities       Relationships   Organizations       │
 │ People         Accounts        Products            │
 │                                                    │
 ├────────────────────────────────────────────────────┤
 │                                                    │
 │                    WORK GRAPH                      │
 │                                                    │
 │ Work → Tasks → Decisions → Actions → Dependencies │
 │                                                    │
 ├────────────────────────────────────────────────────┤
 │                                                    │
 │                  OPERATIONAL STATE                 │
 │                                                    │
 │ Current State │ Status │ Events │ Evidence        │
 │                                                    │
 ├────────────────────────────────────────────────────┤
 │                                                    │
 │                  ORGANIZATIONAL MEMORY             │
 │                                                    │
 │ Decisions │ Knowledge │ Patterns │ History        │
 │                                                    │
 ├────────────────────────────────────────────────────┤
 │                                                    │
 │                     LOOP STATE                     │
 │                                                    │
 │ Identified → Contextualized → Defined              │
 │ → Allocated → Deciding → Executing                │
 │ → Observing → Re-ingesting → Reconciling          │
 │ → Learning → Next Work                             │
 │                                                    │
 └────────────────────────────────────────────────────┘

---

What Spine Fabric Contains

Business Context

• Goals, needs, objectives
• Entities, relationships, organizations
• People, accounts, products
• Constraints, policies

Work Graph

• Work items, tasks, decisions, actions
• Dependencies, priorities, assignments
• Status, progress, blockers

Operational State

• Current state of all entities
• Real-time events and signals
• Evidence and audit trail
• Attribution and provenance

Organizational Memory

• Decisions and their rationales
• Knowledge and patterns
• History and learnings
• Outcomes and their context

Loop State

• Where every work item is in the cycle
• What has been attempted
• What has been verified
• What needs to happen next

---

The Five Spine Stores

Store	Technology	Contents	Governance
Canonical Spine	Neon / Postgres	Authoritative truth, long-term memory, governed writes	Strict — organization-controlled
Operational Spine	D1 / Durable Objects	Working context, real-time state, short-term working sets	Moderate — tenant-scoped
Edge / Session State	Workers / Cache	Ephemeral state, per-session / per-device, fast access	Light — session-scoped
Audit Store	Append-only	Immutable audit trail, compliance evidence	Immutable — no modifications
Memory Store	Knowledge DB	Organizational memory, patterns, learnings	Governed — promotion-controlled

---

The Universal Record Envelope

Every Spine entity conforms to a single envelope:

interface SpineRecord {
  id: string;
  tenantId: string;
  entityType: EntityType;
  state: EntityState;
  version: number;
  createdAt: string;
  updatedAt: string;
  metadata: Record<string, unknown>;
  payload: unknown;
}

Canonical Entity Types

Entity	Prefix	Description
Connection	conn_	Authenticated link to an external system
Connector	cplr_	Integration adapter definition
SyncJob	sync_	Data synchronization task
Webhook	wh_	Inbound event listener
Schema	sch_	Data transformation definition
Capability	cap_	Registered platform capability
TimelineEvent	evt_	Audit/continuity event

---

Spine Fabric Is Bidirectional

Spine Fabric both provides and receives:

Reads From (Spine → Everything)

Consumer	What It Reads
Human Workbench	Business context, work items, KPIs
Twin Workbench	Context, reasoning material, work graph
Projections	Raw data for role-specific shaping
Governance	Policies, constraints, risk data
Agents	Context, capabilities, work assignments

Writes To (Everything → Spine)

Writer	What It Writes
Ingestion	New events, entity updates
Execution	Action outcomes, state changes
Reconciliation	Verified state, discrepancy records
Memory	Promoted knowledge, learned patterns
Human	Decisions, approvals, context
Twin	Reasoning, recommendations, plans

---

Storage Boundaries (Frozen Doctrine §29)

• Neon controls tenant registry and cross-tenant queries
• Per-tenant D1 holds V0 operational Spine
• Fortress-adjacent stores audit/evidence data
• Stores never leak across tenant boundaries
• Every query is scoped to tenantId at the storage layer

---

Spine Fabric Connects to

Layer	Relationship
Business Context	Organizes and maintains Business Context
Organizational Memory	Stores accumulated knowledge
Work Graph	Derives work from context
Projections	Provides data for role-specific shaping
Communication Bridge	Exchanges context with agents and systems
Reconciliation	Receives verified outcomes
Loop State	Tracks work item lifecycle