
Building Ranex in the Open: What Gating My Own Code Actually Caught
Ranex gates Ranex. Here are the real failures that came out of pointing a verification kernel at its own test suite, including the ones that had already passed human review.
The same belief applied to one incident at a time: the 2am bug, the mutation run that found the lie in a green check.

How a retryable timeout can make every watchdog test pass while a stalled provider stream still hangs your session.

A real agent can work in a clean worktree without a signing key. See the delegation boundary that yields a candidate, never a self-issued PASS.

If your agent can author its own success, your checks are decoration. Learn the structural split that keeps a harness from grading itself.

Nine defects appeared only when the Ranex CLI was driven like a new operator would use it. Here is what to test at your tool surface.

HTTP 200 can hide a broken dependency. Reproduce 12 Uptime Kuma monitor results and learn when keyword checks miss what a JSON query catches.

A SQLite file copy passed its integrity check but missed committed rows. Reproduce it, then use the included backup utility and restore verification lab.

A passing uv sync can leave a new dependency uninstalled. Run this small lab to see why, then use the lockfile check that matches your CI requirement.

A valid credential is not proof of what it was about. Learn how six false PASS paths exposed one weak observation boundary.

Week 1 roundup: five verified highlights, five plain corrections, and what we left out, every restated fact re-checked against primary sources.

Five observable GitHub signals (response times, external-PR merges, release cadence) that tell you more than any good first issue label.

What these three releases changed, what to verify before an upgrade, and a reproducible Gitea startup check with recorded results.

A practical six-check method for examining a newly discovered GitHub repository before your team commits engineering time to it.

Compare three self-hostable Notion alternatives by workflow, export, and maintenance. Use the migration acceptance kit to test your own shortlist.

A signature can prove who made a record, not whether the policy deciding it came from a trusted committed state.

Your AI assistant cited source code, but which exact version? A practical way to check AI source code provenance with primary, verifiable evidence.

Exit code zero can conceal skipped or missing tests. Freeze outcomes and judge them against a manifest instead.

Mutation testing exposed 59 refusal paths no test executed. Learn how to measure the safety net instead of trusting a green suite.

Learn why a stable-looking test report is not evidence, and how rerunning checks against disk exposed a 12% flaky suite.