| Case | Proposed shortcut |
|---|---|
| A: engine B now handles new work; engine A's old operation is unresolved | Ask the currently configured engine B what happened. |
| B: worker generation 8 took over; generation 7 returns late | Accept generation 7's result because it still owns a Rust value. |
| C: a private helper was replaced | Preserve its old three-call sequence because a test expects it. |
Predict what each shortcut could break.
Engineering Depth
A recovery record must retain its source binding. A worker result may need a current claim or generation check before it can settle stored work. These distributed mechanisms lie beyond the in-memory reference.
For C, trace the assertion to the consumer's requirement. Keep required behavior and compatibility; retire obsolete private arrangements. CS-06, CS-11.
Your Reflection
Which case changes authority? Which needs a decision about old work?
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.
Worked Discussion
A needs evidence from the original source or an authorized migration. B needs the current right to settle. C needs the actual consumer promise, which may never have required three calls.