Forge
Builds the supply as fast as agents can run.
Forge is the agentic build environment for constructing and maintaining apps on the framework it is given: DAF today, Frame in the DAAC-native form, or another substrate once Forge holds its contracts and source. It is the operational form of the shift behind the whole suite: humans build the agents, and the agents build the apps.
Agents work in four modes. Compose assembles an app from the substrate’s existing units; Extend proposes a new reusable unit when the substrate does not yet cover a need; Convert turns a running system into an app on a target substrate, data migration included; Maintain carries substrate evolution down into apps already shipped. Human supervision sits at the scope boundaries (which apps, which spec changes, which extensions are admitted), not on every line.
Forge and Frame are separable in both directions: a customer can run Frame with human developers and no Forge, and Forge can be tasked against DAF or another framework. Frame stays its reference substrate, the one whose component doctrine gives the agents their richest starting pattern; a Datastake-style deployment uses both, which is how the ecosystem can add apps in hard sectors faster than headcount ever allowed.
Where it sits. Framework-agnostic: builds against DAF, Frame or another substrate it holds contracts for, with Frame the DAAC-native reference. Independent of Spine and Scribe; neither Frame nor Forge requires the other.
- 01ComposeHigher volume
Agents select and parameterise the target substrate’s existing units to assemble an app against its spec.
- 02ExtendHigher stakes
When the substrate can’t cover a need, agents propose a new reusable unit, admitted under that substrate’s own rules.
- 03ConvertFrom a running system
An existing system becomes an app on a target substrate, behaviour parity and data fidelity verified against the source.
- 04MaintainNothing rots
Substrate evolution is carried down into apps already shipped, so no app falls silently behind substrate.
Substrate reconnaissance first, fail-closed; new units pass a curation-review admission gate. Supervised at the seams, scope changes and unit admission, not every config line.
how often a capability was reused rather than rebuilt, the flagship metric
composed, extended, converted and maintained, per build
supervision events at the seams
drift of shipped apps against the evolving framework each was built on
the lifecycle counters
Born wired, the telemetry shape is fixed before the packaged agent runs a build. The method already works under supervision: a production app has been rebuilt on a new substrate and verified to behave identically. Until the agent itself runs, the snapshot reads “connected, awaiting builds”, every field zeroed. Nothing is faked.
- Digital system development and maintenanceA described situation becomes a system people work in, and it stays in step with what it was built on instead of drifting behind it.
- Migration of existing systems for interoperabilityThe system people already depend on keeps working, on a substrate that can be maintained, and the legacy records come across with it, reconciled rather than stranded.
- Targeted knowledge discoveryA local data supply reaches the markets that want it: discoverable, permissioned and payable at the holder’s own discretion, with nobody taking custody of it to make that true.