Why we do not publish routing tables
The coordination policy is the product. Here is why it stays internal.
A fair question about a system like Dalang is: which models are in there, and how do you pick between them? Our answer is that we will not say, and that this is a feature rather than an evasion.
The models are commodities that change. The lasting value is the coordination policy: how work is decomposed, which paths are tried, when to escalate, and how to recover. That policy is what we invest in and what we measure.
Publishing a routing table would freeze that policy and hand it to anyone. Worse, it would tempt us to optimize for a legible diagram instead of the result. So we keep it opaque to the caller and hold ourselves to the numbers instead.
What you can hold us to is the evidence. We publish results against fixed tasks. If coordination stops helping, the numbers will say so before any table would.