Evidence

A passing command for one commit proves nothing about another. Bind evidence to the exact digest or let stale proof stop counting.

A race test passed because its framework ran sequentially. Learn how to prove your concurrency test can fail on broken code.

How the Ranex journal blocks ordinary rewrites, detects edited rows, and where its rollback and truncation limit remains open.

GitHub rulesets, editor hooks, and CI gate channels. Ranex asks a separate question: what must the evidence prove?

Why Ranex fails a required claim with no evidence, including why a fresh clone correctly starts with a failing verdict.

A session report describes a run. Re-run the command against the artifact on disk before you let that description decide anything.

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.

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

Why a Ranex verdict uses only gate, evidence, subject, and approver so the same proof always gets the same result.

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

A failure sentence cannot reliably carry its category. Keep the cause as structured data, render the prose from it, and block unknown values.

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

A GIT_* variable redirected Ranex checks to the wrong repository. Learn the boundary a git flag cannot enforce and the fix that closed it.

A single run cannot prove a change helped. Freeze the comparison, set the rules first, and keep observations separate from grades.

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

A SHA-256 hash identifies approved dependency bytes. It cannot prove that imported code will report your test result honestly.

A citation can be fabricated from memory. Fetch and record the source bytes before you let a design claim borrow their authority.

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.

Ranex judges AI-written work by evidence and executable checks, never by model confidence. Here is the whole mechanism: three ports, one kernel, and only one of them produces a verdict.