Boundary Intelligence
A multi-project program (986+ pre-registered trials) finding that simple mechanisms at system boundaries can match or beat far larger internal-model approaches. Reported with its honest negatives.
Synthesis · 986+ trialsIndependent AI-safety research
I built a small lab to measure when an AI can catch its own mistakes. So far the answer is that self-correction is competence-gated: a model can only check what it already half-knows, and the checking fails on exactly the hard cases where oversight needs it. I derived the pattern from a minimal model, confirmed it on seven real ones, and worked out what it implies for when a verifier is worth deploying.
The finding
Most plans for overseeing AI lean on one move: use another AI to check the first one. I measured when that move works. A checker helps inside its own competence region, and outside it, its objections are mostly noise. The models also turn out to be less independent than they look. When two of them are wrong, they hand you the same wrong answer more than half the time, like students who studied from the same textbook. I derived this from a minimal model first, then confirmed it on seven real ones, then replicated it on fresh tasks.
Scope, stated up front: one open-weight 32B model, tasks a program can grade, a single GPU in my office. I claim the measurements, not more than that. The rigor standard behind them has refuted four of my own headline hypotheses in writing, so the surviving results have earned some trust. Methods, result cards, and the full writeup are on the research page, and I'm glad to share the underlying evidence directly.
Selected work
A multi-project program (986+ pre-registered trials) finding that simple mechanisms at system boundaries can match or beat far larger internal-model approaches. Reported with its honest negatives.
Synthesis · 986+ trialsA local, OpenAI-compatible execution gateway (~13,300 LOC, 133 tests): tiered model routing, async task management, and a containment validator that caught 100% of adversarial proposals in testing.
Working softwareA git-native, test-gated wrapper for LLM code-repair loops. Restores reliable multi-file repair where a bare loop silently reverts good fixes. Packaged and benchmarked on 22 workspaces.
Alpha · PyPIA keyword classifier at the request boundary that routes each turn to the cheapest adequate model tier — 23–65% cost reduction at 95–96% quality in measured sessions.
Open source · MITThe tool repositories — governor andlattice-commit — are public. Research code, data, and reproduction bundles are available to reviewers and collaborators on request.
About
I'm an independent researcher running a focused program on a single workstation GPU. The work is deliberately small and falsifiable. Expectations are pre-registered, every claim has kill criteria, and the uncomfortable controls get run even when they threaten the thesis. When I get something wrong, the record says so: four of my own headline hypotheses have been refuted by my own harness, and the retractions are written down.
The through-line is legibility: mechanisms a human can read, audit, and reason about. I think oversight you can't read is oversight you can't trust, and I'd rather demonstrate that on narrow, checkable problems than assert it broadly.
How a sustainability educator ended up working on legible AI →
Open to research collaboration, funding conversations, and reviewer access to the full evidence.
bentleymoonperkins@gmail.com