Pranav Bhave
Claim CC-001 — 1 of 21 in the registry Supported within scope

CC-001Warrant reviewed 2026-08-24 · expires 2026-12-22

Frechet-Hoeffding endpoint bounds from declared marginals

cc.kernel.strict.frechet_bounds computes Fréchet–Hoeffding endpoint bounds for composed binary guardrail failure from declared marginals; for marginals (0.10, 0.10) it returns [0.0, 0.10] for the AND event and [0.10, 0.20] for OR.

01Falsifier — what changes this claim

A clean-clone execution of the bound module on marginals (0.10, 0.10) returns AND or OR bounds other than the recorded endpoints, beyond the stated tolerance.

Consequence REJECT

This is the condition and consequence recorded in the registry. The vocabulary this is published in defines what each consequence commits the author to.

02Scope

The kernel module at the bound commit. Reproduced from a clean clone (venv, pip install, execute, assert) most recently on 2026-08-23, and re-reproduced by CI on every push and weekly. No claim about any deployed system.

03Forbidden rescues

Repairs declared unavailable in advance; using one after a failure would breach the recorded commitment.

04Non-claims — what this does not license
05Binding and freshness
Binding
Cubits11/cc-framework @ 167aa1ee
Output recorded verbatim in /essays/when-marginals-are-not-enough/; continuously reproduced by scripts/reproduce_cc001.py in CI. Re-bound 2026-08-23 from a commit stranded by an upstream history rewrite to a main-reachable commit; kernel file content verified byte-identical across both refs before re-binding.
Reviewed
2026-08-24 · window 120 days
Expires
2026-12-22 — after this date the recorded review is overdue; this does not make the claim false
Triggers
  • executable fires when the kernel module on the default branch diverges from the bound revision
  • manual kernel semantics change outside the bound module file
Dimensions
visibilityPublicprovenanceMachine-generated, owner-executedsupport roleExecuted outputmaturityReleased