The problem
"Where am I this week?" deserves a number, not a model's guess.
Why I have it
Training questions have exact answers in the data. Kobe computes them in code, so the answer is the same every time and costs nothing to produce.
What it does
- Reads the watch data and what the gym has programmed for the week.
- Answers the week, today, the plan and what's next, computed in code.
- Hands workout design to Fraser and the wind-down to Huberman.
Where it helped
- Everyday asks (the week, yesterday's numbers, tomorrow's workout) are answered in code with no model call, checked Oct 17.
- Before Kobe had one ordered dispatcher, 7 of 10 routing layers needed fixes within 48 hours for the same kind of question.
Who it keeps score for
Every rep ends up as a number.
Kobe turns days like this into the week's numbers: what I did, how it compares with the plan, and what's next, computed in code from the watch. CrossFit is my reset; Kobe makes sure the numbers behind it are right.
How it works
One message, step by step
Each step lights up in turn. The names are the real components in the code.
- TelegramI ask a numbers question.
- Miya's runnerGives it a trace id.
- The ladderRecognizes a numbers question in code.
- Kobe's dispatcherOne ordered table of commands, all in code.
- The vaultWatch data and the gym's week, from one SQLite file at home.
- ValidatorChecks the reply against what's true.
- Word for wordExact numbers go out exactly as computed.
Not built yet
- Kobe's model calls are logged, but not yet held to the shared budget gate.