docs: bind routing numbers to the published artifact - #16
Merged
Conversation
Six numbers here were hand-maintained and had drifted: 41+ models (the catalog serves 66), 78% savings in three places against no stated baseline, 14 scoring dimensions (the scorer runs 15), and a free tier described as 9 models in one table and 8 in another — in the same README. They now regenerate from blockrun.ai/brand/numbers.json, checked offline in CI against the committed snapshot. The two 'Saved 78%' comments in the code samples are updated by hand: they sit inside fenced blocks, which the sync script deliberately leaves alone so that documenting a marker does not rewrite it.
VickyXAI
force-pushed
the
feat/brand-numbers-sync
branch
from
July 26, 2026 05:11
4bd8206 to
d1e0fef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consumes blockrun#288's
/brand/numbers.json.What was wrong
The free-tier count contradicted itself inside the same README — one table said 9, another said 8. That is the failure mode this replaces: every number maintained by hand, in more places than anyone remembers to check.
The dimension count was wrong across the whole org, in both directions: the code comments said 14, but the scorer builds a 14-entry array and then pushes the agentic dimension, so 15 are actually scored. Corrected at the source in ClawRouter#220.
Code samples
The two
// 'Saved 78%'comments are updated by hand rather than marked. They sit inside fenced blocks, whichsync-brand-numbers.mjsdeliberately skips — otherwise documenting a marker would rewrite it.CI
--checkruns offline against the committedbrand-numbers.jsonand never fetches, so a blockrun.ai deploy in progress cannot fail this repo's CI.Suite on this branch: 218 passed, 12 skipped, 0 failed.
Diff scope
Four files, all additive or docs: