Decisions we had to make, measurements that changed our minds, and the parts that went wrong before they went right. Same rule as the rest of this site: if we can't show you the check behind a claim, we don't make it.
A technician at a stopped machine needs to know which kind of answer they just got. That is why our system has three verdicts instead of two — and why the third one firing on real hardware mattered more than it sounds.
We changed one instruction to make Solomon trust a veteran's notes over the manual. It obeyed — and silently stopped telling technicians to cut the power first. Nobody in review caught it. A test did, within minutes.
We put a 60-second demo on our product page. It contacts YouTube only after you press play — because a page arguing that your data should stay in your building has no business handing you to Google before you've asked for anything.
These posts describe how we build. If you'd rather see what it actually scores — including the questions Solomon still gets wrong — that lives on the Measured page.
See the measurements →