Your build is green. Do you know what that green light proved?
Not “did the tests pass” — did the thing that says PASS actually run anything, against the code you think it ran against? I couldn’t answer that about my own repository, so I pointed the verifier at itself. Ranex gates Ranex: the kernel evaluates this repository’s own test suite — 738 frozen test IDs, run provisioned, sealed and offline against the real current commit. It didn’t validate the design. It kept catching me. What it caught is below, so you can go looking for the same shapes in your own build.
Why dogfooding a verifier is different
Two real states from this build. Neither was caught by reading a report.
Most dogfooding is a marketing exercise. “We use our own product!” Fine. But a verification tool pointed at itself has a sharper property: every time it catches something, it’s evidence the thing works — and every time it misses something, that’s a defect in the product itself, not just in the code.
