The Kernel
The Security Check That Checked Nothing
A trust-root check returned when its file was absent. Learn how to test security controls for missing inputs, not only bad ones.
The Kernel
How Ranex judges AI-written work: a kernel outside the loop, and a verdict that is a pure function of gate, evidence, subject, and approver.
8 articles
The Kernel
What Ed25519 Signing Actually Proves About a Test Result
What Ranex Ed25519 evidence signatures prove, what they cannot prove about approval or truth, and how the committed public keyring works.
The Kernel
Inside the Append-Only, Hash-Chained Journal
How the Ranex journal blocks ordinary rewrites, detects edited rows, and where its rollback and truncation limit remains open.
The Kernel
Absence Blocks: Why No Evidence Is a Fail, Never a Skip
Why Ranex fails a required claim with no evidence, including why a fresh clone correctly starts with a failing verdict.
The Kernel
Why a Verdict Has to Be a Pure Function
Why a Ranex verdict uses only gate, evidence, subject, and approver so the same proof always gets the same result.
The Kernel
Cause Is Structure, Not Prose
A failure sentence cannot reliably carry its category. Keep the cause as structured data, render the prose from it, and block unknown values.
The Kernel
An Environment Variable Can Choose the Repo You Judge
A GIT_* variable redirected Ranex checks to the wrong repository. Learn the boundary a git flag cannot enforce and the fix that closed it.
The Kernel
How Ranex Judges AI-Written Code: The Kernel, Explained
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.