The bugs we shipped, by name.

A team ran a trading bot with real money. Their runbook said "✅ alert policy: unauthorized_401". The metric existed — it incremented, it charted. But no alert policy consumed it: zero policies in the cloud. A wall of 401s could climb forever and page no one.

Our law said alerts not configured. The team went and looked instead of dismissing it — and found the zero.

A backend team adopted the recommended config and discovered their old one had been quietly hiding 42 laws. Running the honest scope surfaced four real bugs — including an infra outage that looked like "an expired token": every user got 401 and nothing logged it.

Zero waivers taken. The debt stayed visible until each was fixed.

One of our own laws required a pre-deploy checklist, committed to the repo, 90% ticked. But a ticked box is a promise a human typed, not a performed check — the gate graded the claim, not the work.

A consumer read it and refused to lie. They reported the law instead of satisfying it. They were right. We fixed the law.

Our license-consistency law only knew open-source licenses — so a proprietary project could "pass" only by deleting its LICENSE file. The gate was rewarding the removal of the one thing it existed to check.

The consumer didn't delete it. They kept the red mark and waited for the law to be fixed. It was.

Our security-test discovery scanned only .ts/.tsx/.js/.jsx — so for a Python codebase, the security-testing laws were unpassable by construction. Not failing because the work was missing; failing because the detector couldn't see the work.

The consumers didn't waive them. They left them as visible debt until we fixed the detectors — which we did, in the Python-blindness batch.

Our own regression shrank the pre-commit hook from 122 laws to 27 — quietly. The laws that stopped running couldn't fail, so everything stayed green, and the absence of red read as health.

This is the failure the whole product is named after, and we shipped it. It's why the liveness floor exists: the audit now reports how many laws ran and refuses below the floor. We built the floor because we fell through it.

Sixteen dead config keys silently shrank our own gate to 5 laws — while the banner printed "FULL … 173 LAWS!". The verdict engine was honest (it printed 5 and refused); the banner lied about scope.

The capture of that refusal became the hero of this website. The banner was fixed, and orphan config keys now scream instead of whispering.

Building this site's design system, we wrote three disarmed gates in a row: a contrast checker that printed FAIL and exited 0; a token validator blind to 19 of its 54 references (dark silently overwrote light in a merged map); and a contrast checker v2 that guarded a hardcoded copy of the palette instead of the tokens — break a real token and it stayed green.

None was found by reading the code. Two fell to deliberate red-proofs; the third was caught by our own frontend, who refused to wire a gate that couldn't see its subject.

Our testing-quality law matched (?:it|test)\( without word boundaries — so the it inside split( parsed as a test named "\n". An innocent e2e helper failed the live dogfood audit and took the site build down.

The gate did its job — loudly, against us. The fix is a word boundary; the finding went straight to the maintainer.

Porting the /dogfood page, our frontend wrote a test describe() one word too short. The testing-excellence law flagged it at error severity, the live self-audit failed, and the build fell — while building the page about the audit.

That's the whole system working: the gate doesn't know or care that its own builders are on the other side of it.

Building the colophon on /why — the section that owns up to an AI building this — our designer pushed from a design/* branch. The Branch Governance law rejected it at error severity: the convention is feature/*, and the push went nowhere.

They renamed the branch and it passed — no override, no exception. The gate doesn't know it's the tool's own builder on the other side. That's the entire point.