openness.endpoint-only-insufficient
and · drafted
Statement
Exact counterexample: a two-transition evolution open at both endpoints whose middle state has a live concern with no adequate route; it is not a legitimate segment. This is why openness is required at every state.
Source
projects/normativity/CLAIMS.md, entry openness.endpoint-only-insufficient (class lean-proved, status active, origin round 2026-09-07-final-pressure-pass; answers item 78). Documentation: verification: projects/normativity/legitimacy/rounds/2026-09-07-final-pressure-pass/THEOREMS.md; context: projects/normativity/legitimacy/rounds/2026-09-07-final-pressure-pass/READINESS.md. The signature of Workspace.Normativity.Contrib.OpenIntegrityEvolution.Witness.endpoint_only_insufficient in lean/Workspace/Normativity/Contrib/OpenIntegrityEvolution.lean.
Notes
Filed by the map-as-canonical round (prompts/2026-10-22-map-as-canonical) from the registry entry and the declaration's signature; its hypotheses are unread (ruling F1, 2026-10-23): the record's Source carries the signature verbatim, and a reader files the hypothesis leaves. Registry note: Exact counterexample: a two-transition evolution open at both endpoints whose middle state has a live concern with no adequate route; it is not a legitimate segment. This is why openness is required at every state. Renamed 2026-09-25 (the legitimacy-internal-external round): a Robust Openness necessity witness; the id names the component of external legitimacy. The registry's answers_item is the priorities pointer to item 78 (ruling F2).
Bridge card
Connected to no informal claim yet: held by openness-and-non-capture.
Declaration Workspace.Normativity.Contrib.OpenIntegrityEvolution.Witness.endpoint_only_insufficient in lean/Workspace/Normativity/Contrib/OpenIntegrityEvolution.lean (record openness.endpoint-only-insufficient.record)
Registry openness.endpoint-only-insufficient: class lean-proved, status active, review ci-only, origin round 2026-09-07-final-pressure-pass; bears on item 78
The statement of record of `openness.endpoint-only-insufficient` formalizes the registered claim as the registry reads it: endpoint-only openness admits laundered exclusion.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (openness.endpoint-only-insufficient.complete): No premise beyond the signature's binders enters the declaration; the kernel checks it as stated. The result is the record, this leaf and the bridge, and its hypotheses are unread: the record's Source carries the signature verbatim and no hypothesis leaf is filed until a reader files one.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
- held by openness-and-non-capture
Children
- part: openness.endpoint-only-insufficient.record leaf/record
- part: openness.endpoint-only-insufficient.bridge leaf/bridge
- part: openness.endpoint-only-insufficient.complete leaf/completeness
Work pointers
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by openness-and-non-capture",
"hypotheses unread"
],
"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.