Pranav Bhave
Claim CC-004 — 4 of 21 in the registry Supported within scope

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

The sharp interval for the both-fail query

For marginals (0.10, 0.10) and the both-fail query, cc.kernel.strict identify() returns the sharp interval [0.0, 0.10] together with endpoint witness distributions that sum to one, are nonnegative, satisfy both marginal constraints, and attain each endpoint — verified to 1e-9 from a clean clone.

01Falsifier — what changes this claim

Bound identify() execution fails any stated interval, witness feasibility constraint, marginal constraint, or endpoint-attainment assertion at the declared 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 identification module at the bound commit, re-verified by CI on every push and weekly in the witness stage of scripts/reproduce_cc001.py. 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
Shares CC-001's bound commit so a single clean-clone checkout reproduces both claims; the reproduction script enforces that the two bindings stay equal.
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 identification module on the default branch diverges from the bound revision
  • manual witness API change outside the bound module file
Dimensions
visibilityPublicprovenanceMachine-generated, owner-executedsupport roleExecuted outputmaturityReleased