02
Book the airport shuttle
The request already knows the reservation, the flight, the terminal and whether you have cleared customs. Today that form captures a name, a phone number and a headcount, with no link to a booking at all.
Compare it with the today/with-the-portal board beside the form. Then open the Auckland Downtown booking, where no shuttle runs, and see how the portal says so rather than offering something that cannot happen.
BRIEF §3.5 · PROPOSAL §4 — SHUTTLE
Needs a booking open — stop 01 does that in one tap.
03
Make the reservation system fail
Add an extra and it works. Then pick one of the four ways RCM actually misbehaves and add another. Nothing is charged twice, nothing silently succeeds, and a change whose outcome is genuinely unknown says so.
Choose “RCM never answers”, add an extra, then open the engine room. The request is logged before it leaves, sits as unknown, and the reconciliation pass reads RCM back and settles it about twenty seconds later.
BRIEF §3.2, §5 · PROPOSAL §4 — PLATFORM
The button in the black bar at the top opens the engineering view — every write to the reservation system, every access attempt, and how stale the data is. Off by default because customers should never see it; here because a document cannot demonstrate any of it.
Anything marked Mocked tells you what is standing in for something real, and which question discovery settles before it can stop being a stand-in. We would rather show you the seams than paper over them.