The numbers.
BrainOS · proof-gated · local
ReVerse — Claude Code drives UEFN
Righteous Recon · 80/100 gate · live
Northbridge Horizon · live
plus: public-key verify live · ~1s revocation · two-person approval
BrainOS, running.
This is the loop BrainOS runs: a run starts, a claim or lesson gets made, it's checked against a proof gate, and a record gets written either way — pass or fail. Nothing gets promoted unless the proof passes. The learning loop runs the same way — lessons become skills, and a skill only activates once a proof passes. The runs below are synthetic; the rule they show is real, and it's running on my machine right now.
The loop never trusts itself. That's the point.
Every cycle binds a claim to evidence before anything ships. Pass the proof gate, get a receipt. Miss the threshold, get rejected — and the rejection is logged too.
demo loop · synthetic tasks
What I've built, and why.
Tap one. It'll explain itself.
Thirty tools, in rotation.
The working stack behind everything above — literally on a belt. Tap a mark: the belt pauses and the logo charges to full glow.
Three rules, checkable.
HTML is truth
The semantic layer never leaves the DOM — kill every script on this page and it still reads, ranks, and works.
Status is honest
Live, prototype, private, draft. Labels describe reality. Nothing on this site claims a state it hasn't earned.
Proof over polish
Every claim binds to evidence — receipts, gates, audit trails. Even the demo above shows a rejection, because real systems get told no.