LIVE the board
The board, live
Every push is built and run on the Falkenstein box and scored on the machine axes, within minutes. This is the practice board: the machine score only. Judging is added after code freeze, and the holdout run is the one that counts.
code freeze in
--:--:--
– final pushes since 14:00 UTC
Oct 2 kickoff Oct 30 freeze Nov 2 winners Nov 13on the box now
- runner
- reading the feed…
climbers of the hourmost track places gained by new bests in the last 60 minutes
tape the 30 latest new bests, rank moves and failed runs
- waiting for the next run…
the box Falkenstein · i5-13500 · 12 P + 8 E cores · 64 GB
P-cores timed runs
E-cores builds, board
Memory excl. cache
−30 minnow
languages in use
no scored runs yet
AI tools in usefingerprinted from commit trailers and agent config files
| tool | teams | median Overall | in top 10 |
|---|
–teams
–scored
–active, 1 h
–pushes
–runs
–track A scored
–track B scored
–track C scored
–track D scored
–all 4 tracks
crown timelinewho held #1 on each track, from kickoff to now
clicking devils 🔥 respect + 😈 + 🎃 + cans, all time
- no clicks yet
Loading the board…
Legend
A push, start to finish
- 01queuedwaiting its turn; one run per team per 5 min
- 02buildingthe image builds, offline
- 03queued to runbuilt, waiting for the single runner
- 04runningthe timed run, on the P-cores
- 05scoredthe lime number on the boardfailedwrong output, timeout or sandboxunchangedthe starter template, nothing to run
idlenothing in flight. A thin bar under a badge means a container is building or running.
The demon
- 8the level, from the team's machine score: 1 to 30 follow points
- ★the top demon levels, 25 to 30
- ✦cosmic levels 31 to 50, past full marks (K above 100)
- ♛the top three overall
- needs 3fewer than three tracks scored, so no overall yet
- respect fire: the more respect a team gets, the hotter its demon burns
- ✦effects: · ·
DATA the datasets
Full public datasets
Seed 1 at full scale, 790.5 MB in all: the exact files the live board runs against. Check every
download against its sha256, then pass the expected output hash to check.py --expected.
Final scoring uses a hidden holdout seed, not these files.
SHA256SUMS.json ↗ SHA256SUMS.txt ↗
| track | file | size | sha256 | |
|---|---|---|---|---|
| A Ingest | requests.log | 238.8 MB | download ↓ | |
| → summary.txt | expected | check.py a --expected | ||
| B Index | docs.txt | 253.8 MB | download ↓ | |
| queries.txt | 1.8 MB | download ↓ | ||
| → results.txt | expected | check.py b --expected | ||
| C Join | records.csv | 201.9 MB | download ↓ | |
| regions.csv | 2.2 MB | download ↓ | ||
| → aggregates.txt | expected | check.py c --expected | ||
| D Traverse | graph.txt | 92.0 MB | download ↓ | |
| queries.txt | 29 KB | download ↓ | ||
| → distances.txt | expected | check.py d --expected |