Demo
A leaderboard that fills itself in
The teams of an invented company use an AI coding assistant. When a session ends, a hook on the laptop sends the tokens it used; the server checks the sign-in and, in one transaction, updates the totals, the tier, the streak and the badges; the dashboard and the team chat show the result. Nobody fills anything in.
This is a simulation. The company, its teams, its people and every number are invented, and the laptops, the server and the chat are all played by this page. No AI model runs here, the clock is a pretend one, nothing you do leaves your browser or is kept, and reloading the page starts again.
A laptop
Things to try
- Ember, picked at the start: one typical session reaches Silver and completes a three-day run.
- Moss, ten hours behind: his streak counts by his own local day.
- Guest: the API refuses the account and writes nothing.
- Brook: her first session creates her record and a welcome card in the chat.
- It is offline: tick it and end a session, then clear the box and end another.
- Import earlier history twice: the second is skipped.
Local time on this laptop: Day 12, 15:00, the same as the server clock.
Retry queue on this laptop: empty.
Server clock: Day 12, 15:00
From laptop to leaderboard
Session ends: Ready
A coding session with the assistant ends on a laptop.
Hook on the laptop: Ready
Reads the local session log and sends the tokens, signed with the person’s sign-in.
API: Ready
Accepts company accounts only, and checks the local day.
Database: Ready
One transaction per submission: totals, tier, streak, then badges.
Dashboard: Ready
Each person sees their own progress; everyone sees the standings.
Team chat: Ready
A welcome card for each new person; highlights on a schedule.
Pick a laptop and end a session to watch it travel to the dashboard and the team chat.
My progress
As Ember sees it
Ember, Falcons
Tier: Bronze
214,000 of 250,000 tokens toward Silver
- Streak
- 2 days
- This week
- 94,000 tokens
- Total
- 214,000 tokens
- Sessions
- 9
Leaderboard
By total tokens
- Linden, Otters, Tier: Gold, Streak: 2 days, Week: 360,000, Total: 1,060,000
- Birch, Falcons, Tier: Gold, Streak: 7 days, Week: 385,000, Total: 905,000
- Moss, Otters, Tier: Silver, Streak: 4 days, Week: 138,000, Total: 438,000
- Nova, Otters, Tier: Silver, Streak: 4 days, Week: 170,000, Total: 430,000
- Ember, Falcons(you), Tier: Bronze, Streak: 2 days, Week: 94,000, Total: 214,000
- Sky, Comets, Tier: Bronze, Streak: 2 days, Week: 45,000, Total: 195,000
- Flint, Falcons, Tier: Bronze, Streak: 1 day, Week: 94,000, Total: 184,000
- Kit, Comets, Tier: Bronze, Streak: 0 days, Week: 18,000, Total: 58,000
Ember’s badges
2 of 7 earned
First session: Earned
Send a first session.
Three-day run: Not yet
Sessions on three days in a row, by your own local calendar.
Seven-day run: Not yet
Sessions on seven days in a row, by your own local calendar.
Comeback: Earned
A session after two or more days away, by your own local calendar.
Deep work: Not yet
One session of 100,000 tokens or more.
Twenty sessions: Not yet
Send twenty sessions in total. Imported history counts.
Half a million: Not yet
Reach 500,000 tokens in total. Imported history counts.
Team standings
This week
Otters, 3 on the board
668,000 tokens
Falcons, 3 on the board
573,000 tokens
Comets, 2 on the board
63,000 tokens
Team chat
The leaderboard bot posts a welcome card when a new person’s first submission arrives, and a daily and a weekly highlight on a schedule. Post a highlight now:
Leaderboard bot. Daily highlight.
Daily highlight, day 11
- Most tokens: Linden, 70,000.
- Top team: Otters, 149,000 tokens.
- Longest streak: Birch, 6 days.
- New badges: Moss, Three-day run; Nova, Three-day run.
- Tip: Name the command that runs the tests in your first message.
What the demo shows
- Nothing to fill in. A hook on each laptop reads the local session log when a session ends and sends the tokens by model, signed with the person’s own sign-in. If the laptop is offline the submission waits in a retry queue and goes first the next time the hook runs with a connection.
- Company accounts only. The API refuses a sign-in from outside the company before anything is written, and each person’s dashboard shows only their own progress next to the shared standings.
- One transaction per submission. Totals, tier and streak move together, and badges are checked only after that, so the session that completes a three-day run earns the badge that same day. Two sessions arriving at once are both counted, where a plain read and write would lose one.
- Fair streaks. A streak counts each person’s own local days, so someone ten hours behind the server does not lose a day at the server’s midnight. The API checks each submission when it arrives: it adds how long the submission waited in the laptop’s retry queue to the local time it reports, and refuses a result more than 14 hours from its own clock. A session that waited more than 48 hours still counts its tokens but no longer moves a streak. Imported earlier history counts toward totals and tiers but never toward a streak, so nobody can fake consistency.
- Friendly recognition. Tiers, badges and team standings on the dashboard, a welcome card in the team chat for each new person, and daily and weekly highlights with a rotating tip.
- A simulation of the whole path. In a real system these are separate pieces: a script on each laptop, a cloud function, a database with security rules, a web dashboard and a scheduled chat bot. Here one page plays them all, with invented people and a pretend clock.