value-change-base-layer
frame · drafted
Question
Does the representation of value change as belief change hold, and how far does it carry toward systems corrected through training?
Owners: @anson (GitHub A-M-Berns)
Path: the-program › corrigibility-landscape › value-change-base-layer
Roots (the frame's goals)
plan
Theorem 2.4 of the value-change note (a reflection-satisfying change is closer to the value variable in mean square and selects acts of higher expected value) and the three-term decomposition of its section 1.4 hold over the finite distributions of the formalization library as kernel-checked statements, with the note's fixture numbers as witnesses.
shared-claim
A change of an agent's utility function can be written as a change of belief about a value variable on an expanded algebra, and the agent that results acts identically on the original propositions; the direction from the expanded algebra back to the original is marginalization and the converse is a choice of decomposition that is not unique.
The murder-pill inequality, that the utility of the best act under U is at least the utility under U of the best act under the changed utility, yields resistance to value change only for a utility that does not depend on the modification event; in the note's two-step example an expected-utility agent strictly prefers having its values changed, 0.9 for accepting against 0.6 for declining.
The value to an agent of a change of its utility function splits exactly into a term that is never positive (the murder-pill term), a payment term (intrinsic preference for the change) and an information term (instrumental preference, positive only when the outcome of the change is uncertain).
An update that satisfies no expected net update can be valued strictly below no update (the note's coin-driven change, 0.5 against 0.6), so the rule that licenses wanting a modification is reflection with respect to the modification event and not the martingale condition alone.
The representation of value change as belief change on an expanded algebra can be improved until it reflects a trained system corrected through its training data well.
want
The representation of corrigibility covers changes of the sigma-algebra, taken up after the absolutely continuous case has been studied thoroughly.
Statement
Value change is represented as belief change on an expanded algebra, the murder-pill argument's hidden flat-utility assumption is exhibited, and the representation is kernel-checked and refined toward trained systems.
Source
projects/deference/corrigibility-note-dump-2026-10-01/value-change-as-epistemic-update.md, sections 1 to 2 and 7; the author's thesis of 2026-09-13 as republished in projects/deference/corrigibility-note-dump-2026-10-01/corrigibility-discussion-outline.md.
Notes
The base layer of the corrigibility line, filed as a sub-frame under corrigibility-landscape. Its plan root is the kernel-check; its shared claims are the note's four derivations, none vetted by a human; the improvement claim carries the note's open directions as routes with their tasks. The map-read of the note by its author is the single vetting act this frame most needs, and the ranking's map-read units on the four derivations are that act.
Author and human events
Author @smithy-verity; version 1; size L.
No human event has touched this node.
Edges
Above
- part of corrigibility-landscape
- root (plan) of corrigibility-landscape
Children
- part: value-change-kernel-checked leaf/step
- part: value-change-is-belief-change leaf/step
- part: gandhi-argument-assumes-flat-utility leaf/step
- part: value-change-three-terms leaf/step
- part: no-net-update-insufficient leaf/step
- part: value-change-is-belief-change.improvable or
- part: want-sigma-algebra-changes leaf/want
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": null,
"draft": "ai",
"root": {
"status": "open",
"Pr": {
"hi": "1/1",
"lo": "3/10",
"mid": "4/5"
},
"value": {
"hi": "1/1",
"lo": "-1/1",
"mid": "4/5"
},
"cost": "240/1",
"margin": "no established leaves"
}
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.