Create the supplyThe application frameworkWhere apps are built

Frame

The substrate the supply is built on.

StatusDesign

Frame is the DAAC-native application framework: the substrate that apps run on. It shares most of its DNA with DAF, the framework a decade of live deployments runs on; what sets it apart is that it is agent-oriented, built for apps to be composed and realigned by agents in Forge rather than by hand. It extends DAF for the agent era, it does not replace it.

What makes Frame load-bearing for DAAC is that compatibility is not a feature you add. Every app built on Frame implements the shared conventions (identity, schema, provenance, sharing rules) from the inside. The data it captures is exchangeable across the ecosystem from the moment it exists, with no later integration step.

Apps are built on Frame by humans writing configuration directly, or by agents in Forge. Frame is the substrate; it does not build apps itself.

Where it sits. Stands on the shared conventions at within-app scope. Forge builds on Frame; the data Frame apps capture is the supply.

What it does
01
Configuration-driven
Apps are declared, not hand-coded, so a spec change is a configuration change, not a rebuild.
02
Tradable by construction
The shared conventions are implemented from within, so captured data is a tradable asset the instant it is recorded.
03
Sovereign by default
Custody, permissions, and channels are part of the substrate, so data stays under its owner’s control at the point of capture.
Frame 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
ForgeThe agentic build environmentCrawlThe public-source engineScribeThe conformance engineSpineThe cross-system protocol
← All five productsInvestor brief →