thin.converse-fails-on-correct
and · drafted
Statement
The revealing process on two worlds with the point mass at one record and the prior at the other has value against the blank reference for every decision problem and is not correct. A witness claim; its own inhabitant.
Source
projects/deference/CLAIMS.md, entry thin.converse-fails-on-correct (class lean-proved, status active, origin round 2026-10-01-thin-legitimacy-and-effective-authority; answers item 107). Documentation: verification: projects/deference/rounds/2026-10-01-thin-legitimacy-and-effective-authority/REPORT.md; context: prompts/2026-10-01-thin-legitimacy-and-effective-authority/REPORT.md. The signature of Workspace.Deference.Contrib.ThinLegitimacy.Witness.value_not_correct in lean/Workspace/Deference/Contrib/ThinLegitimacy.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: The revealing process on two worlds with the point mass at one record and the prior at the other has value against the blank reference for every decision problem and is not correct. A witness claim; its own inhabitant. The registry's answers_item is the priorities pointer to item 107 (ruling F2).
Bridge card
Connected to no informal claim yet: held by authorship-and-transparency.
Declaration Workspace.Deference.Contrib.ThinLegitimacy.Witness.value_not_correct in lean/Workspace/Deference/Contrib/ThinLegitimacy.lean (record thin.converse-fails-on-correct.record)
Registry thin.converse-fails-on-correct: class lean-proved, status active, review ci-only, origin round 2026-10-01-thin-legitimacy-and-effective-authority; bears on item 107
The statement of record of `thin.converse-fails-on-correct` formalizes the registered claim as the registry reads it: Value does not imply correct: a wrong credence that happens to be the reference's.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (thin.converse-fails-on-correct.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 authorship-and-transparency
Children
- part: thin.converse-fails-on-correct.record leaf/record
- part: thin.converse-fails-on-correct.bridge leaf/bridge
- part: thin.converse-fails-on-correct.complete leaf/completeness
Work pointers
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by authorship-and-transparency",
"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.