E.13:4 - Solution
Use ProxyToValueAlignment to recover the intended value, the proxy’s current use, the value at risk, and the justified repair or stop. A short answer or local repair is enough when it settles the case. When later review, reuse, or reliance needs a note, use the fields below that change the conclusion.
ProxyToValueAlignment:
ObjectOfConcern:
IntendedValueOrObjective:
ProxyOrVisibleMeasure:
ProxyKind:
CurrentProxyUse: <orientation | measure | target | incentive | gate | release argument | decision driver | reputation signal | repair target>
AffectedDecisionOrWork:
ProtectedQualities:
WhatImproved:
WhatGotWorse:
MinimallyViableValueSlice:
AdmissibleUseNow:
BlockedOverread:
RepairOrStop:
ReopenCondition:
Keep any note as small as the case allows. Its fields help explain how the proxy serves the intended value; fill only those needed for the current conclusion, repair, stop, or later reliance.
E.13:4.1 - Name the Value Before the Proxy
Name the intended value, objective, or practical payoff in terms of the work it is supposed to improve. If only the proxy can be named, lower the claim: the project has a measure, not a demonstrated value relation.
E.13:4.2 - Type the Proxy Use
A proxy can be harmless as an orientation cue and dangerous as a target. State the current proxy use explicitly.
| Proxy use | Admissible use | Danger |
|---|---|---|
| Orientation cue | Helps decide where to look next. | Mistaken for evidence of value. |
| Measure | Reports one declared characteristic under C.16. | Treated as the whole objective. |
| Target | Work is optimized to move the proxy. | Goodhart pressure. |
| Incentive | People or agents are rewarded for the proxy. | Behavioral distortion and gaming. |
| Gate or release argument | Passage depends on the proxy. | Proxy becomes authority. |
| Reputation or status signal | People, teams, models, or patterns are ranked by the proxy. | Surrogation and status gaming. |
| Repair target | The object is changed to raise a coordinate or score. | Apparatus is added instead of value. |
E.13:4.3 - Ask What Got Worse
Whenever a proxy improves under optimization pressure, ask what became worse or more fragile. Check at least usability, affordability, safety or harm boundary, maintainability, domain fit, source preservation, decision quality, learning, and neighboring-pattern fit when they are live in the case.
If nothing worsened, say which loci were checked. If no loci were checked, do not claim value alignment.
E.13:4.4 - Require a Minimally Viable Value Slice
Require a minimally viable value slice: one compact case, worked slice, observation, trial, user/operator moment, or decision replay where the intended value is visible enough for the declared use. State whether the slice is an illustration, desk replay, or observed use, and what conclusion it supports.
The value slice may be small. It must show the intended value rather than merely the proxy. A worked illustration can explain how a proposed repair would serve that value; it does not by itself establish an observed gain. Keep any claim about actual improvement within the comparison and evidence that support it.
E.13:4.5 - Repair by Value Movement
When the proxy has displaced the value, repair one of these:
- where the governing rule permits it, change the proxy use from target/gate/incentive to orientation or bounded measure; if a binding requirement must change, propose the amendment under its authority and keep the current requirement in force until that amendment takes effect;
- add a protected quality or counter-metric that names the value at risk;
- change the work or design so the value slice improves, not only the proxy;
- split the claim: one measure report, one value claim, one assurance or gate claim if needed;
- stop the value claim until a value slice or better proxy relation exists.