robotensor/icil-competition-results
ICIL competition results The signed, append-only result store of the RoboTensor one-demonstration in-context imitation learning competition. The dashboard is a pure reader of this repository: everything a visitor sees is here, and anyone can check it without trusting the site. What a duel publishes Two models run an identical unit list — same tasks, same initial states, same demonstration per unit, same seeds. Each skill is one success rate; the score is their… See the full description on the dataset page: https://huggingface.co/datasets/robotensor/icil-competition-results.
ICIL competition results
The signed, append-only result store of the RoboTensor one-demonstration in-context imitation learning competition. The dashboard is a pure reader of this repository: everything a visitor sees is here, and anyone can check it without trusting the site.
What a duel publishes
Two models run an identical unit list — same tasks, same initial states, same demonstration per unit, same seeds. Each skill is one success rate; the score is their mean; the challenger takes the crown only by beating the reigning model's average by the published margin. Every per-unit outcome for both sides is published, with three clips per unit: the demonstration the model was shown, the reigning model's attempt and the challenger's.
Layout
manifest.json validator key, spec version and fingerprint, pool id
tracks/<track>/head.json the newest record and who holds the crown
tracks/<track>/index-NNNN.jsonl one '<canonical json>\t<ed25519 signature>' per record
tracks/<track>/queue.json challengers waiting for a slot (rewritten, not signed)
events/<track>/<event_id>.json the full record: every unit, both sides
media/<sha[:2]>/<sha>.mp4 clips, addressed by content hashRecords are canonical JSON signed with the validator's ed25519 key (manifest.validator_key), so a line cannot be edited after the fact without the signature failing.
Verifying it
hf download robotensor/icil-competition-results --repo-type=dataset --local-dir ./store
icilval store verify ./store # signatures, sequence, events, media, schemaThe unit list of any duel can be regenerated from published fields alone — the specification version, the track, both models' keys and revisions, and the pool id — so a third party can confirm which units a duel actually ran.
Current contents
Store schema 2 (per-skill scoring): the genesis record crowning `robotensor/bpp-genesis`, and the organizer's smoke duel — the baseline against a copy of itself on pool 2026.09-v2, 18 units per side, every unit tied, which is the point: identical weights on identical units cannot clear the margin.
MIT.
