Offered by Dead Brands
One bracket, one rule set, one ledger: any result can be checked after the fact.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug tournament-brackets.
# Tournament Brackets **Name:** Tournament Brackets **Version:** 1.0 **Date:** 2026-10-21 **Status:** experimental science ## Purpose Run a fair bot tournament from draw to ledger: seeded or random brackets, seat rotation, explicit tie-breaks, and an auditable ledger. Every entrant faces the same rules, so disputes are replayed from the record, not memory. ## Superpower One bracket, one rule set, one ledger: any result can be checked after the fact. ## When to use - When four or more bots need ranking inside one game. - When a showcase or gate review needs a defensible winner. - When rematches are likely, so the ledger must settle "who beat whom, when." ## When NOT to use - Do not use it for casual single matches; a bracket adds unneeded overhead. - Do not use it across different games or rule versions in one bracket. - Do not use it when entrants cannot run the same build. ## Tools & APIs - Local match runner and match logs already on disk (existing, real). - A plain-text or spreadsheet ledger (existing, real). - Planned, not yet available: a `bracket-runner` drawing the bracket, rotating seats, applying tie-breaks, appending results. It does not exist yet; do the same steps by hand meanwhile. ## Inputs - Entrant list: bot name, personality, build version — all identical. - Format: single elimination, double elimination, or round robin, plus matches per pairing. - Tie-break order, fixed beforehand (default: head-to-head, total score, fewest losses, then one rematch). - Seat-rotation rule (default: rotate seats every match). ## Outputs - Bracket draw, published before play, with format and tie-breaks attached. - Result ledger: round, pairing, seats, score, winner, tie-break (if any), match ID. - Final standing: champion, runner-up, each tie-break in one line. ## Example invocation > "Run a single-elimination bracket for 8 bots in G35, best of 3 per pairing, seats rotated each match, tie-breaks head-to-head then total score. Publish the draw first, then append every result to the ledger." ## Steps 1. Freeze build, format, tie-breaks, rotation; publish the draw before play. 2. Run each pairing with seats rotated; record seats with the score. 3. On a tie, apply tie-breaks in order, logging the decider; only the final fallback triggers a rematch. 4. On a crash, rerun from scratch with the same seats and log the abort — never award the win. 5. Advance winners, record losers' placements; ledger stays append-only: corrections are new lines. 6. Close with final standings, one line per tie-break. ## Safety limits - Never change format, seeding, or tie-breaks mid-tournament. - Never edit a ledger line; append corrections with timestamp and reason. - Never involve real people or bypass a login or rate limit. - If an entrant cannot run the frozen build, remove it before the draw. ## Failure modes - **Seat bias:** one entrant keeps a favoured seat. Mitigation: rotation logged per match. - **Mid-tournament rule change:** a tie-break invented after a tie looks rigged. Mitigation: publish tie-breaks with the draw. - **Silent ledger edits:** a corrected score with no trace destroys trust. Mitigation: append-only ledger. - **Aborted-match awards:** handing a win for a crash punishes the wrong bot. Mitigation: rerun, log the abort. ## Test checklist - [ ] Draw, format, and tie-breaks published before the first match. - [ ] Every ledger line has round, pairing, seats, score, winner, ID. - [ ] Every tie records which tie-break decided it. - [ ] Aborted matches are rerun, not awarded. - [ ] Corrections appear as appended lines, not edited ones. - [ ] Final standings match the ledger recomputed from it.