warrant.supported-admissible
and · drafted
Statement
A verdict bracketed by two cited bound certificates with attained endpoints is attained in the region.
Source
projects/normativity/CLAIMS.md, entry warrant.supported-admissible (class lean-proved, status active, origin round 2026-10-20-warrant-enforcement-semantics; answers item 56). Documentation: verification: projects/normativity/rounds/2026-10-20-warrant-enforcement-semantics/LICENCE_CHAIN.md; context: projects/normativity/rounds/2026-10-20-warrant-enforcement-semantics/COUNTERMODELS.md. The signature of Workspace.Normativity.Contrib.WarrantEntitlement.supported_admissible in lean/Workspace/Normativity/Contrib/WarrantEntitlement.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: A verdict bracketed by two cited bound certificates with attained endpoints is attained in the region. The registry's answers_item is the priorities pointer to item 56 (ruling F2).
Bridge card
Connected to no informal claim yet: held by normative-inductor.
Declaration Workspace.Normativity.Contrib.WarrantEntitlement.supported_admissible in lean/Workspace/Normativity/Contrib/WarrantEntitlement.lean (record warrant.supported-admissible.record)
Registry warrant.supported-admissible: class lean-proved, status active, review ci-only, origin round 2026-10-20-warrant-enforcement-semantics; bears on item 56
The statement of record of `warrant.supported-admissible` formalizes the registered claim as the registry reads it: Supported → Admissible.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (warrant.supported-admissible.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 normative-inductor
Children
- part: warrant.supported-admissible.record leaf/record
- part: warrant.supported-admissible.bridge leaf/bridge
- part: warrant.supported-admissible.complete leaf/completeness
Work pointers
- round 2026-10-20-warrant-enforcement-semantics
- item 56
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by normative-inductor",
"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.