CS-15 · What-if Probes

Aliases: counterfactual; variation; derivability; independent change; consequence tracing.

For each change, predict the consequence from the story, then telescope to explain it. These are reasoning prompts, not an automatic test or a prescribed implementation.

What changes?	What must be followed?
A label becomes a network lookup.	Which newly selected story owns the real failure; the original pure label need not inherit it.
Preview wording changes; archival wording does not.	Whether the two promises accidentally share a reason to change.
The one organization-owned identifier policy changes.	Both intended consumers must follow it; surrounding presentation stays independent.
Registration stops collecting a password.	That choice does not decide every later login policy.
Pre-confirmation entry changes from allowed to blocked.	The selected contract must change actual initial and later entry behavior.
A configured provider has the same Rust type as another instance.	The occurrence must retain the selected actual provider, not merely its type.
A record changes after admission.	Which resource/lifetime prevents substitution, or where current version is re-established.
A user leaves before a follow-up runs.	Who still owns the obligation and how it survives the claimed boundary.
A response is lost after the effect.	Original operation and intent survive; a changed form is different work.
A newer worker claims the operation.	Which generation may settle; consuming the older local value is insufficient.
An engine is replaced for new work.	Existing unknown work retains its original binding unless an authorized migration says otherwise.
An implementation is rewritten without changing the promise.	Which evidence protects the commitment and which incidental checks can retire.

Related: CS-03, CS-05, CS-06, CS-09, CS-12.

Your Reflection