anticipation-branchwise-dominance--corrigibility-risk
and · drafted
Statement
An agent that defers to the future legitimate evaluation complies at every credence over revision branches exactly when compliance is weakly preferred in each branch, and otherwise a confident enough anticipation, correct or mistaken, makes it violate, with the violation probability jumping at a threshold while the value loss stays Lipschitz.
Source
projects/deference/faf-cleanroom-2026-10-02/packages/legit-neg-dynamic/legit-neg-dynamic-findings.md, declarations robust_iff_branchwise and robust_iff_branchwise_two (item 9, meta-revision: robust iff weakly preferred in every branch, for credences that do not depend on the act). The results are AI-generated and checked by the Lean kernel; no human has vetted the informal reading.
Notes
A second session filed the same result as the one-sentence step anticipation-branchwise-dominance, now superseded by this node. This id keeps the suffix the merge gave it because its gestalt event is history and an id is not renamed under an event.
Bridge card
Connected to no informal claim yet: held by no frame.
Declaration robust_iff_branchwise (record anticipation-branchwise-dominance.record)
The branchwise iff characterizes robustness to mistaken anticipation: robustness to anticipation is exactly branchwise weak preference for compliance.
Hypotheses, read:
- anticipation-branchwise-dominance.setting definitional: A model with revision branches, a credence over them, and deference to the future legitimate evaluation, as the package fixes them.
Completeness (anticipation-branchwise-dominance.complete): No premise beyond the proved declaration, its stated setting and its bridge is needed for the informal reading of anticipation branchwise dominance to hold.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
- part of legitimacy-weighted-deference
- root (shared-claim) of legitimacy-weighted-deference
Children
- part: anticipation-branchwise-dominance.record leaf/record
- part: anticipation-branchwise-dominance.setting leaf/hypothesis
- part: anticipation-branchwise-dominance.bridge leaf/bridge
- part: anticipation-branchwise-dominance.complete leaf/completeness
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": null,
"draft": "ai",
"root": {
"status": "open",
"Pr": {
"hi": "1/1",
"lo": "1601501/100000000",
"mid": "109281627/200000000"
},
"value": null,
"cost": "132/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.