legit-locality-forced
and · drafted
Statement
On finite frames the global L-conditioned Total Trust criterion forces every positive-mass legitimate candidate to be certain of the legitimacy event, and the local form, Total Trust on a question, does not.
Source
projects/deference/faf-cleanroom-2026-10-02/packages/corr-legit-general/corr-legit-general-findings.md: the declaration legitimizingTT_certain_of_legit and the contrast witness leak4.
Notes
A formal result filed in leaf form (the record and bridge split is a spell-out task). It bears on the crux legit-condition-vs-predict-reality: only the local form leaves room for the maintainer's "accurate assessments of risks to legitimacy" (projects/deference/note-dump-2026-08-11/notes/li-deference.md). Done in Lean; unvetted.
Filed as a formal result (record, setting, bridge, completeness) in place of the one-sentence step the branch filed: what the kernel settled is the record, and what a human still checks is the bridge, whether the declaration says what this sentence says. The step's estimate (smithy-verity-100) stays in the ledger as history. The declaration is not in a claims registry, so the record reads not in a claims registry until it is registered.
Bridge card
Connected to no informal claim yet: held by legitimacy.
Declaration legitimizingTT_certain_of_legit (record legit-locality-forced.record)
The declaration is the note's T3(a): under the global criterion every positive-mass legitimate candidate is certain of L, so only the local form leaves room for assessments of risks to legitimacy; leak4 is the contrast witness.
Hypotheses, read:
- legit-locality-forced.setting definitional: The general-object model of legitimizing total trust with a legitimacy event L of positive mass, as the package fixes it.
Completeness (legit-locality-forced.complete): No premise beyond the proved declaration, its stated setting and its bridge is needed for the informal reading of legit locality forced to hold.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
- held by legitimacy
Children
- part: legit-locality-forced.record leaf/record
- part: legit-locality-forced.setting leaf/hypothesis
- part: legit-locality-forced.bridge leaf/bridge
- part: legit-locality-forced.complete leaf/completeness
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"AI number",
"held by legitimacy",
"stale"
],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": {
"J": 0,
"mid": "47/50",
"range": [
"11/25",
"1/1"
],
"width": "1/1"
},
"draft": "ai"
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.