How Foundry
builds.
Forge, Temper, Anvil, and Lore are products your team touches every day. Underneath each of them is a small shared platform — a workflow engine, a measurement loop, and an institutional memory system. This page shows how the layers fit together.
Platform layers,
not separate products.
None of these are things you buy separately. They're the engineering foundation Foundry uses to build products that hold up — and that compound in capability every time we ship.
Anvil — Workflow Engine
State machines defined as data, not code. Anvil drives every structured workflow — from software development tracks to financial review to operations planning. The same engine generalizes across domains because a workflow is a workflow: inputs, steps, decision points, outputs.
Lore — Institutional Memory
Decisions, architectural rationale, historical traces, and prior art — stored in a form that both people and AI agents can query. Lore is how Foundry avoids repeating itself, and how AI agents get context that goes beyond their training data.
Forge — Visual Cockpit
The supervision layer. Forge renders Anvil workflows visually, surfaces AI agent actions in real time, and gives teams the control plane to supervise, approve, and intervene. Forge is what you interact with; Anvil is what executes underneath.
Temper — Measurement Loop
Continuous quality tracking for AI agents. Temper archives what agents do, grades outcomes over time, detects when something changes, and runs controlled experiments to find what improves it. The research layer that keeps everything honest.
One platform.
Every product benefits.
Because all four products share the same foundation, improvements to any layer make every product better — automatically, without extra work.
01.Shared improvement cycles
A better memory model in Lore makes Forge answers sharper and Temper experiments more accurate. A better workflow primitive in Anvil makes every product that uses it faster. Improvements don't stay local.
02.Cross-domain learning
Patterns that work in construction estimating inform how we structure financial review workflows. Measurement techniques proven in one vertical generalize to others. Every engagement raises the baseline.
03.No integration tax
Because the layers were designed to work together from the start, there's no glue code between memory, engine, cockpit, and measurement. Each layer is thin; the system is cohesive.
04.Customers inherit the platform
When Foundry works with your business, your workflows run on this foundation. You don't operate the platform — you benefit from it. The products we build for you compound with every engagement.
See how Foundry deploys
this for you.
When Foundry works with a business, customers benefit from this platform without having to understand or operate it themselves. The products we build for you run on the same foundation we use for everything else — and get better with every engagement.
See how an engagement works →