#๏ธโฃ Harness Path โ HashSmash Mage
18 ยท hashsmash_mage โ the arena, with an AI judge (added 2026-10-07) โ an entry in the origin fleet catalogued in The Harness Paths (group: Descendant lanes). The catalogue is the operator's work WITH the harness, not part of the system you adopt; none of its code lives in the harness repo. This is the map entry, so you can see what a filled config looks like at this weight.
(instance at ~/hashsmash_mage/; Yukon hashsmash, reduced-round collision
claims judged by an AI reviewer the organiser runs)
The first lane where the judge is itself a model, so the prover seat was
split: assay A re-derives every number from per-call CPU ledgers in which
everything is charged (abandoned calls, stopped calls, the watcher's kills);
assay B rehearses the judge from its own archived dossiers and its
aggregation rule (one unsupported anywhere sinks a package). Three packages
passed: 1ded36a8 at 52.1 first try, then 8bad82c1 at 47.6, the only entry on
the board whose route search is fully measured (59 solver calls, 593,858.32
CPU-s, callgrind-calibrated unit, itemised margin); sha3-r6 02d6a703 at
125.58. One package failed on "participant-reported only" and was repaired by
shipping an organiser-executed replay and a credited certificate. The
measurement was then copied verbatim by others, which is where the ฮบ evidence
ledger (#20) was born. Rules A9-A12, A17, A19, A27-A34 of CHALLENGE_LANES.md
come from here. On HOLD awaiting owner review.
Navigation
โ Welcome Visitors ยท The Harness Paths ยท Adopting The Harness ยท Workflows And Runtimes
the wiki is a projection; ~/dual-agent-harness (git) is the source of truth ยท (โ๏ธโฅโฟปโฅ๐ง)๐ = neg โ bnot โ succ