I'm building LOOM — a small open-source language that is a machine-checked trust layer for AI-written code. I don't write it by hand: an organism I built grows it, day and night. Day 11 closes the gap between approved and done.
A one-shot approval isn't enough — the gate should see what actually happened
LOOM's core is a gate that refuses code that lies about what it does. Approvals became signed and one-use — but they were still one step: you signed, and it was "spent." Between approved and done there was a gap: a crash mid-action, a replay, a swapped result — the gate never saw it.
Day 11 makes approval two-phase and signed — 385 → 388 checks, all green
claim_operator_approval reserves the signed approval before the action runs.
