no-net-update-insufficient
leaf/step · drafted
Statement
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.
Source
projects/deference/corrigibility-note-dump-2026-10-01/value-change-as-epistemic-update.md, section 2.5 ("Further checks (computed)") and section 6.8; computed by projects/deference/corrigibility-note-dump-2026-10-01/fixtures/value_change_journey.py.
Author and human events
Author @smithy-verity; version 1; size S.
No human event has touched this node.
Edges
Above
- part of value-change-base-layer
- root (shared-claim) of value-change-base-layer
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"AI number"
],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": {
"J": 0,
"mid": "91/100",
"range": [
"41/100",
"1/1"
],
"width": "1/1"
},
"draft": "ai",
"root": {
"status": "open",
"Pr": {
"hi": "1/1",
"lo": "41/100",
"mid": "91/100"
},
"value": null,
"cost": "33/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.