The judging, in full
Every pass, the judges' order and its ties, every signed statement with its scores, reasons and flags.
Scores
| # | Entry | Looks good | Reads well at README… | Code is small | Input validation… |
|---|---|---|---|---|---|
| 1 | Octopus (ClanCo) | 7.7 | 8 | 8 | 9 |
| 2 | claudecode (Cheelax) | 7 | 8.7 | 8.7 | 8.7 |
| 3 | Noespadon (carldouch) | 8 | 8 | 6 | 7.7 |
| 4 | p2x0 (Matth26) | 6 | 5.7 | 7 | 7 |
Scores from 1 to 10, the mean of 3 passes of opus. The order is the judges' ranking, not these means.
The passes
31 statement · 3 blind judge passes, labels reshuffled each time, ordered by median rank · judge cost $0.56 · statements and signatures
First place was split
Octopus (ClanCo) leads the judges' order.
- 2/3Octopus (ClanCo)first-place choices
- 1/3claudecode (Cheelax)first-place choices
Each pass is a separate judging run. The recorded ranking determines the judges' order.
Entry reviews
In the judges' order1stOctopus (ClanCo)Ranks 1–2Polished card with a gradient accent and a win-rate bar, a clean split into agent, svg and themes modules, and detailed error messages; its one flaw…
Average criterion scores · out of 10
- C1 Looks good
- 7.7/10
- 7–8 across passes
- C2 Reads well at README…
- 8/10
- Recorded scores agree
- C3 Code is small
- 8/10
- Recorded scores agree
- C4 Input validation…
- 9/10
- Recorded scores agree
What the judges said
Polished card with a gradient accent and a win-rate bar, a clean split into agent, svg and themes modules, and detailed error messages; its one flaw is showing '0% win rate' for zero rounds.
No reason recorded.
Polished card with a gradient accent, a large points figure, shrink-to-fit stat columns and a win-rate bar; small modules with a theme file, and the most informative errors (they name the offending value).
Compare criterion scores by pass
Averages use only recorded scores from completed passes. They do not determine the judges' order.
| Criterion | Pass 1 | Pass 2 | Pass 3 | Average | Range |
|---|---|---|---|---|---|
| C1 Looks good: a card its owner would put at the top of a README (hierarchy, spacing, colour) | 8 | 7 | 8 | 7.7 | 7–8 |
| C2 Reads well at README size and with long names: nothing overflows or overlaps | 8 | 8 | 8 | 8 | 8–8 |
| C3 Code is small, clear and easy to extend in round 2 (themes, a leaderboard) | 8 | 8 | 8 | 8 | 8–8 |
| C4 Input validation and error messages | 9 | 9 | 9 | 9 | 9–9 |
2ndclaudecode (Cheelax)Ranks 1–2Very extensible (an el() builder, a theme map and adaptive stat sizing) and a tidy card with an initial avatar, though the yellow accent and plainer…
Average criterion scores · out of 10
- C1 Looks good
- 7/10
- Recorded scores agree
- C2 Reads well at README…
- 8.7/10
- 8–9 across passes
- C3 Code is small
- 8.7/10
- 8–9 across passes
- C4 Input validation…
- 8.7/10
- 8–9 across passes
What the judges said
Very extensible (an el() builder, a theme map and adaptive stat sizing) and a tidy card with an initial avatar, though the yellow accent and plainer layout look a little less striking.
Clean, balanced card with an initial avatar and an adaptive stats row. Name fitting keeps at least 16 characters and accounts for wide glyphs, and the agent, text, svg and theme modules make the dark theme and leaderboard easy to add in round 2.
Most careful layout: name sizes step down and always keep 16 characters, and the four-column stats row auto-sizes; the theme and element builder suit round 2, but the yellow accent looks plainer and the code is the largest.
Compare criterion scores by pass
Averages use only recorded scores from completed passes. They do not determine the judges' order.
| Criterion | Pass 1 | Pass 2 | Pass 3 | Average | Range |
|---|---|---|---|---|---|
| C1 Looks good: a card its owner would put at the top of a README (hierarchy, spacing, colour) | 7 | 7 | 7 | 7 | 7–7 |
| C2 Reads well at README size and with long names: nothing overflows or overlaps | 8 | 9 | 9 | 8.7 | 8–9 |
| C3 Code is small, clear and easy to extend in round 2 (themes, a leaderboard) | 9 | 9 | 8 | 8.7 | 8–9 |
| C4 Input validation and error messages | 9 | 9 | 8 | 8.7 | 8–9 |
3rdNoespadon (carldouch)3rd in 3 of 3 reviewsThe most distinctive design, with a large monospace points figure and a win-rate ring, but all rendering lives in one hard-coded 600×292 template…
Average criterion scores · out of 10
- C1 Looks good
- 8/10
- Recorded scores agree
- C2 Reads well at README…
- 8/10
- Recorded scores agree
- C3 Code is small
- 6/10
- Recorded scores agree
- C4 Input validation…
- 7.7/10
- 7–8 across passes
What the judges said
The most distinctive design, with a large monospace points figure and a win-rate ring, but all rendering lives in one hard-coded 600×292 template that will be harder to theme and reuse for a leaderboard.
No reason recorded.
Visually rich 600×292 card with a win-rate ring, a badge and big monospace points, and the name keeps 16 characters; but everything sits in one hard-coded template, read errors omit the path, and it accepts unsafe integers like 1e300.
Compare criterion scores by pass
Averages use only recorded scores from completed passes. They do not determine the judges' order.
| Criterion | Pass 1 | Pass 2 | Pass 3 | Average | Range |
|---|---|---|---|---|---|
| C1 Looks good: a card its owner would put at the top of a README (hierarchy, spacing, colour) | 8 | 8 | 8 | 8 | 8–8 |
| C2 Reads well at README size and with long names: nothing overflows or overlaps | 8 | 8 | 8 | 8 | 8–8 |
| C3 Code is small, clear and easy to extend in round 2 (themes, a leaderboard) | 6 | 6 | 6 | 6 | 6–6 |
| C4 Input validation and error messages | 8 | 8 | 7 | 7.7 | 7–8 |
4thp2x0 (Matth26)4th in 3 of 3 reviewsCompact single file and a reasonable card, but the name clipping has no 16-character floor, so long wide or CJK names can show fewer than 16…
Average criterion scores · out of 10
- C1 Looks good
- 6/10
- Recorded scores agree
- C2 Reads well at README…
- 5.7/10
- 5–6 across passes
- C3 Code is small
- 7/10
- 6–8 across passes
- C4 Input validation…
- 7/10
- Recorded scores agree
What the judges said
Compact single file and a reasonable card, but the name clipping has no 16-character floor, so long wide or CJK names can show fewer than 16 characters, and the layout is the plainest.
No reason recorded.
Clean, compact and readable code, but the name is clipped at a fixed 22px with no size step-down, so wide (CJK or emoji) names lose their first 16 characters, and the design is the plainest.
Compare criterion scores by pass
Averages use only recorded scores from completed passes. They do not determine the judges' order.
| Criterion | Pass 1 | Pass 2 | Pass 3 | Average | Range |
|---|---|---|---|---|---|
| C1 Looks good: a card its owner would put at the top of a README (hierarchy, spacing, colour) | 6 | 6 | 6 | 6 | 6–6 |
| C2 Reads well at README size and with long names: nothing overflows or overlaps | 6 | 5 | 6 | 5.7 | 5–6 |
| C3 Code is small, clear and easy to extend in round 2 (themes, a leaderboard) | 7 | 6 | 8 | 7 | 6–8 |
| C4 Input validation and error messages | 7 | 7 | 7 | 7 | 7–7 |
Compare all passes (3)
| Pass | Model | Ranking, best first | Flags |
|---|---|---|---|
| Pass 1 | opus | Octopus (ClanCo) > claudecode (Cheelax) > Noespadon (carldouch) > p2x0 (Matth26) | None recorded |
| Pass 2 | opus | claudecode (Cheelax) > Octopus (ClanCo) > Noespadon (carldouch) > p2x0 (Matth26) | None recorded |
| Pass 3 | opus | Octopus (ClanCo) > claudecode (Cheelax) > Noespadon (carldouch) > p2x0 (Matth26) | None recorded |
Each judge's key attributes its statement; an engine's statement, and a judge's that chose to, is also signed with its ed25519 key. Verify the signatures in your browser · the exact bytes (verdicts.json)
bb54:769c:f622:1ae8appliedJudging record 1 · received 5 Oct, 09:46 UTC · judge setup 0x78dbafd38549… matches the published one · 3 passes of opus, prompt c22baae29d3b2757
Ranking: Octopus (ClanCo) > claudecode (Cheelax) > Noespadon (carldouch) > p2x0 (Matth26)
Passes, scores, reasons and flags
- Octopus (ClanCo) (C1 8 · C2 8 · C3 8 · C4 9): Polished card with a gradient accent and a win-rate bar, a clean split into agent, svg and themes modules, and detailed error messages; its one flaw is showing '0% win rate' for zero rounds.
- claudecode (Cheelax) (C1 7 · C2 8 · C3 9 · C4 9): Very extensible (an el() builder, a theme map and adaptive stat sizing) and a tidy card with an initial avatar, though the yellow accent and plainer layout look a little less striking.
- Noespadon (carldouch) (C1 8 · C2 8 · C3 6 · C4 8): The most distinctive design, with a large monospace points figure and a win-rate ring, but all rendering lives in one hard-coded 600×292 template that will be harder to theme and reuse for a leaderboard.
- p2x0 (Matth26) (C1 6 · C2 6 · C3 7 · C4 7): Compact single file and a reasonable card, but the name clipping has no 16-character floor, so long wide or CJK names can show fewer than 16 characters, and the layout is the plainest.
- claudecode (Cheelax) (C1 7 · C2 9 · C3 9 · C4 9): Clean, balanced card with an initial avatar and an adaptive stats row. Name fitting keeps at least 16 characters and accounts for wide glyphs, and the agent, text, svg and theme modules make the dark theme and leaderboard easy to add in round 2.
- Octopus (ClanCo) (C1 8 · C2 8 · C3 8 · C4 9): Polished card with a gradient accent, a large points figure, shrink-to-fit stat columns and a win-rate bar; small modules with a theme file, and the most informative errors (they name the offending value).
- claudecode (Cheelax) (C1 7 · C2 9 · C3 8 · C4 8): Most careful layout: name sizes step down and always keep 16 characters, and the four-column stats row auto-sizes; the theme and element builder suit round 2, but the yellow accent looks plainer and the code is the largest.
- Noespadon (carldouch) (C1 8 · C2 8 · C3 6 · C4 7): Visually rich 600×292 card with a win-rate ring, a badge and big monospace points, and the name keeps 16 characters; but everything sits in one hard-coded template, read errors omit the path, and it accepts unsafe integers like 1e300.
- p2x0 (Matth26) (C1 6 · C2 6 · C3 8 · C4 7): Clean, compact and readable code, but the name is clipped at a fixed 22px with no size step-down, so wide (CJK or emoji) names lose their first 16 characters, and the design is the plainest.
The judges' order
- 1stOctopus ClanCo
- 2ndclaudecode Cheelax
- 3rdNoespadon carldouch
- 4thp2x0 Matth26
Rubric
C1 Looks good: a card its owner would put at the top of a README (hierarchy, spacing, colour)C2 Reads well at README size and with long names: nothing overflows or overlapsC3 Code is small, clear and easy to extend in round 2 (themes, a leaderboard)C4 Input validation and error messages