Make the marketThe cross-system protocolMakes data move

Spine

The protocol that lets data trade without leaving home.

StatusSpec

Spine is the cross-system protocol: the layer that makes data from any participating system discoverable, queryable, and exchangeable, without the data ever leaving the system that owns it. It is the gate between systems and the plumbing of the market.

The mechanics are continuous with what happens inside a single app. The same three modules (Store, Query, Channels) govern sharing within an app (where Frame implements them) and across apps (where Spine extends them over system boundaries). The principles do not change at the boundary; only the scope does. That is what keeps custody intact end-to-end: querying across the ecosystem is the same sovereignty model as sharing inside one app.

Spine is deliberately designed for participants that were never built on Frame. A government registry, an NGO database, or a traceability platform can publish to or subscribe from Spine. Anyone can build a protocol; Spine is worth using because of the supply already flowing through it.

Where it sits. Stands on the shared conventions at cross-system scope. Sibling to Scribe; independent of Frame and Forge.

What it does
01
Discover across boundaries
Query a place, a company, or a person and get every available source, whichever system holds it.
02
Data stays at source
Buyers pay for permissioned access on the owner’s terms; the records themselves never change hands.
03
Open to any system
Frame-built or not, a participant joins by speaking Spine, not by rebuilding on our stack.
Spine in the suite
FIG.01 · five products, two supply paths, one foundation
A · Create the supplyB · Make the marketForgeagents build appsFramethe app frameworkappscapture field databuildsrun onPublic sourcesregistries · portals · reportsCrawlscan · verify · organiseScribemap · reconcile · conformpublic weborganisedpublishesPublic hubopen · source-rated · kept freshSpineexchange, at sourcecaptured dataconformedIntelligencethe demand-side payoffpriced accessrisk managementimpact measurementdue diligenceopportunity assessmentwithin-appcross-systemThe foundationShared conventionsidentity · schema · provenance · sharing rules
DAAC product — Spine, in copper, is the load-bearing gateApps built on Frame — the ecosystem that captures the supplyExternal — public sources scanned in, intelligence served out
The other four
FrameThe application frameworkForgeThe agentic build environmentCrawlThe public-source engineScribeThe conformance engine
← All five productsInvestor brief →