Define each action outcome
Synthetic A1 button says “View sessions” and needs destination D1 listing sessions. A2 says “Request a callback” and needs D2 callback-request entry. Draft links both to D1. Local policy requires action meaning and destination function to match.
| Action | Draft/required | Correction |
|---|---|---|
| A1 view | D1/D1 | None |
| A2 callback request | D1/D2 | Change to D2 |
Match the action/destination tuple
- Read action meaning
- Inspect supplied destination function
- Retain A1/D1
- Correct A2 to D2
A destination with unverified function cannot be labelled ready from its name alone.
How many links need correction?
Show the worked answer
One, A2. Both links working as navigation would not make the callback action accurate.
Correct the mismatched route
| Case | Decision or result | Reason |
|---|---|---|
| A2 opens session list | Reject tuple | No callback request entry |
| A2 opens D2 | Matches supplied action | Request destination |
Keep the action text with its destination key in the handoff sheet so future route edits preserve intent.