Write a short user-facing result for each case.
| Case | Facts |
|---|---|
| A | Registration was recorded. Confirmation is queued. The account view failed to load. |
| B | A remote source received a send request. The response was lost; its effect is unknown. |
| C | An authorized reviewer recorded a rejection. Another person was refused permission to review. |
Engineering Depth
For B, retain the original operation ID, input and source binding. A retry's correlation ID may change; it does not identify a new business intent by itself.
If the source can establish that the original effect did not occur, follow its retry contract. Otherwise preserve uncertainty. CS-09.
Your Reflection
What is known, what is unknown, and what can safely happen next?
Saved in this browser. Export a copy before changing devices.
Worked Discussion
| Case | Result and next action |
|---|---|
| A | Registration recorded; confirmation pending; view unavailable. Retry the view. |
| B | Send outcome unknown. Reconcile the original operation before an unsafe resend. |
| C | First review completed with rejection. Second review request was refused. |
Now replace a pure label formatter with a network lookup. The lookup story needs failure handling; the pure formatter can remain total.