post.witness-hindsight
and · drafted
Statement
Re-pointed by the follow-up (prompts/2026-10-01-thin-legitimacy-and-effective-authority/FOLLOWUP.md, Part 1) from `hindsight_vs_approval`, which was `0 < 1 ∧ 1/5 < 4/5`. With `approval_ignores_realized` (approval-time scoring unchanged when the realized value changes) and `appearance_move` (raising the appearance raises the approval score and leaves the later score fixed).
Source
projects/deference/CLAIMS.md, entry post.witness-hindsight (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.EffectiveAuthority.hindsight_instance in lean/Workspace/Deference/Contrib/EffectiveAuthority.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: Re-pointed by the follow-up (prompts/2026-10-01-thin-legitimacy-and-effective-authority/FOLLOWUP.md, Part 1) from hindsight_vs_approval, which was 0 < 1 ∧ 1/5 < 4/5. With approval_ignores_realized (approval-time scoring unchanged when the realized value changes) and appearance_move (raising the appearance raises the approval score and leaves the later score fixed). 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 public-corrigibility-line.
Declaration Workspace.Deference.Contrib.EffectiveAuthority.hindsight_instance in lean/Workspace/Deference/Contrib/EffectiveAuthority.lean (record post.witness-hindsight.record)
Registry post.witness-hindsight: 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 `post.witness-hindsight` formalizes the registered claim as the registry reads it: Hindsight against immediate approval: approval-time scoring reads the appearance, later-evaluation scoring the realized value, and the two rules pick different options.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (post.witness-hindsight.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 public-corrigibility-line
Children
- part: post.witness-hindsight.record leaf/record
- part: post.witness-hindsight.bridge leaf/bridge
- part: post.witness-hindsight.complete leaf/completeness
Work pointers
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by public-corrigibility-line",
"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.