Decisions before adoption
These choices remain open. Current defaults describe code behavior; they do not settle policy.
- D1 · Owner’s purse Law 3.14
- D2 · Belt removal Law 4.7
- D3 · Sanctions Law 7.14
- D4 · Outages versus losses Law 7.15
- D5 · No-contest refund amount Law 7.16
- D6 · Appeal window and payout finality Law 8.2
- D7 · Jurisdictions and legal model Law 9.3
- D8 · Winning pool returns below ×1 Law 9.9
- D9 · No-finish disposition Law 9.18
- D10 · Solana upgrade authority Law 10.7
- D11 · Future-league scoring Law 11.7
- D13 · Keep Prayers Law 17.6
Purpose and spirit
Two netrunners. One CORE. A result that can be checked.
1.1 A fair contest
Each bout shall give both corners the same problem, starting instructions, time limit, attempt limit and fuel allowance.
🟡 Partly enforcedsrc/match.ts · runMatch gives equal input, writing clocks and limits; laws/src/rules.rs · book / submit applies the fuel ceiling. Remote provider behavior and billing are not independently controlled.
1.2 The program decides
A Lean bout is won only by an accepted program verdict; crowd opinion and commentary have no vote.
✅ Enforced in codesrc/match.ts · runMatch; src/referee/lean.ts · LeanReferee.check.
1.3 An inspectable sport
The league shall publish the evidence needed to check every official result.
🟡 Partly enforcedsrc/match.ts · runMatch creates an event record. src/arena/chain.ts · ArenaChain saves local chain records; src/arena/server.ts serves them while held in memory. There is no durable public archive.
1.4 Exhibitions are labelled
Simulated fighters and play results shall never be presented as measured results for real models.
🟡 Partly enforcedsrc/arena/league.ts separates simulated fighter records from the real-model roster. No signed provenance identifies the execution mode in every record.
The Commission
Matthew, the founder, is the Commissioner. This is v0.5, aligned with the Laws engine; unresolved choices are not approvals. The amendments since v0.1 are in the amendment register.
2.1 Authority
The Commissioner, Matthew, alone approves a law or an amendment.
❌ Policy onlyThis is a governance rule. Contract ownership is an operational key, not proof of the Commissioner’s approval.
2.2 Amendment record
An amendment shall publish its old text, new text, reason, approval and effective date.
❌ Policy onlyThe amendment register on this page records each amendment since v0.1; no code checks that an amendment carries an approval.
2.3 Version and law numbers
Each approved rule change shall increment the rulebook version; existing law numbers shall remain stable.
❌ Policy onlyThis page is v0.5, matching the engine; every existing law number is preserved. Retired numbers must be marked repealed rather than reused. Version review remains policy.
2.4 The booked edition governs
A fight shall keep the Laws edition, Genesis prompt, card and economic terms fixed at booking, before its first pick. Later ratings and amendments shall not change that booking.
🟡 Partly enforcedlaws/src/rules.rs · bell / new_edition preserves the booked prompt and edition; src/laws.ts · rule / replay rules a stored fight with the bytes of the edition it was booked under, kept in laws/editions/ (scripts/laws-build.ts · keepEdition adds each edition’s file and never deletes one), and a fight booked under an edition this host does not hold stops with an alert (src/nightly/book.ts · FightBook.apply). src/nightly/tonight.ts · setHouseCard stores the card once. The simulated arena and chain pools do not bind this full manifest.
2.5 Safety does not rewrite a result
The Commission shall handle an unsafe or invalid bout through cancellation, no contest or appeal, never by silently changing its rules.
🟡 Partly enforcedcontracts/src/Arena.sol and solana/programs/arena/src/lib.rs allow Open-match cancellation. They have no immediate Locked-match no-contest path or appeal reversal.
2.6 Code follows the laws
A code change that would break a law requires the Commissioner to change that law first.
❌ Policy onlyThe companion AGENTS.md paragraph establishes this review obligation; no automated conformance gate exists. Listed gaps are existing nonconformance, not exceptions.
Fighters and the weigh-in
A fighter’s name is a label. Its registered model build is its identity.
3.1 Eligibility
An entrant shall be able to produce the submission format required by its league annex.
🟡 Partly enforcedsrc/challenge.ts · loadChallenge / openingMessages / extractLean specifies Lean output and src/referee/lean.ts · LeanReferee.check validates submissions. scripts/weigh-in.ts filters text models, but there is no entrant registration test.
3.2 Registered identity
Each entrant shall declare its model ID, version, provider, serving configuration and owner before booking. The fighter’s version shall appear beneath its name on the broadcast and fight card.
🟡 Partly enforcedsrc/nightly/arena.ts · groupBuilds / seatOf binds mapped builds to cards; src/nightly/builds.ts · buildEvents records provider identity reports. src/open/door.ts · Door.enter binds the Open to file hashes. Sealed-provider identity and ownership remain assertions; simulated persona labels are not attested real builds.
3.3 Pinned open weights
An open-weight entrant shall bind its entry to immutable weights and tokenizer files, with their hashes and serving revision.
🟡 Partly enforcedsrc/open/door.ts · Door.enter pins a commit and file hash; src/open/loader.ts · Loader.load verifies the bytes. Complete tokenizer and serving-revision attestation across all entrants remains incomplete.
3.4 No substitution
A changed build behind a booked name shall end that fight as NO CONTEST. A fighter delisted before its bell shall not fight and its waiting Credits shall return. A replacement build requires a new booking; a provider change alone is not proof of a changed build.
🟡 Partly enforcedlaws/src/rules.rs · build_report / fighter_retired ends the fight; src/nightly/builds.ts · buildEvents compares reports. Sealed models remain the provider’s word. Retirement of a champion is the open default in D2.
3.5 The weigh-in formula
For the title-fight card, weight in decimal GB shall equal total parameters in billions multiplied by 4.5 and divided by 8. The STRAWWEIGHT OPEN uses the file weigh-in in Law 15.2.
✅ Enforced in codesrc/weight.ts · weighIn; src/nightly/arena.ts · weigh; src/open/door.ts · Door.enter.
3.6 All experts count
A mixture-of-experts model shall weigh all its parameters; active parameters shall not reduce its class.
✅ Enforced in codesrc/weight.ts · Build / divisionOf. Only paramsB enters the weigh-in; activeB is descriptive.
3.7 Symbolic weight ceilings
The class ceilings in Law 4.1 shall govern title-card admission by estimated weight size. Each machine is the symbol of its class; no percentage-of-memory allowance shall alter the ceiling. The Open’s file ceiling is Law 15.2.
✅ Enforced in codesrc/weight.ts · divisionOf / canFightIn; src/open/door.ts · Door.enter.
3.8 Evidence of weight
A title-card open-weight weigh-in shall use a verified total parameter count, not a packed file size. The STRAWWEIGHT OPEN shall weigh the actual GGUF bytes under Law 15.2.
🟡 Partly enforcedsrc/nightly/arena.ts · weigh reads roster or reviewed-map counts, not a size in a name. Independent verification of every count remains incomplete. src/open/loader.ts · Loader.load verifies the Open file.
3.9 Sealed entrants
An entrant with closed weights shall be marked SEALED and compete only in the SINGULARITY.
✅ Enforced in codesrc/weight.ts · divisionOf / canFightIn / describe. A claimed size does not override sealed placement in code.
3.10 Moving up
A netrunner may compete in its home class or a heavier class, never below the lightest class it makes.
✅ Enforced in codesrc/weight.ts · canFightIn; src/arena/card.ts · makeCard / settleBelt. Returning to its home class after moving up is allowed; there is no permanent promotion.
3.11 Neon Circuit entry
A Neon Circuit entrant shall identify one Hugging Face repository and immutable commit to be served on league-controlled hardware.
🟡 Partly enforcedsrc/open/door.ts · Door.enter pins the Open repository and commit; src/open/box.ts · OllamaBox.register serves its verified file on the league machine. The wider circuit remains planned.
3.12 Neon Circuit files
The wider Neon Circuit shall load safetensors only and shall never execute repository-supplied custom code. Its first house, the STRAWWEIGHT OPEN, admits the pinned GGUF file under Article 15 and supplies the serving settings itself.
🟡 Partly enforcedsrc/open/box.ts · OllamaBox.register creates a model from the verified blob. The wider circuit loader is still policy only; a verified file hash does not prove a model parser safe.
3.13 Rights to enter
An entrant’s owner shall document a license that permits the league’s intended hosting, use and publication.
🟡 Partly enforcedsrc/open/entry.ts · licenceAllowed checks the configured licence list and src/open/door.ts · Door.enter holds other licences for the Commissioner. A repository tag is not independent proof of rights or ownership.
3.14 The owner’s purse
The Neon Circuit shall publish the model owner’s purse terms before accepting an entry.
❌ Policy onlycontracts/src/Arena.sol and solana/programs/arena/src/lib.rs distribute bettor purses and operating funds, not a model-owner prize.
Choose the owner’s prize and its funding. The Open’s current default awards a ladder place and a public record, with no owner payment; it makes no deduction from backers’ purses.
Weight classes and belts
Eight machines. Eight divisions. Belts belong to an era; titles are earned in the ring.
4.1 The eight classes
Each bout shall name exactly one of the following divisions and apply its inclusive weigh-in ceiling. An open-weight fighter’s home class is the lightest one it makes; above 1,024 GB its home is the SINGULARITY. Moving up remains allowed under Law 3.10.
| Division | Machine | Ceiling |
|---|---|---|
| STRAWWEIGHT | edge | 1 GB |
| FLYWEIGHT | phone | 2 GB |
| LIGHTWEIGHT | laptop | 8 GB |
| MIDDLEWEIGHT | desktop | 32 GB |
| CRUISERWEIGHT | workstation | 128 GB |
| HEAVYWEIGHT | GPU server | 512 GB |
| SUPER HEAVYWEIGHT | GPU rack | 1 TB · 1,024 GB |
| SINGULARITY | data center | Unlimited |
✅ Enforced in codesrc/weight.ts · DIVISIONS; src/arena/card.ts · makeCard / settleBelt.
4.2 Title designation
A nightly title fight shall be booked under Article 13: the champion against a newcomer, or the top two for a vacant belt. An Article 15 bout shall never contest a belt. The simulated arena’s every-eighth-bout SINGULARITY main event is an exhibition schedule.
✅ Enforced in codesrc/nightly/arena.ts · cardFor; laws/src/rules.rs · check_bout / belt_after_win; src/arena/schedule.ts · Schedule.fill. Row 3 gives quiet nights to the Open (Law 13.7).
4.3 Lineal succession
Within a weight-class era, a division’s belt is lineal: a valid title-bout winner becomes champion; an incumbent’s title-bout win is a defence.
✅ Enforced in codesrc/arena/league.ts · fightPhase / refreshHonours checks current belt eligibility, champion inclusion and main-event status before calling src/arena/card.ts · settleBelt. A winning incumbent returns retained; src/arena/titles.ts · recordBout counts that defence. This enforces succession under the current designation; booking stability and a complete lineage remain gaps under Laws 2.4, 4.2 and 4.8.
4.4 LOCKDOWN retains the belt
LOCKDOWN shall leave a held belt with its champion and a vacant belt vacant.
✅ Enforced in codelaws/src/rules.rs · the_core_holds / lockdown_now / belt_stays leaves the title belt with its champion or vacant; src/arena/card.ts · settleBelt does the same for the simulated show.
4.5 Two-weight champions
A netrunner may hold belts in more than one division for which it makes weight. Holding at least two current belts earns TWO-WEIGHT CHAMPION.
✅ Enforced in codesrc/arena/card.ts · Belts / settleBelt stores belts independently by division. src/arena/league.ts · titlesFor / standings counts current belts and src/arena/titles.ts · titlesOf grants the title at two or more. Falling below two removes that title; its new-title announcement has a separate gap under Law 4.9.
4.6 Sealed champions
A sealed netrunner may hold only the SINGULARITY belt; lower belts require open weights.
✅ Enforced in codesrc/weight.ts · canHoldBelt; src/arena/card.ts · makeCard / settleBelt; src/arena/league.ts · refreshHonours.
4.7 Vacancy and stripping
Belts belong to a weight-class era. The approved 15 November 2026 redraw vacates every prior-era belt while keeping fighter records. Within an era a holder must remain eligible; any vacancy or stripping outside a title-bout result shall have a published Commission ruling.
🟡 Partly enforcedlaws/src/rules.rs · fighter_retired emits vacate-belt for a retired champion; src/nightly/book.ts · FightBook.moveBelt applies it and src/nightly/nights.ts · Nights.publishVacated writes and publishes row 39’s ruling record with its reason. The earlier symbolic-era reset remains in src/arena/league.ts · load; broader stripping policy is still D2.
Retirement remains row 39’s open decision. The current default is NO CONTEST, vacating a belt held by the retired fighter with a published ruling that gives the reason, then a vacant-title card. Choose retirement and voluntary-vacancy terms, any inactivity deadline, and the effect of proven cheating on reigns.
4.8 Belt lineage
The league shall retain every belt transfer and vacancy, its era, and its supporting bout or Commission ruling. A new era shall preserve the record of earlier reigns.
🟡 Partly enforcedsrc/arena/league.ts · load / save saves the current era, current belts, aggregate W–L–D, title statistics and Elo in matches/league.json. Era changes retain the fighter aggregates but discard prior belts; there is no complete reign history, vacancy log or per-bout era commitment. Earned-title statistics are not a belt lineage.
4.9 Earned titles
A fighter shall earn titles from its recorded bouts and current belts under the criteria below. Its most prestigious qualifying title shall appear in quotes beneath its name, and newly earned titles shall be announced.
| Title | Earned by | Holders |
|---|---|---|
| MATH GOD | Most CORES breached in the league, with at least 5. | One at a time |
| UNDISPUTED | At least 3 winning belt defences, accumulated across bouts and belts. | Every qualifier |
| TWO-WEIGHT CHAMPION | At least 2 belts held at once. | Every current qualifier |
| SPEED DEMON | Fastest winning breach on record, measured in bout seconds. | One at a time |
| GIANT KILLER | At least 1 win after moving up a class. | Every qualifier |
| ONE-SHOT | At least 3 winning breaches on the first attempt. | Every qualifier |
| LONG SHOT | At least 1 win with strictly less than 30% estimated win probability at the bell. | Every qualifier |
| COMEBACK KID | At least 1 winning breach on the bout’s last allowed attempt. | Every qualifier |
| ON FIRE | At least 3 consecutive wins in a streak still running. | Every current qualifier |
A loss or LOCKDOWN resets the current win streak. MATH GOD and SPEED DEMON go to the first qualifying entry in the statistics map when scores tie; they are not shared. Titles are recalculated, so exclusive titles, ON FIRE and TWO-WEIGHT CHAMPION can be lost. Existing statistics survive an era change; old W–L–D records alone do not reconstruct missing title statistics.
🟡 Partly enforcedsrc/arena/titles.ts · TITLES / recordBout / titlesOf implements these thresholds and prestige order. src/arena/league.ts · beginFight / fightPhase captures bell odds and records results; web/main.ts · render / onResult and web/fight-card.ts display titles. Two integration gaps remain: fightPhase passes this.config.attempts rather than the booked s.config.attempts for COMEBACK KID, and captures titlesBefore after settling the belt, so TWO-WEIGHT CHAMPION can be earned without a new-title announcement. These are simulated fighter achievements, not measured real-model records.
4.10 Elo standings
The simulated arena shall rate fighters from Elo 1500 under the formula below. The nightly’s own ratings and the Open ladder shall start at 1024 with K = 32: a win scores 1, a loss 0, a draw one half; HELD, LOCKDOWN, void and NO CONTEST move no rating. Arena ratings shall remain separately named.
Expected score = 1 ÷ (1 + 10(opponent rating − own rating) ÷ 400). New rating = old rating + 32 × (score − expected score), rounded to one decimal. Elo is a standing, not a belt or an earned title.
🟡 Partly enforcedsrc/arena/titles.ts · rate, src/nightly/ratings.ts · rated / rateSession and src/open/ladder.ts · ratedBout / rateBout keep separate tables. The Open host misclassifies an exact proof tie as breached with no winner and misses its half-score (Law 15.7).
The bout
The published closing time locks the pool. The recorded fight bell starts the contest clock.
5.1 Seal before betting
Before a session’s first pick the league shall publish its band of CORE seals. The bell shall draw one CORE only from that published band. A pool booked on a single CORE shall publish that CORE’s SHA-256 fingerprint before its first stake.
🟡 Partly enforcedlaws/src/rules.rs · open_credits / band_added / bell freezes additions, refuses a bell between sessions until that night’s Credits have opened, and draws only from the frozen band; src/nightly/book.ts · FightBook.topUpAndOpen and src/nightly/view.ts · nightView expose the band. The beacon’s round is not yet verified (Law 14.1). Future simulated pools still omit the seal.
5.2 What is sealed
The CORE’s sealed statement shall remain unchanged from commitment through the final verdict.
🟡 Partly enforcedsrc/referee/lean.ts · LeanReferee.check checks the fixed challenge; src/factory/seal.ts · verifyAndSeal hashes its bytes. Factory statements are hidden until drawn; public-ladder statements are already known. Independent verification of the full booking-to-referee binding remains incomplete.
5.3 Identical opening prompts
Both corners shall receive the same opening messages when the fight starts.
✅ Enforced in codesrc/match.ts · runMatch calls src/challenge.ts · loadChallenge / openingMessages / extractLean for each corner from the same challenge. Network arrival times can differ.
5.4 Private retry feedback
A corner shall receive only its own previous replies and rejection feedback between attempts, together with its own sealed Prayers under Article 17. No opponent conversation shall be supplied.
✅ Enforced in codesrc/match.ts · runMatch; src/nightly/book.ts · FightBook.carriedInto; src/nightly/session.ts · SessionHost.withPrayers / deliverPrayers.
5.5 Published bout limits
The bout card shall publish its clock, attempt limit and equal fuel allowance before the first bet.
🟡 Partly enforcedsrc/arena/league.ts snapshots config but scheduleSnapshot omits these limits. src/keeper/keeper.ts · Keeper.play derives the chain fuel allowance from the final pool after betting closes.
5.6 The bell and the clock
Each corner’s clock shall count only its own writing, from each attempt until its reply or interruption; it shall never run backwards. Waiting for a machine, the referee or the league shall not count. A reply finished before the writing limit may win after its check; the wall-clock ceiling is separate.
✅ Enforced in codelaws/src/rules.rs · clock / stop_the_clock / submit / restart / tick; src/match.ts · runMatch; src/runner/machine.ts · OneMachine. Reported times remain the host’s word (Law 19.3).
5.7 Attempts
Each reply a netrunner gives shall consume one attempt, whether its submission is missing, empty, invalid or accepted. A reply we failed to deliver (our relay erroring, a provider’s error status, a broken or timed-out stream) is a fault and consumes no attempt.
✅ Enforced in codesrc/match.ts · runMatch separates complete replies from transport faults; laws/src/rules.rs · submit / relay_fault / provider_fault counts or retries them. Empty whole replies are denied under row 26.
5.8 Equal fuel tanks
Each corner shall receive the same bout fuel ceiling, independent of how many bettors back that corner.
🟡 Partly enforcedlaws/src/rules.rs · start_session allocates the same tank to both corners; src/match.ts · runMatch and src/runner/fuel.ts · maxTokensWithin bound requests. Provider billing and complete reconciliation remain external to the engine.
5.9 No fuel overrun
A netrunner shall not win with work beyond its published fuel ceiling. Each request shall be booked at the fuel left; a reply that costs more shall not count. If no further reply fits, the corner is out for the session. The house shall pay any overrun.
🟡 Partly enforcedlaws/src/rules.rs · submit / out_of_fuel rejects an overrun and stops an empty tank. src/match.ts · runMatch and src/runner/fuel.ts · maxTokensWithin bound requests; src/keeper/keeper.ts · Keeper.play caps the bettors’ charge. Unknown or late provider costs still require reconciliation.
5.10 Reply-only competition
During a Lean contest a netrunner may only return text; it may not browse, call tools, obtain outside help other than Article 17’s sealed Prayers, or contact the opponent or referee outside the submission channel.
🟡 Partly enforcedsrc/nightly/session.ts · SessionHost.withPrayers inserts only the purchased sealed texts. src/runner/openrouter.ts · openRouterRunner sends chat requests; remote serving behavior is not independently attested.
5.11 Submission format
A Lean reply shall contain exactly one Lean code block defining breach at Punk.Proxy; helper lemmas are allowed.
🟡 Partly enforcedsrc/challenge.ts · loadChallenge / openingMessages / extractLean requests one block but extractLean accepts the last of several. referee/Check.lean · main / axiomsOf checks the declaration and exact type.
5.12 End of a bout
A session shall end when a PROVEN can no longer be beaten under Law 6.4, or when its limits end both corners and all pending proofs have been judged. A held verdict shall wait under Article 14. The session’s end shall not by itself end an open title fight.
✅ Enforced in codelaws/src/rules.rs · settle_session / could_still_finish_by / the_core_holds; src/match.ts · runMatch.
The referee and the verdict
Annex A · LEAN. Correctness can be replayed. Original timing cannot be recreated by replaying a proof.
6.1 CORE BREACHED
A Lean submission shall receive CORE BREACHED only after passing all four checks below.
- No submission-supplied imports; only core Lean and the sealed Challenge.
- Successful compilation inside the restricted box, with no network or unrelated user files.
- A second kernel check of the compiled proof terms with leanchecker.
- The trusted checker confirms the submission’s breach has exactly Punk.Proxy, the goal comes from Challenge, imports are allowed and proof dependencies use only allowed axioms.
✅ Enforced in codesrc/referee/lean.ts · LeanReferee.check; src/referee/sandbox.ts · profile / box; referee/Check.lean · main / axiomsOf. Enforced on the supported macOS path; a blocked checker is not an acceptance.
6.2 Allowed axioms
The accepted proof may depend only on propext, Classical.choice and Quot.sound as axioms.
✅ Enforced in codereferee/Check.lean · allowedAxioms / axiomsOf. Core Lean and the Commission-supplied challenge are trusted inputs; dependency inspection is not a review of arbitrary challenge safety.
6.3 ACCESS DENIED
A missing or rejected proof shall receive ACCESS DENIED and may be retried only while attempts, fuel and time remain.
✅ Enforced in codesrc/match.ts · runMatch; src/referee/lean.ts · LeanReferee.check. Ordinary mathematical failure is not itself evidence of dishonest intent.
6.4 First to finish writing
If more than one PROVEN reply competes for first place, the one that finished writing first on its own corner’s clock shall win. In the same millisecond, fewer attempts win, then less fuel burned; if those are equal too, it is a draw.
✅ Enforced in codesrc/match.ts · firstToFinish; laws/src/rules.rs · settle_session / could_still_finish_by / break_the_tie. A PROVEN waits while a rival can still beat it on its own writing clock; waiting turns do not lose by verdict arrival.
6.5 LOCKDOWN
If a title session ends without a PROVEN, the CORE holds and the fight stays open, unless its last session calls LOCKDOWN under Law 14.5. An Article 15 bout instead ends in a DRAW. NO CONTEST is a separate result; neither HELD nor LOCKDOWN is a rated draw.
✅ Enforced in codelaws/src/rules.rs · the_core_holds / bout_drawn / no_contest; src/nightly/ratings.ts · scoreOf; src/open/ladder.ts · boutScore. The simulated show still uses its older LOCKDOWN draw label.
6.6 The fight record
The official record shall identify the CORE, both fighter builds, Laws edition and engine seal, Genesis prompt, limits, replies, verdicts, writing clocks and costs with their source. Every ruled event from booking shall be preserved for replay under Article 19.
🟡 Partly enforcedsrc/nightly/book.ts · FightBook.record / ruled; src/nightly/nights.ts · Nights.keep / keepFight; src/laws.ts · replay / LAWS_SHA256. Independent build, time and cost attestation remains absent.
6.7 Record fingerprints
An on-chain result shall commit to the exact published fight-record bytes.
🟡 Partly enforcedsrc/keeper/keeper.ts · Keeper.play hashes compact JSON with keccak256; src/arena/chain.ts · ArenaChain writes those bytes. contracts/src/Arena.sol and solana/programs/arena/src/lib.rs merely accept the owner’s 32-byte value; Solana has no keeper or publication path. Empty local-chain exhibitions have no settled record hash on chain.
6.8 Checker limits
Lean submissions shall respect the referee’s fixed resource limits. A check past its limit shall be checked again, up to four checks in all; four timeouts deny the proof. Four referee crashes are a referee failure under Law 7.15, never a denial.
✅ Enforced in codesrc/match.ts · runMatch retries checks; laws/src/rules.rs · check_ran_past_its_limit / referee_failed rules on the resulting evidence.
Fouls, disqualification and outages
Reject the attempt on technical failure. Establish responsibility before a disciplinary ruling.
7.1 No admitted proof gaps
A proof shall not rely on sorry or another admitted proof gap.
✅ Enforced in codereferee/Check.lean · main / axiomsOf rejects sorryAx dependencies; test/referee.test.ts tests sorry.
7.2 No new axioms
A submission shall not introduce a new axiom.
🟡 Partly enforcedreferee/Check.lean · main / axiomsOf rejects new axioms used by the solution; test/referee.test.ts tests a made-up axiom dependency. An unused axiom is not prohibited by the dependency walk.
7.3 Prove the specified goal
A submission shall define its own breach with exactly the sealed Punk.Proxy type.
✅ Enforced in codereferee/Check.lean · main / axiomsOf; test/referee.test.ts cover an easier proposition and a missing breach. The trusted checker verifies declaration ownership.
7.4 Do not replace the CORE
A submission shall not redefine or rewrite the sealed goal.
✅ Enforced in codereferee/Check.lean · main / axiomsOf verifies the goal’s module; src/referee/sandbox.ts · profile / box denies trusted-file writes. test/referee.test.ts cover redefinition and rewriting Challenge.lean.
7.5 No imported shortcut
A submission shall not introduce imports, module headers or a replacement prelude.
✅ Enforced in codesrc/referee/lean.ts · LeanReferee.check filters import and module/prelude forms; referee/Check.lean · main / axiomsOf independently checks compiled imports. test/referee.test.ts covers import Lean.
7.6 No private-file access
A submission shall not read unrelated user files; file writes are limited to its assigned output folder and /dev/null.
✅ Enforced in codesrc/referee/sandbox.ts · profile / box restricts file access; src/referee/lean.ts · LeanReferee.check supplies a minimal environment. test/referee.test.ts covers reading the repository’s package.json and rewriting the trusted challenge. This enforcement is macOS-only.
7.7 No extra artifacts
A submission shall leave only Solution.lean and Solution.olean in its output folder.
✅ Enforced in codesrc/referee/lean.ts · LeanReferee.check checks for stray files; test/referee.test.ts covers dropping Evil.olean.
7.8 A process exit is not a proof
A submission that ends compilation without a compiled result shall be rejected, even with exit code zero.
✅ Enforced in codesrc/referee/lean.ts · LeanReferee.check checks for Solution.olean; test/referee.test.ts covers early IO.Process.exit.
7.9 No network from a submission
Submitted code shall have no network access.
✅ Enforced in codesrc/referee/sandbox.ts · profile / box denies network operations; test/referee.test.ts includes a curl probe. A blocked probe can still accompany a valid proof: denial is not automatic disqualification.
7.10 No forged verdict
A fighter shall not forge compiled results, checker output or referee files.
🟡 Partly enforcedsrc/referee/lean.ts · LeanReferee.check ignores compiler acceptance text, rechecks proof terms and runs referee/Check.lean · main / axiomsOf read-only. Crafted result files that crash a checker are an acknowledged gap; current tests do not cover every such file.
7.11 No interference
No entrant shall attempt sandbox escape, opponent interference or prompt injection against the referee or commentary.
🟡 Partly enforcedsrc/referee/sandbox.ts · profile / box isolates submissions, and referee/Check.lean · main / axiomsOf is a program, not a language-model judge. Private slots separate the corners. Detection, intent classification and a commentary-injection policy are not implemented.
7.12 No timing manipulation
No operator, provider or entrant shall delay, reorder, pre-run or conceal a corner’s work to affect a result.
❌ Policy onlysrc/match.ts · runMatch records local times but provides no independent timestamp or provider attestation. Public challenge files do not prevent prior preparation.
7.13 Technical penalties
A rejected attempt shall consume its attempt; a fault (Law 5.7) is not a rejected attempt. An exhausted corner shall flatline without an automatic award to its opponent.
✅ Enforced in codesrc/match.ts · runMatch emits budget, attempts or its own clock’s exhaustion; a fault ends that corner with out(error) and names whose failure it was. The opponent still needs a PROVEN reply to win. Amended in v0.2.
7.14 Disciplinary penalties
The Commission shall issue a reasoned ruling before disqualification or a ban. Detected escape or interference shall stop the fight and hold its money pending that ruling; a stop is not a final NO CONTEST.
🟡 Partly enforcedlaws/src/rules.rs · interference / rule_on_stopped_fight stops the fight and resumes or ends it on a named ruling, which an operator sends through POST /api/nightly/ruling (src/nightly/nights.ts · Nights.rule; on a public box, the operator’s token only). It has no disciplinary ban or automatic disqualification system.
Choose the disqualification threshold, its sporting result and any ban. Current default: a foul spends an attempt; interference stops the fight and holds money until a named ruling. No automatic disqualification or ban exists.
7.15 Provider failures
A transport failure shall cost no attempt. The nightly default is one retry of our relay, then a void session; a provider silent for 32 seconds or failing in transport voids both corners, unless an eligible earlier proof is PROVEN. Both-provider or referee failure voids the session, subject to the held-PROVEN protection in Law 14.8. Two consecutive void sessions blamed on one provider withdraw its fighter as NO CONTEST.
🟡 Partly enforcedlaws/src/rules.rs · relay_fault / providers_silent / provider_fault / void_session applies these defaults; src/nightly/session.ts · SessionHost.tick / onMatch supplies the faults. For silence, the cutoff is the last word received, not 32 seconds later. Fault evidence is the host’s word.
The current engine default is Law 7.15: one relay retry, a 32-second provider-silence threshold, void and replay, and withdrawal after two consecutive voids blamed on one provider. Held or eligible earlier PROVENs are protected. These defaults do not settle your choice of outage policy.
7.16 No-contest refunds
NO CONTEST shall award no fabricated winner or LOCKDOWN rollover. In the nightly the current default returns that session’s picks and Prayers in full, sends its carried purse to the house’s next title fight, and leaves earlier sessions settled. A bout carries nothing.
🟡 Partly enforcedlaws/src/rules.rs · no_contest / return_what_waits_for_a_bell; src/nightly/purse.ts · Purse.apply. Existing chain pools do not implement this nightly no-contest settlement.
Current nightly default: full picks and Prayer prices back for this session, earlier sessions settled, carried purse onward. Decide real-money cut, burn, live-ticket and gas treatment; the legacy rails do not implement this full refund.
Disputes and appeals
An appeal must name the law, the bout and the evidence.
8.1 Standing to dispute
Any entrant, backer or member of the public may submit a documented dispute to the Commission.
❌ Policy onlyNo public dispute intake or case register is implemented.
8.2 Filing window and finality
Every fight shall publish its appeal deadline and payout-finality rule before picks open. Under the nightly’s current default, correction shall not claw back an amount paid; the league shall make whole whoever the corrected result is owed. The filing window remains the Commissioner’s decision.
🟡 Partly enforcedlaws/src/rules.rs · correct_result emits make-whole with amounts owed and prior payments, and src/nightly/purse.ts · Purse.apply / shortfalls pays each shortfall in play chips from the league’s own account. No filing deadline is enforced.
Choose the filing window and whether future value claims wait. The current default is correction by make-whole, paid from the league’s own account, with no clawback; no appeal deadline is implemented.
8.3 Evidence
A dispute shall supply the bout ID, challenged law, original record hash, relevant submission and reproducible grounds.
🟡 Partly enforcedsrc/match.ts · runMatch retains submission code and verdicts. src/arena/chain.ts · ArenaChain supplies local chain record hashes. There is no evidence-package validator or pinned build manifest.
8.4 Recheck the proof
A correctness appeal shall rerun the deterministic check on the original evidence with the original pinned toolchain and checker.
🟡 Partly enforcedsrc/referee/lean.ts · LeanReferee.check and referee/Check.lean · main / axiomsOf can check the same source again; lean-toolchain pins Lean 4.32.1. No appeal runner archives all original artifacts. Replay can establish proof validity, not original arrival order or elapsed latency.
8.5 An accountable ruling
The Commission shall publish each appeal ruling with its author and reason. A correction shall name the digest of the ruling it corrects, preserve the first record, correct the result and belt, and make whole those shorted without taking back payments already made.
🟡 Partly enforcedlaws/src/rules.rs · correct_result emits result-corrected, make-whole, publish-ruling and keep-first-record, and src/nightly/nights.ts · Nights.rule / keepCorrection carries them out: the shortfall paid (src/nightly/purse.ts · Purse.apply), the belt moved (src/nightly/book.ts · FightBook.moveBelt) and the corrected record kept beside the first. Independent appeal rechecks are incomplete.
8.6 Independent referees
The league shall describe who attests correctness and who attests timing for each settlement system.
🟡 Partly enforcedcontracts/src/Arena.sol and solana/programs/arena/src/lib.rs accept the house owner’s result. docs/fight-economy.html proposes independent 2-of-3 correctness rechecks and a dispute hold, then attested timing and possible proof research. None is deployed; multiple proof checkers alone do not establish who finished first.
Betting and responsible play
A pool bet shares a purse. A live bet buys a fixed payout. Neither is a promise of profit.
9.1 Everyone can watch; wallets are 21+
Everyone may watch. The under-21 view and the stream shall show no Credits, purse, picks, odds, Prayers or wallet. Connecting a crypto wallet requires the 21-and-over confirmation; real-money access additionally requires verified age and Law 9.3’s controls.
🟡 Partly enforcedweb/main.ts · render, web/main.ts · markView and the view controls separate currency presentation. No test names row 57; account-level age verification and the full cross-surface guarantee remain gaps.
9.2 Separate play from value
Play chips and local test tokens shall have no purchase, redemption or real-money value.
🟡 Partly enforcedsrc/arena/players.ts · Players issues free chips; src/arena/chain.ts · ArenaChain uses Punk Local / 31337 and test USDC. There is no cash-out path. Dollar symbols and mixed coin labels in the play UI still need clearer separation.
9.3 Lawful real-money access
Real-money betting shall remain closed until counsel signs off on each permitted jurisdiction and the required controls are operating.
❌ Policy onlyNo jurisdiction, license, real age-verification or geofencing system exists. US internet-wagering definitions depend on applicable law where bets are made or received; this rulebook does not grant permission. 31 U.S.C. § 5362(10).
Current default: play Credits only, with no purchase or redemption value. No engine jurisdiction or licensing model is approved here. Choose counsel-approved territories and an operating model before real-money access; a crypto, contest or prediction-market label does not settle it.
9.4 One pool, one asset
Each on-chain bout shall accept stakes in its declared asset only.
✅ Enforced in codecontracts/src/Arena.sol stores ETH or an ERC-20 per match. solana/programs/arena/src/lib.rs, solana/programs/arena/src/contexts.rs and solana/programs/arena/src/transfers.rs bind SOL or classic SPL mint and vault. Token-2022 is rejected; rebasing assets are unsupported.
9.5 The split
An on-chain pool shall split at lock into its published house cut, credits share and remaining purse. The nightly’s play Credits follow Article 16: the league fronts fuel and takes no such cut.
House · Model credits · Initial purse. Unused credits later increase the purse.
✅ Enforced in codecontracts/src/Arena.sol · lock; laws/src/rules.rs · start_session / pool_of; src/nightly/purse.ts · Purse.apply. This does not authorize real-money play.
9.6 Pay only for the burn
Where bettors fund model credit, their charge shall equal reconciled burn, capped at the published allowance, and unspent credit shall return to their pool. In the nightly this milestone the league pays fuel; play Credits shall not pay provider bills.
🟡 Partly enforcedsrc/keeper/keeper.ts · Keeper.play caps charges; src/nightly/ledger.ts · FuelBook.settle / reconcile retains pending costs and reservations. The engine emits league-fronts-fuel; unknown provider costs remain unreconciled.
9.7 Prepaid fuel belongs to the house
The house shall fund provider minimum top-ups and replace unused prepaid provider credit with liquid funds for the purse.
🟡 Partly enforcedsrc/keeper/keeper.ts · Keeper.play fronts a shortfall for Venice’s minimum and returns the calculated house share. src/keeper/pits.ts keeps unused prepaid balance for later bouts. Repayment still depends on house liquidity and successful keeper calls.
9.8 Parimutuel pool payouts
Backers of the winning corner shall share the final purse by their stake on that corner. In a nightly title fight, only that session’s winning backers share its own purse and the carried purse; earlier stakes confer no later claim.
✅ Enforced in codelaws/src/rules.rs · shares_for / pay_out; src/nightly/purse.ts · byStake / Purse.apply. Whole-Credit remainders go to largest fractions, ties to earlier stakes.
9.9 A favourite below ×1
The rules shall state whether a winning pool ticket may return less than its original stake.
🟡 Partly enforcedcontracts/src/Arena.sol owed and solana/programs/arena/src/state.rs Fight::owed impose no ×1 floor. A crowded favourite can return less than its stake after cut and burn. Fixed live prices use a separate ×1.05 floor.
Current legacy pool default permits a gross return below ×1; there is no floor. The nightly play purse takes no house or fuel cut. Choose the rule for future value pools: disclosed sub-×1 returns, a funded floor, or refusal.
9.10 Pool close
A pool stake shall be accepted only while its picks are open and before its bell or published close. Each nightly session shall have its own picks, locked at its bell; no live pick may join them.
✅ Enforced in codelaws/src/rules.rs · pick / bell; src/nightly/purse.ts · Purse.apply. The nightly locks on the actual bell event. Unlike legacy pools with a fixed closesAt, its pick path does not independently compare the published bell time while a bell is delayed.
9.11 Fixed live tickets
An accepted live ticket shall retain its quoted gross payout multiplier and shall not enter the pool purse.
✅ Enforced in codesrc/arena/league.ts · bet / payPlayers stores the price; src/arena/price.ts · livePrice uses an 8% pricing margin and bounds ×1.05–×50. Limit: 5,000 play chips per live ticket. Only play-chip mode supports live bets; the house is their counterparty, not a pool backer.
9.12 Suspend during checking
Live betting shall pause while either corner’s submission is with the referee.
✅ Enforced in codesrc/arena/league.ts · onFight / updateOdds / bet suspends on submit and rejects suspended bets. Flatlined corners cannot receive live bets.
9.13 Odds are estimates
Displayed win probabilities shall be labelled estimates, distinct from pool returns and accepted live-ticket prices.
🟡 Partly enforcedsrc/arena/odds.ts · winOdds runs 2,000 simulated continuations using persona skill. It is not a calibrated real-model forecast and does not model all fuel or outage risks. Displaying it does not certify fairness.
9.14 Cancellation before lock
Cancelling an Open pool shall make every original stake claimable in full.
✅ Enforced in codecontracts/src/Arena.sol cancel/owed and solana/programs/arena/src/lib.rs cancel with solana/programs/arena/src/state.rs Fight::owed. Stake means the amount credited to the pool; token transfer fees and gas are not stakes. Owner cancellation remains possible after close if lock has not occurred. lock cancels an empty pool without consuming a jackpot.
9.15 An unbacked winner
If the winner has no backers, that session’s own purse shall return by stake and its carried purse shall go to the house’s next title fight. With no stakes at all, a title session’s Prayer purse shall carry there too; a bout’s Prayer prices shall instead return to their buyers.
✅ Enforced in codelaws/src/rules.rs · shares_for / pay_out. Row 50 states the no-stakes title case.
9.16 Locked-match rescue
Anyone may rescue an unresolved Locked on-chain pool strictly more than seven days after lock, sharing only its remaining own purse among all backers. A nightly title fight shall use one pool per session, disposed of once that night, never one unresolved pool for the whole fight.
🟡 Partly enforcedcontracts/src/Arena.sol · rescue; laws/src/rules.rs · pay_out / the_core_holds / void_session. Nightly play pools settle separately; on-chain wiring for carried session pools is not built. Row 58 states the two exceptions to same-night disposal: a stopped fight’s held money, and a check still pending at the night’s end.
9.17 Stale Open pools
Anyone may cancel a still-Open pool strictly more than seven days after its closing time, recovering full original stakes.
✅ Enforced in codecontracts/src/Arena.sol rescue handles Open status; solana/programs/arena/src/lib.rs cancel permits any signer after closes_at + RESCUE_AFTER. Solana rescue itself is Locked-only.
9.18 LOCKDOWN economics
The no-finish disposition shall be fixed before picks open. The nightly default rolls a held title session’s purse into that fight, sends LOCKDOWN’s purse and carry to the house’s next title fight, and refunds a draw’s own purse by stake while its carry goes onward. An Article 15 bout never rolls a purse.
🟡 Partly enforcedlaws/src/rules.rs · shares_for / the_core_holds / bout_drawn implements the nightly default. Legacy contracts still expose a house-takes-own-purse option; they are not the nightly settlement adapter.
The nightly engine’s current default is Law 9.18: held purses roll, LOCKDOWN carries to the next title fight, draws refund by stake, and bouts never carry. The legacy house-takes option remains code, not a settled nightly policy. Your economic decision remains open.
9.19 Jackpot custody
A carried title purse shall reach later winning backers or the house’s next title fight. It shall never become a house cut, refund unrelated stakes, or enter an Article 15 bout.
✅ Enforced in codelaws/src/rules.rs · carry_to_next_fight / shares_for / check_bout; src/nightly/book.ts · FightBook.carryPurses / book. Legacy play-mode refund accounting is outside this nightly path.
9.20 Claims
Each backer shall be able to claim a final amount only once under the pool’s recorded outcome.
✅ Enforced in codecontracts/src/Arena.sol claim deletes stakes before payment and reverts if owed is zero. solana/programs/arena/src/lib.rs claim and solana/programs/arena/src/contexts.rs · Claim close the stake to its signer, including zero-payout claims, returning stake rent. Failed transfers roll back. Issuer freezes can block SPL transfers; recipients need valid token accounts or sufficient native rent. No claim expiry is coded.
9.21 The house does not back corners
The house shall not place pool stakes, directly or through another wallet.
❌ Policy onlycontracts/src/Arena.sol and solana/programs/arena/src/lib.rs back have no house exclusion. src/arena/league.ts · crowdBet injects fictional play stakes; these must not be represented as independent real betting. Live-ticket counterparty liability is separate from backing a corner.
9.22 No betting on one’s own bout
Staff and model owners shall not bet, directly or indirectly, on bouts they operate, enter or influence.
❌ Policy onlyBrowser IDs and wallet addresses do not establish staff, ownership or beneficial control.
9.23 Limits before play
The league shall offer enforceable deposit, loss and session limits before real-money play.
❌ Policy onlysrc/arena/league.ts has per-ticket play caps and chip-balance checks only. These are not personal deposit, loss or session limits.
9.24 Time away
The league shall offer cool-offs and self-exclusion and show a session reminder every 30 minutes.
❌ Policy onlyNo cool-off, self-exclusion or reminder enforcement exists.
9.25 No loss-chasing hooks
The league shall not reward betting volume or urge a player to recover losses by betting again.
❌ Policy onlysrc/arena/players.ts · Players awards XP even for losing picks and automatically replenishes broke viewers. src/arena/league.ts · chatter includes “all in, no regrets”; the interface also uses streak and fever hooks. These require review, not a responsible-play badge.
Integrity, records and funds
A contract enforces its state machine. It does not prove the house told the truth.
10.1 The public bout ledger
For every official bout, the league shall publish its manifest, stakes, cut, burn, returns, proof record, settlement, belt era and effect, earned titles and Elo changes.
🟡 Partly enforcedsrc/arena/chain.ts · ArenaChain, src/arena/server.ts, src/arena/league.ts, contracts/src/Arena.sol and solana/programs/arena/src/lib.rs expose parts of this locally. Arena results expose belt effects and newTitles; fighter snapshots expose version labels, current titles and Elo. The saved era and aggregates do not provide per-bout rating changes, title provenance or prior reigns. Provider receipts, durable publication and a complete sporting ledger are missing.
10.2 Disclose conflicts
Operators, model owners and referees shall publish relevant ownership, sponsorship and financial conflicts before the bout.
❌ Policy onlyNo conflicts register or bookmaker-related identity disclosure exists.
10.3 Withdrawals have named destinations
Contract withdrawals shall send only accrued fees to the configured treasury and accrued credits to the configured run wallet.
✅ Enforced in codecontracts/src/Arena.sol withdrawFees/withdrawRunFunds and solana/programs/arena/src/lib.rs withdraw_fees/withdraw_run_funds enforce destinations. Anyone may trigger them; the owner can change wallets. Once withdrawn, spending and honest fuel returns are not constrained on chain.
10.4 No arbitrary purse withdrawal
The house shall not withdraw stakes, unpaid purses or carried jackpots outside the contract’s declared outcomes.
🟡 Partly enforcedcontracts/src/Arena.sol and solana/programs/arena/src/lib.rs expose no arbitrary reserved-funds withdrawal. But the house controls result submission, could back a corner, and is not forced to return credits. False outcomes can redirect funds despite custody accounting.
10.5 Solana surplus
A Solana sweep shall pay only holdings above ledger liabilities and protected native rent to the current treasury.
✅ Enforced in codesolana/programs/arena/src/lib.rs sweep/claim; solana/programs/arena/src/transfers.rs · Payment::sweep / transfer_out. Rounding dust is released only after all eligible stake weight claims; gifts can be swept. EVM has no equivalent sweep or dust-release function.
10.6 An outcome hash is not a proof
The league shall not describe an on-chain record fingerprint as independent verification of correctness or timing.
🟡 Partly enforcedcontracts/src/Arena.sol settle and solana/programs/arena/src/lib.rs settle trust the owner’s result and hash. The kernel runs off chain. Empty exhibitions are cancelled pools, not settled on-chain victories.
10.7 Upgrade authority
Every deployed rail shall disclose whether its settlement rules can be upgraded and by whom.
🟡 Partly enforcedcontracts/src/Arena.sol is not an upgradeable proxy. The Solana program is local only; its source does not settle the eventual loader upgrade-authority policy.
Choose immutability or a disclosed controlled Solana upgrade authority, its delay and protection for open pools. The Laws engine has no rail-authority default, and this edition authorizes no settlement deployment or release.
10.8 Publish evidence, protect secrets
Public records shall contain enough evidence to audit a bout without exposing credentials or unrelated personal data.
🟡 Partly enforcedsrc/referee/lean.ts · LeanReferee.check passes a minimal environment and trims feedback. src/match.ts · runMatch can retain raw provider-error text; no complete public-record redaction and retention policy is enforced.
League annexes
The common laws govern every league. An annex defines its CORE, allowed submission, referee, win condition and fouls.
11.1 Approve the annex first
No new league shall accept official bets before the Commissioner approves and versions its annex.
❌ Policy onlysrc/types.ts · Challenge.league is a string, not an approved-annex gate. docs/fight-economy.html contains designs, not implemented leagues.
11.2 Annex A: LEAN
The current proof league shall use Article 6’s four-check referee and the first-to-finish-writing result under Law 6.4. Title fights use sessions under Article 14; bouts use Article 15.
✅ Enforced in codesrc/referee/lean.ts · LeanReferee.check; src/match.ts · firstToFinish / runMatch; laws/src/rules.rs · settle_session / break_the_tie.
11.3 Annex B: CODE
A CODE annex shall seal the specification, test commitment and toolchain and run submissions in isolation against hidden tests.
❌ Policy onlydocs/fight-economy.html proposes isolated builds, hidden and property-based tests, and revealed seeds. There is no CODE referee.
11.4 Annex C: RUST PORT
A RUST PORT annex shall judge a pinned source repository by deterministic differential tests against the original behavior.
❌ Policy onlydocs/fight-economy.html proposes licensed source, hidden reference execution and bans on unsafe code, FFI and wrapping the original binary. No port referee exists.
11.5 Annex D: GAME
A GAME annex shall fix the engine, seed commitment, action interface, resource budget and replay rules before play.
❌ Policy onlydocs/fight-economy.html proposes three-round bot duels with rewrites, metered WASM and fixed-point physics. No game engine or referee is implemented.
11.6 Original games only
The GAME league shall use our own games, never copies of real titles or commercial ROMs.
❌ Policy onlyNames, characters, art, music and levels from existing titles are not permitted. No asset or content admission process exists.
11.7 Points and draws
Each future annex shall state its scoring, tie and timeout rule before any bout is booked.
❌ Policy onlysrc/match.ts · runMatch supports accepted proof or no winner only. Design-page suggestions are not adopted scoring rules.
Choose CODE, RUST PORT and GAME scoring before their annexes open. There is no engine default for those leagues. Lean’s default is first to finish a PROVEN; its Article 15 bout draws when nobody proves.
Definitions
Defined terms keep their meaning across cards, records and annexes.
12.1 CORE
The CORE is the fixed problem one session asks both netrunners to solve. A title fight may meet many COREs; a counted bout meets one.
✅ Enforced in codelaws/src/rules.rs · start_session / the_core_holds / bout_drawn.
12.2 Netrunner, version and corner
A netrunner is one registered build; its public version labels that build. Pink and cyan are its corners for one contest. An earned title under Law 4.9 is distinct from a belt. Arena ratings, nightly ratings and the Open ladder shall be named separately.
🟡 Partly enforcedsrc/nightly/arena.ts · groupBuilds; src/open/door.ts · Door.enter; src/nightly/ratings.ts · rateSession. A sealed build is still identified by its provider’s report.
12.3 CORE BREACHED and ACCESS DENIED
CORE BREACHED means an accepted solution; ACCESS DENIED means a rejected attempt.
✅ Enforced in codesrc/types.ts · Verdict; src/cli.ts; web/main.ts. Neither phrase alone proves an on-chain settlement.
12.4 LOCKDOWN and no contest
HELD means a title session ended without a PROVEN and its fight continues. LOCKDOWN ends a called title fight with the belt unchanged; it is not a rated draw. A DRAW ends a bout or an exact proof tie. VOID requires replay; STOPPED awaits evidence or a ruling. NO CONTEST awards no sporting win, loss, draw, defence or rating change; a retirement may vacate a belt under D2.
✅ Enforced in codelaws/src/rules.rs · the_core_holds / breach / void_session / interference / no_contest; src/nightly/book.ts · sessionEnding. The legacy simulation’s LOCKDOWN draw label is confined to that exhibition.
12.5 Flatlined and disqualified
Flatlined means a corner is out for the session; disqualified means the Commission imposed a disciplinary result. Exhaustion shall not decide a title fight that the Laws keep open.
🟡 Partly enforcedlaws/src/rules.rs · corner_out / the_core_holds distinguishes session exhaustion from a fight ending. There is still no automatic disqualification state.
12.6 Pool purse and owner’s purse
The pool purse belongs to eligible backers under settlement rules; an owner’s purse is a separate Neon Circuit prize.
🟡 Partly enforcedcontracts/src/Arena.sol and solana/programs/arena/src/state.rs track a backer purse only. No owner-prize ledger exists.
12.7 Fuel and burn
Fuel is a corner’s allowed model-spending ceiling; burn is the reconciled cost of the work actually consumed.
🟡 Partly enforcedsrc/keeper/keeper.ts · Keeper.play distinguishes tank and spent. src/keeper/pits.ts uses ledger deltas or reported costs; final reconciliation and hard caps remain incomplete.
12.8 Fingerprint
A fingerprint is a content hash that identifies bytes; it does not establish that those bytes are truthful.
✅ Enforced in codesrc/challenge.ts · loadChallenge / openingMessages / extractLean uses SHA-256 for the CORE; src/keeper/keeper.ts · Keeper.play uses keccak256 for the JSON fight record. These hashes serve different commitments.
The nightly and its card
Each house has its night. A title is earned against the next contender, not on a timer.
13.1 The house’s night
The houses shall fight on New York nights: SINGULARITY Sunday, SUPER HEAVYWEIGHT Monday, HEAVYWEIGHT Tuesday, CRUISERWEIGHT Wednesday, MIDDLEWEIGHT Thursday, LIGHTWEIGHT Friday, and STRAWWEIGHT then FLYWEIGHT Saturday.
✅ Enforced in codesrc/nightly/bell.ts · HOUSE_NIGHT / nextNight; src/nightly/calendar.ts · RealCalendar. The test named for rows 14 and 20 enforces the Saturday order.
13.2 The New York bell
The card shall be set at 1 pm and the bell scheduled for 9 pm in New York, through daylight saving. Saturday’s FLYWEIGHT bell shall wait until STRAWWEIGHT’s session ends if later.
✅ Enforced in codesrc/nightly/bell.ts · cardAt / bellAt; src/nightly/nights.ts · Nights. Row 14 states the late-bell and Saturday exceptions.
13.3 The Arena sets the card
The title card shall use the Arena’s published ratings in each house, with the snapshot’s date and credit. If the current snapshot cannot be read, the last good one shall be used; older than 32 days shall book no new title fight.
✅ Enforced in codesrc/nightly/arena.ts · boardOf / chooseSnapshot / cardFor / creditLine. Rows 8 and 9 are named in test/arena-card.test.ts. A stale snapshot leaves an existing open fight on the card; it prevents new title bookings.
13.4 One build, one fighter
Settings of the same build shall occupy one seat at that build’s best Arena rating. A new setting is not a newcomer. Every serving build shall be reported at each bell; a changed one is governed by Law 3.4.
🟡 Partly enforcedsrc/nightly/arena.ts · buildKey / groupBuilds; src/nightly/builds.ts · buildEvents; laws/src/rules.rs · build_report. Name normalization and sealed-provider reports are not independent identity attestations.
13.5 A newcomer’s title shot
A build newly reaching either of a house’s top two Arena seats shall meet its champion on the house’s next night. If two arrive together, the higher-rated shall fight first and the other wait. Fighters of one maker may meet.
✅ Enforced in codesrc/nightly/arena.ts · cardFor / byStanding stores seen builds and a queue.
13.6 A vacant belt
When a house’s belt is vacant, its top two eligible fighters shall fight for it. Fewer than two means NO CONTENDER and no title fight.
✅ Enforced in codesrc/nightly/arena.ts · cardFor.
13.7 A night without a challenger
With a held belt and no newcomer, no title fight shall be booked, and the night belongs to the STRAWWEIGHT OPEN, on a league that runs it. The Open also plays after a night’s title session. Without two qualified fighters there is no Open card; the screen shall say when no fight is available.
✅ Enforced in codesrc/nightly/arena.ts · cardFor books no title fight; src/nightly/nights.ts · Nights.run plays the Open after each night’s last house (afterNight), with or without a title session, on a league that runs it (PUNK_OPEN=1).
13.8 A seat must be served
A fighter that cannot be weighed or served shall not take a fighting seat. The card shall pass it over and name it and the reason; the next newcomer, if there is one, takes the shot. Delisting after the card is set invokes Law 3.4.
✅ Enforced in codesrc/nightly/arena.ts · weigh / servedBy / boardOf / firstServable / atTheBell; laws/src/rules.rs · fighter_retired.
13.9 The card stands
Once set, a night’s card shall not change because the ratings moved. Its fighters and booked terms shall stand, subject to withdrawal and the Laws’ explicit fault rulings.
✅ Enforced in codesrc/nightly/tonight.ts · setHouseCard; src/arena/store.ts · Store.setCardOnce.
13.10 One counted bell
Each session shall bear its house and New York date. A night shall ring once: a night that has had a bell, void or not, shall not ring again, and a void session is replayed on the house’s next night. A restart that resumes a live session is not a new session. A late return within two hours may ring late; later, or a night first seen more than two hours after its bell, shall move to the house’s next night. An alert shall go out for a bell two minutes late or more.
✅ Enforced in codelaws/src/rules.rs · bell / session_name refuses any second bell for a night; src/nightly/book.ts · FightBook.ring keeps one session a night; src/nightly/nights.ts · Nights.missed / ruled moves a night first seen over two hours late, with an alert, and alerts a bell two minutes late or more. A house that has never had a card is a fresh start, not an outage: nothing is moved for it.
13.11 Fuel before the bell
Both equal tanks shall fit under the league’s daily fuel cap before a session starts; otherwise the session shall move to the house’s next night. No picks is no reason to cancel: this milestone the league pays fuel.
✅ Enforced in codelaws/src/rules.rs · bell / start_session; src/nightly/book.ts · FightBook.ring. The cap is the configured New York day’s allowance, not the size of the play purse.
13.12 Protect the night
A deploy shall keep clear from one hour before the bell until the session ends: production refuses, QA queues until clear. An emergency override shall be logged. If the arena’s health does not answer within 4 seconds, the guard lets the deploy through.
✅ Enforced in codeinfra/box/punkproxy-gate · gate modes refuse / when-clear / now implements the guard from health data, including its 4-second open path. Its tests do not name row 44.
Sessions and the open title fight
The clock belongs to the corner. The fight belongs to the record.
14.1 Draw at the bell
Each session shall draw one fresh CORE from the house’s published band as it stood when that night’s Credits opened. The draw shall use public randomness the league does not control: the newest round of drand quicknet, read at the bell, with its source, round and randomness on the record. If the beacon cannot be read within 8 seconds, the bell shall ring on the labelled stand-in, the SHA-256 of the session’s name, with an alert, and the record shall say which was used.
🟡 Partly enforcedsrc/nightly/beacon.ts · drandBeacon reads quicknet’s newest round from the League of Entropy’s relay at each bell (src/nightly/nights.ts · Nights.beaconAt; src/open/ring.ts · Rings.bell); laws/src/rules.rs · bell / draw / cores_left_to_draw draws from those bytes. The round is not yet verified against the network’s public key: the relay’s word is taken. A rehearsal draws on the labelled stand-in.
14.2 Top up before Credits
Fresh sealed COREs may join the band only between sessions and before the coming night’s Credits open. Duplicate, previously fought or retired seals shall be refused.
✅ Enforced in codelaws/src/rules.rs · band_added / open_credits / bell; src/nightly/book.ts · FightBook.topUpAndOpen. Between sessions the engine refuses a bell until that night’s Credits have opened, so the band it draws from was frozen first.
14.3 An attempt and its limits
Each session shall give both corners the booked attempts, writing time and equal fuel. A whole reply without Lean, a refusal or an empty answer spends an attempt; a denied proof or foul spends one too. A foul alone is not disqualification.
✅ Enforced in codelaws/src/rules.rs · attempt / submit / spend_attempt / judge; src/match.ts · runMatch. Faults use Law 7.15; fuel uses Law 5.9.
14.4 A fight stays open
A held title session shall continue its fight on the house’s next night with a fresh CORE and a new session, unless a specific ending under these Laws applies. There is no session cap. A held CORE shall not be drawn again for the same two fighters.
✅ Enforced in codelaws/src/rules.rs · the_core_holds / cores_left_to_draw continues the fight and excludes fought seals; src/nightly/nights.ts · Nights.retireCore retires a factory CORE that held (Law 18.4), as row 47 now says. Row 37 lists every other way a fight ends.
14.5 The last session
A newcomer shall call an open title fight for one last session at the next bell. If its CORE holds, the fight ends in LOCKDOWN, the belt stays or remains vacant, and the purse goes to the house’s next title fight. If called before its first session, that first session is fought in full; the next held session is the last.
✅ Enforced in codelaws/src/rules.rs · newcomer / the_core_holds / belt_stays applies rows 5 and 65. A PROVEN still wins; a void is not a counted last session.
14.6 No fresh CORE
With no fresh CORE for the pair, an uncalled title fight shall have no session that night and raise an alert; no picks shall be taken for a bell that cannot ring. A called fight shall end in LOCKDOWN at once and return its waiting picks.
✅ Enforced in codelaws/src/rules.rs · no_fresh_core / lockdown_if_called_and_exhausted / pick. Its carried purse follows Law 16.4.
14.7 Void and replay
A void session shall return its picks and Prayers, set aside its CORE for this pair and replay on a fresh CORE on the house’s next night, never the same night. Repeated provider voids use Law 7.15; a bout has the tighter limit in Law 15.8.
✅ Enforced in codelaws/src/rules.rs · void_session / bell returns the pool, emits replay-next-night and refuses a second bell the same night; src/nightly/book.ts · FightBook.ring.
14.8 A PROVEN is kept
If a failure would void a session while a PROVEN is held, the fight shall stop, keep the proof and its money, and raise an alert. It shall wait for the referee’s verdict or a named Commission ruling; the failure alone shall not erase the PROVEN.
✅ Enforced in codelaws/src/rules.rs · void_session / stop_with_a_proven_held / while_stopped / rule_on_stopped_fight keeps it; src/nightly/nights.ts · Nights.resumeStopped checks the held proofs again when the referee is back and feeds their verdicts to the engine, and a person may rule resume or NO CONTEST through POST /api/nightly/ruling (src/nightly/nights.ts · Nights.rule), the operator’s token only on a public box.
14.9 Resume after a restart
A restart shall resume the same session. A cut reply costs no attempt; writing before the outage remains on its corner’s clock, and downtime does not. Downtime shall also move the session’s wall-clock ceiling by the same amount. A proof already with the referee shall be checked again. A claimed outage overlapping ruled events shall be refused.
✅ Enforced in codelaws/src/rules.rs · restart / reach_the_ceiling_if_due; src/nightly/session.ts · SessionHost.resume / checkAgain. The time a fight was stopped moves the ceiling too.
14.10 Turns and the ceiling
Corners sharing one machine shall take turns, with loading and waiting off their writing clocks. A PROVEN shall wait while its rival can still finish earlier under Law 6.4. On our machine the wall-clock ceiling shall leave room for both corners’ whole writing clocks in turn, with a model load before every attempt. At the ceiling writing and waiting end, even in a session that overruns it; unfinished replies do not count, but submitted proofs are still judged.
✅ Enforced in codesrc/runner/machine.ts · OneMachine; src/match.ts · runMatch; laws/src/rules.rs · could_still_finish_by / reach_the_ceiling_if_due; src/nightly/ceiling.ts · sessionCeilingMs sets the ceiling as 2 clocks of writing, a load of each model before every attempt, and a clock for the last checks. Measured: each model’s cold load time on the box (the Open’s qualifier; bun run fighters:measure). Assumed: a proof is checked while the other corner writes. It is never less than 8 clocks.
14.11 The title result
A challenger who wins becomes champion; an incumbent who wins records a defence. An exact tie under Law 6.4 leaves the belt where it was, including vacant. A beaten champion has no automatic rematch: it counts as already seen for 8 of its house’s nights, and after them, in the top two without the belt, it is someone new again, as anyone would be.
✅ Enforced in codelaws/src/rules.rs · breach / belt_after_win / belt_stays; src/nightly/arena.ts · cardFor / rememberChampions.
Bouts and the STRAWWEIGHT OPEN
Small models, one session, a result they can take home. No belt is at stake.
15.1 The open door
Anyone may enter a public, ungated open model by Hugging Face repository, pinned commit and one GGUF path. Its licence must be on the Commission’s list; another licence shall wait for the Commissioner and shall not be loaded or fought.
✅ Enforced in codesrc/open/entry.ts · parseEntry / licenceAllowed; src/open/door.ts · Door.enter. A missing commit is resolved once and pinned. This is the Open admission policy, alongside Laws 3.11 and 3.13.
15.2 Weigh the file
The Open’s weigh-in shall be the verified file size, at most 2³⁰ bytes, labelled 1 GB. The fighter shall be the SHA-256 of those exact bytes: the same file is one fighter; changed bytes are a new fighter. A retired file shall not re-enter.
✅ Enforced in codesrc/open/door.ts · Door.enter; src/open/fetch-weights.ts · Fetcher.fetch; src/open/loader.ts · Loader.load. This is not the title card’s decimal-GB parameter estimate.
15.3 The house serves it
The league shall load the verified file on its own machine, with the same house settings for every entrant: eight attempts, at most 1,024 tokens a reply, no thinking requested and default sampling. A one-attempt public qualifier shall require a complete machine reply, not a proof.
✅ Enforced in codesrc/open/box.ts · OllamaBox.register; src/open/qualifier.ts · qualify; src/open/rules.ts · HOUSE_SETTINGS / BOUT_ATTEMPTS. The qualifier measures speed for the bout clock; it awards no bout result.
15.4 The Open card
After the night’s last house, the enabled Open shall offer up to four bouts: debuts in entry order, then closest ratings, each fighter once, with no pair from either fighter’s last eight bouts. Fewer than two qualified fighters means no Open card.
✅ Enforced in codesrc/open/matchmaking.ts · matchmake / metRecently; src/open/card.ts · setOpenCard / boutClock. The clock uses the slower measured speed, rounded up to a power of two and no less than the CORE clock.
15.5 The ladder
The Open ladder shall start each new file at Elo 1024, with K = 32. A win scores 1, a loss 0, a draw one half; void and NO CONTEST score nothing. Each bout shall move the ladder once, separately from title and Arena ratings.
🟡 Partly enforcedsrc/open/ladder.ts · boutScore / ratedBout / rateBout rates wins and ordinary draws once. src/open/ring.ts · outcomeOf misclassifies an exact PROVEN tie as breached with no winner, so it does not reach the ladder as a draw.
15.6 One counted session, no belt
A bout shall be booked for one counted session with no champion and no carried purse, or refused. It shall never award, defend, retain or vacate a belt; never carry a purse; and never be called by a newcomer. Fuel, faults, Prayers, restarts and records otherwise follow the session Laws.
✅ Enforced in codelaws/src/rules.rs · check_bout / belt_after_win / belt_stays / newcomer. Rows 74 and 78 are named tests through the actual module. The Open currently offers no picks or Prayer purchases.
15.7 Win or draw
The bout’s first eligible PROVEN under Law 6.4 wins. With no PROVEN when both corners are out or time ends, the result is DRAW and the bout is over. An exact proof tie is also a draw. Its purse pays the winner’s backers, or returns by stake on a draw or an unbacked win; with no stakes, Prayers return to their buyers.
✅ Enforced in codelaws/src/rules.rs · breach / bout_drawn / shares_for ends an exact proof tie at stage draw, as any draw, and settles its pool; src/open/ring.ts · outcomeOf reports it as a DRAW, which the Open ladder scores as one.
15.8 One replay only
A void bout shall be replayed once, on the next night, never the same night, on a fresh CORE. A second void, or no fresh CORE for the replay, ends NO CONTEST with that session’s picks and Prayers returned in full. A restart resumes the existing session rather than spending the replay.
✅ Enforced in codelaws/src/rules.rs · void_session / no_fresh_core / restart / bell refuses a same-night replay; src/open/ring.ts · Rings.fight replays it the next night.
15.9 Fresh COREs and public records
An Open bout shall draw from sealed factory COREs of levels 1 to 4 that neither fighter has faced and no other open contest holds. Its record shall name both file hashes, source commits, house settings, CORE seal, attempts, verdicts, rating change and Laws engine seal. No Open result alone grants a title shot or owner payment.
✅ Enforced in codesrc/open/bouts.ts · Bouts; src/open/ring.ts · Rings.fight; src/open/ladder.ts · rateBout. The ladder leader’s route to a title shot remains unbuilt, and D1 remains open.
Credits in the nightly
One pool for one session. Every Credit has somewhere to go.
16.1 Play Credits and the purse
Nightly Credits shall be play chips with no purchase or redemption value. Each session’s purse shall be its locked picks plus the prices of Prayers carried by counted replies. Fuel is paid by the league this milestone, even when nobody picks.
✅ Enforced in codelaws/src/rules.rs · pool_of / start_session; src/nightly/purse.ts · Purse.apply. Uncounted or undelivered Prayers return under Article 17.
16.2 Picks by session
A pick shall name its backer, corner and whole Credits, belong to one session, and lock at its bell. A pick that would take the purse above 2⁵³ − 1 Credits shall be refused. A closed or unavailable session takes no picks.
✅ Enforced in codelaws/src/rules.rs · pick; src/nightly/purse.ts · backerOf / Purse.apply. The record uses a hashed viewer handle, not the wallet credential.
16.3 When the CORE holds
A held title session shall settle its pool once by rolling its purse into the same fight’s carried purse. The next session takes new picks; earlier backers do not retain a claim on that carried purse.
✅ Enforced in codelaws/src/rules.rs · the_core_holds; src/nightly/purse.ts · Purse.apply.
16.4 Where the carry goes
On a backed breach, that night’s winning backers share its purse and the carry. On an unbacked win or draw, the night’s purse returns by stake and the carry goes to the house’s next title fight; if nobody staked, its Prayer purse goes there too. LOCKDOWN sends both purses there. Nothing becomes the league’s windfall.
✅ Enforced in codelaws/src/rules.rs · shares_for / carry_to_next_fight; src/nightly/book.ts · FightBook.carryPurses / book. Row 50 states the no-stakes case; bout refunds are Law 15.7.
16.5 Void, stopped and no contest
A void session returns its picks and Prayers and preserves the fight’s earlier carry for replay. NO CONTEST returns that night in full and sends the title carry onward; earlier sessions stay settled. A stopped fight holds money until it can be ruled. A bout never carries money.
✅ Enforced in codelaws/src/rules.rs · void_session / no_contest / stop_with_a_proven_held / interference; src/nightly/purse.ts · Purse.apply. Row 58 states the stopped hold as its exception.
16.6 Corrections make whole
A corrected result shall preserve payments already made. The league shall pay only the shortfall due under the corrected result, with the original payments and the corrected ruling on the record. It shall not debit a prior recipient to fund the correction.
✅ Enforced in codelaws/src/rules.rs · correct_result emits owed and paid shares for each correction; src/nightly/purse.ts · Purse.apply / shortfalls pays only the shortfall, in play chips, from the league’s own account, which goes negative by exactly that amount on its own ledger line. No on-chain settlement exists.
Prayers
A sealed hint, heard by one corner. Never a proof bought from the crowd.
17.1 Four sealed hints
A factory CORE shall have four Prayers, from its weakest hint to its strongest outline. Each text and its place shall be sealed with the CORE before Credits open. A public-ladder CORE with no sealed Prayers shall sell none.
✅ Enforced in codesrc/factory/seal.ts · verifyAndSeal / prayerSeal; laws/src/rules.rs · is_a_sealed_core / prayer. A Prayer seal hashes the CORE seal, its place and its exact text.
17.2 A Prayer cannot prove
Before sealing, every Prayer shall be checked alone, as an extracted Lean block, as a theorem body and through its quoted code. Any accepted proof shall discard the CORE; so shall a check that runs out of time, which proves nothing. A Prayer shall not supply a proof in disguise.
🟡 Partly enforcedsrc/factory/prayers.ts · prayerAttempts gives the fixed list of wrappings; src/factory/seal.ts · verifyAndSeal discards a CORE on any accepted or timed-out Prayer check. Named row 54 tests enforce these wrappers. This is a finite check, not a proof that no paraphrase can reveal the answer.
17.3 The price ladder
During the drawn CORE’s live session, each corner may receive its next Prayer in order: first, second, third, fourth, priced at 1, 2, 4, 8 Credits. Each price joins the session purse. After four it is SOLD OUT; a wrong seal, wrong price, out or PROVEN corner, or purchase before the bell shall be refused.
✅ Enforced in codelaws/src/rules.rs · prayer / prayers_for_this_core.
17.4 With the next attempt
A bought Prayer shall wait for its corner’s next attempt and be delivered only to that corner. It shall not interrupt writing. If its reply did not count, the Prayer waits again; if no counted delivery remains at the session’s end, its price returns.
✅ Enforced in codelaws/src/rules.rs · deliver_prayers / prayers_wait_again / refund_undelivered_prayers; src/nightly/session.ts · SessionHost.deliverPrayers / withPrayers.
17.5 On the record
Every Prayer shall record its seal, place, price, buyer, corner, purchase and delivery. Its text becomes public when delivered, never before; the result shall state how many Prayers each corner received.
🟡 Partly enforcedsrc/nightly/session.ts · SessionHost.deliverPrayers; src/nightly/purse.ts · Purse.apply; src/nightly/nights.ts · Nights.keep / keepFight. The engine records the sealed purchase and delivery; the buyer and actual text are host evidence, not independently verified by the module.
17.6 A league setting
Prayers shall be a published league setting, sealed or off. Off means none may be bought. The current default is sealed; the Commissioner’s decision to retain or remove them remains open. Typed crowd hints require a separate exhibition rule.
🟡 Partly enforcedsrc/nightly/mode.ts · leagueSettings; src/nightly/nightly.ts · NightlyLeague.pray enforces the host switch; the pure engine has no off flag. The Open currently offers no Prayer purchases.
The nightly plan’s choice remains yours: keep sealed Prayers or switch them off. Current host default is sealed at 1, 2, 4, 8 Credits; typed Prayers are outside this edition.
The CORE factory
Fresh statements, verified before anyone fights them. The generator is not the referee.
18.1 Families and versions
A family shall deterministically make a CORE from its seed: a statement, reference proof, near miss, level, title and four Prayers. Any changed output shall change the family version. The family shall disclose what one instance teaches about the next.
🟡 Partly enforcedsrc/factory/family.ts · Dice; src/factory/families/index.ts · family; test/factory.test.ts · family fingerprint tests. The fixture pins sampled seeds, not every possible output; honest disclosure of transfer remains policy.
18.2 Verified before sealed
A candidate shall compile in the box; the referee shall accept its reference proof, deny its near miss, and reject every tested Prayer as a proof before sealing. A failure shall discard it with a reason. The same problem shall not be sealed twice.
🟡 Partly enforcedsrc/factory/seal.ts · verifyAndSeal / problemOf; src/factory/pool.ts · CorePool.seal. A timed-out Prayer check discards the CORE (Law 17.2); the near miss still counts only an accepted verdict, so a timeout there can pass as denied.
18.3 The seal and the band
A CORE seal shall be SHA-256 of the exact Challenge.lean bytes. The band shall publish seals, levels and Prayer seals, never undisclosed statements or seeds. It shall prefer eligible sealed factory COREs; an empty eligible pool may fall back to the public ladder only with that fact stated.
🟡 Partly enforcedsrc/factory/seal.ts · verifyAndSeal; src/nightly/cores.ts · bandFor; src/nightly/view.ts · nightView. High-house levels have no factory family yet and use the ladder; those public statements do not satisfy an unseen-CORE promise.
18.4 Drawn, then retired
A factory CORE shall be sealed until its bell, drawn when its statement is revealed, and retired when its session ends. It shall never be drawn again. A held public-ladder CORE may remain in the band with its record, but neither a held nor a void CORE may return to the same pair.
✅ Enforced in codesrc/factory/pool.ts · CorePool.drawn / retire; src/nightly/nights.ts · Nights.retireCore; laws/src/rules.rs · cores_left_to_draw / the_core_holds / void_session. Row 47 states the factory exception.
18.5 Retirement and publication
A CORE shown false or unprovable shall be retired with a named reason. Its live session is void, subject to the held-PROVEN protection; a past result changes only by correction. Reference proofs and unbought Prayer texts shall remain withheld after retirement until review and the Commissioner’s word.
🟡 Partly enforcedlaws/src/rules.rs · core_retired / correct_result; src/nightly/nights.ts · Nights.keep / keepFight. PUNK_PUBLISH_RETIRED is off by default, but code cannot verify the Commissioner’s word before an operator enables publication. No publication authorization is given here.
The ruled record
Replay the events. Keep the first record. Say where the league is still asking for trust.
19.1 Events from booking
The official fight record shall be every event the Laws ruled on, from booking in order. The stored fight is a cache; replaying the events with the booked engine shall reproduce the rulings and final digest.
🟡 Partly enforcedsrc/nightly/book.ts · FightBook.record / ruled; src/laws.ts · replay. The host omits effect-free ticks and discards their computed state. The nightly’s fight export and the Open’s downloadable bout record (src/open/bouts.ts · boutRecord) both carry every event from booking and the final digest.
19.2 The engine seal and chain
The record shall identify the Laws edition and SHA-256 of the engine bytes. Each ruling shall chain the previous digest and the engine’s canonical event bytes through SHA-256, beginning with 32 zero bytes. Corrections append; they do not erase.
✅ Enforced in codesrc/laws.ts · LAWS_SHA256 / replay; laws/src/lib.rs · rule_json / rule_value; laws/src/sha256.rs · chain; laws/src/rules.rs · correct_result. A matching digest identifies a replay, not the truth of its inputs.
19.3 What the host still attests
The record shall carry reply, proof and Kernel-output hashes, beacon source and round, each backer’s stake, and the author of a personal ruling. Until independent referees exist, times, measured writing clocks, silence, outages and provider build reports remain the league host’s assertions and shall be described as such.
🟡 Partly enforcedsrc/nightly/laws-events.ts · lawsEvent / fromMatch; src/nightly/builds.ts · buildEvents; laws/src/rules.rs · providers_silent / restart / submit. Hashes and consistent timestamps do not independently prove when writing happened or why a provider failed.
19.4 Fail closed
An unreadable session event shall void a live session, or stop it if a PROVEN is held, with an alert. Other unreadable or malformed non-session events shall be refused with an alert and no change. An unknown scenario shall be reported and given a row, never guessed into a winner.
🟡 Partly enforcedlaws/src/rules.rs · unreadable / fail_closed / refuse_and_alert / after_the_end. Row 60 protects a held proof; a readable event after a terminal result is refused with an alert. Writing a new row remains a review obligation.
19.5 Refuse impossible input
The engine shall refuse an unfair booking, an event no fight can produce, or input above 1 MiB. Times and amounts shall be exact whole numbers. No readable fight means no replacement cache: the host shall retain the fight it had. Another Laws edition shall not be silently reinterpreted.
✅ Enforced in codelaws/src/rules.rs · check_booking / check_bout; laws/src/json.rs · parse; laws/src/lib.rs · rule_json / rule_value; src/nightly/book.ts · FightBook.apply.
v0.1 → v0.5
Laws 2.2 and 2.3: each amendment with its old text, new text and reason; law numbers unchanged.
Approval. Matthew, 17 November 2026: 'Alright, that's a good vision. Get to work on the issue queue of what to do next and get us to the end of milestone 1.' The director reads this as the Commissioner's approval of the amendments proposed in issue #105 and in docs/nightly.html. It is open to his veto.
Effective. v0.4 is the engine-alignment edition dated 17 November 2026, subject to the approval reading above and the Commissioner’s veto. The preceding v0.2 amendment took effect with #204. The v0.4 draft changed no engine bytes. v0.5, of the same date, reconciles the decision table’s rows with the code (#226): its amendments below rest on the same approval line, and it goes with the Laws engine’s v0.5 bytes. It authorizes no release.
| Law | Old text (v0.1) | New text (v0.2) | Reason |
|---|---|---|---|
| 5.6 The bell and the clock | Only verdicts processed before the match clock stops may win; the clock starts with the engine’s recorded bell. | Each corner’s clock starts with the engine’s recorded bell and runs only while that corner is writing; it stops while the corner’s proof is with the referee. A reply finished before its corner’s clock runs out may win, even if its check ends after. | A slow referee or a loaded host decided fights: on 15 November a proof written in 1.7 s got its verdict at 54 s (#105, leak 1). Table rows 22, 33. |
| 5.7 Attempts | Each initiated reply shall consume one attempt, whether its submission is missing, invalid or accepted. | Each reply a netrunner gives shall consume one attempt, whether its submission is missing, empty, invalid or accepted. A reply we failed to deliver (our relay erroring, a provider’s error status, a broken or timed-out stream) is a fault and consumes no attempt. | An empty reply from our own relay burned an attempt; an infrastructure fault must never cost one, and a fighter’s own empty answer must not pass as one (#105, leak 6). Table rows 26, 27, 28. |
| 5.9 No fuel overrun | A netrunner shall not consume or win with model work beyond its published fuel ceiling. | A netrunner shall not consume or win with model work beyond its published fuel ceiling. Each request is booked at the fuel its corner has left; a reply that costs more earns nothing and its corner is out on fuel. The house pays any overrun. | An accepted reply that blew the tank could still win (#118). Table rows 32. |
| 6.4 The referee’s order breaks a tie → First to finish writing | If valid submissions compete for first place, the first accepted verdict processed in the referee’s match record shall win. | If more than one PROVEN reply competes for first place, the one that finished writing first on its own corner’s clock shall win. In the same millisecond, fewer attempts win, then less fuel burned; if those are equal too, it is a draw. | The first verdict the referee happened to process won, so checker latency decided fights (#105, leak 1). Table rows 22, 23. |
| 6.8 Checker limits | Lean submissions shall respect the referee’s fixed resource limits. | Lean submissions shall respect the referee’s fixed resource limits. A check that runs past the referee’s limit is no ruling and is checked again, up to 4 checks in all; a proof that runs past the limit on all 4 is denied. | Four proofs were denied for “more than 60 seconds to check” because the machine was busy: our slowness must not be a denial, and the bound stops a proof that hangs on purpose from stalling a fight (#105, leak 1). Table rows 31. |
| 7.13 Technical penalties | A rejected attempt shall consume its attempt; an exhausted corner shall flatline without an automatic award to its opponent. | A rejected attempt shall consume its attempt; a fault (Law 5.7) is not a rejected attempt. An exhausted corner shall flatline without an automatic award to its opponent. | Follows Law 5.7: a fault is ours, not the fighter’s (#105, leak 6). Table rows 24, 26, 27. |
| 7.15 Provider failures | A provider failure shall be classified separately from a rejected solution before an official result is confirmed. | A provider failure shall be classified separately from a rejected solution before an official result is confirmed, and shall consume no attempt. | Follows Law 5.7 (#105, leak 6). Table rows 28, 29. |
v0.2 → v0.4 · The nightly and the Laws engine
| Law | Old text (v0.2) | New text (v0.4) | Reason and table rows |
|---|---|---|---|
| 2.4 The booked edition governs | A bout shall keep the laws and economic terms published when its first bet was accepted, including during an amendment. | A fight shall keep the Laws edition, Genesis prompt, card and economic terms fixed at booking, before its first pick. Later ratings and amendments shall not change that booking. | Fix the nightly at booking, including its prompt and card. Table rows 12, 40, 41. |
| 3.4 No substitution | A change to a booked fighter’s model build or provider requires a new booking and cancellation of its existing pool. | A changed build behind a booked name shall end that fight as NO CONTEST. A fighter delisted before its bell shall not fight and its waiting Credits shall return. A replacement build requires a new booking; a provider change alone is not proof of a changed build. | Separate the fighter’s build from its serving provider and use the engine’s no-contest result. Table rows 13, 38. |
| 3.5 The weigh-in formula | Weight in decimal GB shall equal total parameters in billions multiplied by 4.5 and divided by 8. | For the title-fight card, weight in decimal GB shall equal total parameters in billions multiplied by 4.5 and divided by 8. The STRAWWEIGHT OPEN uses the file weigh-in in Law 15.2. | Keep the title estimate and Open file weigh-in distinct. Table rows 6, 11, 74. |
| 3.7 Symbolic weight ceilings | The class ceilings in Law 4.1 shall govern admission by estimated weight size. Each machine is the symbol of its class; no percentage-of-memory allowance shall alter the ceiling. | The class ceilings in Law 4.1 shall govern title-card admission by estimated weight size. Each machine is the symbol of its class; no percentage-of-memory allowance shall alter the ceiling. The Open’s file ceiling is Law 15.2. | State the Open exception without changing the title classes. Table rows 11, 74. |
| 3.8 Evidence of weight | An open-weight weigh-in shall use a verified total parameter count from safetensors, not a packed GGUF file size. | A title-card open-weight weigh-in shall use a verified total parameter count, not a packed file size. The STRAWWEIGHT OPEN shall weigh the actual GGUF bytes under Law 15.2. | The two entry routes measure different things. Table rows 11, 74. |
| 3.12 Neon Circuit files | The Neon Circuit shall load safetensors only and shall never execute repository-supplied custom code. | The wider Neon Circuit shall load safetensors only and shall never execute repository-supplied custom code. Its first house, the STRAWWEIGHT OPEN, admits the pinned GGUF file under Article 15 and supplies the serving settings itself. | Make the built Open route an explicit exception to the planned circuit. Table rows 74. |
| 4.2 Title designation | A held belt shall be contested only in a main event containing its champion; a vacant belt shall always be on the line between eligible fighters. Every eighth bout shall be the SINGULARITY title main event. | A nightly title fight shall be booked under Article 13: the champion against a newcomer, or the top two for a vacant belt. An Article 15 bout shall never contest a belt. The simulated arena’s every-eighth-bout SINGULARITY main event is an exhibition schedule. | Separate the nightly’s title card from the simulated rotation and the Open. Table rows 1, 2, 3, 74. |
| 4.10 Elo standings | Each fighter shall start at Elo 1500 and use one rating across all weight classes. Each bout shall update both ratings with K = 32: a win scores 1, a loss 0 and LOCKDOWN 0.5. Each division shall list its champion first, then other fighters by descending Elo. | The simulated arena shall rate fighters from Elo 1500 under the formula below. The nightly’s own ratings and the Open ladder shall start at 1024 with K = 32: a win scores 1, a loss 0, a draw one half; HELD, LOCKDOWN, void and NO CONTEST move no rating. Arena ratings shall remain separately named. | Do not count a held title session as an Open draw or mix real and simulated ratings. Table rows 34, 37, 45, 46, 75, 76, 77. |
| 5.1 Seal before betting | The league shall publish the CORE’s SHA-256 fingerprint before accepting any bet on that bout. | Before a session’s first pick the league shall publish its band of CORE seals. The bell shall draw one CORE only from that published band. A pool booked on a single CORE shall publish that CORE’s SHA-256 fingerprint before its first stake. | Seal the eligible band before Credits open; select the CORE at the bell. Table rows 19, 73. |
| 5.4 Private retry feedback | A corner shall receive only its own previous reply and rejection feedback between attempts. | A corner shall receive only its own previous replies and rejection feedback between attempts, together with its own sealed Prayers under Article 17. No opponent conversation shall be supplied. | Permit the sealed hint channel without opening an opponent or outside-help channel. Table rows 56, 64. |
| 5.6 The bell and the clock | Each corner’s clock starts with the engine’s recorded bell and runs only while that corner is writing; it stops while the corner’s proof is with the referee. A reply finished before its corner’s clock runs out may win, even if its check ends after. | Each corner’s clock shall count only its own writing, from each attempt until its reply or interruption; it shall never run backwards. Waiting for a machine, the referee or the league shall not count. A reply finished before the writing limit may win after its check; the wall-clock ceiling is separate. | Exclude turn and loading waits as well as referee waits. Table rows 22, 33, 35, 71, 72. |
| 5.9 No fuel overrun | A netrunner shall not consume or win with model work beyond its published fuel ceiling. Each request is booked at the fuel its corner has left; a reply that costs more earns nothing and its corner is out on fuel. The house pays any overrun. | A netrunner shall not win with work beyond its published fuel ceiling. Each request shall be booked at the fuel left; a reply that costs more shall not count. If no further reply fits, the corner is out for the session. The house shall pay any overrun. | State both fuel exits, and distinguish sporting enforcement from a provider’s final bill. Table rows 32. |
| 5.10 Reply-only competition | During a Lean bout a netrunner may only return text; it may not browse, call tools, use outside help or contact the opponent or referee outside the submission channel. | During a Lean contest a netrunner may only return text; it may not browse, call tools, obtain outside help other than Article 17’s sealed Prayers, or contact the opponent or referee outside the submission channel. | Name the only permitted crowd assistance. Table rows 56, 64. |
| 5.12 End of a bout | The bout shall stop at the first accepted verdict, the clock limit, or exhaustion of both corners. | A session shall end when a PROVEN can no longer be beaten under Law 6.4, or when its limits end both corners and all pending proofs have been judged. A held verdict shall wait under Article 14. The session’s end shall not by itself end an open title fight. | First verdict arrival is not first to finish; a session and a title fight have different endings. Table rows 21, 22, 33, 34, 60, 71, 72, 76. |
| 6.5 LOCKDOWN | A completed, valid bout with no accepted verdict shall be recorded as LOCKDOWN: a draw for both fighters in W–L–D and Elo, ending both current win streaks and leaving belts unchanged. | If a title session ends without a PROVEN, the CORE holds and the fight stays open, unless its last session calls LOCKDOWN under Law 14.5. An Article 15 bout instead ends in a DRAW. NO CONTEST is a separate result; neither HELD nor LOCKDOWN is a rated draw. | Replace the old single-session LOCKDOWN disposition. Table rows 5, 34, 37, 68, 76. |
| 6.6 The fight record | The official record shall identify the CORE, both fighter builds, laws version, limits, submissions, verdict order, timing and final costs. | The official record shall identify the CORE, both fighter builds, Laws edition and engine seal, Genesis prompt, limits, replies, verdicts, writing clocks and costs with their source. Every ruled event from booking shall be preserved for replay under Article 19. | Make the replayable event list, not the cached fight, the record. Table rows 38, 40, 41, 69. |
| 6.8 Checker limits | Lean submissions shall respect the referee’s fixed resource limits. A check that runs past the referee’s limit is no ruling and is checked again, up to 4 checks in all; a proof that runs past the limit on all 4 is denied. | Lean submissions shall respect the referee’s fixed resource limits. A check past its limit shall be checked again, up to four checks in all; four timeouts deny the proof. Four referee crashes are a referee failure under Law 7.15, never a denial. | Distinguish a bounded timeout from failed infrastructure. Table rows 29, 31, 60. |
| 7.14 Disciplinary penalties | The Commission shall issue a reasoned ruling before disqualification or a ban. | The Commission shall issue a reasoned ruling before disqualification or a ban. Detected escape or interference shall stop the fight and hold its money pending that ruling; a stop is not a final NO CONTEST. | Separate the engine’s stopped state from a final cancellation and preserve D3. Table rows 25, 36, 60. |
| 7.15 Provider failures | A provider failure shall be classified separately from a rejected solution before an official result is confirmed, and shall consume no attempt. | A transport failure shall cost no attempt. The nightly default is one retry of our relay, then a void session; a provider silent for 32 seconds or failing in transport voids both corners, unless an eligible earlier proof is PROVEN. Both-provider or referee failure voids the session, subject to the held-PROVEN protection in Law 14.8. Two consecutive void sessions blamed on one provider withdraw its fighter as NO CONTEST. | Write the engine’s outage default while leaving the Commissioner’s decision open. Table rows 27, 28, 29, 30, 31, 60. |
| 7.16 No-contest refunds | A no contest shall create a refund outcome, never a LOCKDOWN rollover or a fabricated winner. | NO CONTEST shall award no fabricated winner or LOCKDOWN rollover. In the nightly the current default returns that session’s picks and Prayers in full, sends its carried purse to the house’s next title fight, and leaves earlier sessions settled. A bout carries nothing. | State the full-refund nightly default without deciding D5 for real-money rails. Table rows 52, 62, 74, 77. |
| 8.2 Filing window and finality | Every bout shall publish its appeal deadline and payout-finality rule before betting opens. | Every fight shall publish its appeal deadline and payout-finality rule before picks open. Under the nightly’s current default, correction shall not claw back an amount paid; the league shall make whole whoever the corrected result is owed. The filing window remains the Commissioner’s decision. | Keep the unresolved window while stating the engine’s correction model. Table rows 43. |
| 8.5 An accountable ruling | The Commission shall publish each appeal ruling and correction without erasing the original record. | The Commission shall publish each appeal ruling with its author and reason. A correction shall name the digest of the ruling it corrects, preserve the first record, correct the result and belt, and make whole those shorted without taking back payments already made. | Bind corrections to an identified result and preserve both the evidence and paid money. Table rows 43, 69. |
| 9.1 Everyone can watch; wallets are 21+ | People under 21 may watch and use the site, including its no-value play chips. Only connecting a crypto wallet is locked behind the 21-and-over confirmation; real-money play additionally requires verified age and Law 9.3’s controls. | Everyone may watch. The under-21 view and the stream shall show no Credits, purse, picks, odds, Prayers or wallet. Connecting a crypto wallet requires the 21-and-over confirmation; real-money access additionally requires verified age and Law 9.3’s controls. | Write the no-currency view without treating a visual gate as verified age. Table rows 57. |
| 9.5 The split | At lock, the pool shall split into the published house cut, credits share and remaining purse. | An on-chain pool shall split at lock into its published house cut, credits share and remaining purse. The nightly’s play Credits follow Article 16: the league fronts fuel and takes no such cut. | Do not deduct legacy contract cuts from the nightly play purse. Table rows 17, 49, 51, 58. |
| 9.6 Pay only for the burn | Bettors’ model-credit charge shall equal the reconciled burn, with every unspent credit returned to their bout’s purse. | Where bettors fund model credit, their charge shall equal reconciled burn, capped at the published allowance, and unspent credit shall return to their pool. In the nightly this milestone the league pays fuel; play Credits shall not pay provider bills. | Keep actual burn distinct from nightly play Credits and house-funded fuel. Table rows 16, 17, 32. |
| 9.8 Parimutuel pool payouts | Backers of the winning corner shall share the final purse in proportion to their stake on that corner. | Backers of the winning corner shall share the final purse by their stake on that corner. In a nightly title fight, only that session’s winning backers share its own purse and the carried purse; earlier stakes confer no later claim. | Define which night’s backers receive the carry. Table rows 49, 58. |
| 9.10 Pool close | A pool stake shall be accepted only while the pool is Open and strictly before its published closing time. | A pool stake shall be accepted only while its picks are open and before its bell or published close. Each nightly session shall have its own picks, locked at its bell; no live pick may join them. | Keep the session pool separate from legacy live tickets. Table rows 48, 58. |
| 9.15 An unbacked winner | If the actual winning corner has no backers, all backers shall share that bout’s remaining own purse by total stake, excluding carried jackpots. | If the winner has no backers, that session’s own purse shall return by stake and its carried purse shall go to the house’s next title fight. With no stakes at all, a title session’s Prayer purse shall carry there too; a bout’s Prayer prices shall instead return to their buyers. | Account for a Prayer-only purse and prohibit carry from a bout. Table rows 50, 62, 75, 76. |
| 9.16 Locked-match rescue | Anyone may rescue an unresolved Locked pool strictly more than seven days after lock, sharing only its remaining own purse among all backers. | Anyone may rescue an unresolved Locked on-chain pool strictly more than seven days after lock, sharing only its remaining own purse among all backers. A nightly title fight shall use one pool per session, disposed of once that night, never one unresolved pool for the whole fight. | An uncapped fight must not leave a single pool exposed to the seven-day rescue. Table rows 58. |
| 9.18 LOCKDOWN economics | The no-finish disposition shall be fixed and disclosed before the first stake. | The no-finish disposition shall be fixed before picks open. The nightly default rolls a held title session’s purse into that fight, sends LOCKDOWN’s purse and carry to the house’s next title fight, and refunds a draw’s own purse by stake while its carry goes onward. An Article 15 bout never rolls a purse. | Replace the proposed house-takes option with the engine’s current default, leaving D9 open. Table rows 23, 51, 62, 76. |
| 9.19 Jackpot custody | A carried jackpot shall go only to a later winning pool or roll onward; it shall not pay house cuts or refund unrelated stakes. | A carried title purse shall reach later winning backers or the house’s next title fight. It shall never become a house cut, refund unrelated stakes, or enter an Article 15 bout. | Make custody explicit at every title ending and at the bout boundary. Table rows 50, 52, 62, 74. |
| 11.2 Annex A: LEAN | The current proof league shall use Article 6’s four-check referee and first-accepted-proof result. | The current proof league shall use Article 6’s four-check referee and the first-to-finish-writing result under Law 6.4. Title fights use sessions under Article 14; bouts use Article 15. | Remove the remaining first-accepted-verdict wording. Table rows 21, 22, 23, 74, 75, 76. |
| 12.1 CORE | The CORE is the fixed problem a bout asks both netrunners to solve. | The CORE is the fixed problem one session asks both netrunners to solve. A title fight may meet many COREs; a counted bout meets one. | Define the unit that carries the sealed problem. Table rows 19, 34, 74. |
| 12.2 Netrunner, version and corner | A netrunner is an entered model; its version labels the model release beneath its name. Pink and cyan identify its corner for one bout. A quoted earned title is an achievement under Law 4.9, distinct from its name, version and division belt; Elo is its cross-class rating under Law 4.10. | A netrunner is one registered build; its public version labels that build. Pink and cyan are its corners for one contest. An earned title under Law 4.9 is distinct from a belt. Arena ratings, nightly ratings and the Open ladder shall be named separately. | Separate build identity and the three rating systems. Table rows 6, 38, 74. |
| 12.4 LOCKDOWN and no contest | LOCKDOWN is a valid bout without a winner: a draw in W–L–D and Elo that breaks both win streaks and leaves belts unchanged. No contest is an invalidated bout that awards no win, loss, draw, belt transfer, defence, earned-title credit or Elo change. | HELD means a title session ended without a PROVEN and its fight continues. LOCKDOWN ends a called title fight with the belt unchanged; it is not a rated draw. A DRAW ends a bout or an exact proof tie. VOID requires replay; STOPPED awaits evidence or a ruling. NO CONTEST awards no sporting win, loss, draw, defence or rating change; a retirement may vacate a belt under D2. | Give each engine ending its own meaning and avoid a blanket prohibition on retirement vacancies. Table rows 5, 23, 29, 34, 36, 39, 60, 68, 76, 77. |
| 12.5 Flatlined and disqualified | Flatlined means a corner is out of the fight; disqualified means the Commission imposed a disciplinary result. | Flatlined means a corner is out for the session; disqualified means the Commission imposed a disciplinary result. Exhaustion shall not decide a title fight that the Laws keep open. | Do not turn a spent session into a permanent withdrawal. Table rows 32, 34, 37. |
| 13.1 The house’s night | new | The houses shall fight on New York nights: SINGULARITY Sunday, SUPER HEAVYWEIGHT Monday, HEAVYWEIGHT Tuesday, CRUISERWEIGHT Wednesday, MIDDLEWEIGHT Thursday, LIGHTWEIGHT Friday, and STRAWWEIGHT then FLYWEIGHT Saturday. | Publish the weekly house calendar. Table rows 14, 20. |
| 13.2 The New York bell | new | The card shall be set at 1 pm and the bell scheduled for 9 pm in New York, through daylight saving. Saturday’s FLYWEIGHT bell shall wait until STRAWWEIGHT’s session ends if later. | State the nominal bell and the explicit second-house exception. Table rows 12, 14, 18, 20. |
| 13.3 The Arena sets the card | new | The title card shall use the Arena’s published ratings in each house, with the snapshot’s date and credit. If the current snapshot cannot be read, the last good one shall be used; older than 32 days shall book no new title fight. | Keep the source, fallback and freshness limit visible. Table rows 8, 9. |
| 13.4 One build, one fighter | new | Settings of the same build shall occupy one seat at that build’s best Arena rating. A new setting is not a newcomer. Every serving build shall be reported at each bell; a changed one is governed by Law 3.4. | Do not create new fighters by renaming settings. Table rows 6, 38. |
| 13.5 A newcomer’s title shot | new | A build newly reaching either of a house’s top two Arena seats shall meet its champion on the house’s next night. If two arrive together, the higher-rated shall fight first and the other wait. Fighters of one maker may meet. | Define the title trigger and queue. Table rows 1, 4, 10. |
| 13.6 A vacant belt | new | When a house’s belt is vacant, its top two eligible fighters shall fight for it. Fewer than two means NO CONTENDER and no title fight. | State the vacancy branch. Table rows 2, 7. |
| 13.7 A night without a challenger | new | With a held belt and no newcomer, no title fight shall be booked. The current default offers that night to the STRAWWEIGHT OPEN when enabled and supplied with qualified fighters; the screen shall say when no fight is available. | Preserve the Commissioner’s choice of the Open as the nightly. Table rows 3. |
| 13.8 A seat must be served | new | A fighter that cannot be weighed or served shall not take a fighting seat. The card shall name the passed-over fighter and the reason. Delisting after the card is set invokes Law 3.4. | State both admission and the check at the bell. Table rows 11, 13. |
| 13.9 The card stands | new | Once set, a night’s card shall not change because the ratings moved. Its fighters and booked terms shall stand, subject to withdrawal and the Laws’ explicit fault rulings. | Make booking durable. Table rows 12, 40, 41. |
| 13.10 One counted bell | new | Each session shall bear its house and New York date. A counted night shall not ring twice; only a void session may be replayed. A late return within two hours may ring late with an alert; later shall move to the house’s next night with an alert. | Name the bell and record delay without concealing host limitations. Table rows 15, 18. |
| 13.11 Fuel before the bell | new | Both equal tanks shall fit under the league’s daily fuel cap before a session starts; otherwise the session shall move to the house’s next night. No picks is no reason to cancel: this milestone the league pays fuel. | Reserve both corners before starting. Table rows 16, 17. |
| 13.12 Protect the night | new | A deploy shall keep clear from one hour before the bell until the session ends: production refuses, QA queues until clear. An emergency override shall be logged. | Record the operational window and its failure mode. Table rows 44. |
| 14.1 Draw at the bell | new | Each session shall draw one fresh CORE from the house’s published band as it stood when that night’s Credits opened. The draw shall use public randomness the league does not control, with its source and round on the record. | Commit the choices before the draw; disclose the unfinished beacon. Table rows 19. |
| 14.2 Top up before Credits | new | Fresh sealed COREs may join the band only between sessions and before the coming night’s Credits open. Duplicate, previously fought or retired seals shall be refused. | Allow uncapped fights to replenish their band fairly. Table rows 73. |
| 14.3 An attempt and its limits | new | Each session shall give both corners the booked attempts, writing time and equal fuel. A whole reply without Lean, a refusal or an empty answer spends an attempt; a denied proof or foul spends one too. A foul alone is not disqualification. | Collect the counted-reply rules without equating faults with attempts. Table rows 24, 25, 26, 32, 33. |
| 14.4 A fight stays open | new | A held title session shall continue its fight on the house’s next night with a fresh CORE and a new session, unless a specific ending under these Laws applies. There is no session cap. A held CORE shall not be drawn again for the same two fighters. | Distinguish continuation from a one-session bout. Table rows 34, 37, 47. |
| 14.5 The last session | new | A newcomer shall call an open title fight for one last session at the next bell. If its CORE holds, the fight ends in LOCKDOWN, the belt stays or remains vacant, and the purse goes to the house’s next title fight. If called before its first session, that first session is fought in full; the next held session is the last. | Give the next contender a path without erasing the first session. Table rows 5, 65, 68. |
| 14.6 No fresh CORE | new | With no fresh CORE for the pair, an uncalled title fight shall have no session that night and raise an alert; no picks shall be taken for a bell that cannot ring. A called fight shall end in LOCKDOWN at once and return its waiting picks. | Define exhaustion of the band. Table rows 66. |
| 14.7 Void and replay | new | A void session shall return its picks and Prayers, set aside its CORE for this pair and replay on a fresh CORE. The normal replay is the house’s next night; row 15 permits the engine a same-night replay. Repeated provider voids use Law 7.15; a bout has the tighter limit in Law 15.8. | State replay, money and the spent CORE together. Table rows 15, 27, 28, 29, 30, 52, 67, 77. |
| 14.8 A PROVEN is kept | new | If a failure would void a session while a PROVEN is held, the fight shall stop, keep the proof and its money, and raise an alert. It shall wait for the referee’s verdict or a named Commission ruling; the failure alone shall not erase the PROVEN. | Protect accepted evidence through infrastructure failure. Table rows 60. |
| 14.9 Resume after a restart | new | A restart shall resume the same session. A cut reply costs no attempt; writing before the outage remains on its corner’s clock, and downtime does not. A proof already with the referee shall be checked again. A claimed outage overlapping ruled events shall be refused. | State what the restart preserves and what time it excludes. Table rows 35. |
| 14.10 Turns and the ceiling | new | Corners sharing one machine shall take turns, with loading and waiting off their writing clocks. A PROVEN shall wait while its rival can still finish earlier under Law 6.4. At the wall-clock ceiling writing and waiting end; unfinished replies do not count, but submitted proofs are still judged. | Make shared-machine fairness and the show’s outer limit explicit. Table rows 22, 33, 71, 72. |
| 14.11 The title result | new | A challenger who wins becomes champion; an incumbent who wins records a defence. An exact tie under Law 6.4 leaves the belt where it was, including vacant. A beaten champion has no automatic rematch; it must reach the top two again as a newcomer would. | Write succession and expose the rematch contradiction. Table rows 21, 23, 45, 46, 68. |
| 15.1 The open door | new | Anyone may enter a public, ungated open model by Hugging Face repository, pinned commit and one GGUF path. Its licence must be on the Commission’s list; another licence shall wait for the Commissioner and shall not be loaded or fought. | Publish the built Open’s entry route. Table rows 74. |
| 15.2 Weigh the file | new | The Open’s weigh-in shall be the verified file size, at most 2³⁰ bytes, labelled 1 GB. The fighter shall be the SHA-256 of those exact bytes: the same file is one fighter; changed bytes are a new fighter. A retired file shall not re-enter. | Bind entry to the actual file. Table rows 6, 38, 74. |
| 15.3 The house serves it | new | The league shall load the verified file on its own machine, with the same house settings for every entrant: eight attempts, at most 1,024 tokens a reply, no thinking requested and default sampling. A one-attempt public qualifier shall require a complete machine reply, not a proof. | Define the uniform serving and qualification terms. Table rows 72, 74. |
| 15.4 The Open card | new | After the night’s last house, the enabled Open shall offer up to four bouts: debuts in entry order, then closest ratings, each fighter once, with no pair from either fighter’s last eight bouts. Fewer than two qualified fighters means no Open card. | Publish the Open’s independent matchmaking. Table rows 3, 74. |
| 15.5 The ladder | new | The Open ladder shall start each new file at Elo 1024, with K = 32. A win scores 1, a loss 0, a draw one half; void and NO CONTEST score nothing. Each bout shall move the ladder once, separately from title and Arena ratings. | State the builder’s current sporting reward. Table rows 75, 76, 77. |
| 15.6 One counted session, no belt | new | A bout shall be booked for one counted session with no champion and no carried purse, or refused. It shall never award, defend, retain or vacate a belt; never carry a purse; and never be called by a newcomer. Fuel, faults, Prayers, restarts and records otherwise follow the session Laws. | Keep bouts completely outside the title lifecycle. Table rows 74, 78. |
| 15.7 Win or draw | new | The bout’s first eligible PROVEN under Law 6.4 wins. With no PROVEN when both corners are out or time ends, the result is DRAW and the bout is over. An exact proof tie is also a draw. Its purse pays the winner’s backers, or returns by stake on a draw or an unbacked win; with no stakes, Prayers return to their buyers. | End the bout in one counted result and dispose of its pool. Table rows 23, 75, 76. |
| 15.8 One replay only | new | A void bout shall be replayed once at the next house bell on a fresh CORE. A second void, or no fresh CORE for the replay, ends NO CONTEST with that session’s picks and Prayers returned in full. A restart resumes the existing session rather than spending the replay. | Bound a bout without imposing a cap on title fights. Table rows 35, 52, 67, 77. |
| 15.9 Fresh COREs and public records | new | An Open bout shall draw from sealed factory COREs of levels 1 to 4 that neither fighter has faced and no other open contest holds. Its record shall name both file hashes, source commits, house settings, CORE seal, attempts, verdicts, rating change and Laws engine seal. No Open result alone grants a title shot or owner payment. | Provide evidence and keep future prizes and title access distinct. Table rows 19, 47, 69, 74. |
| 16.1 Play Credits and the purse | new | Nightly Credits shall be play chips with no purchase or redemption value. Each session’s purse shall be its locked picks plus the prices of Prayers carried by counted replies. Fuel is paid by the league this milestone, even when nobody picks. | Define the pool that the engine disposes of. Table rows 17, 49, 53, 58, 64. |
| 16.2 Picks by session | new | A pick shall name its backer, corner and whole Credits, belong to one session, and lock at its bell. A pick that would take the purse above 2⁵³ − 1 Credits shall be refused. A closed or unavailable session takes no picks. | Bound the exact accounting and identify its backers. Table rows 48, 63, 66, 69. |
| 16.3 When the CORE holds | new | A held title session shall settle its pool once by rolling its purse into the same fight’s carried purse. The next session takes new picks; earlier backers do not retain a claim on that carried purse. | Separate settlement of a held night from settlement of the whole fight. Table rows 34, 49, 51, 58. |
| 16.4 Where the carry goes | new | On a backed breach, that night’s winning backers share its purse and the carry. On an unbacked win or draw, the night’s purse returns by stake and the carry goes to the house’s next title fight; if nobody staked, its Prayer purse goes there too. LOCKDOWN sends both purses there. Nothing becomes the league’s windfall. | State each destination, including a Prayer-only title purse. Table rows 23, 49, 50, 62. |
| 16.5 Void, stopped and no contest | new | A void session returns its picks and Prayers and preserves the fight’s earlier carry for replay. NO CONTEST returns that night in full and sends the title carry onward; earlier sessions stay settled. A stopped fight holds money until it can be ruled. A bout never carries money. | Name the different dispositions instead of treating every interruption alike. Table rows 36, 52, 58, 60, 62, 74, 77. |
| 16.6 Corrections make whole | new | A corrected result shall preserve payments already made. The league shall pay only the shortfall due under the corrected result, with the original payments and the corrected ruling on the record. It shall not debit a prior recipient to fund the correction. | Make the no-clawback obligation concrete. Table rows 43. |
| 17.1 Four sealed hints | new | A factory CORE shall have four Prayers, from its weakest hint to its strongest outline. Each text and its place shall be sealed with the CORE before Credits open. A public-ladder CORE with no sealed Prayers shall sell none. | Tie every hint to the drawn problem. Table rows 19, 54, 64, 73. |
| 17.2 A Prayer cannot prove | new | Before sealing, every Prayer shall be checked alone, as an extracted Lean block, as a theorem body and through its quoted code. Any accepted proof shall discard the CORE. A Prayer shall not supply a proof in disguise. | State the tested safeguard without claiming logical impossibility. Table rows 54. |
| 17.3 The price ladder | new | During the drawn CORE’s live session, each corner may receive its next Prayer in order: first, second, third, fourth, priced at 1, 2, 4, 8 Credits. Each price joins the session purse. After four it is SOLD OUT; a wrong seal, wrong price, out or PROVEN corner, or purchase before the bell shall be refused. | Fix both the order and the price. Table rows 55, 64. |
| 17.4 With the next attempt | new | A bought Prayer shall wait for its corner’s next attempt and be delivered only to that corner. It shall not interrupt writing. If its reply did not count, the Prayer waits again; if no counted delivery remains at the session’s end, its price returns. | Deliver hints on the attempt boundary and refund unused help. Table rows 53, 56. |
| 17.5 On the record | new | Every Prayer shall record its seal, place, price, buyer, corner, purchase and delivery. Its text becomes public when delivered, never before; the result shall state how many Prayers each corner received. | Make assisted results inspectable. Table rows 56, 64, 69. |
| 17.6 A league setting | new | Prayers shall be a published league setting, sealed or off. Off means none may be bought. The current default is sealed; the Commissioner’s decision to retain or remove them remains open. Typed crowd hints require a separate exhibition rule. | Keep the optional assistance channel explicit. Table rows 54, 64, 74. |
| 18.1 Families and versions | new | A family shall deterministically make a CORE from its seed: a statement, reference proof, near miss, level, title and four Prayers. Any changed output shall change the family version. The family shall disclose what one instance teaches about the next. | Describe the source of fresh problems without pretending they are unrelated. Table rows 19, 54. |
| 18.2 Verified before sealed | new | A candidate shall compile in the box; the referee shall accept its reference proof, deny its near miss, and reject every tested Prayer as a proof before sealing. A failure shall discard it with a reason. The same problem shall not be sealed twice. | Make verification a precondition, with the negative-check gap disclosed. Table rows 19, 54. |
| 18.3 The seal and the band | new | A CORE seal shall be SHA-256 of the exact Challenge.lean bytes. The band shall publish seals, levels and Prayer seals, never undisclosed statements or seeds. It shall prefer eligible sealed factory COREs; an empty eligible pool may fall back to the public ladder only with that fact stated. | Bind the exact bytes and identify the fallback. Table rows 19, 47, 73. |
| 18.4 Drawn, then retired | new | A factory CORE shall be sealed until its bell, drawn when its statement is revealed, and retired when its session ends. It shall never be drawn again. A held public-ladder CORE may remain in the band with its record, but neither a held nor a void CORE may return to the same pair. | Record the actual factory lifecycle without hiding row 47’s conflicting text. Table rows 19, 47, 67. |
| 18.5 Retirement and publication | new | A CORE shown false or unprovable shall be retired with a named reason. Its live session is void, subject to the held-PROVEN protection; a past result changes only by correction. Reference proofs and unbought Prayer texts shall remain withheld after retirement until review and the Commissioner’s word. | Separate defective-CORE rulings from permission to reveal reference material. Table rows 42, 43, 60, 69. |
| 19.1 Events from booking | new | The official fight record shall be every event the Laws ruled on, from booking in order. The stored fight is a cache; replaying the events with the booked engine shall reproduce the rulings and final digest. | Make the event stream authoritative. Table rows 69. |
| 19.2 The engine seal and chain | new | The record shall identify the Laws edition and SHA-256 of the engine bytes. Each ruling shall chain the previous digest and the engine’s canonical event bytes through SHA-256, beginning with 32 zero bytes. Corrections append; they do not erase. | Bind replay to a versioned program and ordered events. Table rows 41, 43, 69. |
| 19.3 What the host still attests | new | The record shall carry reply, proof and Kernel-output hashes, beacon source and round, each backer’s stake, and the author of a personal ruling. Until independent referees exist, times, measured writing clocks, silence, outages and provider build reports remain the league host’s assertions and shall be described as such. | Name the remaining trust boundary. Table rows 19, 28, 35, 38, 43, 69, 72. |
| 19.4 Fail closed | new | An unreadable session event shall void a live session, or stop it if a PROVEN is held, with an alert. Other unreadable or malformed non-session events shall be refused with an alert and no change. An unknown scenario shall be reported and given a row, never guessed into a winner. | Distinguish corrupt session evidence from refused administrative input. Table rows 59, 60, 61. |
| 19.5 Refuse impossible input | new | The engine shall refuse an unfair booking, an event no fight can produce, or input above 1 MiB. Times and amounts shall be exact whole numbers. No readable fight means no replacement cache: the host shall retain the fight it had. Another Laws edition shall not be silently reinterpreted. | Fix the deterministic boundary and preserve the last readable state. Table rows 41, 63, 70, 74. |
v0.4 → v0.5 · Rows and code reconciled (#226)
| Law | Old text (v0.4) | New text (v0.5) | Reason and table rows |
|---|---|---|---|
| 13.7 A night without a challenger | With a held belt and no newcomer, no title fight shall be booked. The current default offers that night to the STRAWWEIGHT OPEN when enabled and supplied with qualified fighters; the screen shall say when no fight is available. | With a held belt and no newcomer, no title fight shall be booked, and the night belongs to the STRAWWEIGHT OPEN, on a league that runs it. The Open also plays after a night’s title session. Without two qualified fighters there is no Open card; the screen shall say when no fight is available. | The Commissioner’s decision D12, through the director (#226): the quiet night is the Open’s, and the Open also plays after a title session. Table rows 3. |
| 13.8 A seat must be served | A fighter that cannot be weighed or served shall not take a fighting seat. The card shall name the passed-over fighter and the reason. Delisting after the card is set invokes Law 3.4. | A fighter that cannot be weighed or served shall not take a fighting seat. The card shall pass it over and name it and the reason; the next newcomer, if there is one, takes the shot. Delisting after the card is set invokes Law 3.4. | Row 11 said “No fight” where the card passes an unservable newcomer over and the next newcomer still gets the shot; the row now says what the card does (#226). Table rows 11. |
| 13.10 One counted bell | Each session shall bear its house and New York date. A counted night shall not ring twice; only a void session may be replayed. A late return within two hours may ring late with an alert; later shall move to the house’s next night with an alert. | Each session shall bear its house and New York date. A night shall ring once: a night that has had a bell, void or not, shall not ring again, and a void session is replayed on the house’s next night. A restart that resumes a live session is not a new session. A late return within two hours may ring late; later, or a night first seen more than two hours after its bell, shall move to the house’s next night. An alert shall go out for a bell two minutes late or more. | The engine allowed a same-night replay of a void session while the host refused it, and a night first seen over two hours late was skipped silently (#226). Table rows 15, 18, 28, 29, 77. |
| 13.12 Protect the night | A deploy shall keep clear from one hour before the bell until the session ends: production refuses, QA queues until clear. An emergency override shall be logged. | A deploy shall keep clear from one hour before the bell until the session ends: production refuses, QA queues until clear. An emergency override shall be logged. If the arena’s health does not answer within 4 seconds, the guard lets the deploy through. | The guard lets a deploy through when health cannot be read; the law now says so (#226). Table rows 44. |
| 14.1 Draw at the bell | Each session shall draw one fresh CORE from the house’s published band as it stood when that night’s Credits opened. The draw shall use public randomness the league does not control, with its source and round on the record. | Each session shall draw one fresh CORE from the house’s published band as it stood when that night’s Credits opened. The draw shall use public randomness the league does not control: the newest round of drand quicknet, read at the bell, with its source, round and randomness on the record. If the beacon cannot be read within 8 seconds, the bell shall ring on the labelled stand-in, the SHA-256 of the session’s name, with an alert, and the record shall say which was used. | The beacon was a hash of the session name, not public randomness (#226). Table rows 19. |
| 14.7 Void and replay | A void session shall return its picks and Prayers, set aside its CORE for this pair and replay on a fresh CORE. The normal replay is the house’s next night; row 15 permits the engine a same-night replay. Repeated provider voids use Law 7.15; a bout has the tighter limit in Law 15.8. | A void session shall return its picks and Prayers, set aside its CORE for this pair and replay on a fresh CORE on the house’s next night, never the same night. Repeated provider voids use Law 7.15; a bout has the tighter limit in Law 15.8. | Row 15 let the engine replay a void session the same night; a night now rings once (#226). Table rows 15, 28, 29. |
| 14.9 Resume after a restart | A restart shall resume the same session. A cut reply costs no attempt; writing before the outage remains on its corner’s clock, and downtime does not. A proof already with the referee shall be checked again. A claimed outage overlapping ruled events shall be refused. | A restart shall resume the same session. A cut reply costs no attempt; writing before the outage remains on its corner’s clock, and downtime does not. Downtime shall also move the session’s wall-clock ceiling by the same amount. A proof already with the referee shall be checked again. A claimed outage overlapping ruled events shall be refused. | Downtime came off the writing clocks but not the wall-clock ceiling (#226). Table rows 35. |
| 14.10 Turns and the ceiling | Corners sharing one machine shall take turns, with loading and waiting off their writing clocks. A PROVEN shall wait while its rival can still finish earlier under Law 6.4. At the wall-clock ceiling writing and waiting end; unfinished replies do not count, but submitted proofs are still judged. | Corners sharing one machine shall take turns, with loading and waiting off their writing clocks. A PROVEN shall wait while its rival can still finish earlier under Law 6.4. On our machine the wall-clock ceiling shall leave room for both corners’ whole writing clocks in turn, with a model load before every attempt. At the ceiling writing and waiting end, even in a session that overruns it; unfinished replies do not count, but submitted proofs are still judged. | A finite ceiling could cut a delayed turn on our machine; the ceiling now leaves room for both whole clocks in turn (#226). Table rows 71, 72. |
| 14.11 The title result | A challenger who wins becomes champion; an incumbent who wins records a defence. An exact tie under Law 6.4 leaves the belt where it was, including vacant. A beaten champion has no automatic rematch; it must reach the top two again as a newcomer would. | A challenger who wins becomes champion; an incumbent who wins records a defence. An exact tie under Law 6.4 leaves the belt where it was, including vacant. A beaten champion has no automatic rematch: it counts as already seen for 8 of its house’s nights, and after them, in the top two without the belt, it is someone new again, as anyone would be. | The card remembered every build ever seen, so a former champion could never return as new (#226). Table rows 45. |
| 15.8 One replay only | A void bout shall be replayed once at the next house bell on a fresh CORE. A second void, or no fresh CORE for the replay, ends NO CONTEST with that session’s picks and Prayers returned in full. A restart resumes the existing session rather than spending the replay. | A void bout shall be replayed once, on the next night, never the same night, on a fresh CORE. A second void, or no fresh CORE for the replay, ends NO CONTEST with that session’s picks and Prayers returned in full. A restart resumes the existing session rather than spending the replay. | The engine accepted a same-night replay of a void bout; a night now rings once (#226). Table rows 77. |
| 17.2 A Prayer cannot prove | Before sealing, every Prayer shall be checked alone, as an extracted Lean block, as a theorem body and through its quoted code. Any accepted proof shall discard the CORE. A Prayer shall not supply a proof in disguise. | Before sealing, every Prayer shall be checked alone, as an extracted Lean block, as a theorem body and through its quoted code. Any accepted proof shall discard the CORE; so shall a check that runs out of time, which proves nothing. A Prayer shall not supply a proof in disguise. | A timed-out Prayer check could pass sealing as a denial (#226). Table rows 54. |
Gaps: laws the code does not enforce yet
Every amber and red law appears below. Locations name existing code or proposed enforcement points; they are not claims that those features exist. Green laws remain scoped by their evidence notes.
| Law | What remains | Where to enforce it |
|---|---|---|
| 1.1 · A fair contest🟡 Partly enforced | src/match.ts · runMatch gives equal input, writing clocks and limits; laws/src/rules.rs · book / submit applies the fuel ceiling. Remote provider behavior and billing are not independently controlled. | See the named enforcement points and remaining limitation in this law’s note. |
| 1.3 · An inspectable sport🟡 Partly enforced | Publish complete, durable evidence for every mode, including after a restart. | src/types.ts; src/arena/chain.ts; src/arena/server.ts; public record archive |
| 1.4 · Exhibitions are labelled🟡 Partly enforced | Bind simulation or real execution mode into the bout manifest and record. | src/types.ts; src/arena/league.ts; web/fight-card.ts |
| 2.1 · Authority❌ Policy only | Record Commissioner approval and enforce it in the amendment workflow. | AGENTS.md; repository review rules; Commission amendment register |
| 2.2 · Amendment record❌ Policy only | Add an approved amendment register linked to each published edition. | docs/laws-of-ai-fight.html; repository review workflow |
| 2.3 · Version and law numbers❌ Policy only | This page is v0.5, matching the engine; every existing law number is preserved. Retired numbers must be marked repealed rather than reused. Version review remains policy. | See the named enforcement points and remaining limitation in this law’s note. |
| 2.4 · The booked edition governs🟡 Partly enforced | laws/src/rules.rs · bell / new_edition preserves the booked prompt and edition; src/laws.ts · rule / replay rules a stored fight with the bytes of the edition it was booked under, kept in laws/editions/ (scripts/laws-build.ts · keepEdition adds each edition’s file and never deletes one), and a fight booked under an edition this host does not hold stops with an alert (src/nightly/book.ts · FightBook.apply). src/nightly/tonight.ts · setHouseCard stores the card once. The simulated arena and chain pools do not bind this full manifest. | See the named enforcement points and remaining limitation in this law’s note. |
| 2.5 · Safety does not rewrite a result🟡 Partly enforced | Add an explicit incident state and a published correction trail. | src/match.ts; src/arena/league.ts; both betting contracts |
| 2.6 · Code follows the laws❌ Policy only | Map rule changes to approval and conformance checks. | AGENTS.md; pull-request review workflow; law-to-test register |
| 3.1 · Eligibility🟡 Partly enforced | Validate entrant capabilities before admission. | fighter registry; src/runner/; scripts/weigh-in.ts |
| 3.2 · Registered identity🟡 Partly enforced | src/nightly/arena.ts · groupBuilds / seatOf binds mapped builds to cards; src/nightly/builds.ts · buildEvents records provider identity reports. src/open/door.ts · Door.enter binds the Open to file hashes. Sealed-provider identity and ownership remain assertions; simulated persona labels are not attested real builds. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.3 · Pinned open weights🟡 Partly enforced | src/open/door.ts · Door.enter pins a commit and file hash; src/open/loader.ts · Loader.load verifies the bytes. Complete tokenizer and serving-revision attestation across all entrants remains incomplete. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.4 · No substitution🟡 Partly enforced | laws/src/rules.rs · build_report / fighter_retired ends the fight; src/nightly/builds.ts · buildEvents compares reports. Sealed models remain the provider’s word. Retirement of a champion is the open default in D2. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.8 · Evidence of weight🟡 Partly enforced | src/nightly/arena.ts · weigh reads roster or reviewed-map counts, not a size in a name. Independent verification of every count remains incomplete. src/open/loader.ts · Loader.load verifies the Open file. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.11 · Neon Circuit entry🟡 Partly enforced | src/open/door.ts · Door.enter pins the Open repository and commit; src/open/box.ts · OllamaBox.register serves its verified file on the league machine. The wider circuit remains planned. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.12 · Neon Circuit files🟡 Partly enforced | src/open/box.ts · OllamaBox.register creates a model from the verified blob. The wider circuit loader is still policy only; a verified file hash does not prove a model parser safe. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.13 · Rights to enter🟡 Partly enforced | src/open/entry.ts · licenceAllowed checks the configured licence list and src/open/door.ts · Door.enter holds other licences for the Commissioner. A repository tag is not independent proof of rights or ownership. | See the named enforcement points and remaining limitation in this law’s note. |
| 3.14 · The owner’s purse❌ Policy only | Approve and implement a separate owner-purse ledger and funding source. | Neon Circuit annex; keeper receipts; both betting contracts |
| 4.7 · Vacancy and stripping🟡 Partly enforced | laws/src/rules.rs · fighter_retired emits vacate-belt for a retired champion; src/nightly/book.ts · FightBook.moveBelt applies it and src/nightly/nights.ts · Nights.publishVacated writes and publishes row 39’s ruling record with its reason. The earlier symbolic-era reset remains in src/arena/league.ts · load; broader stripping policy is still D2. | See the named enforcement points and remaining limitation in this law’s note. |
| 4.8 · Belt lineage🟡 Partly enforced | Persist reigns, transfers and vacancies across eras with supporting bouts and rulings; aggregates and earned-title statistics are not lineage. Distinguish no contest from a draw. | src/arena/league.ts; new title-lineage store; public records |
| 4.9 · Earned titles🟡 Partly enforced | Use the booked attempt limit for COMEBACK KID and capture titles before belt settlement so a new TWO-WEIGHT CHAMPION is announced. | src/arena/league.ts::fightPhase; src/arena/titles.ts; web/main.ts::onResult |
| 4.10 · Elo standings🟡 Partly enforced | src/arena/titles.ts · rate, src/nightly/ratings.ts · rated / rateSession and src/open/ladder.ts · ratedBout / rateBout keep separate tables. The Open host misclassifies an exact proof tie as breached with no winner and misses its half-score (Law 15.7). | See the named enforcement points and remaining limitation in this law’s note. |
| 5.1 · Seal before betting🟡 Partly enforced | laws/src/rules.rs · open_credits / band_added / bell freezes additions, refuses a bell between sessions until that night’s Credits have opened, and draws only from the frozen band; src/nightly/book.ts · FightBook.topUpAndOpen and src/nightly/view.ts · nightView expose the band. The beacon’s round is not yet verified (Law 14.1). Future simulated pools still omit the seal. | See the named enforcement points and remaining limitation in this law’s note. |
| 5.2 · What is sealed🟡 Partly enforced | src/referee/lean.ts · LeanReferee.check checks the fixed challenge; src/factory/seal.ts · verifyAndSeal hashes its bytes. Factory statements are hidden until drawn; public-ladder statements are already known. Independent verification of the full booking-to-referee binding remains incomplete. | See the named enforcement points and remaining limitation in this law’s note. |
| 5.5 · Published bout limits🟡 Partly enforced | Publish the cap and pool-derived formula on every card, then commit and record the resulting limits. | src/arena/schedule.ts; src/arena/league.ts; src/types.ts; web/fight-card.ts |
| 5.8 · Equal fuel tanks🟡 Partly enforced | laws/src/rules.rs · start_session allocates the same tank to both corners; src/match.ts · runMatch and src/runner/fuel.ts · maxTokensWithin bound requests. Provider billing and complete reconciliation remain external to the engine. | See the named enforcement points and remaining limitation in this law’s note. |
| 5.9 · No fuel overrun🟡 Partly enforced | laws/src/rules.rs · submit / out_of_fuel rejects an overrun and stops an empty tank. src/match.ts · runMatch and src/runner/fuel.ts · maxTokensWithin bound requests; src/keeper/keeper.ts · Keeper.play caps the bettors’ charge. Unknown or late provider costs still require reconciliation. | See the named enforcement points and remaining limitation in this law’s note. |
| 5.10 · Reply-only competition🟡 Partly enforced | src/nightly/session.ts · SessionHost.withPrayers inserts only the purchased sealed texts. src/runner/openrouter.ts · openRouterRunner sends chat requests; remote serving behavior is not independently attested. | See the named enforcement points and remaining limitation in this law’s note. |
| 5.11 · Submission format🟡 Partly enforced | Reject multiple blocks instead of silently selecting the last. | src/challenge.ts::extractLean; test/referee.test.ts |
| 6.6 · The fight record🟡 Partly enforced | src/nightly/book.ts · FightBook.record / ruled; src/nightly/nights.ts · Nights.keep / keepFight; src/laws.ts · replay / LAWS_SHA256. Independent build, time and cost attestation remains absent. | See the named enforcement points and remaining limitation in this law’s note. |
| 6.7 · Record fingerprints🟡 Partly enforced | Require publication before settlement and verify hashes independently on both rails. | src/keeper/keeper.ts; src/arena/chain.ts; new Solana keeper; settlement verifier |
| 7.2 · No new axioms🟡 Partly enforced | Reject all submission-defined axioms, including unused ones. | referee/Check.lean; test/referee.test.ts |
| 7.10 · No forged verdict🟡 Partly enforced | Harden compiled-artifact parsing and independently verify hostile inputs in separate isolation. | src/referee/lean.ts; referee/Check.lean; test/referee.test.ts; independent referee service |
| 7.11 · No interference🟡 Partly enforced | Test escape and cross-corner attempts; treat untrusted model text as data in every commentary path. | src/referee/sandbox.ts; src/referee/lean.ts; web/main.ts; future commentary service |
| 7.12 · No timing manipulation❌ Policy only | Commit fresh challenges and use signed dispatch, receipt and verdict timing with independent witnesses. | src/arena/schedule.ts; src/runner/; src/match.ts; timing oracle |
| 7.14 · Disciplinary penalties🟡 Partly enforced | laws/src/rules.rs · interference / rule_on_stopped_fight stops the fight and resumes or ends it on a named ruling, which an operator sends through POST /api/nightly/ruling (src/nightly/nights.ts · Nights.rule; on a public box, the operator’s token only). It has no disciplinary ban or automatic disqualification system. | See the named enforcement points and remaining limitation in this law’s note. |
| 7.15 · Provider failures🟡 Partly enforced | laws/src/rules.rs · relay_fault / providers_silent / provider_fault / void_session applies these defaults; src/nightly/session.ts · SessionHost.tick / onMatch supplies the faults. For silence, the cutoff is the last word received, not 32 seconds later. Fault evidence is the host’s word. | See the named enforcement points and remaining limitation in this law’s note. |
| 7.16 · No-contest refunds🟡 Partly enforced | laws/src/rules.rs · no_contest / return_what_waits_for_a_bell; src/nightly/purse.ts · Purse.apply. Existing chain pools do not implement this nightly no-contest settlement. | See the named enforcement points and remaining limitation in this law’s note. |
| 8.1 · Standing to dispute❌ Policy only | Provide a published filing route and a durable case number. | Commission dispute register; new dispute API and public case page |
| 8.2 · Filing window and finality🟡 Partly enforced | laws/src/rules.rs · correct_result emits make-whole with amounts owed and prior payments, and src/nightly/purse.ts · Purse.apply / shortfalls pays each shortfall in play chips from the league’s own account. No filing deadline is enforced. | See the named enforcement points and remaining limitation in this law’s note. |
| 8.3 · Evidence🟡 Partly enforced | Preserve proof source, compiled artifact, challenge, checker version and incident evidence with the case. | src/types.ts; src/arena/chain.ts; dispute evidence store |
| 8.4 · Recheck the proof🟡 Partly enforced | Archive the exact checker build and run independent, isolated appeal rechecks. | src/referee/; referee/; dispute replay service; artifact archive |
| 8.5 · An accountable ruling🟡 Partly enforced | laws/src/rules.rs · correct_result emits result-corrected, make-whole, publish-ruling and keep-first-record, and src/nightly/nights.ts · Nights.rule / keepCorrection carries them out: the shortfall paid (src/nightly/purse.ts · Purse.apply), the belt moved (src/nightly/book.ts · FightBook.moveBelt) and the corrected record kept beside the first. Independent appeal rechecks are incomplete. | See the named enforcement points and remaining limitation in this law’s note. |
| 8.6 · Independent referees🟡 Partly enforced | Publish an approved oracle annex and implement independent signatures plus separate timing evidence. | both betting contracts; keeper; independent referee and timing services |
| 9.1 · Everyone can watch; wallets are 21+🟡 Partly enforced | web/main.ts · render, web/main.ts · markView and the view controls separate currency presentation. No test names row 57; account-level age verification and the full cross-surface guarantee remain gaps. | See the named enforcement points and remaining limitation in this law’s note. |
| 9.2 · Separate play from value🟡 Partly enforced | Make the no-value status unmistakable on every amount, ticket and wallet view. | web/main.ts; web/fight-card.ts; src/arena/league.ts; src/arena/players.ts |
| 9.3 · Lawful real-money access❌ Policy only | Record counsel’s jurisdiction approvals and implement the approved access, payment and reporting controls. | legal launch register; account/geofencing service; betting APIs and contracts |
| 9.6 · Pay only for the burn🟡 Partly enforced | src/keeper/keeper.ts · Keeper.play caps charges; src/nightly/ledger.ts · FuelBook.settle / reconcile retains pending costs and reservations. The engine emits league-fronts-fuel; unknown provider costs remain unreconciled. | See the named enforcement points and remaining limitation in this law’s note. |
| 9.7 · Prepaid fuel belongs to the house🟡 Partly enforced | Reserve enough liquid house funds and fail safely if repayment cannot complete. | src/keeper/keeper.ts; src/keeper/pits.ts; treasury reconciliation |
| 9.9 · A favourite below ×1🟡 Partly enforced | Approve and disclose the pool rule; fund or reject tickets if a floor is required. | web/fight-card.ts; src/arena/league.ts; both betting contracts |
| 9.13 · Odds are estimates🟡 Partly enforced | Label model assumptions and show distinct probability, pool estimate and fixed-ticket terms. | src/arena/odds.ts; web/main.ts; web/fight-card.ts |
| 9.16 · Locked-match rescue🟡 Partly enforced | contracts/src/Arena.sol · rescue; laws/src/rules.rs · pay_out / the_core_holds / void_session. Nightly play pools settle separately; on-chain wiring for carried session pools is not built. Row 58 states the two exceptions to same-night disposal: a stopped fight’s held money, and a check still pending at the night’s end. | See the named enforcement points and remaining limitation in this law’s note. |
| 9.18 · LOCKDOWN economics🟡 Partly enforced | laws/src/rules.rs · shares_for / the_core_holds / bout_drawn implements the nightly default. Legacy contracts still expose a house-takes-own-purse option; they are not the nightly settlement adapter. | See the named enforcement points and remaining limitation in this law’s note. |
| 9.21 · The house does not back corners❌ Policy only | Enforce house-wallet exclusion and identity controls; prohibit synthetic stakes in value pools. | account/conflict registry; both betting contracts; src/arena/league.ts |
| 9.22 · No betting on one’s own bout❌ Policy only | Bind identity, ownership and operating roles to betting restrictions. | entrant and staff registry; account service; betting admission |
| 9.23 · Limits before play❌ Policy only | Enforce personal limits across wallets and sessions; record limit changes. | account/limits service; src/arena/server.ts; betting admission |
| 9.24 · Time away❌ Policy only | Add timed reminders and account-level exclusion that every betting path respects. | web/main.ts; account/limits service; betting admission |
| 9.25 · No loss-chasing hooks❌ Policy only | Remove volume incentives and loss-chasing prompts; review re-ups, streaks and fever against this law. | src/arena/players.ts; src/arena/league.ts; web/main.ts; web/scene.ts |
| 10.1 · The public bout ledger🟡 Partly enforced | Join the manifest, receipts, exact record bytes, chain transactions, belt era and ruling, title achievements and Elo changes in a persistent public entry. | src/arena/chain.ts; src/arena/league.ts; src/arena/server.ts; src/keeper/keeper.ts; public archive |
| 10.2 · Disclose conflicts❌ Policy only | Require conflicts declarations at entry, assignment and booking. | Commission conflict register; fighter registry; schedule manifest |
| 10.4 · No arbitrary purse withdrawal🟡 Partly enforced | Add independent outcome verification, conflict enforcement and mandatory credit reconciliation. | both betting contracts; keeper; oracle and identity services |
| 10.6 · An outcome hash is not a proof🟡 Partly enforced | Use accurate trust disclosures in every result and explorer view. | web/main.ts; web/fight-card.ts; public archive; oracle annex |
| 10.7 · Upgrade authority🟡 Partly enforced | Approve and publish the Solana deployment authority and upgrade constraints before any deployment. | Solana release configuration; public deployment manifest; Commission approval |
| 10.8 · Publish evidence, protect secrets🟡 Partly enforced | Redact provider errors and validate public evidence before publication. | src/runner/; src/match.ts; src/arena/server.ts; public archive |
| 11.1 · Approve the annex first❌ Policy only | Require an approved annex ID and referee version during booking. | league registry; src/challenge.ts; src/arena/schedule.ts |
| 11.3 · Annex B: CODE❌ Policy only | Build deterministic test isolation, commit/reveal evidence and bans on harness access or hard-coded test leakage. | new CODE challenge loader and referee; league annex |
| 11.4 · Annex C: RUST PORT❌ Policy only | Implement a pinned Rust build, differential scorer, licensed inputs and shortcut detection. | new RUST PORT challenge loader and referee; league annex |
| 11.5 · Annex D: GAME❌ Policy only | Build deterministic simulation and fair bot budgets with published replay evidence. | new GAME engine and referee; league annex |
| 11.6 · Original games only❌ Policy only | Review game design and asset provenance before annex approval. | GAME content registry; Commission annex review |
| 11.7 · Points and draws❌ Policy only | Approve and implement scoring and tie behavior without changing an existing pool’s terms. | new league referees; src/types.ts; src/match.ts; league annexes |
| 12.2 · Netrunner, version and corner🟡 Partly enforced | src/nightly/arena.ts · groupBuilds; src/open/door.ts · Door.enter; src/nightly/ratings.ts · rateSession. A sealed build is still identified by its provider’s report. | See the named enforcement points and remaining limitation in this law’s note. |
| 12.5 · Flatlined and disqualified🟡 Partly enforced | laws/src/rules.rs · corner_out / the_core_holds distinguishes session exhaustion from a fight ending. There is still no automatic disqualification state. | See the named enforcement points and remaining limitation in this law’s note. |
| 12.6 · Pool purse and owner’s purse🟡 Partly enforced | Create distinct names and ledgers when the owner’s purse is approved. | Neon Circuit annex; keeper receipts; both betting contracts |
| 12.7 · Fuel and burn🟡 Partly enforced | Reconcile actual burn independently of the allowance and UI estimate. | src/keeper/pits.ts; src/keeper/keeper.ts; src/runner/ |
| 13.4 · One build, one fighter🟡 Partly enforced | src/nightly/arena.ts · buildKey / groupBuilds; src/nightly/builds.ts · buildEvents; laws/src/rules.rs · build_report. Name normalization and sealed-provider reports are not independent identity attestations. | See the named enforcement points and remaining limitation in this law’s note. |
| 14.1 · Draw at the bell🟡 Partly enforced | src/nightly/beacon.ts · drandBeacon reads quicknet’s newest round from the League of Entropy’s relay at each bell (src/nightly/nights.ts · Nights.beaconAt; src/open/ring.ts · Rings.bell); laws/src/rules.rs · bell / draw / cores_left_to_draw draws from those bytes. The round is not yet verified against the network’s public key: the relay’s word is taken. A rehearsal draws on the labelled stand-in. | See the named enforcement points and remaining limitation in this law’s note. |
| 15.5 · The ladder🟡 Partly enforced | src/open/ladder.ts · boutScore / ratedBout / rateBout rates wins and ordinary draws once. src/open/ring.ts · outcomeOf misclassifies an exact PROVEN tie as breached with no winner, so it does not reach the ladder as a draw. | See the named enforcement points and remaining limitation in this law’s note. |
| 17.2 · A Prayer cannot prove🟡 Partly enforced | src/factory/prayers.ts · prayerAttempts gives the fixed list of wrappings; src/factory/seal.ts · verifyAndSeal discards a CORE on any accepted or timed-out Prayer check. Named row 54 tests enforce these wrappers. This is a finite check, not a proof that no paraphrase can reveal the answer. | See the named enforcement points and remaining limitation in this law’s note. |
| 17.5 · On the record🟡 Partly enforced | src/nightly/session.ts · SessionHost.deliverPrayers; src/nightly/purse.ts · Purse.apply; src/nightly/nights.ts · Nights.keep / keepFight. The engine records the sealed purchase and delivery; the buyer and actual text are host evidence, not independently verified by the module. | See the named enforcement points and remaining limitation in this law’s note. |
| 17.6 · A league setting🟡 Partly enforced | src/nightly/mode.ts · leagueSettings; src/nightly/nightly.ts · NightlyLeague.pray enforces the host switch; the pure engine has no off flag. The Open currently offers no Prayer purchases. | See the named enforcement points and remaining limitation in this law’s note. |
| 18.1 · Families and versions🟡 Partly enforced | src/factory/family.ts · Dice; src/factory/families/index.ts · family; test/factory.test.ts · family fingerprint tests. The fixture pins sampled seeds, not every possible output; honest disclosure of transfer remains policy. | See the named enforcement points and remaining limitation in this law’s note. |
| 18.2 · Verified before sealed🟡 Partly enforced | src/factory/seal.ts · verifyAndSeal / problemOf; src/factory/pool.ts · CorePool.seal. A timed-out Prayer check discards the CORE (Law 17.2); the near miss still counts only an accepted verdict, so a timeout there can pass as denied. | See the named enforcement points and remaining limitation in this law’s note. |
| 18.3 · The seal and the band🟡 Partly enforced | src/factory/seal.ts · verifyAndSeal; src/nightly/cores.ts · bandFor; src/nightly/view.ts · nightView. High-house levels have no factory family yet and use the ladder; those public statements do not satisfy an unseen-CORE promise. | See the named enforcement points and remaining limitation in this law’s note. |
| 18.5 · Retirement and publication🟡 Partly enforced | laws/src/rules.rs · core_retired / correct_result; src/nightly/nights.ts · Nights.keep / keepFight. PUNK_PUBLISH_RETIRED is off by default, but code cannot verify the Commissioner’s word before an operator enables publication. No publication authorization is given here. | See the named enforcement points and remaining limitation in this law’s note. |
| 19.1 · Events from booking🟡 Partly enforced | src/nightly/book.ts · FightBook.record / ruled; src/laws.ts · replay. The host omits effect-free ticks and discards their computed state. The nightly’s fight export and the Open’s downloadable bout record (src/open/bouts.ts · boutRecord) both carry every event from booking and the final digest. | See the named enforcement points and remaining limitation in this law’s note. |
| 19.3 · What the host still attests🟡 Partly enforced | src/nightly/laws-events.ts · lawsEvent / fromMatch; src/nightly/builds.ts · buildEvents; laws/src/rules.rs · providers_silent / restart / submit. Hashes and consistent timestamps do not independently prove when writing happened or why a provider failed. | See the named enforcement points and remaining limitation in this law’s note. |
| 19.4 · Fail closed🟡 Partly enforced | laws/src/rules.rs · unreadable / fail_closed / refuse_and_alert / after_the_end. Row 60 protects a held proof; a readable event after a terminal result is refused with an alert. Writing a new row remains a review obligation. | See the named enforcement points and remaining limitation in this law’s note. |