The Emerald Foundry
We publish the rule and the thing that obeys it.
Framework and working system, published together
The position
Policy is written at a distance from the thing it governs, and the distance is where the harm lives. A remedy is drafted, published, and only then handed to the people who must live under it - who discover what it costs, what it quietly forbids, and whether it was ever buildable at all. The drafters are never among them.
We think that arrangement is illegitimate, not merely inefficient. Anyone proposing a constraint should have made the thing that has to satisfy it, and should publish both, so the proposal arrives having already been answerable to something real.
So we build. Every framework we put forward comes with a working version of the system it describes, made from first principles rather than from the previous draft's assumptions. Not to prove we can, but because the right to ask something of others is earned by having done it first.
The programme
The Emerald Foundry
The Emerald Foundry is where the pairing gets made. It replaces the two arms the organisation used to run - one that built, one that funded other people's building - with a single way of working, because that split described our internal structure rather than what we believe.
Each piece of work moves through the same four stages, and neither half is published alone. A framework without the thing built is the paper everyone already writes. The thing built without the framework is a demonstration of nothing in particular.
How a piece of work moves
04 stagesFind the failure
Start from first principles rather than from the existing rulebook. What is the system actually doing, to whom, and which part of it is load-bearing? Most policy inherits the previous draft's assumptions; this stage exists to refuse that inheritance.
Write the framework
Regulatory in nature: what a jurisdiction would have to require, with the thresholds named and the obligations stated precisely enough to build against. Precision here is not pedantry - a threshold you cannot implement is a threshold nobody can comply with.
Build the reference
The system as it would exist if the framework were already law, built from first principles. Not a mock and not a slide: something that runs and satisfies the rule, so what compliance costs is a measured figure rather than a matter of whoever argues hardest.
Publish both, together
The framework, the build, and what building it revealed - including where the framework had to change because the reference could not satisfy it. That last part is the most useful thing the method produces and the part a paper alone can never report.
Where the Foundry works
05 areasEnergy & Industry
How can we make it cheaper and faster to build in the world of atoms?
Cryptocurrency & Future of Money
How can value move without asking permission, and still be safe to hold?
AI & Robotics
How can we get capable machines into the physical work nobody is left to do?
Innovation & Digital Economy
How can we stop good ideas dying between the laboratory and the market?
Safe AI and Regulation
How can a frontier system be made answerable before it fails rather than after?
The Foundry takes problems where the rule and the build have to be designed against each other. If that describes the thing you are stuck on, say so in the subject line.