updateless-engineering-value-exists
leaf/assumption · drafted
Statement
At least one situation that arises between humans and AI systems, developers selecting systems on their predicted policies or a shutdown commitment a fully updated system would not renew, is one in which the updateful and the updateless prescriptions differ, so at least one engineering decision depends on which is followed.
Source
projects/deference/note-dump-2026-08-11/wiki/open-problems.md, Research direction: trust the policy, not the decision rule (the maintainer, 2026-07-25): "Value is an instrumental notion, and no decision rule is optimal across all embedded environments (Death in Damascus and Counterfactual Mugging are both in the family the scope condition excludes)."
projects/deference/note-dump-2026-08-11/notes/li-deference.md, open problem Decision theory: "The framework here, like DDB, is decision-theoretically unambitious. It does not take a well-considered stance on CDT vs EDT, it does not seek to model the decision-theoretic consequences of environments containing powerful predictors, and it ignores updatelessness."
Notes
The existence half of the engineering-value crux, split from the magnitude half because the crux as stated is about magnitude, and any predictor-rich human–AI situation witnesses existence, so the two deserve separate numbers. This leaf is the given parent of the magnitude table's rows that name a concrete engineering situation.
Not a duplicate of updateless-engineering-value, the cases table beside it in the frame's list: that table weighs how much the dependence is worth; this leaf says only that it exists.
Author and human events
Author @smithy-verity; version 1; size S.
No human event has touched this node.
Edges
Above
- part of stance-and-level
- root (shared-claim) of stance-and-level
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": "31/40",
"range": [
"11/40",
"1/1"
],
"width": "1/1"
},
"draft": "ai",
"root": {
"status": "open",
"Pr": {
"hi": "1/1",
"lo": "11/40",
"mid": "31/40"
},
"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.