Eight studies. Each names its verdict and the file it comes from. The real-use one is the newest and the least flattering.
detection · a theoremproven
The fixed reference
Can displacement from a goal be detected at all, and can an agent do it by watching only itself?
A proof over agent states in a metric space, with the ground state as the goal as first spelled.
A fixed, unchangeable, findable reference is necessary and sufficient to detect when an agent has left the ball around where it started, in O(1) memory. No monitor that compares an agent only to a window of its recent states can be both sound and complete, for any window and any rule. So the proof forces the reference never to change. It says nothing about how often real drift is caught.
source · laserbrain: research/PROOF.md
the metric · by constructionbuilt
A real displacement
Is the reference a genuine measure?
The JSON grammar the agent spells its state into carries a pseudometric.
Displacement Φ is well-defined, deterministic and symmetric, so “distance from ground” is a real quantity. Which grammar is rich enough for a given agent’s reasoning is a separate, open question; the theorem covers a fixed reference, never a particular vocabulary.
source · laserbrain: research/SUBSTRATE.md
coverage · H2 · N = 18measured
Shorter runs
Does an agent with the harness stop sooner than one left to run?
Open-ended tasks, control against harness, replicated.
Yes, runs with the harness stopped sooner. The caveat travels with it: fewer steps is not fewer tokens. Steps do not charge the monitor for its own calls, and a run can be short and expensive. Whether the shorter run gave a better answer was tested three ways and not established.
about half the steps
open-ended runs stopped sooner (median 5 against 10, N = 18); a better result was tested three ways and not established
offline
source · laserbrain: research/STUDY.md; research/CLAIM.md
benefit · H1 pilot · N = 12inconclusive
The judge could not tell
Does the early return keep the answer as good as running longer?
A blind, stronger judge scored every pair in both orders; a win had to survive the swap.
The preregistered rule read “supported”, but the judge often disagreed with itself. Judging open-ended answers that have no right answer is near a coin flip. The pairs where the harness acted were ties or clean losses (the return produced a worse answer). Consistent with the hope, dominated by noise, not a result.
source · laserbrain: research/GRADER.md
benefit · ground-truthed · N = 15negative
Where there is a right answer
And on tasks that do have an objective answer?
Debug and loop coding tasks with hidden unit tests: Pass@1, no judge needed.
The harness did not help. It trailed the control, and every ceiling failure was a run where it intervened. That fits the theory: a task with its own built-in criterion does not need an outside reference, and the nudge derails a run that was fine. laserbrain is not for well-specified, test-backed work. Its domain is open-ended work, which is exactly where quality has no ground truth.
12 of 15
coding tasks with hidden tests passed with the harness, against 15 of 15 without it, at 4.4 times the tokens; suggestive, not significant (p about 0.11)
offline · N = 15 per arm
source · laserbrain: research/CLAIM.md
benefit · powered re-run · N = 16inconclusive
The panel, in its own domain
So we ran it only where it should help, with the best measure we could afford.
Criterion-absent tasks, a three-judge panel, each pair in both orders, and a rule fixed before any data: if the judges cannot agree, the verdict is inconclusive.
The panel could not agree, so the output is inconclusive: the pilot’s problem confirmed at scale. Criterion-free answers cannot be reliably judged even by three models, and the κ-gate refused to read a verdict from a broken measure. It was not neutral, though: the harness rarely acted, and where it did and the judges could agree, the control won. Cost was swamped by noise.
source · laserbrain: research/RETEST.md
live · AI-labelled real sessions · one developer · 2026-11negative
In real use
On real working sessions, labelled by AI agents, does the live check catch the drift that happened?
Real sessions with known drifted helper agents and known main-session misreads, plus 60 days of alarms labelled by an AI reviewer.
Mostly not. It caught 1 of 16 live · one session · AI-labelled drifted helper agents and 0 of 10 live · one session · AI-labelled main-session misreads, and none of its own alarms over 60 days was a true catch (0 of 39 live · 60 days · one AI reviewer). An outside AI judge did better on the same helpers: 10 of 12 offline · one session · AI-labelled with each helper’s final report in view, which it does not have live, and 9 of 12 dev · replay · one session · AI-labelled re-scored with only what it sees live. That judge does not run from the package and runs only on our machine today.
source · one developer’s working sessions and a 60-day log on one machine (local, not published)
multi-agent · M1 · N = 40inconclusive
The echo spiral
A group of agents has a failure a single one does not. Can a fixed reference catch it where the group cannot?
Checkable-answer tasks, so resolution is objective (no judge). Two transcript-only arms, the fixed reference (agents agree and add no new ground) against a recent-history baseline, scored by balanced accuracy, with the decision rule frozen before the run.
Run, and NULL by the frozen rule: the fixed reference did no better than chance; the same in the unseeded split that carries the claim. The fixed reference did fire where the recent-history baseline stayed silent, and leaned the right way, but two capable models resolved most tasks, so there were almost no real spirals to catch. The labels were noisier than “checkable” promised, too: one answer key was wrong. Not established; the multi-agent extension stays a prototype.
source · laserbrain: research/M1.md