Gate Verdicts

A passing Ranex gate proves tested conformance to an approved graph and exact digest. It does not prove correctness, security, or performance.

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

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.

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

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.

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.