root@construct:~/logs/fable-5-fallback-route$
<-- back to /logs
2026-06-09//LOG

Model handoffs need to be traceable

When a product changes the model executing a request, I want that switch to be visible when I need it. At the Fable 5 launch on June 9, 2026, Anthropic said sensitive requests would be routed to Opus 4.8. That safety route was part of the product, so the name in the selector could not explain where every answer came from. The same question applies to any handoff between executors: who received what, and who checks the result.

A transition can work without attracting attention. When an answer changes unexpectedly, though, I need information to investigate. Which part was forwarded? Did the next executor receive the whole objective or a fragment? Who checks that the response still answers the request? If this stays hidden even from whoever has to review the work, I end up depending on what the interface decides to show.

I also do not need a screen showing every internal connection whenever I ask something. I want details available when they help. An indication of the route and the material handed over gives me a better starting point than guessing from writing style. Identifying a model through its punctuation sounds like a terrible use of my afternoon.

In the coordination setup I want, an executor receives a bounded assignment and the coordinator checks the delivery against it. A confident message does not make that connection on its own. Reformulating a problem can help solve it, and it can also change the request without anyone noticing. When an answer comes back, the coordinator should check whether it resolves the assigned task or a more convenient version of it. Only after it matches the original objective can anyone mark it complete. If I have to reconstruct the original request myself, I am still doing the coordination I tried to delegate.

Model handoffs need to be traceable | The Broad Way