li.assessment.budgeter-value
and · drafted
Statement
The registered claim li.assessment.budgeter-value (lem:budgeter 1 over an assessment process) holds as its declaration states it; the registry's note is quoted in the Source.
Source
projects/normativity/CLAIMS.md, entry li.assessment.budgeter-value (class lean-proved, status active, origin round 2026-08-16-traderized-enforcement; answers item 47). Documentation: verification: projects/normativity/notes/GENERALIZED_LI_PAPER_HANDOFF.md; context: projects/normativity/rounds/2026-08-16-traderized-enforcement/THEOREM_MAP.md. The signature of Workspace.Normativity.Contrib.AssessmentProcess.BudgeterAt_value_eq_of_safe in lean/Workspace/Normativity/Contrib/AssessmentProcess.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 budgeted trader's value equals the raw trader's while the budget is safe, over an arbitrary assessment process. Nesting is consumed here as well as in the floor: the available capital in each world's loss cap must be positive. The registry's answers_item is the priorities pointer to item 47 (ruling F2).
Bridge card
Connected to no informal claim yet: held by operative-force.
Declaration Workspace.Normativity.Contrib.AssessmentProcess.BudgeterAt_value_eq_of_safe in lean/Workspace/Normativity/Contrib/AssessmentProcess.lean (record li.assessment.budgeter-value.record)
Registry li.assessment.budgeter-value: class lean-proved, status active, review ci-only, origin round 2026-08-16-traderized-enforcement; bears on item 47
The statement of record of `li.assessment.budgeter-value` formalizes the registered claim as the registry reads it: lem:budgeter 1 over an assessment process.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (li.assessment.budgeter-value.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 operative-force
Children
- part: li.assessment.budgeter-value.record leaf/record
- part: li.assessment.budgeter-value.bridge leaf/bridge
- part: li.assessment.budgeter-value.complete leaf/completeness
Work pointers
- round 2026-08-16-traderized-enforcement
- item 47
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by operative-force",
"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.