warrant.admissible-not-supported.bridge
leaf/bridge · drafted
Statement
The statement of record of `warrant.admissible-not-supported` formalizes the registered claim as the registry reads it: Admissible does not imply Supported.
Source
projects/normativity/CLAIMS.md, entry warrant.admissible-not-supported (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. Short name: Admissible does not imply Supported. Conclusion of the signature: Admissible G stDefeat F φ (1/2) ∧ ¬ Supported G stDefeat F φ (1/2) (cert 1) ∧ Supported G stDefeat F φ (1/2) (cert 2).
Author and human events
Author @smithy-verity; version 1; size S.
No human event has touched this node.
Edges
Above
- part of warrant.admissible-not-supported
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"attribution unvetted",
"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.