Forge shapes.
Pipelines are declared, versioned and replayable. Every transform records its inputs, its code hash and its output objects, so every derived dataset can prove exactly how it was made.
Data operations with a memory
Transforms are code, reviewed and versioned like code. A pipeline is a declaration the platform executes, not a diagram someone once drew.
Same inputs, same code hash, same outputs. Any object in the fabric can be rebuilt from its recorded lineage, byte for byte.
Each derived object carries its provenance line: source feed, transform, code hash. Halt on signature mismatch, never on a guess.
Errors state the fact and the fix
When an upstream feed breaks its signature, Forge does not shrug. Ingest halts at the exact object, the lineage names the last good state, and the operator sees the fact and the fix, not an apology.
This is the platform's temperament everywhere: precision is trust.
$ forge status feed-atlantic-raw
signature mismatch on feed-atlantic-raw
ingest halted · last good object: vessel-1188
fix: re-sign upstream or quarantine with
forge quarantine feed-atlantic-raw --after vessel-1188On the record
| Property | Specification |
|---|---|
| Transforms | versioned code · recorded inputs · code hash · signed outputs |
| Replay | Deterministic rebuild of any derived object from lineage. |
| Sealing | Outputs sealed like any Midgard object: AES-256-GCM under ML-KEM-wrapped keys. |
| Governance | Pipeline access and purpose constraints enforced by the enclosure, logged per run. |
| Competes with | Palantir Foundry. |