Law IV
Instruments Over Theory
Hidden structure stays hidden until you build the instrument.
The claim in full
Hidden structure exists in every domain; it stays hidden because the instrument to reveal it hasn't been built yet — and building it changes the thing being observed. Progress comes from new observables, not more theory.
What would falsify it
A law that cannot fail is not a law. Each of these is the observation that would break this one, written before the evidence was looked for, so the frame can lose.
A domain breakthrough that came purely from theoretical insight without any new observational capability.
How it is standing
Every candidate counter-example logged against the falsifier above, counted. Dismissed means examined and found not to bear on the claim; watching means open.
- Challenges logged
- 0
- Currently watching
- 0
- Examined, dismissed
- 34
- Last examined
- Not yet challenged
A low challenge count is not strength. It can equally mean the law has not been aimed at anything hard enough to break it, which is why the date matters as much as the number. Record compiled 27 Aug 2026.
Amendments
The statement above is not the original. Each row is a time the law was rewritten because it failed a test, with the reason it failed.
-
21 Jun 2026
Domain-scope clause. Law IV holds in engineering and applied domains, where we build things and then understand why they work, so progress is instrument-led. In fundamental physics and pure mathematics the order systematically reverses: theory precedes the confirming instrument, often by years to a century (general relativity 1915 → Eddington 1919 → gravitational waves 2015; the Standard Model predicting the Higgs decades before detection; non-Euclidean geometry; the Langlands program). This publication operates in the engineering/investment regime, where Law IV is load-bearing. NOT claimed as universal across fundamental science.
Essays that stress-test it
- The Work That Comes Due After You Leave A checklist can only confirm the steps you remembered to put on it. The one you forgot is caught by a record you did not write.
- Stop Re-Priming Claude Code by Hand The context you paste at the start of every session, put into one file you invoke with /prime.
- The Guardrail Your Agent Can Reach Most guardrails end up with an escape hatch. Check whether the thing you are constraining can reach yours. 20 sourced claims
- The Average Is Nobody's Result Of 255 studies on AI-assisted colonoscopy, 21 split the result by who held the scope. They disagree. 35 sourced claims
- Your Robot Coworker Is Still a Pilot Built, shipped, installed, working: four counts, quoted as one. Almost nobody publishes the fourth. 24 sourced claims
- The Most Expensive AI Errors Are Made of True Numbers Two months auditing an AI research agent. Nine ways a true number lies, and the check that catches each.
- Your AI Stack Has Three Bugs Other Fields Already Fixed Your benchmark, your model jury, your agent swarm: three old structures, and the obvious fix is usually wrong.
- Your Tests Pass. So What? A green suite only proves your agent cleared the gate. Mutation testing shows whether the tests behind it can bite.
- Where Your Metrics Fold A metric can be perfectly accurate and still hide the distinction your decision depends on.
- Never Let Claude Code Tell You It's Done A test the agent can't talk its way past, wired to run itself.
- How Reliable Is Your AI Agent? A month running an autonomous agent. Everyone who does comes back having built the same thing: a verifier.
- Same Model, Different Product: The Case for Harness Engineering Harness engineering, the code wrapped around an AI model, now drives more of the performance gap than the model you pick.
Read this law in the framework essay All writing The claim ledger