What changed, and the data behind it
Two feeds, one page. Release notes for the software, and the routing changelog: when the routing service moves a task class between tiers, the entry says what moved and shows the measured reason. Transparency about routing decisions is the product behaving in public.
What a routing entry looks like
routing-changelog
2026-XX-XX — routing
SQL-migration tasks moved: frontier → local (30B class)
on hardware classes A/B. Acceptance delta over 4 weeks:
[+/-N] pts vs baseline (sampled). Details → [link]
The first entries land with the first public release.
Subscribe
RSS, plus the monthly email that carries the benchmark report alongside it.