MAKE IT BETTER / SWITCHYARD
See why
the courier waits.
By Alvin
Help a reader understand a jam before changing its rules. “Make the agents smarter” leaves the success condition open. An inspectable decision gives the agent a clearer improvement to implement.
Complete brief / keep the acceptance checks
Improve a separate copy of Switchyard for someone learning why a courier waits. Preserve routing, sequential reservations and collision rules. Add a last-tick inspector showing each courier’s starting cell, target, chosen move or safe wait, and a reason derived from its actual decision. Keep a bounded history of twenty completed ticks. Selecting a history row shows a read-only snapshot; Return to live restores the active view. Reset clears history. Preserve One tick, paused wall editing, keyboard controls and notebook validation. Compare the original and instrumented depot from the same start for 100 ticks. Show their positions, delivery totals, waiting counts and collision checks.
Why the prompt changes the build
The engine needs to return a structured decision record alongside its state update. The interface needs a live/history distinction. A plausible explanation invented after the tick would miss the requirement to report the decision actually taken.
Proposed improvement: the existing routing tests remain the baseline. The history inspector and its comparison need a new implementation and checks.