Blog

Notes on living programs.

Deep dives into what ALGAL is, the research it sits next to, and why the machinery is shaped the way it is.

Self-evolving software needs a selection boundaryDarwin-Gödel Machine, Voyager, AlphaEvolve, and TextGrad all converge on the same loop — propose, evaluate, select. The hard part is not getting a model to write programs; it is deciding what gets to run. ALGAL makes that boundary the contract.
Receipts are the fossil record of an executionAgent runs are usually logs — prose about what happened that nobody can check. An ALGAL receipt is a content-addressed artifact that replays bit-for-bit offline: execution evidence you can hand to someone who does not trust you.
A program that can waitDurable execution engines keep workflow state in a service and replay code around it. ALGAL takes the stranger route — the program is data, so a wait is a checkpointed capability a brand-new process can resume, even in a different runtime.