dataqbs
Release

Octorato 6.0: From Coverage to Enforcement

Octorato 6.0 stops labeling its gates and demonstrates them: every blocking gate passes a self-test with one case it must deny and one it must allow, on every push.

Why it matters A 'wired' rule can rot with nobody noticing. Octorato 6.0 breaks each gate on purpose on every push and watches it close again; if it does not close, the push does not leave. And it prints two numbers separately: how much is covered and how much is actually enforced.

Octorato 6.0: From Coverage to Enforcement

In 4.0 every rule had to name its mechanism. That proves it exists, not that it works. A gate can stay listed while its logic no longer blocks anything.

What changed

Every fail-closed gate now carries its own self-test: a case it must deny and a case it must allow. The health check runs all of them on every push; if one stops biting, the push fails. Three rules moved from prose to real gates, each observed blocking. And the honesty is printed: coverage and enforcement are two separate numbers, never one dressed as the other.

Why it matters

A control that exists on paper protects you until the day it matters. In 6.0 the brain breaks its own gates every day to prove they still close.