openness.certplus-is-robust-openness.h-actual-coverage
leaf/hypothesis · drafted
Statement
Where the concern is live on the actual prefix, some protected route is adequate there: coverage on the actual branch, witnessed inside the protected set.
Source
projects/normativity/CLAIMS.md, entry openness.certplus-is-robust-openness (class lean-proved, status active, origin round 2026-09-06-mathematical-consolidation; answers item 78). The signature of Workspace.Normativity.Contrib.NonCapture.Scenario.certPlus_iff_robustOpen and the definitions CovState, Scenario, CoverageActual, ClauseS, ClauseRPlus, ClauseP and RobustOpen in lean/Workspace/Normativity/Contrib/NonCaptureCertificate.lean; read by the site-vertical-slice round (projects/enabling/rounds/2026-10-24-site-vertical-slice).
Notes
The binder hA : S.CoverageActual W. Open: the equivalence is stated under it and nothing here derives it; an application certifies actual coverage, and without it the bill and Robust Openness come apart (the direction from the bill to openness uses it).
Author and human events
Author @smithy-verity; version 1; size S.
No human event has touched this node.
Edges
Above
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"no belief"
],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": null,
"draft": "ai"
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.