Forge · the engine beneath The Bridge

The engine beneath The Bridge.

Forge is the layer that executes: the hands that do the work, isolated behind approvals. The Bridge is what you read; Forge is what runs — and nothing changes the world until a decision you can see approves it.

See The Bridge Register interest

The Bridge is the eyes. Forge is the hands. They are one system: a read model you can trust only because the layer underneath it executes in a way you can trust. Meet The Bridge, the product this runs →

Why it exists

An agent that can act is a liability until it can be trusted

The moment AI stops suggesting and starts doing — moving money, changing records, sending messages — the interesting problem is no longer capability. It is control. What ran, on whose authority, and can you prove it happened exactly once.

Forge is the answer to that question. It is a small, dependency-light execution kernel that runs work in isolation, admits nothing without a signed approval, and records every effect as it happens — so the briefing above it can be honest about what is real.

What the engine does

Isolate

Every unit of work runs in its own workspace with an exclusive writer. No shared mutable state, no two hands reaching for the same thing at once.

Approve

Nothing that changes the world runs without a signed grant bound to the exact intent. The kernel can check authority but can never mint it — and it fails closed.

Execute

Effects are created once per idempotency key. A crash mid-flight is closed on recovery against a durable commit record, not the mere presence of a file.

Record

Every effect is written to a canonical event log before it is published. The briefing reads that log — so what you see traces back to something that actually happened.

How the engine runs

Follow one request through

Nothing runs without a signed approval, nothing is created twice, and nothing is reported that was not first written down. Watch one request go through, then crash it after the effect and watch recovery read the record rather than guess.

Illustration — modelled, not executed evidence

The outcome is the same lookup the how-it-works page labels as a model. No process is run here.

One request arrives as an intent, in words. Nothing has been done yet.

effects 0events 0outcome in flight

What the engine can run

Domain packs on the same kernel

The kernel is general. What it runs is a domain pack — a specialised pipeline that turns a structured intent into validated, recorded work. Two are in development.

Code Build Engine

The designed pipeline for software development — from a structured specification to tested, documented, deployable code, validated at every stage. Specified, not built.

Explore the Code Engine →

Forge Knowledge

A pipeline that structures organisational expertise — documents, processes, know-how — into validated, reusable knowledge the engine can run against.

How a pack runs →

Research preview

Forge is in active development, and we are deliberate about that. We would rather ship one honest slice that runs than a platform that only looks alive. If you are building AI that acts and need isolation, approvals, and a real record underneath it — let's talk.