The mechanism itself: what the kernel enforces, and what a gate looks like before and after a fix. A verdict is a pure function of gate, evidence, subject, and approver.
A trust-root check returned when its file was absent. Learn how to test security controls for missing inputs, not only bad ones.
What Ranex Ed25519 evidence signatures prove, what they cannot prove about approval or truth, and how the committed public keyring works.
How the Ranex journal blocks ordinary rewrites, detects edited rows, and where its rollback and truncation limit remains open.
Why Ranex fails a required claim with no evidence, including why a fresh clone correctly starts with a failing verdict.
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.
A GIT_* variable redirected Ranex checks to the wrong repository. Learn the boundary a git flag cannot enforce and the fix that closed it.
