Board

Jordan (30 Sep). All from hello@tacticalreroll.com; two links per email (the site, /rankings/), no attachments. The drafts in design/sources.md ("Drafts for Jordan") are the source of truth; the first lines only here. In this order: 1. Tabletop Herald, info@code-b.com (confirmed on their imprint; their Discord discord.gg/MqNmSuxVmn as a second route): "Hi there, I'm Jordan, and I run Tactical Reroll, a free mathhammer calculator for Warhammer 40,000…" Most likely yes, so first: an early yes gives the others a "Tabletop Herald has already agreed" line if we need it. 2. Longshanks, admin@longshanks.org (from their help and about pages; Discord discord.gg/2CjNkGHpYa): "Hi there, I'm Jordan… I'd like to ask permission to read the public results of ended 40k events on Longshanks…" 3. Listhammer: no address published anywhere on the site (about, privacy, home and footer read in full 30 Sep). Route: an issue on github.com/N041M/grimstat-corpus (its README invites issues) saying who we are, that we'd like Listhammer's permission to use the listhammer/ part, and asking the maintainer to pass the message on or say how to reach Listhammer, with the Listhammer email verbatim in the issue so it can be forwarded; keep it short and polite, as the corpus's maintainer and Listhammer's author may be the same person. In parallel: a message to the account that posts Listhammer's updates on r/WarhammerCompetitive, if Jordan finds one. First line: "Hi there, I'm Jordan, and I run Tactical Reroll, a free mathhammer calculator for 40k…" 4. T3: the contact form on tabletopturniere.de/impressum (click the operator's name, Matthias "Blackhawk" Althaus; needs a free T3 account), the German draft with the English under it; feedback.tabletoptournaments.net as a fallback. Lowest yield, so last; skip if time is short. First line: "Hallo, mein Name ist Jordan und ich betreibe Tactical Reroll…" Not sent: Best Coast Pairings only if Listhammer says no or stays silent for two weeks (then support@bestcoastpairings.com, asking whether they have a data programme a small free site can join); List Engine and Hutber later, only if these four leave a gap. After sending: a follow-up nudge after two weeks of silence, once; on any yes, reply with thanks and, once it's live, the link to the page where their credit appears; each send date and each answer recorded here (T-411 and T-412 switch on per source as answers arrive). Sent: (none yet) · Answers: (none yet)

Checked 30 Sep with tools/sources/check.js on GitHub's runners (.github/workflows/sources-check.yml, by hand; our container's proxy blocks these sites; one request a second as TacticalRerollBot). Findings, in design/sources.md: Longshanks: robots.txt allows reading (20 s between requests), no terms page; its /results/ page is public (players' records and armies, filterable to 3+ wins), per-event faction stats need a login. Tabletop Herald: robots.txt allows everything, no terms page; each tournament page embeds its size, rounds, country and each player's army, but army lists need a login and standings come from an undocumented API; its events already reach us through Listhammer with full results. T3: its terms need written consent to reuse content. tabletop.to: the domain is parked (dropped). List Engine: no terms, one developer on Discord. Hutber: a bot checkpoint. Listhammer's own robots.txt disallows its events and API (so only through the corpus, with their OK). No reader built yet: none states a licence to reuse its data, so each waits on Jordan (the four questions tonight) and, where needed, an email; drafts for Listhammer, Longshanks, Tabletop Herald, T3, List Engine and Hutber in design/sources.md. Each is listed off in tools/sources.json with what was found Jordan, 30 Sep: yes to direct readers wherever robots.txt and terms allow, one request a second (Longshanks asks 20 s), a named agent, no player names, a credit and a link on every page that shows the data, never BCP. From the check (30 Sep): Longshanks (robots.txt and its About page read) and Tabletop Herald (robots.txt, privacy and imprint read; no terms page) allow it; T3's terms (tabletopturniere.de/terms §8) need written consent, so not T3; tabletop.to is gone. Next: the Longshanks and Tabletop Herald readers, each off until switched on Readers, 30 Sep 03:46Z: Longshanks now answers our runner's reads with a bot challenge (a captcha page, HTTP 202) instead of its results, so it isn't open to machines after all: no reader, and we don't work around it; Tabletop Herald's standings only come from an undocumented API and its lists need a login, so a reader would have to use a private API: not built. Both go the email route (drafts in design/sources.md); each stays off in tools/sources.json. The only source open to machines with results today is Listhammer's, through the corpus, which waits on the T-411 email Addresses (30 Sep 04:56Z, check.js --contacts): Longshanks admin@longshanks.org; Tabletop Herald info@code-b.com (confirmed); T3 only an on-site form behind the operator's name on its imprint (for registered users); Listhammer publishes none (routes in design/sources.md). Jordan's warmer drafts (30 Sep) are in design/sources.md verbatim, T3's in German with the English underneath

The armies where one more list would help most (single-list armies with many graded units and low agreement); Jordan sources, the panels are added in our own words. The list (5 Oct, from tools/edition.js and the 11e exam): (1) Thousand Sons: one list, 28 units, we score 38% (below chance): a second list says whether it is us or that reviewer; (2) Dark Angels: one list, 77 units, 54%; (3) Death Guard: 36 units, 55%; (4) Astra Militarum: 61 units, 68%; (5) Orks: 45 units, 64%; (6) Space Wolves: 20 units, 51%. Full videos or transcripts preferred (their reasons feed T-705)

Jordan (27 Sep): tacticalreroll.com is last on the first page for "mathhammer", just under honorrollmath.com. Google hides results "very similar" to ones it shows, and honorrollmath.com carries the same title and description as ours, so the two domains compete; a permanent redirect (or taking the old copy down) would give its standing to tacticalreroll.com. That's Jordan's domain (hands off for Claude). Jordan (27 Sep): honorrollmath.com is the kids' app now, so that result is stale and will drop out as Google recrawls it. Then: Search Console, links from the community (Reddit, Discord, YouTube mathhammer channels), and pages for searches we can own (tier lists, unit mathhammer, loadouts, T-225) 27 Sep, Jordan picked: the faction tier list (T-257), best units for the job (T-258) and shorter snippets (T-259), all built. Search Console now comes in weekly (T-309). Left: the wording pass with T-129, and community posts if wanted Jordan, 30 Sep: the wording pass over the static pages on main this week, by T-129's rules; the community posts wait until beta is on main (T-416)

Today's source is European events on MiniHeadQuarters. For US/UK GTs, email Listhammer (listhammer.info), Best Coast Pairings (support@bestcoastpairings.com) and List Engine asking permission. Template: "Hi, I run tacticalreroll.com, a free Warhammer 40k mathhammer site, and I'd like to show a small 'recent tournament-winning lists' panel per faction using your data, with a clear credit and link back to you on every list. Would you be willing to allow this, or point me to an API, feed or licence terms you'd like me to follow?" Jordan, 30 Sep: one email, to Listhammer (the draft is on T-411); none to Best Coast Pairings, ever; the others by T-412's findings

The meta report's first full week of counts ends 4 Oct; check it renders on /meta/ and in the app's Overview, and read the analytics report for the Monday round-up (T-065). Prep done 30 Sep: the report is one command on main, node tools/report.js (the tournament data's coverage, T-413; the goals still to add, T-317; the cards by status; the last weekly analytics), and the weekly workflow posts it to its run's summary after the Monday pull. T-398's data audits and placings tiers (beta) join it when beta comes to main

Built on branch ci-fix (from main 36d189db65), three commits, waiting for Jordan's push (git push origin ci-fix:main). (1) Docs drift: /lab/reports/ runs tools/report.js, which read reports/analytics/2026-10-05.md raw; a Windows checkout's CRLF put "\r" into nine lines of the committed page (2eea84ad27), so CI's LF build always differed. report.js now folds line endings to LF; the page rebuilt as CI builds it (pinned BSData and corpus): drift-free. The weekly-analytics and daily-demand bots commit files the site renders (reports/analytics/*.md through report.js; pulse.json into unit pages and the Lab) with [skip ci], so main drifted after each one: both workflows now fetch the pinned BSData and corpus, run CI's four build commands and commit docs/ with the report, and keep nothing when the rebuild fails. (2) Deploy beta (red since #265): Cloudflare Pages refuses files over 25 MiB; beta.yml publishes a copy of docs/ without them, a warning naming each (today docs/lab/ledger/space-marines.json, 47.4 MiB; beta's Lab goes without it; T-762). (3) Refresh 11e data (red since #14, 4 Oct): the three failing tests assumed the data of their day: points (Termagants and Tyrant Guard's points), detachments (pairs that fit the Detachment Points) and /meta/'s army filter (Tyranids with a winning detachment in the last two months; the months Jun to Sep). T-579 moved two to the 30 Sep update, but that reached main after the last run (#16 tested main at 45bdf24945); all three now read today's values from the data, and pass on the pinned BSData and on BSData's 5 and 6 Oct heads with the newest corpus. No site bug.

docs/lab/ledger/space-marines.json is 12,326 forms over 84 units (Librarian 940: every size, loadout, detachment and leader; forms merge across the 16 detachments only when dice and rules match), each with kill and killNC per horizon and class (44% of the bytes), lend (10%), rules, weapons. The Lab's ledger page never loads it (index.html fetches tyranids.json and benchmarks.json only): it is a working file of the ledger tools (ledger.js, charge.js, burst.js, killrobust.js, dgchecks.js, ledger-steps.js, ledgercheck.js read it from docs/), published to both sites for nothing, and close to GitHub's 50 MB file warning. Proposed, not done (the ledger's frozen-input rules): write it to build/ledger/space-marines.json like the other seven armies (the tools' path helpers already know build), or to a tracked folder outside docs/ if it must stay in git; the page unchanged. Slimming alone doesn't reach 25 MiB: dropping lend and weapons (unused by the page) 40.5 MiB, byClass as arrays 30.0, two decimals 27.5. Until then beta deploys without it (T-761)

The Visual workflow's screens drifted from tests/visual/base/ since 3 Oct (the T-579 data and the pages since). Review the drifted shots and diffs its runs upload, then run Visual by hand with mode "update" on the branch that should carry them. Its commit adds or renames files only when screens change, and /lab/reports/ lists the screens: a run that adds or drops a screen also needs the pages rebuilt (T-761's bots do this; Visual doesn't yet)

Needs T-041. Fill in docs/shop.js IDS, rebuild pages, bump the SW cache; check our eBay link format against the one EPN's link generator makes

A search link plus the network's deep-link wrapper per store, shown in the visitor's region. Needs T-066

The Meta score (T-198), the tracker (T-161), the army tiers (T-257, T-332) and the sparklines (T-387) all rest on one source, grimstat-corpus's MiniHeadQuarters lists: 150–190 lists and 6–10 events a month, almost all French. That's why the tiers went wrong and why they're off. Goal: several sources, many more events, coverage by region, so per-army counts can carry tiers again. Sub-cards: T-410 the source layer; the Listhammer part (win-loss lists and every event's results; needs Listhammer's OK); the platforms' terms and readers (Longshanks, Tabletop Herald, tabletop.to, T3; List Engine and Hutber by permission); the coverage report. Never Best Coast Pairings directly (its EULA; Jordan won't email them). Stat Check, Goonhammer, Listhammer's /stats and GW's Metawatch are a monthly cross-check only (T-332), never copied into our data

The header gains the unit's pixel figure beside the tier badge; scores, tags, wounds-per-100-pts bars and rating stay; the Simulate box goes; it ends with one gradient button "Open the unit page ›" and a text link "Compare in Rankings ›". It stays a sheet (reading, not editing). The T-383 face-off button becomes a small text link "📷 Share picture: default vs best loadout" under the best-loadout chip (or in the 🔗 menu), here and on the unit page Built on main 30 Sep: the header carries the unit's figure beside the tier (figHead); from a calculator card ({ onCalc: true }) the Simulate box goes; the foot is "Open the unit page ›" in the site gradient and "Compare in Rankings ›", which opens the tier list on the unit's army. From the tier list, 🔍 and My army the Simulate box stays (there it is the way into the calculator). The face-off picture's label (T-383) is beta code: it lands with the merge (T-452). Test in unitcard.test.js

The accordion, docked row, lists on the card, four toggles, Simulate row, corner pill, new keys and link bits, the removed surfaces; the repo tree for tools/sources/, icons.js, pixelfit.js and the rest Main's half done 30 Sep: CLAUDE.md (layout.js, myarmy.js, the ✨ key's opener) and design/streamline.md (the pieces table, a built note for T-434 to T-439) match the work branch; beta's half comes with the merge (T-452)

All the families in one place he can revisit any time: design/weaponfx-preview.html stays the source of truth, and tools/stamp_assets.js (run by build_pages.js, so CI's drift check keeps it current) copies it to docs/lab/effects/index.html with noindex and the site's title pattern; not linked, not in the sitemap. It shows only our own effects and weapon names (names only, no rules text or profiles), so it sits within the hard rules. Every gallery round updates the source, so the page moves with the push; the artifact keeps updating too until Jordan says the page is enough Built 30 Sep: https://tacticalreroll.com/lab/effects/; design/weaponfx.md names the address. CLAUDE.md's layout line waits for the design session (the build session's edits to CLAUDE.md are stopped by the permission check)

Checked 2 Oct: GW updated 16 PDFs on 30 Sep (14 faction packs, 2 Legends-only packs; links and versions in reports/dataslate/2026-09-30.json, the PDFs not kept: GW data). The site, beta and the branch use BSData 374f505 (10:16 UK, 30 Sep); BSData added the update at 15:17 and 16:02 that day ("20260930 MFM and Faction Packs"), fixed through 2 Oct (cc1830f). Moving to it changes 240 units (188 points, 131 profiles), a balance update. The daily refresh's branch hasn't moved since 13:01 UTC on 30 Sep. To do: (1) refresh to BSData's latest on beta, rebuild rankings and pages, record the patch; (2) data/detfx.json, Emperor's Children Frenzied Host: Frantic Focus is now Sustained Hits 1 for Battleline after advancing or falling back, not +1 S (scoring.md changelog); (3) Legion of Excess's stratagem note: Thieves of Pain is now Rapturous Agony; (4) find out why the daily refresh stopped. Report: reports/dataslate/2026-09-30.md. Built 3 Oct (local commit, not pushed): BSData 374f505 → 8b91e6b (3 Oct, 06:44 UK); index, detachments, rankings, pages rebuilt and stamped; the patch recorded (241 units: 188 points, 132 profiles; a balance update, /meta/patch/; 21 letters move; Detachment Points changed on 9 detachments). Frantic Focus → Sustained Hits 1 (detfx.json; moves no score, only Frenzied Host's synergy line); Legion of Excess's note names Rapturous Agony. The refresh: see the report (main's own tests fail on the new data, so the run never pushes). Tests fixed for the new data: points (Termagants 60 → 55), detachments (Lords of the Forge 2 DP), hill (risers keyed by id, tools/hill.js; the verdict line awaited). Ledger outputs byte-identical (frozen inputs). Matrix test's 0.5% gap: T-606. Report: reports/dataslate/2026-10-03-refresh.md.

Built 2 Oct (local commit, not pushed): tools/tiertest.js switch r8 (over r7, so round 7's Feed the Swarm cap and one-drop Tyrannocyte stay), --r8json, --r8sliders: (1) score = best allowed job + V8C.ELITE_STEP 5 for each other allowed job ≥ V8C.ELITE 90, + V8C.STRONG_STEP 2 for each ≥ V8C.STRONG 80, never capped, ties by the mean of the others; (2) letters on fixed cuts over every army (S ≥ 95, A ≥ 88, B ≥ 80, C ≥ 65) and a within-army view by position (10/15/25/30/20%); strict on our ruler now against the within-army view; (3) the Lab's sliders page, docs/lab/reports/tiers/sliders/ (four sliders, the view toggle, three yardsticks live; data reports/tiers/2026-10-02-round8-sliders.json, a copy beside the page). Numbers (7 → 8): Tyranids ρ 0.50 → 0.47, strict on our ruler 20 → 20 within army (chance 10.6), raw 12 → 19 all armies, within one 29 → 31, Tyranid list share 0.39 → 0.41, every unit 0.164 → 0.162, Space Marines −0.05 → −0.18, Orks −0.13 → −0.12; 561 of 1,161 letters move (520 up); 246 S on the fixed cuts (Space Marines 35 of 84; ρ between an army's S share and its top-quarter lists −0.37). Tyrannofex S → A (94.4: its Hammer is 89.2 in round 8's pool). Report: reports/tiers/2026-10-02-tyranids-round8.md. Open: the fixed cuts make S common in armies with many similar datasheets; Jordan's read of the cuts.

Built 2 Oct (local commit, not pushed): tools/tiertest.js switch r9 (over r8), --r9json, --sweep, V9C { GATE1 0.5, GATE2 0.8, PEAK 0.75, REVIVE 1.15, SETDOWN 3 }: (1) Anvil = hits to destroy × OC ÷ points (the geometric mean was rank-identical to round 8, so not used) × the gate on Hammer's turns alive; (2) the sweep, 39 constants at low and high; (3) V2b to round 9 rerun against Auspex, Tista Minis and Sprues & Brews, with an SVG chart (tools/md.js shows images, build_pages.js copies them beside a tier page); (4) proposed frozen cuts S 98.79, A 94.49, B 86.13, C 71.15 (8/15/27/30/20%), not adopted. Numbers (8 → 9): Tyranids ρ 0.47 → 0.49, Space Marines −0.18 → −0.10, Orks −0.12 → −0.12, every unit 0.162 → 0.077, Tyranid list share 0.41 → 0.45; 240 of 1,161 letters move; S-share ρ with top-quarter lists −0.37 → −0.39 (current cuts), −0.24 (proposed). Fixed on the way: mwkOf's cache keyed on variant objects (a memory leak across runs). Report: reports/tiers/2026-10-02-tyranids-round9.md (data beside it, .json). Open: Jordan's call on the proposed cuts; Runner's points gate and the movement geometry are the most sensitive constants.

Built 2 Oct (local commit, not pushed): tools/tiertest.js switch r10 (over r8), V10C { TMAX 5, MAXPTS 2000, S 92.02, A 77.02, B 49.96, C 20.03 }, --r10json, --explain "<unit>" [--army] [--out] (standalone about 25 s): (1) Anvil = OC × min(turns alive, 5) ÷ points × Battle-shock × position × revive, round 9's gate and its constants removed; (2) the list-share headline (per-army median ρ, AUC, hit rate, ρ among taken, the Tyranid overfit gauge) over every version V2b to 10; (3) units over 2,000 pts out of the pool (8: six Titanicus Titans, the Phantom, the Manta); (4) final score = the pool percentile of the composite, letters on cuts frozen at 8/15/27/30/20%; (5) eight explainer files (reports/tiers/2026-10-02-explain-*.md). Numbers (9 → 10): Tyranids ρ 0.49 → 0.51, Space Marines −0.10 → −0.07, Orks −0.12 → −0.18; pooled list share 0.077 → 0.157; per-army median 0.113 → 0.165; AUC 0.536 → 0.582; Anvil's ρ with points 0.41 → 0.19 (target ±0.15: missed); no unit over 1,000 pts at S; S-share ρ with top-quarter lists −0.39 → −0.16. Report: reports/tiers/2026-10-02-tyranids-round10.md (data beside it, .json). Open: Anvil still leans to cost (0.19); the S-per-army check stays negative; the explainers point to three missing raw quantities (hidden arrival, protection lent, Battle-shock's worth) and three weights.

Built 2 Oct (local commit, not pushed): node tools/tiertest.js --rawdump tyranids (about 35 s) writes build/tier-raw-tyranids.json, reports/tiers/2026-10-02-tyranids-raw.json and .csv: every Tyranid per detachment, Norn branch, datasheet size and BSData leader pairing (15 pairs, scored as one unit; leaders' own attacks also delivered inside each squad), each way in, plus every pool unit's chosen context; tools/tierbench.js compose(raw, config) (about 12 ms a run) with every knob of the appraisal's spec and ten switches, one per residual-report finding (--fix a,b, --all, --config, --check). With every switch off it reproduces round 10 exactly (52 of 52 Tyranids, every other unit's composite). First pass: within one 31 of 44 (70%) baseline, 30 all on (ρ 0.51 → 0.71), best of the 1,024 subsets 36 (82%); the line is 38. bannerLendOnly alone 35; bestSize costs (all but it: 34). 14 units two or more letters off all on. tools/banner.js's onSquad exported (lendOnly, models; its report unchanged). Report: reports/tiers/2026-10-02-tyranids-bench-1.md. Next: the 14 gaps from section 3; reasons for each switch beyond the panel; the null columns (loadouts, Battle-shock lend) Superseded on the gate (3 Oct, T-580): the every-army gate is lift over shuffle on every fitting panel, none worse than its frozen predecessor; 38 of 44 within one of Auspex is a bench sanity number only.

Built 2 Oct (local commit, not pushed): tools/tiertest.js o.r11 switches, all on, every unit of the pool: bannerLendOnly, bannerModelCount, turnsHarmonic, reArriveAfterKill, reArriverGateExempt, lendOnBestSquads (every lend on the two squads of its army it lifts most; stand-ins and the Feed the Swarm cap gone), stealthSurvival, bestSize, bestLeader, sameLoadout (effects on the squad the damage uses); --r11json (standalone, about 2 min: each fix alone, all on, all on but one). Bug fixes: docs/bsdata.js rule links read as a bare unit has them (76 unit rows, 21 traits; tests/unit/ruleslinks.test.js) and a model's maximum raised by another's count (Neurogaunts 22); the aura pattern widened; tools/banner.js matches squads ignoring case; tools/tierbench.js banOf takes off the stored multiplier; --rawdump holds a lock and renames into place (--raw-out). Numbers (round 10 on today's data → 11): Tyranids ρ 0.52 → 0.66, Space Marines −0.07 → 0.14, Orks −0.19 → −0.15; per-army median 0.139 → 0.173; AUC 0.582 → 0.585; Tyranid within one 31 (ruler) / 36 (Auspex's shape) of 44, the 85% line not reached. Live data: 21 units lose a trait (Utility only; no letter on the site moves); Neurogaunts 11 to 22. Not done: wargear costs (documented, scoring.md's gaps). Report: reports/tiers/2026-10-02-tyranids-round11.md (data beside it, .json). Documents from the worktrees folded in (design/decisions.md, the brief and critique, residuals 1 to 3, benches 2 to 4).

Checked 2 Oct (T-565), Wahapedia's 11th-edition core rules with their errata and FAQ: engagement range is 2" horizontally and 5" vertically; a charge declares on an enemy unit within 12"; the 2D6 roll is the charge move's maximum distance, and only enemy units within that distance can be charge targets; after the move the unit must be engaged with every target. The rules' own example: a unit beyond the roll can't be a target even when the move could end within 2" of it. So the claim doesn't hold: a charge from a gap of d" needs a roll of d, as tiertest.js pChg (and V4's pCh) play it; a Deep Strike charge (set up more than 8" away) needs a 9, 28%, as design/scoring.md says. No change needed to the calculator or the tier test. One small difference found: Deep Strike sets up "more than 8"" away; V3C.DS places it at 9" for range checks (the charge roll needed is the same). Jordan: close, or move V3C.DS to 8" for ranges.

Written 2 Oct (local commit, not pushed): about 5,000 words, built on design/tier-plan.md v2, its critique, scoring.md, decisions.md, the brief, the method appraisal and round 11; five ideas taken from sports ratings, credit scorecards, search ranking, critic aggregation and chess-engine tuning. CLAUDE.md points to it; it is updated in the same commit as every tier round ("Where we are today", section 7 since v3, each round). Not in the Lab's docs list yet (tools/build_pages.js LAB_DOCS, a code change for a later card).

Every real weapon profile (about 3,000) against every distinct defender profile (a few hundred once grouped), as expected damage per attack in each context that changes it (cover, a detachment's effect, a leader's buff), by ev.js's closed form, cached by the BSData commit's and the engine's hashes. A report and a cached file only; nothing on the site; no hypothetical profiles. Spec: design/matrix.md (sections 2 to 5, build plan 11). Round one of three built 3 Oct (local commit, not pushed; steps 1 and 2): tools/matrix.js (profiles: attacker dice keys, defender grouping keys, mixed units' groups, the id indexes, the keywords not read in full; the cell kernel: profileVs, the renewal count, variance, for one context) and tests/unit/matrix.test.js. At BSData 374f505, pool 1,161 rows: 2,121 attacker dice keys (spec 2,125; 1,304 ranged, 817 melee), 2,164 with range kept (2,207); defenders 608 on the spec's basis (614), 681 on the full key (expected 650 to 750); 75 mixed datasheets (98). Parity of r with profileVs 1.8e-15 on 10,000 real cells; e within 0.474% of killDP's 300-attack volley; section 10's cells to 3 decimals. 34 keywords not read in full (24 unread, 10 read in part) touch 136 of the 2,121 profiles. Round two of three built 3 Oct (local commit, not pushed; steps 3 to 5): context keys (H of the canonical merged modset per weapon and for the defending side; conditions on the target kept in the key) and each pool unit's contexts (own and army rules always; no detachment or each of its army's, every way to answer their choices; alone or joined; marks off), deduplicated, each unit carrying its context count (detachments × joins × sizes × ways in): median 24, 90th percentile 150, max 2,992 (Bladeguard Veterans; distinct dice contexts median 8, max 374); 2,174 attacking modsets, 107 defending, 32,867 (profile, modset) rows. node tools/matrix.js --build --bsdata <checkout> writes build/matrix/<hash12>/ (layers base, cover, half, half-cover, charge; attackers, defenders, contexts, the unit table, manifest): 55.8 MB in 38 s (the unit table 26 s of it). The unit table: 1,161 units × 681 target columns, kills and P(destroy) from killDP's pAll, exported from docs/ev.js with no change in behaviour (ev and volley tests unchanged and passing; rankings.json rebuilt byte-identical). 14 matrix tests. Built, three rounds: round three 3 Oct (local commit, not pushed; steps 6 and 7 and a fix to round two): vouched conditions (when.manual) are a flag on the modset, met for the tier test's round 5 shares (objective 50%, Synapse 75%, below half and below Starting Strength 35%, Battle-shocked 20%; any other condition still all game) instead of always: of 969 units with one on an attacking effect (532 with a share below 100%), the pooled lift over never-met falls from 3,409 to 2,834 wounds per 100 pts (574 of 20,441). Step 6: cells addressed by content; a build copies every cell an older folder with the same cell hash holds (engine, effects files, layers; not the commit or rankings.json); one army's edited catalogue (a copy) computes 1 row and 1 column, 2,801 of 1.44 M base cells, 1.8 s against 13.9 s, byte-identical to a build from scratch. Step 7: node tools/matrix.js --check: parity 1.8e-15 (float32 read-back 5.2e-8); today's Offense from the cells with the unit pages' squads (rankings.json lt), a volley read with VOLLEY.FRESH = 0.5 and a normal taper: ρ 0.9968 to 0.9999, medians 0.02% to 1.57%, 2 pairs beyond 15% (Corvus Blackstar into Terminators, mixed damage; no panel-graded unit). Report reports/tiers/2026-10-03-matrix.md (--report); scoring.md section 7b; 18 matrix tests. Next: T-569 reads it; the keywords not read in full are T-582.

The allocation rule (each weapon fires at its best target in the field, with a cap on the fire one target absorbs; the game-plan sheet's pairing to start), and meta states clustered from winning lists by composition, each with its field and prevalence; a tier list per state, the generic one as their prevalence-weighted aggregate. List data enters only through the field, labelled; a unit's own score never uses its own popularity. Spec: design/matrix.md (sections 6 to 9, build plan 11, open questions 12). Steps 1 and 2 built 3 Oct (local commit, not pushed): tools/field.js (+ tools/field-names.json, 277 French and variant unit names; tests/unit/field.test.js), corpus 570b8c6, BSData 374f505. Step 1: 512 lists read, 447 in the field's pool (45 under 1,500 points, 18 off their size by more than 5%, 2 under 85% matched); 99.70% of unit lines matched (99.94% top quarter; roster.js alone 86.3%; the 208 French lists 74% to 99.4%). Step 2: the top quarter (115 lists) holds one stable state at seed 569: its best split, 4 states (heavy infantry, armour, mixed, monsters; silhouette 0.23), misses the 0.6 bar by 0.005 on one state and passes at 4 other seeds; every list (447) keeps 4 stable states (Jaccard 0.76 to 0.85). Report: reports/tiers/2026-10-03-field.md (states: -field-states.json). Decided 3 Oct (supervisor and design advisor): v1 runs on one meta state, the whole top-quarter field; the k = 4 split becomes four lenses by composition (each state's class shares re-weight the whole field; tools/field.js lensField). Step 3 built 3 Oct (local commit, not pushed): tools/allocate.js (the allocation kernel: soft best target, β, saturation and spill, reach; the reference battle; the matrix read through one interface, live or stored cells) and tests/unit/allocate.test.js (7 tests) plus a lens test in field.test.js. β = ∞ and one round give the game-plan sheet's best targets 54/54; the matrix's own choices agree with the sheet 65%, 61%, 59% at β 3, 6, 12; anti-tank fire into chaff 1.30%, 0.32%, 0.04% of round one; a five-round battle of the 630-unit field 0.75 s. Lenses: heavy infantry (43%), armour (heavy vehicles 45%), mixed (light vehicles 30%, chaff 13%), monsters (39%), names provisional. Report: reports/tiers/2026-10-03-allocation.md. Waiting on: Jordan's names for the lenses and the proposed meta-state convention (report, For the supervisor); then step 4 (X as a marginal entrant) after T-568 step 7.

Built 3 Oct (local commit, not pushed): tools/tierbaseline.js (its own script; reads docs/data/rankings.json and round 11's JSON only): per panel, ρ with a bootstrap 95% interval, within one and same on the reviewer's shape, each as lift over 2,000 shuffles; list share alone, points alone (both signs), frozen round 11, the shuffle; the pooled held-out ρ, round 11's per-army median, the two-reviewer ceiling (no pair yet); fixed seeds; unmatched panel units listed. A panel file's "locked": true is counted, not scored, without --final-check (tests/unit/tierbaseline.test.js); none of the three is locked. Numbers: held-out pooled ρ (Marines + Orks, 75 units) list share 0.21 [−0.03, 0.44], points ±0.01, round 11 −0.03 [−0.27, 0.20]; round 11 beats list share on 0 of 3 panels; per-army median 0.173 (10 of 27 under 0.10). Verdict: near zero on several armies: redesign the jobs (T-568, T-569) before fitting. Waiting on Jordan: the new lists to lock. Report: reports/tiers/2026-10-03-baselines.md (.json beside it).

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-03-astra-militarum-auspex.json, "locked": true (one of the plan's two locked panels: nobody scores it or compares it with the engine until the final check). Tier 1 to 5 as S to D; 61 datasheets graded after expanding the families (S 26, A 15, B 10, C 9, D 1; Leman Russ, Rogal Dorn, Baneblade and Heavy Weapons families recorded in groups). Unmatched: Tempestor Prime (no datasheet; the command squad is graded) and "Lord Marshal Draxus" (best guess Lord Marshal Dreir, not graded). BSData 074eabc (5 Sep), the site's commit on the video date; no Astra Militarum points moved since, so patchDrop is empty. Open: the video's title, address and exact date, and the Draxus name, if Jordan has them.

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-03-leagues-of-votann-discussion.json. Locked at first as the plan's second held-back panel; unlocked the same day once Jordan dated it to early April 2026, before 11th edition came out in June: "use": "reference: 10th edition, not scored or fitted, not compared with the engine", "locked": false, nothing of ours scored against it while locked. 13 datasheets graded (S 2, A 6, B 4, C 1); Hearthguard's C and Grimnyr's D second mentions kept in variants; Hearthkyn Theyn unmatched. Not patch-aligned (10th edition). With no more lists the second lock is waived (supervisor's call; Jordan: "use what you can"); Astra Militarum (T-574) is the one locked panel.

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-03-leagues-of-votann-2025.json, "use": "reference: …", "locked": false; never scored, fitted or compared with the engine, and never a fitting panel (it is the locked panel's army). tools/tierbaseline.js now skips any file whose use starts with "reference", even at --final-check (unit tests added). 17 datasheets graded (S 2, A 5, B 5, C 4, D 1); the two Steeljacks loadouts are separate datasheets in our stubs, so both are graded. Unmatched: "Grimnyr Strategist" (Grimnyr or Memnyr Strategist; ungraded). No BSData commit exists for its date. Reviewer against reviewer, across editions, with T-577: ρ 0.14 on 10 shared units (within one 7, same 5).

Written 3 Oct (local commit, not pushed): design/tier-plan.md section 4 (every convention frozen: minimum size, turns capped at 5, every lend on the two squads of its army it lifts most, the site's job names, the matrix's six answers; β joins the fitted weights) and section 10 step 2 done; design/tier-engine.md (conventions, the healer item closed, site job names in the glossary, "Next" item 2 done); design/matrix.md section 12 decided (questions 1 and 3 overridden by Jordan: the top-quarter lists make the field; β = 6 to start, fitted later, leave-one-army-out, never on locked panels) with sections 6.3, 6.4, 7.2, 7.6 and 8 to match; design/decisions.md 3 Oct entry, sections 3 and 4. package.json at the root ({"type": "commonjs"}, Node's default made explicit; the Workers keep their own "type": "module").

In the engine (tools/tiertest.js, tools/tierbench.js, reports' headings), design/scoring.md, design/tier-engine.md and anything the site shows; the data's "Support character" label is renamed (e.g. "joining character") so the job owns the word "Support". Internal names stay until this card.

Built 3 Oct (local commit, not pushed): tools/outcomes.js reads every placed list from the sources switched on (grimstat-corpus top level, CC BY 4.0; listhammer/ not read) and writes per army and unit: lists with and without, mean finishing percentile each side, lift with a 95% interval, win rates whenever a source gives game records; reports/tiers/2026-10-03-outcomes.md and .json; tests/unit/outcomes.test.js. 382 lists, 23 events, 33 armies (July to September), 86% of unit lines matched, none outside our stubs; final placings only, no game results in the licensed files. 33 of 418 units clear zero (chance: about 21): a yardstick in aggregate, never per unit. Faction tables: none lets a machine read them (Stat Check, 40kstats/Goonhammer, Metawatch, Listhammer, Hutber); statcheck, ttbattles and metawatch added to tools/sources.json switched off. Waiting on: Jordan whether to ask Stat Check and Tabletop Battles; Listhammer reply (T-418) for game records; a later card to teach roster.js the French export (up to 92 more lists).

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-03-space-marines-auspex.json, a fitting panel (not locked): 46 units with the reviewer's seven-step grade (ord) and a letter, Company Champions unmatched (no stub). BSData commit in force: 0c02471 (2 Sep, from BSData's commit list; our history starts 19 Sep); patchDrop empty, but 3 to 19 Sep is unchecked. Ceiling on 15 shared units: ρ 0.69 (95% 0.33 to 0.92), √ρ 0.83; the two videos straddle the 30 Aug points update. Report: reports/tiers/2026-10-03-space-marines-ceiling.md. Not scored against our engine (another card's battery).

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-03-tyranids-hivemind.json ("locked": false, fitting): 49 graded (S 4, A 12, B 19, C 11, D 3; "Detachment Dependent" as B, a condition rather than a rank), Sky-slasher Swarms unmatched (Legends). BSData 80568cc (2 Jul); points 2 Jul to 30 Sep read from BSData's files at run time, four units in patchDrop (Pyrovores, Neurotyrant, Tyrannocyte, Toxicrene). Ceiling against Auspex's Tyranids: ρ 0.73 [0.53, 0.86] on 38 units, √ρ 0.86 (about two months apart). T-575's points gap checked: no Space Marine move 2 to 30 Sep. tools/tierbaseline.js honours patchDrop and gives ceilings an interval; the step-1 round's report reports/tiers/2026-10-03-step1.md (held-out pooled ρ over 166 units: list share 0.41, round 11 0.19), with scoring.md, decisions.md and tier-engine.md section 7.

34 keywords at BSData 374f505 (node tools/matrix.js --unread), ranked by the corpus lists holding a unit they touch (grimstat-corpus, July to September, every placing, lists of 1,500+ points; list points = lists × the unit's minimum-size points, a floor; T-569's top-quarter field isn't built yet): (1) Lethal Hits only against non-Monster/Vehicle, read as unconditional (26 profiles, 39 units, 141 lists, 17.6k list pts; Orks mostly); (2) Cleave 1, 2, 2+, 3, 4, unread (25 profiles, 24 units, 99 lists, 15.1k; Boyz, Battlewagon, Ghazghkull, Kommandos, Squighog Boyz, Gorkanaut, Stompa); (3) Sustained Hits D3, read as 1 (13 profiles, 14 units, 41 lists, 8.7k; Avatar of Khaine, Commander Dante, Doom Scythe, Armiger Moirax); (4) Blast X (Blast 1, 2, 3), read as plain Blast (23 profiles, 24 units, 68 lists, 6.6k); (5) Conversion (5 profiles, 7 units, 25 lists, 4.8k; Knights, Hekaton, Thunderkyn); (6) the Anti-Monster/Vehicle spellings (Anti-Monster/Vehicle 2+, 3+, 4+; Anti-Non-Monster/Vehicle 2+, 3+; "Anti Vehicle 3+" without its hyphen; "Anti-Fly 2" without its "+"), unread (19 profiles, 15 units, 35 lists, 4.5k; Beast Snagga Boyz, Breaka Boyz, Hunta and Kill Rigs, Stonesinger, Mozrog); (7) Rapid Fire D6+3 and D3, unread (5 profiles, 9 units, 14 lists, 4.5k; four Knights, Deathwatch kill teams); (8) Twin Linked without its hyphen (5 profiles, 11 units, 4.0k; Aeldari vehicles, Hellions); (9) a stray "-" keyword on 5 profiles (Deathwatch Terminators, Kastelan Robots, Lychguard, Blight-hauler: data noise, nothing to read); (10) the one-offs: Harpooned (Norn Assimilator), Reverberating Summons (Great Unclean One), Devastating Wounds and Sustained Hits 2 against Monster/Vehicle, Infantry or non-Monster/Vehicle, Linked Fire, Overcharge, Plasma Warhead, Defensive Array, Hive Defences, Psychic Assassin. Each one read changes ev.js's numbers, so it moves the live Offense numbers and letters: per keyword, before it ships, list the live units whose Offense moves and by how much (rankings.json before and after), add a scoring.md changelog line, and run the stamps on Linux. Until then each stays in the matrix's dice key as x:<keyword>. Built 3 Oct (local commit, not pushed): 27 of the 34 read in docs/ev.js and the calculator's dice engine with the same counts: each keyword read whole ("Psychic Assassin" isn't Psychic); an ability followed by keywords counts only against a target that meets them (Lethal Hits, Devastating Wounds, Sustained Hits); Anti-X in every spelling, and the calculator now reads every weapon's Anti-X against the target's keywords (it read none, only the manual pick); Blast X, Cleave X, Sustained Hits D3, Rapid Fire D3 and D6+3 (the calculator's field takes dice), Twin Linked, Conversion (beyond half range), Psychic Assassin (6 attacks into a Psyker), Overcharge (hazard fails on 1 to 4). Not read, not dice: Harpooned, Reverberating Summons, Linked Fire, Plasma Warhead, Defensive Array, Hive Defences (and the data's lone "-"). 81 units' Offense moves (71 live; Stonesinger +57.2%, Gunwagon +41.0%, Deffkilla Wartrike +31.9%, Warboss in Mega Armour +30.0%, Night Spinner +22.8%, Beastboss −16.6%); 16 letters (9 live by their own numbers: Gunwagon, Warboss in Mega Armour, Ancient in Terminator Armour B → A, Stonesinger C → B, Night Spinner and both Acastus Asterius D → C, Wartrakks and Wazbom Blastajet C → D; 3 live by re-sorting). Each keyword's own moves from ten isolation builds. The ledger: byte-identical with this ev.js (sha256, all nine outputs); with the matrix.js edit only meta.engine moves, committed outputs kept. tests/unit/keywords.test.js (hand values, parity with the dice engine, the two readers on every weapon); scoring.md changelog line per keyword; report reports/tiers/2026-10-03-keywords.md.

Built 3 Oct (local commit, not pushed): reports/tiers/panel/2026-10-02-orks-spruesandbrews.json moved to panel/retired/ (tools/tierbaseline.js reads it only with --sanity, a sanity list outside every pool, ceiling and gate; tools/tiertest.js's hand list drops it, the old rounds' Orks columns print "–", and adds Auspex's Space Marines and both new Tyranid files); tierbaseline.js classes panels (held out = armies never tuned on, same army and new reviewer, tuned, sanity), pools held out, new reviewer, unseen and fitting, gives an army with three reviewers the ceiling √ of the mean pairwise ρ, and runs the gate (gates: pooled lift over shuffle on the unseen panels rises above frozen round 11's with a paired bootstrap interval; no fitting panel more than one SE below); unit tests added. Jordan's ruling: the two new Tyranid files are two creators' lists, both fitting (attribution uncertain, noted in the files); the second drops Neurotyrant, Tyrannocyte and Toxicrene for points (builder's call, flagged). Gate text in tier-plan.md, tier-engine.md, tier-briefing.md (with the two sessions' protocol, section 3) and T-564; the list-share correction (entrants', not top-quarter) in decisions.md, tier-plan.md, the baselines report and tierbaseline.js; tier-plan.md section 2's cross-army checks and floor; matrix.md 7.5's size note, T-569 step 4's test and question 7 (not yet asked); decisions.md entries for the answers and the stop rule. Battery: held out (76 units) entrants' list share 0.23, round 11 0.30; same army, new reviewer (86) 0.72 and 0.38; unseen (162) 0.49 and 0.34; Tyranid ceiling √0.65 = 0.80. Report: reports/tiers/2026-10-03-step1.md, addendum (.json: reports/tiers/2026-10-03-battery-t580.json).

Built 3 Oct (local commit, not pushed): tools/tierbench.js knobs cost.alpha, cost.runner (both, gate, cheap), composite (best, allowed, log2), fixDet, and every unit's result (every); --check still reproduces round 10. tools/round12.js runs the six experiments in about 7 s, choosing each setting on a rule that reads no panel (the supervisor's "choose, then check") and checking it with the gate. tools/tyrtable.js prints the Tyranid table in a fixed layout every round (Jordan). Numbers: nothing passes the gate. The chosen candidate (Runner's points gate dropped) takes ρ(score, points) −0.16 → +0.10 pooled, but unseen pooled ρ falls 0.27 → 0.16 (frozen round 11 0.34) and Mortarion and friends return as mission units (round 3's failure, tried twice: flagged). Gate kept and cheapness part dropped: −0.10, agreement unchanged (+0.01). α 0.75 alone: cost-neutral pooled. Per army, 18 to 22 of 29 outside ±0.15 in every version. List share counted both ways orders the rounds the same within one SE. Option premium +0.33 [−1.26, 1.94]. The sweep's top ten have owners. Report: reports/tiers/2026-10-03-round12.md (.json beside it), reports/tiers/2026-10-03-tyranids-round12-table.md. Next: carry "cheapness part dropped" into the matrix's first comparison as one change; card the four unowned constants (gate, half weight, Advance and objective and reserve distances).

Built 3 Oct (local commit, not pushed): node tools/tiertest.js --rawdump all (about 40 s, peak 2.0 GB) records every context round 11 scores into build/tier-raw-all/<hash12>.json (70,376 rows, 73.6 MB, git-ignored; latest.txt names it; per-process temporary name; the engine's B0 and B1 keys stored as a check); tools/tierconfig.json (every knob of layers 2 to 4 with value, default, source, date, owner; the layer-1 constants for provenance; profiles B0 = round 11, B1 = Jordan's conventions, minimum size); tools/tierbench.js composeAll (about 130 ms), loadConfig, checkR11; tools/round13.js; tools/tyrtable.js shows the baseline when nothing is adopted and the trial in a last column, with the site's job names; tests/unit/round13.test.js on a 200 KB cut (tests/fixtures/tier-raw-mini.json.gz). Reproduction: 0 differences over 1,153 units and 52 Tyranids; battery identical. Frozen round 11's ρ(score, points) −0.414 (the review's −0.42). B1: unseen 0.33 (round 11 0.34), lean −0.30. Round 12's experiments 3 and 4 on B1 (rules that read no panel): Runner's cheapness part dropped + α 0.6, lean −0.01, unseen 0.36, rise +0.01 [−0.10, 0.13]: not adopted. Report: reports/tiers/2026-10-03-round13.md (.json), reports/tiers/2026-10-03-tyranids-round13-table.md. Next: step 4's second half, the field in place of the five targets, measured as one change on B1.

Each in tools/tierconfig.json with its owner. (1) Runner's points gate (runner.gateFull 75, runner.gateZero 260, V4C, King of the Hill's weight classes; sweep 363 letters): derive it from the points of units that do actions in the corpus's top-quarter lists (grimstat-corpus, the field T-569 builds), else a fitter slot; owner: builder, then fitter. (2) Runner's half weight (runner.half 0.5, V2C.RUNNER_HALF; 162): fitter slot. (3) Advance (V3C.ADV 3.5"; round 9's sweep 288): source, the core rules (the mean of a D6), read on Wahapedia's 11th-edition page and cited in scoring.md. (4) The objectives' distances (V6C.OBJ_MID 15", OBJ_FAR 21", OBJ_DEEP 27"; 286): source, the mission pack's layouts (our measurement, no text kept). (5) Strategic Reserves' arrival distance (V3C.RES 18"; 206): source, the rules' arrival limits and the deployment maps. (6) A Lone Operative's survival (runner.lone ×2; 78): sourced once the matrix's reach rule (matrix.md 7.3) plays the rule, fitter slot until then. (7) Hammer's peak weight (V9C.PEAK 0.75; 60): fitter slot. (8) A spawn's Runner share (runner.spawn 0.5): fitter slot. (9) the estimates in layer 1 with no source: the revive ×1.15 (V9C.REVIVE), below half 0.35 (V3C.BELOW), within Synapse 0.75 (V5C.SYN), near a debuff 0.5 (V5C.NEAR), the position floor 0.5 (V6C.POS_FLOOR): each a source (the matrix or the corpus) or a fitter slot. The steps, cuts, turns cap and a CP's price are Jordan's conventions, not on this card. Done when every row of tierconfig.json names a source or a fitter slot, and scoring.md says which.

On the every-army raw table at round 11's settings (T-583: build/tier-raw-all/<hash>.json from node tools/tiertest.js --rawdump all; each fieldable unit's B1 context from tools/tierbench.js compose(raw, loadConfig("B1")), its row's f and its ways' v): (a) PCA with a rotation and the scree, every fieldable unit, about 30 raw variables standardised: how many dimensions explain the spread, what loads on each, and where the hand gates (joining characters barred from Action and Tank, no-OC units, one-use units) sit against them; (b) a regularised ordinal fit on all raw variables, leave-one-army-out over the fitting panels, as the ceiling benchmark; (c) the four-job composite on the same held-out panels beside it, with bootstrap intervals. Decision rule, written before the run: if (b) beats (c) by more than the interval, the jobs are redesigned from the factors (Jordan names them); otherwise the jobs stay, with that evidence. Nothing tuned on a panel; the locked panel stays shut; the matrix version runs later.

Done 3 Oct (local commit, not pushed; analysis only, nothing adopted): the every-army raw table (BSData 374f505) composed at B0 and B1, each unit's DPS move split exactly into five parts (pool shift, context re-picked, per-turn damage per point, turns alive through delivery, way in). Hive Guard 86 → 65 and Termagants 52 → 30 are all turns alive (T 4.62 → 2.70, 3.52 → 2.09; per-turn damage per point unchanged). Zoanthropes compose at 79 at B1 (with the Neurotyrant), not 65: their 85 → 79 is mostly the leader's fixed points diluting per-turn damage. The Tyrannofex's 84 → 88 is the pool shift alone (median Hammer raw 218 → 195). The two Space Marine squads lose about as much to turns but a leader pair re-picked at minimum size lifts them (Hellblasters 84 → 91, Bladeguard 92 → 97). Over 298 multi-size units, ΔDPS on the parts R² 0.82: turns 58% (61% of the absolute moves), context 21%, per-turn 10%, way 6%, pool 4%. Answer: (a), mostly turns alive: Hammer is damage per point × survival in absolute hits (round 5), so minimum size costs a multi-model damage unit about 20 points; minimum size is neutral only with a size-free survival term, which the matrix's mirror (a hazard per wound) is, for a reason unrelated to targets. Report: reports/tiers/2026-10-03-size-oddity.md (with a paste-ready decisions.md line).

Built 3 Oct (local commit, not pushed; a report, nothing adopted, no form chosen): tools/v4walk.js (node tools/v4walk.js --write, about 8 s): the 52 Tyranid pool units at minimum size, best legal loadout (most field offense) and, for the record, default wargear; offense ranged and melee (enemy points destroyed per 100 points in one phase into the top-quarter field, each gun by the one-phase targeting rule at β 6, every charge landing) and into each of seven unit classes; defense per point from the field's shooting and fight phases (field points spent to destroy it per 100 points, the unit as a marginal target of the targeting rule) and from six weapon classes; defense absolute (share of the field's shooting phase); lends (banner.js lend-only, and in field points); mortal wounds per use (kindfx.json, mortalfx.json); body and reach. The walk: offense, defense, the scaled sum and the geometric mean, each with ρ against the three reviewers (SE, lift; Auspex tuned on), ρ(score, points) and within one as lift over shuffle. tools/tyrtable.js walkTable (the fixed layout); tools/allocate.js keeps weapon names on its groups; tests/unit/v4walk.test.js (parity of 200 cells against ev.js, worst 2.2e−16; a second run byte-identical; volleys equal allocate.js's; shares conserved). Report: reports/tiers/2026-10-03-v4-step1a.md (.json), reports/tiers/2026-10-03-tyranids-v4-walk-table.md. Next: a full stop. Jordan reads the order against the reviewers unit by unit before step 1b or anything else runs. Not computed: spawning (no numbers in the effects files), Tyrant Guard's reverse lend (noted in words only).

A Lab page, noindex: the 52 Tyranids re-sorting live as sliders move (line weights, the Kill premium, melee lands, holding, the 10% combo threshold, rule multipliers, band cuts), each unit's ledger expandable, its best form re-picked live, Auspex beside it and the other two Tyranid lists faded; standing lines: ρ against each reviewer, ρ(value, points), the knob count. Built 3 Oct at /lab/ledger/ (docs/lab/ledger/index.html, ledger.js's compute), tested on a made-up fixture (tests/fixtures/ledger-tyranids-sample.json, tests/unit/ledgerpage.test.js); waits for T-588's tyranids.json, and shows a "the engine hasn't run" message until then. Score, Actions and Hold start at 0.

A typical 2,000-point army from the top-quarter meta; Kill (enemy points removed in one turn, best targets first, limited by what that army holds) and Soak (enemy points that must activate to remove it, the enemy's best tools first, limited by what it carries), per 100 points; OC and actions per 100; every form (size, loadout, detachment, alone or joined to a leader); rules sorted into dice (computed), positional (a multiplier on their line) and army-wide (a multiplier on the total). Writes the JSON the ledger page reads. Pre-dataslate data (BSData 374f505), Tyranids only. Built 3 Oct (local commit, not pushed): tools/ledger.js (node tools/ledger.js --write, about 15 s) writes docs/lab/ledger/tyranids.json (section 11's contract; 1,106 forms, 2.5 MB) and reports/tiers/2026-10-03-ledger-engine.md; tests/unit/ledger.test.js (parity of 200 cells against ev.js 4.4e−16; a second run byte-identical; the contract; supply conserved; a Norn Emissary's Soak against a toy army by hand). metaKillRate 0.444 at β 6; thin classes: aircraft and other (absent). Next: T-589, the page.

Built 3 Oct (local commit, not pushed; a report, nothing adopted): tools/ledgercrack.js (node tools/ledgercrack.js --write, about 48 s on 12 threads): the five line weights, melee lands, β and one multiplier per kind of rule carried by 3+ units (11 kinds), coordinate search from 40 seeded restarts per fit, every Value through ledger.js (valueForm, re-checked with compute()); tests/unit/ledgercrack.test.js. Report: reports/tiers/2026-10-03-ledger-crack.md (.json). Numbers: best Auspex ρ 0.65 (defaults 0.19), unseen -hivemind 0.40 and -second 0.32, ρ(Value, points) 0.35; 20 shuffles × 8 restarts reach median 0.42 (0.16 to 0.55), the real search 0.64 at that budget, above all of them; 40 distinct solutions, 10 near the best, agreeing on order at median ρ 0.95; Objective B 0.50; leave one out 0.57 / 0.35 / 0.33; pinned: melee lands, Lone Operative, debuffs. Nine units stay two bands or more from Auspex. Flagged: a kind's multiplier compounds over a form's rules of that kind on the page.

Replaces the ledger's "melee lands" slider per unit: the tournament layouts' distances, Move and Advance, the 2D6 charge odds, Deep Strike, Scouts and Infiltrators, transports. Not started.

11th edition's tournament deployment maps read on Wahapedia (understood, never copied): each zone as our own polygon, the gaps between zones and to objectives in inches, averaged; tools/deployments.json and a report. Feeds T-590.

The share of shots blocked between deployment zones on the standard layouts (GW, WTC), by ray-casting over terrain footprints, if the layouts are public in a usable form (T-592 reports on that); a scenario block for the ledger, never a free slider.

Fix in docs/lab/ledger/ledger.js; the search report (T-591) rerun before and after.

tools/spawn.js: expected points placed per turn per 100 points (Biovores' and Sporocysts' spores, the Tervigon's Termagants and any other Tyranid spawner), the rules as our own numbers in tools/spawn-rules.json.

Each form's own "melee lands" from tools/charge-tyranids.json and a Spawn line from tools/spawn-tyranids.json in tools/ledger.js and the page; rerun the search; republish the page.

A tough unit only soaks fire if the enemy must shoot it: Soak × threat (its non-Soak lines over the army median, capped at 1) under a slider; each unit compared with the reviewers on its best solo form, combos listed apart; the search rerun; tools/ledger-best.json.

Kill into a target class weighted by how short the army is of good killers of it (the Tyrannofex as Tyranids' scarce anti-tank); tools/scarcity.js.

The Red Terror's return to reserves (exposed less often), tunnels for others, regeneration in Assimilation Swarm and other healing; tools/soakfx.js.

Built 3 Oct, on beta: (1) the defender's Modifiers part has its defense set and a FIGHT-BACK set for its strike-back: +attacks, crits on, Anti-X, +1 hit/wound/Strength, Lethal, Devastating, Sustained, Ignores Cover, Precision, re-rolls to hit and wound (backModOverrides, one set for the unit, laid over each of its weapons' own keywords by mergeBack in strikeBackParams); (2) the attacker's Modifiers part has a DEFENSE set for when the target shoots or fights back: cover (on by default, as before, unseen until now), −1 AP, −1 to hit, −1 to wound, −1 damage, half damage (defModOverrides by the attacker's own unit, which the strike-back already read); both show as ↩ chips on their side's line while Fight back or To the death is on; (3) the defender auto-equips into the attacker (defVsPick, goal "vs"): its guns when the attacker shoots, its melee when it fights, solved again when the attacker, a size or the mode changes, while nobody has edited it; "Best into <attacker>" heads its Auto-equip menu. Hive Guard into a Hekaton now carry 3 shockcannons (Anti-Vehicle 2+) where the all-rounder gave impaler cannons. Tests: browser/fightback (new), browser/autoequip (the defender's default is now "vs").

Built 3 Oct, on beta: the line under each card (layout.js cardLines) took only the leader's buffs and the unit's own abilities; a detachment's effects in play ("Re-roll hit rolls of 1") showed only inside the open Modifiers part. Now they ride the line too, as ⚡ chips that switch off on a tap (detOff, as in the open part), and count in the Modifiers head's badge; an army rule joins once it's switched on (they start off). Test: browser/modline.

tools/ledger.js and friends with --army; Space Marines scored with the Tyranid search's settings, never tuned, against both Marine panels and B1.

One-of-a-kind abilities as hand-set values outside the search: spore mine placement, Better Overwatch; labelled as Jordan's judgement.

Wire scarcity and the Soak effects into the page behind sliders, rerun the search, republish the page.

tools/ledger.js and its modules load docs/ev.js, bsdata.js, the effects files and build/units.json from a recorded commit, every ledger output records it, and a run fails if an input differs; T-579 and T-582 only after this.

Reviewers grade a leader by what it does for its squad; the single-unit comparison scores Librarians, Lieutenants and the Apothecary Biologis alone and sinks them (A → D). Squads compare as single units, characters that can lead on their best joined form. Waits for Jordan's read.

Kill goes into the meta army's characters as if they stood alone; most are joined to squads and can't be picked out. Treat joined characters as part of their squad's target profile (Precision aside). Waits for Jordan's read.

The Synapse multiplier lifts Ranged Warriors' whole Value (12th); at ×1 they fall to 22nd. Measure the marginal worth of an extra Synapse source to an army.

Above 1.07 the clamp at 1 erases Vanguard Onslaught's advance-and-charge edge (0.93 against 0.84).

Generalists' Kill expected to fall 10–20% against specialists'.

About +8% to their melee.

Every unit's non-dice abilities sorted into kinds and checked against the datasheet (the ledger's list misses Biovores' spawning and Raveners' burrowing); a page per army for Jordan to sanity-check.

Plain units set Kill, Soak and melee lands; each rule kind fitted only on the units carrying it against that baseline; Jordan's calls last. Agreement reported at every stage. After T-608 and T-615.

Bradley–Terry over cross-tier pairs, ridge toward simple weights, per-reviewer reliability, a budget of ~8 knobs (the rest hibernated), every-weight-1 baseline, leave-one-list-out, scrambled letters; tools/ledgerfit.js. In progress.

Units our ledger rates in their army's top quarter, taken by few winning lists, rated lower by reviewers, and robust across every saved slider setting; each with its one-line ledger reason. A report for Jordan first, after the switch steps.

Every unit's full ledger, what it kills best, what kills it, its forms, lens views; the sliders with presets and shareable settings (a supporter perk later, under the house rules). Mockup first; after the model settles.

matrix.test.js's profile counts and --check compare the matrix with the live site's data and Offense, which moved to BSData 8b91e6b and the keyword reader (T-579, T-582) while the ledger stays frozen at 374f505: the tests should read the ledger's frozen inputs (tools/ledger-inputs.js), or check the live data separately.

Reviewers who rank "what wins" echo list share. In the fitter (tools/ledgerfit.js), model each reviewer as ledger + γ·log(list share); drop γ when publishing. List share and placings stay as checks, never as training targets in the same fit. A method step, logged in reports/tiers/ledger-steps.md.

The fitter bootstraps the weights only. Add a rank interval per unit (bootstrap over units and lists), shown on the ledger page and in the diamonds report (T-618). A wide interval marks a unit we cannot place, not a diamond.

The ledger counts Kill for one turn and durability on a separate line that the fit weights at nearly nothing, so a unit that dies on turn 2 keeps a full turn's Kill. Switch killOverGame: Kill × the unit's expected share of the game still fighting, against the meta army's fire (best tools first, from the Soak numbers the page already has), squads losing output as models die and single models all at once, normalised so the median unit keeps its Kill. Page-only (no engine field, frozen inputs untouched); one ledger step with a written prediction.

Switch joinedMarginal: a unit ranks at the better of its solo worth and its marginal worth in its best joined form, (combo value × combo points − the partner alone × its points) ÷ its own points, for squads and leaders alike, labelled. Supervisor's check at the step-6 baseline: Genestealers with a Broodlord 1,943 per 100 (about 13th; the reviewers 13.5), Gargoyles with a Winged Prime 1,235 (about 20th; 23), Tyrant Guard with a Hive Tyrant 1,456 (about 16th; 29), the Neurotyrant with Zoanthropes about 10th (13.5). Unlike T-604 (ranked at the whole combo's value), the partner's own worth is taken out. Page-only; one ledger step.

An army takes up to three detachments (Detachment Points: 3 at 2,000) and all their rules apply, so a unit can carry two detachments' rules at once (for example the Warrior detachment, 1 point, with Crusher Stampede, 2). The ledger values each form under one detachment, so a combination such as the Norn detachment's 4+ invulnerable save on the Norn Assimilator with another detachment's rule is missed. Forms for every legal pair (and triple) within 3 points, from the frozen detfx data; an engine change, not an input change.

Today Kill is one number against the typical army, and most units' Kill lands on lone characters (Lictor 73%, Exocrine 55%), so specialists don't stand out. Switch killByJob: Kill per 100 into each target class (byClass, already in the data), each class ranked against every unit's Kill into it; a unit's Kill = its best class's standing, with a step (not a slope) for a second strong class, as Jordan's grading rules say (design/tier-briefing.md section 2: 100/20/20/20 is S). Page-only; one ledger step.

Across 14 armies dedicated transports rank about 21% of the list lower than the reviewers put them (Chaos Rhino 47 to 77% lower in all four Chaos armies; Venom and Raider 85% and 77%): nothing in the ledger values carrying a unit forward. A Delivery line or a joined-style "unit inside" form: the carried unit's Kill and Score arriving a turn earlier and protected, from the charge model and tools/transports.js; one ledger step, on every army.

(1) Factor analysis and archetypal analysis on every unit of the 16 armies' ledgers (raw lines per 100 points, Kill by target class, movement and plain traits): the roles that fall out, each unit as a mix of them, compared with the four hand-made jobs (Hammer, Anvil, Banner, Runner). (2) A mixture of regressions: each role's own weights fitted to the reviewers by the pairwise likelihood, a unit's Value its membership-weighted sum, judged by leave-one-army-out against the single-weight ledger. Roles shown to Jordan before anything is adopted.

Sports analytics calibrates to outcomes, not pundits (regularised plus-minus, box-score models fitted to it, WAR). (1) A deep dive into the related methods (RAPM and its priors, BPM/EPM fitted to it, WAR's replacement level and positional adjustment, player-skill models such as Elo/TrueSkill/Bradley–Terry with covariates, hierarchical models of meta and matchups, selection bias in who picks what, causal and IRT angles) and how each would fit 40k list data; (2) an audit of what grimstat-corpus holds (games or placings per list, players, rounds, opponents, dates, units per army); (3) a design that keeps the ledger as the "why": results give each unit's worth to winning, the ledger's lines explain it (the ledger as the stat model fitted to the results, as BPM is to RAPM), with meta, player skill and matchups as their own terms. Report and design first; no model adopted.

Every variable we have per Tyranid unit (datasheet numbers, weapon summaries, rule flags in our own words, the ledger's lines) and models from linear to flexible (boosted trees with monotone constraints) fitted to the reviewers' consensus. (1) In-sample: can any model reach the consensus (missing variables if not); (2) units held out, rotating over all 52 (rigor and data if (1) passes and this fails); (3) the flexible model against the ledger on held-out units (the ledger's form if it wins). Then what the flexible model keys on (thresholds, interactions) as the "why", for new ledger mechanics.

Switch secondaryVP, off, in place of the crude Actions line (1 per unit per 100 points): each unit's expected secondary VP per game from the 11th-edition mission deck (which cards it can score: actions, positions, reach (arrival, Scouts, Infiltrators), staying alive and hidden (Indirect, Stealth, cheap), bodies), counted at the margin (what the army loses without it, since secondaries are capped and other units score them too), converted at a rate set by the game rather than fitted: points per VP = army points ÷ the VP a typical game hands out. One step with a prediction, judged as steps 20–23. Blocked: the secondary deck's numbers (cap per game, VP per card, how often each scores) must be read on Wahapedia's 11th-edition pages, which this cloud environment's network policy blocks (add wahapedia.ru to Allowed domains), or given by Jordan. The primaries are already read (tools/dispositions.js: 15 VP a round, 45 a game); secondaries were left out there. Partly unblocked 4 Oct: design/rules-notes.md (11th-edition core rules in our own words) gives the caps: secondaries 45 VP a game, at most 15 a round, a fixed card at most 20 (primary 45, painted 10); tactical cards drawn two a Command phase, discards earn 1 CP; actions cost the unit its shooting that turn. Still missing: the individual secondary cards (what each pays for, how much), from the mission deck. Step 27 not kept 4 Oct: headline 72.3% → 73.5% but its aimed units mostly moved away (Biovores, Hormagaunts, Gargoyles) while big tough units rose; back to its builder to find the driving term. Step 27b (fire in proportion to points) not kept 4 Oct either: ρ 0.520 → 0.512; Biovores and Neurolictor nearer the reviewers, but Hormagaunts fell and the Deathleaper and Leapers rose past their grades.

Switch missionVP, off: a catalogue of every secondary card and every primary scoring line (design/mission-notes.md), each with its requirements (OC on which objectives, action and what it costs, surviving the opponent's turn, reach to which zone by which round, hidden, number of units) and its VP; each unit's profile from the rules; P(unit achieves card) × VP; credited at the margin (the typical army's best few scorers per card; what it loses without the unit); primaries weighted by the field's dispositions; converted at about 31 points per VP. Replaces Score, Hold, Actions and own-bodies Presence. Kill cards stay with Kill. One step with a prediction, judged on the step-26 baseline.

A reviewer reads the whole problem (design/ledger.md, the step log, the diagnoses T-632/T-635/T-636, the burst checks) and compares it with established methods for valuing pieces from expert rankings: sports player value (value over replacement / WAR), paired-comparison rating (Bradley–Terry, Elo, TrueSkill), learning to rank, hedonic pricing, conjoint and expert-elicitation, Bayesian hierarchical models across armies. Report: what we do well, what's wrong or missing, ranked recommendations.

Inventory every slider and switch (what it means in the game, its sensible range, whether it's fitted or set by reasoning). Several tuning methods with overfitting guards (held-out lists, units and the 14 never-fitted armies): coordinate search one knob at a time, sensitivity sweeps, Bayesian/CMA-style search on a small set, hierarchical shrinkage across armies, expert priors. Every tuned setting saved as a versioned benchmark, judged by the provisional keep rule and the movement view.

Switch supportCredit, off: Value = worth without support + κ × Σ(m − 1) × the army's median support-free Value per 100 points (the detachment kind stays a multiplier); κ re-fitted by ledgerfit with the support multipliers, judged on the 14 never-fitted armies and held-out units. One step. 5 Oct: 35a not kept; 35b provisional (fixes the Tyranid order in sample; the 14 armies and held-out re-fits fall).

Switch preferredTargets, off: each unit's Burst Kill by target class from its weapons (the matrix's cells against the field's units of each class); its fire goes first to the classes it's best at, limited by how much of each class the field holds; characters treated as joined at the field's real join rate (targetable alone only by Precision, or when fielded alone); the field's class composition read from one swappable file (pooled today; per faction, detachment or list style later). One step with a prediction, judged as usual. Also fixes the finding that most units' damage lands on characters.

From the tournament lists (grimstat-corpus, CC BY 4.0; and our own data later), a field file per enemy faction, per detachment and per meta state; the ledger and the calculator read any of them in place of the pooled field, so a unit's value can be shown against a chosen opponent. Data is thin today (about 700 lists), so each field carries its list count and is pooled toward the whole field when thin.

Switch supportMeasured, off: the support kinds stop multiplying the carrier's own Kill; instead each support rule's worth is measured with the engine on the friends it reaches: the typical friendly unit's Kill (and Soak, for defensive buffs) with and without the effect, × how many friends a game it reaches (aura range, Synapse coverage), in points, per 100 of the carrier's points. Game-derived, no fitted strength. One step.

Switch vpLedger, off: Kill converted to VP (enemy points removed → VP denied from the enemy's scoring units and kill cards scored, at the game's rates in design/mission-notes.md), the mission line (T-647) in VP as built, Soak as VP saved; Value = VP a game per 100 points × 2,000 ÷ 65. Neither line dominates by its units; the conversion rates are the game's. One step.

A unit's burst on its preferred targets minus the expected points the field takes back from it in its reply (its Soak against the field's preferred targeting), over the turns it survives. Joins burst, toughness-with-threat and the colleague's cat-and-mouse point into one number. After T-655 lands.

Switch lifeKill, off: per activation, a blend of Burst (best 3 targets) and Average (points finished per activation over every non-character unit in the field, weighted by how often it's fielded); × the expected number of activations it gets before the field bursts it down (from tools/burst.js --defend's finish chances, fire in proportion to points); characters excluded as targets; the blend fixed by reasoning. Replaces burstKill's Kill. One step. Absorbs T-659 (trade value). Built 5 Oct (switch lifeKill, off; tools/burst.js --life for every army; dials lifeSurvive, lifeBlend, lifeMode; design/ledger.md section 26): step 39 on the Tyranids, Track A 79.3% → 78.0%, Track B 77.7% → 76.4%; tuned as dials (reports/tiers/2026-10-05-dials.md: s > 0 costs). Nothing adopted

Each switch built since step 18 gets a strength dial (0 = off, 1 = as built, up to ~2–3): vpLedger (the mission line's weight, and a per-unit vs per-point split for screens and secondary scorers), missionVP, secondaryVP, scoreFloor, killClassWeight, arrivalKill, scarceAnswers, carryDedicated, threatSoak, shockPressure, supportMeasured, preferredTargets (its caps), lifeKill when built. tools/knobsweep.js sweeps one dial on a base (Track B) over a grid and reports, per value: the five Tyranid lists, held-out Tyranid units (diagnose --quick), the Tyranid movement and the units that move most; and a combined pass over the few best dials. Strengths are set from the curves with held-out units as the guard. Built 5 Oct (ledger.js DIALS, 17 dials, the fingerprint test; tools/knobsweep.js; design/ledger.md section 27): four help the Tyranids held out (arrivalKillW 1.5, secondaryVPW 0.5, supportMeasuredW 3, shockPressureW 2; Track B 77.7% → 81.4% stacked), saved as the candidate tools/ledger-benchmarks/2026-10-05-trackB-dials4.json; they don't transfer (T-668's exam). reports/tiers/2026-10-05-dials.md. Nothing adopted

Built: ledger.js profileDials (whole Value, hibernated), profileLines (each family on the parts of Value it affects) and the pointsExp dial, all off (benchmarks reproduce); tools/ledgerprofile.js (the datasheet features as data), tools/crack2model.js (the ledger's maths in flat arrays, exact to 1e-15 against compute()), tools/crack2core.js and tools/ledgercrack2.js (G2: switches and dials with the weights, 10.1M combinations; G3: twelve family dials, 531,441 combinations on each of 62 settings, 32.9M; 3 shuffles, 8 fake worlds, placebo families, leave-one-list-out, leave-units-out; the wide net and the staged exam, --net, --exam --armies a,b [--on <gate>]), tools/crack2report.js. 5 Oct: G3 best 84.3% on the five lists (rows) against built A 78.9% (+5.4); the fake worlds gain +0.1 to +0.6 (p ≤ 1/9) but held-out units only +0.4 (79.7% against 79.3%), the shuffles climb +9 to +19 over the built setting, and the placebos sit where the real families do: mostly these 52 units, not a code. Exam: of 16.9M stored Tyranid combinations none reaches 70% on both Space Marines and World Eaters (best mean 72.9% against A's 66.1% ± 3.4); the 2,000 best on all 15: none clears 70% everywhere, the most armies cleared 3 of 15, best mean 61.7% against A 59.4% ± 2.2, B 60.1%. Rung (c) (every feature as a game-wide slope, 152–155 knobs, searched): 92.9% / 92.8% on the five lists, but shuffled letters reach 91.5% / 92.6%, held-out units +0.9 / +2.2 and the 14 armies fall (58.9% → 57.1%, 59.9% → 54.0%): 52 units cannot identify the knobs. The ceiling scan (all 16.9M stored combinations on all 15 armies, in-sample): the best mean is 62.7% (G2; G3 61.6%), none reaches 63%, the best clears 70% on 1 army; picked on 10 armies and scored on the 5 held out, 60.2% (B 59.4%, A 57.5%). This knob space cannot reach 70% broadly: the next gain needs new ingredients, not new weights. Nothing adopted; the rung (c) candidates (tools/ledger-benchmarks/2026-10-05-crack-candidate-A/B.json) are noise fits, not for adoption. reports/tiers/2026-10-05-crack.md, -crack-exam.md. Next: new ingredients for the ledger (what it measures); the exam stays a cheap re-runnable gate (--exam --armies … --on …).

tools/pricelist.js: log points at the minimum size (and per model) of every datasheet of the 16 ledger armies (829 once shared ones count once and Crucible is out) regressed on the engine's capabilities (rankings.json's damage into five targets, durability against five attackers, OC, Move; absolute) and 73 perk variables in families, ridge on within-army deviations, λ by leaving one army out, 500 bootstraps, a lasso, collinear groups jointly, the ledger's own capabilities as a cross-check. Built 5 Oct: left-out R² 88.4% (capabilities alone 85.0%); prices e.g. Fly +10%, Lone Operative +10%, command points rule +8%, Indirect Fire +7%, Stealth +5%, Blast +4%, Feel No Pain −10% at equal durability, Fights First −8%. Under-priced units don't get better letters: Tyranid residual alone 50.9% (Track B 77.7%), blend 67.0%, log blend 76.2%; other armies 49.2%. Dial scale for T-662: weapon keywords 1.12×, Feel No Pain 0.23×, Fights First −0.06× (increment), Lone Operative 8.1×; arrival and Stealth not meaningful as a ratio. reports/tiers/2026-10-05-pricelist.md. A report: nothing adopted

Built: preferred targets and life for all 16 armies (tools/burst.js --prefer/--life, merged; tools/life-space-marines.json; tools/ledger-all.js's chain now builds burst, prefer, life and supportfx), tools/exam.js (per army and pooled pairwise over the Space Marines and the 14 at wCarry 0, paired bootstrap intervals, 19 s), the candidate tools/ledger-benchmarks/2026-10-05-trackB-dials4.json. 5 Oct: pooled A 59.4%, B 60.1% (+0.7 [−2.0, +3.2]), B + four dials 60.0% (−0.1 ± 2.4 against B): neither transfers. The Space Marines' scarcity and soakfx still missing (would move their Track B). reports/tiers/2026-10-05-exam.md. Nothing adopted

Built: tools/misses.js (a report, read-only). For each graded unit it takes the reviewers' percentile minus ours at Track A (step 34b, wCarry 0, the exam's numbers) and tests 1,250 one-condition groups beside our position, held out by army. Report: reports/tiers/2026-10-05-misses.md and .json. Found: our position explains 8% of the reviewers' (slope 0.29). There's no single missing ingredient: ten groups together reach 22% and a lasso on 340 columns 2%. Underrated: psykers (+14 beyond our position, 13 armies), Lone Operative (+18), leaders with a squad buff (+9; every unit's Value is its solo form, so a leader never gets credit for its buff), Epic Heroes (+11). Overrated: aircraft (−26), overwatch (−14), cheapest size ≤70 pts (−6), older multi-pistol line squads (−10). Top three fixed: pooled 59.4 → 63.5 in sample (oracle), 63.0 with the moves held out, 58.3 with the search itself rerun without each army. Next: try a leader credited with its buff, an aircraft board-time discount and Lone Operative in Soak, each as a switch through tools/exam.js.

Built: ledger.js dials aircraftBoard and smallPiece, on /lab/ledger/ as "Ingredients (T-670)" and off by default; leaderCredit and loneOpSoak as code only, off; tests/unit/ledgerpage.test.js; design/ledger.md section 29. Held out on the 15 armies: aircraftBoard +0.2 ± 0.1, smallPiece +1.2 ± 1.0 (Tyranids −3.1), with attachChars +2.2 ± 1.3 (exam: 61.9% pooled, +2.5 [+0.3, +4.7]). Leaders' measured buff hurts (−0.8 at the best λ, and the existing leadersLeading and joinedMarginal −2.3 and −3.4). Lone Operative on Soak gives 0.0. Report: reports/tiers/2026-10-05-ingredients.md. Waiting on the supervisor: adopt any into Track A or B?

tools/panelstale.js → tools/panelstale.json: every panel's BSData commit at its date (git log by date, never a checkout) against the frozen 374f505; per graded unit, points at every size (10%+ flags), the datasheet by field name (patches.js fields() after BSData's bookkeeping is evened out), 10th-edition panels flagged "edition" (and whether the unit is in 11e); severity points > rules > keywords > edition. Then the five Tyranid lists' Track B pairwise and the reviewers' ceiling with and without the flagged units, against random drops of the same size. Finding: no. Gap 12.7 points (ledger 77.7%, reviewers 90.4%); dropping stale units narrows it 0.3 to 1.4 points, random drops 0.1 to 0.7: at most ~0.7 points beyond chance; 3 to 14% of the 4,457 pairs dropped. Keeping only the 11th-edition lists widens it (13.2). Two hygiene notes: patchDrop checked the smallest size only (Leapers −12.5% at 6), and Into the Hive Mind's patchDrop was read at 2 Jul though the video is 27 Jul. reports/tiers/2026-10-05-panelstale.md

tests/unit/matrix.test.js samples the pool's own profiles; at BSData 8b91e6b one cell (S6 AP-2 D3+3 into T7 3+ W5) has e 0.4167 against killDP 0.4190, a 0.55% gap, so the test fails though nothing in the matrix changed. Decide: widen the bound for variable damage into multi-wound models, fix the cell's sum, or fix the sample to a frozen pool (T-568's owner).

One tap sets every slider to a saved benchmark (tools/ledger-benchmarks/, docs/lab/ledger/benchmarks.json).

Raw lines differed by two orders of magnitude, so Presence and Actions could never matter; now Maelstrom included as a fifth list. In progress.

No bug: Warriors legal and right (Synapse lifts their whole value); Genestealers right (Hyper-Aggression wins on scarcity; the lands clamp hides Vanguard Onslaught). Fixes carded T-611 to T-614. reports/tiers/2026-10-03-kill-audit.md

Agrees with the 11th-edition Tyranid lists at 0.84 / 0.83 / 0.72.

Built: ledger.js dial modeScarcity (the army's scarcer attack mode worth more, its summed Kill kept), on /lab/ledger/ as "Army quirks (T-672)" and off by default; armyPick (Burst with an army rule's own choice taken: tools/ledger.js setArmyPick, tools/burst.js --field --army-pick, merged as burstPick) as code only, off; tests/unit/ledgerpage.test.js; design/ledger.md section 30. World Eaters 67.8%, the reviewers' ceiling 82 to 85%. One list left out: modeScarcity 0.2 +2.4 held out (with smallPiece 0.15 +4.5), the other 14 armies −0.1 ± 0.4, Tyranids +0.0. Blessings of Khorne in Burst hurt (−2.2). Leaders cut by 0.2 help the World Eaters only (+2.3 held out, others −0.2): handed to T-673. Candidate: tools/ledger-benchmarks/2026-10-05-we-modescarcity.json. Report: reports/tiers/2026-10-05-world-eaters.md. Waiting on the supervisor: adopt modeScarcity into Track A or B?

tools/crackcascade.js filters all 16.9M stored T-662 combinations (G2 + G3) with the ceiling scan's scores (letters, as tools/exam.js), no re-scoring, about a minute. Chain A: Tyranids → World Eaters → Space Marines → the rest by bootstrap SE (Dark Angels, Astra Militarum, Death Guard, Adeptus Mechanicus, Orks, Thousand Sons, Genestealer Cults, Leagues of Votann, Drukhari, Emperor's Children, Agents, Space Wolves, Blood Angels); chain B without Space Marines until last; A2 with Astra Militarum, Orks, Leagues of Votann, Emperor's Children first. 5 Oct, at 67%: A 16,886,724 → WE 3,054,652 → SM 3 → DA 0; B → WE 3,054,652 → DA 0; A2 → SM 3 → AM 3 → Orks 0. At 65%: A → WE 5,318,799 → SM 208,595 → DA 0; A2 reaches 7 steps (1,587 through Emperor's Children) then DA 0. At 70%: WE 723,060 → SM (or DA) 0. Dark Angels is the wall (no combination reaches 65% there; best 62.7%), then Thousand Sons 65.7%, Death Guard 66.2%, Space Marines 67.2%. No Tyranid-fitted code holds at 67% everywhere in this knob space. Follow-ups (yes from the user): Dark Angels without its stale grades (T-667: 30 points flags; and with rules and absent, 39) stays the wall (best any 63.0% / 63.4%, none at 65%; Track A falls to 52.1% / 50.4%); with Dark Angels last the chains stop at Death Guard instead (65%: chain B 181 through Death Guard, then Adeptus Mechanicus 0). T-670's dials (aircraftBoard 1, smallPiece 0–1, attachChars on/off) on the furthest 1,590: the most armies at 67% stays 4, the best mean over 15 60.9% → 61.4%; attachChars inert there (lifeKill on); smallPiece costs the Tyranids up to 8 points. tools/crackfollow.js; tools/crack2model.js reproduces aircraftBoard and smallPiece (1e-15). reports/tiers/2026-10-05-cascade.md.

Jordan, 5 Oct: go, the next card. The cross-army trio (aircraftBoard 1, smallPiece 0.4, attachChars) is judged together with it; measure after T-680 and T-681. T-669 found characters are the biggest cross-army miss (leaders with a squad buff underrated in 16 armies, psykers in 13, Epic Heroes in 14, Lone Operatives in 11), and T-670 found crediting a leader's measured dice buff alone makes the order worse: what reviewers value in characters isn't in our numbers yet. Build out every character across the 16 armies: what it gives the squad it leads (dice buffs from leaderfx.json, and the non-dice ones: movement, Deep Strike or Infiltrate for the squad, OC, Fights First, Battle-shock, re-rolls, command points), its own abilities and psychic powers (unitfx.json; status modelled, partly or noted, per the coverage reports in reports/tiers/<date>-<army>-coverage.md), Epic Hero rules, auras, and what it unlocks (a squad becomes worth taking, an extra activation, a key unit's best home). Each kind of rule a dial (0 = off = today), general across armies, measured with tools/exam.js held out by army (as T-670) and on Tyranids. Our own words; Wahapedia's 11th-edition pages to understand a rule, never to copy Phase 1 built (5 Oct): tools/characters.js catalogues 316 characters (tools/characters.json); fourteen character dials charLead … charHome (with charShockAmp) and cpOnce in ledger.js, on the page at 0 (design/ledger.md section 33, reports/tiers/2026-10-05-characters.md, predictions as ledger-steps step 40). Phase 2: measure each with tools/exam.js held out by army, after T-680 and T-681. Phase 2 measured (5 Oct): no kind holds out beyond noise (charEpic +0.29 ± 0.54, charAura +0.09 ± 0.12; the rest below 0); with the trio +3.2 [+0.7, +6.0] vs the trio's +2.8; nothing adopted (reports/tiers/2026-10-05-characters-measured.md). Phase 3 (what a kind does on the table) not worth it on this evidence, except perhaps Epic Heroes; charHome and charShockAmp to T-676.

Built: tools/carry.js ridersOf (each transport's riders from its army's ledger: BSData keywords, exclusions, the most models that fit; returned by build(), not written); tools/carrycargo.js, the line rebuilt from the cargo as sliders over the page's Values (rider's delivery carryRide, protection carryShield × fragility carryFrag, carryPer, carryDedOnly, carryCap, carryOnce, carryNeed, carrySquads), with leave-armies-out (3 seeds × 3 folds, 10 choose, 5 score) and exam.js's bootstrap. Why: capacity per point × the Kill weight, so a 60-pt Trukk earns +1,341 whatever it carries. Best shape (protection of fragile riders, dedicated only, capped at the rider): +1.2 pooled in-sample (SE 0.8; Drukhari +14, Emperor's Children +5.2; Tyranids −1.7, or ±0 with carryOnce 1), but chosen honestly it holds out at −0.0 ± 0.5 (strengths alone on the fixed shape +0.7 ± 0.4, leaky). Not productionised: ledger.js unchanged. Report: reports/tiers/2026-10-05-transports.md. Next: a per-army transport dial under T-676 (Drukhari want it, Orks don't)

Built: ledger.js five screen dials (screenArea board denied to arrivals, screenBlock frontage × speed, screenTrade enemy fire to remove it with a one-activation floor, screenScore a scoring slot × OC, screenHide Infiltrators/Scouts/Stealth/Lone Operative) and the screenJob switch, each a worth in points added as w × Q × P ÷ points (0 = today; a dial moves a unit from × 1.005 to × 2 its points and past); tools/screens.js; tests/unit/ledgerpage.test.js; design/ledger.md section 31. Held out (3 splits, 10 armies choose, 5 score): only screenTrade is positive, +0.15 ± 0.06 at 0.01 (exam +0.1 [−0.3, +0.7], Tyranids +0.2), on /lab/ledger/ as "Screens (T-675)", off; area −0.02, block −0.05, score −0.95, hide −1.29 stay in code at 0. World Eaters alone, one list left out: area +5.9, score +5.5, block +4.1 (Jakhals to the 76th to 93rd), but those strengths cost the pooled exam 1 to 3 and the Tyranids 2.5 to 8: cheap squads we overrate elsewhere (Wracks, Hearthkyn, Daemonettes, Cadians) rise with the ones we underrate. Candidate: tools/ledger-benchmarks/2026-10-05-screens.json. Report: reports/tiers/2026-10-05-screens.md. Waiting on the supervisor: adopt screenTrade (noise-sized), or the World Eaters' screen dials as an army-level setting?

Jordan, 5 Oct: after T-673. Note from Jordan's Tyranid notes: the Toxicrene's unwieldy model and slow speed (low priority). Order: (1) game-wide sliders whose INPUT depends on the army (context: what the army needs carried, how scarce its anti-tank or ranged Kill is, as modeScarcity, role scarcity and scarceAnswers do), until every army is at or above about 60% on the exam; (2) then army-specific sliders for each army's genuine quirks (army rule, detachment synergies, unique units such as Biovores), each fitted on that army's own lists, held out list by list where an army has 2+ lists, and pulled toward the game-wide value (army value = game-wide + a small adjustment, kept near 0 unless its lists clearly ask), so an army with one list of 20 units can't fit noise. Report per army what the army-specific layer adds on held-out lists

Built: ledger.js screenSlots (k 1 to 3: only the army's top k units by screen worth, Σ w × Q over area, block, score and trade, get the T-675 credit), screenNext (x: the next unit x of it, the one after x²) and screenRank (0 per point among units that can do actions with OC above 0 and 3+ models, 1 the worth overall); all 0 = today. Battle-shock's reference Value now leaves the screen credit out, as the screens' own did (T-675's numbers barely move). tools/screenslots.js (a fast path checked against compute() on all 16 armies). Held out (10 armies choose, 5 score, 3 splits): no structure positive (best k 3 per point +0.03 ± 0.41; structure chosen too −0.33); exam of the in-sample pick +0.6 [−0.4, +1.6], Tyranids −2.6. The slot goes to the wrong squad: Drukhari's best screen per point is the Wracks (D), Votann's the Hearthkyn (C), Death Guard's the Poxwalkers, not the Nurglings (A). Kept at 0, not on the page. World Eaters alone, one list left out: slotted +6.7 at a pooled cost of 0.5 to 0.9 (unslotted +7.2 at 1.8 to 4.9); Jakhals to the top, Flesh Hounds 28th to 83rd. Candidates: tools/ledger-benchmarks/2026-10-05-screen-slots.json, -we.json, -we0.json. Report: reports/tiers/2026-10-05-screen-slots.md. Waiting on the supervisor: the slotted dials as the World Eaters' army-level setting (T-676)?

Documentation only, nothing deleted, no tool code touched. Built 5 Oct: design/ledger-start-here.md, the front door (what it is and the north star, how to run it, where we stand in one table, every switch and dial of ledger.js checked against SWITCHES/DIALS/BASE plus the research-only sliders, the provenance timeline from 3 Oct, what we learnt, open threads in order, the working rules and a builder's brief); reports/tiers/README.md (every report by date, superseded ones marked); tools/ledger-benchmarks/README.md (every saved setting and its status); pointers from design/tier-engine.md, design/ledger.md, reports/tiers/ledger-steps.md and CLAUDE.md; statuses of T-660, T-661 (built: 🟡) and T-668 (🟡: ✅ is for Jordan's or a merge)

Built: ledger.js switch carryCargo (off) and eleven dials at 0 (carryRide, carryShield, carryFrag, carryFragRef, carryPer, carryDedOnly, carryCap, carryOnce, carryArrive, carryNeed, carrySquads; cargoOf, cargoApply): with it on and Transports above 0, a transport is worth what a ride adds to its best rider, in place of the capacity line. Riders: tools/carry.js ridersOf written to tools/carry.json riders, merged per army as meta.carryRiders by tools/ledger-merge.js (names and numbers only; all 16 armies, Tyranids and Space Marines in docs/lab/ledger/, the rest in build/ledger/). Off or at 0: every saved setting on every army is today's to the bit (30 benchmarks + the page's 11, 16 armies). Shape A (w 0.5, shield 0.4, frag 2 at 150, dedicated only, cap 1) reproduces tools/carrycargo.js unit for unit: exam pooled +1.2 [−0.1, +2.8], Drukhari +14.0, Tyranids −1.7 (tools/exam.js: a carryCargo setting keeps its own wCarry). On /lab/ledger/ as "Transports (T-674)" at 0, with the "Transports by their cargo" switch; tests/unit/ledgercargo.test.js; design/ledger.md section 32.

Built: tools/exam.js pools 14 armies; Votann's row is printed apart with its own interval (APART; --with-votann pools the 15 again and reproduces T-668 to the bit; the bootstrap draws over every army in the same order either way); tests/unit/exam.test.js pins the 14. Re-stated on the new pool (against Track A): Track B −0.0 [−2.7, +2.6] (was +0.7), B + four dials +0.1 [−3.0, +3.0] (was +0.6), the cross-army trio +2.0 [−0.3, +4.3] (was +2.5 [+0.3, +4.7]); Track A 59.4 either way. reports/tiers/2026-10-05-exam14.md; ledger-steps row exam14, decisions.md, the front door. Its two panels are 10th-edition reference lists that design/decisions.md (3 Oct) set as never scored. Moves no ledger value, only the yardstick

Track A's scarcity and soakfx fall back on Space Marines because their per-army files were never built. Build them with the existing tools (scarcity.js, soakfx.js), re-freeze (node tools/ledger-inputs.js --freeze <commit>, T-603) and report it as a new snapshot: Space Marines' lists and exam before and after, Tyranids unchanged to the bit. After T-680. Built (5 Oct): tools/scarcity-space-marines.json, tools/soakfx-rules-space-marines.json and tools/soakfx-space-marines.json, merged into docs/lab/ledger/space-marines.json. No re-freeze needed: the files are the ledger's own live files (tools/ledger-inputs.js LIVE), so the snapshot stays eb3590a (BSData 374f505, 30f0056e6103), pre-dataslate. Found: predicted Space Marines +1 to +3; got scarcity −4.2 [−9.1, +0.7] on their exam row (64.5 → 60.3), Soak effects 0, Tyranids unchanged to the bit; pooled A 59.4 → 59.1, B 59.2. Scarcity, fitted on the Tyranids, hurts out of sample; whether it stays on in Track A is open. reports/tiers/2026-10-05-refreeze-sm.md; ledger-steps step 42

A game-wide dial blending each unit's best form with its typical form (smallest squad, datasheet wargear, its army's middle detachment; no tournament popularity), with sub-dials for size and detachment. Preview tool first; measured after T-682. Phase 1 built (5 Oct): tools/typical.js, typicalSize/typicalDet (typicalW), 0 = today to the bit; sanity print and predictions in reports/tiers/2026-10-05-typical.md; the exam needs a post hook in exam.js (described there). Phase 2: measure after T-673 Jordan, 5 Oct: the size half is tried three game-wide ways, chosen held out: best size (today), the average over all legal sizes, the smallest; no per-unit size and no popularity Phase 2 measured (5 Oct): typicalSizeRule (smallest, mean, best) built in tools/typical.js, with a span placebo. Only the size half helps, read as the mean of a unit's sizes: held out +0.26 ± 0.35 (placebo −0.02), rule chosen too +0.23 ± 0.32 (placebo −0.38); exam at mean 0.25 +0.4 [−0.3, +1.2]; smallest −1.61, detachment half −0.38. For the cascade: typicalSize 0, 0.25, 0.5 at rule mean, typicalDet 0. reports/tiers/2026-10-05-previews-measured.md

A game-wide dial: a unit loses worth to a same-army rival that does the same job better per point, scaled by how alike they are (what their damage lands on, shooting or melee, unit type, speed; an overlap 0 to 1, no hand labels) and by how much better the rival is; the better unit untouched. Preview tool first, no ledger.js change; a placebo with scrambled rivals beside it; measured after T-673, first of the three Phase 1 built (5 Oct): tools/rivals.js, a preview (no ledger file changed): likeness = kill² × mode × type × speed^½ (target tilt, ranged share, body/Character/Fly, Move), the dial rivalW with gap capped at twice as good per point, a scrambled-likeness placebo, scoreArmy/scorePool scoring as the exam does (rivalW 0 = the exam to the bit); tests/unit/rivals.test.js; design/ledger.md section 34; reports/tiers/2026-10-05-rivals.md; predictions as ledger-steps step 41. Phase 2: measure a rivalW sweep with its placebos through the exam, held out by army, after T-673 (exam.js needs a small hook, section 34). Phase 2 measured (5 Oct): not kept. Held out −0.73 ± 0.73, placebo +0.00; exam at 0.5 −0.3 [−1.6, +1.1]; Tyranids −0.5 at 0.5. Each army's top rival pairs printed for Jordan in reports/tiers/2026-10-05-previews-measured.md (tools/previews.js). Hand pairs from Jordan, if any, are scored next.

Jailing: turn-one reach into the enemy deployment zone (move and pre-game moves), width strung out, cheapness. Objective steal: arrives from reserve, moves after shooting, OC enough to take an enemy objective, priced as the primary VP denied in army points. Each a game-wide dial; rules from Wahapedia's 11th-edition pages in our own words; may prove army-specific (then T-676). Preview tool first; measured after T-683. Phase 1 built (5 Oct): tools/steal.js previews jailW and stealW (0 = today to the bit, tests/unit/steal.test.js), placebos and exam-style scoring; the steal qualifies 5 datasheets in 16 armies (Gargoyles, Eliminators, Land Speeder, Pteraxii Skystalkers, Scourges with heavy weapons), Gargoyles 46th → 37th at steal 0.5, Tyranid lists 79.3 → 79.9 (placebo 79.0); jailing barely exists under the 9" coherency rule. reports/tiers/2026-10-05-steal.md, design/ledger.md section 34. Next: measure after T-673 (needs exam.js's post-compute hook or the dials in ledger.js) Phase 2 measured (5 Oct): neither is a game-wide dial. jailW held out −0.00 ± 0.01; stealW held out +0.00 (every fold picks 0), 1/15 armies better, Tyranids +0.5 at 0.5 (placebo +0.1): a Tyranid matter for T-676. reports/tiers/2026-10-05-previews-measured.md

Built 5 Oct (local commit, not pushed): tools/exam.js scores a setting through an optional post: { module, args } (or --post tools/<x>.js --post-args k=v, which adds the first setting again through it): the module's post(D, run, sliders, args) → run rewrites unit values after compute(), the exam re-sorts on them, then pair tables, the shape() check and the paired bootstrap. tools/rivals.js, tools/typical.js and tools/steal.js each export a thin post (their own adjust names were taken, so the hook is post). No number moves: every committed benchmark through exam.js gives today's output to the character; each preview at 0 is Track A to the bit; at 0.5 each matches its own scorer to the bit (smoke test, pooled 14: rivalW 0.5 −0.4 [−1.6, +0.9], typicalW 0.5 +0.1 [−1.3, +1.4], stealW 0.5 −0.1 [−0.3, +0.1]). Measuring each preview is its own card. tests/unit/exam.test.js covers the hook.

Two tests pinned numbers made before T-681 built the Marines' scarcity and Soak-effects files (the step-6 baseline fingerprint; the 3 Oct report's Tista Minis ρ 0.0477). tests/unit/ledger-before-t681.js reads docs/lab/ledger/space-marines.json at e678d9ed81 (git show, sha256 checked; a shallow clone fetches it); ledgerpage and ledgercheck use it, tools/ledgercheck.js run() takes opts.data. Fixture hashes and the report unchanged. Waiting: CI on a shallow checkout

A deliberate re-freeze (T-603): the ledger takes every improvement to our own code and rules files since eb3590a (T-582's full keyword reading in docs/ev.js, effects-file corrections, the BSData reader) but keeps the datasheets, points and panels of BSData 374f505 (before the 30 Sep update the reviewers graded). Each drifted input classed as our improvement (take) or the new data (keep old), build/units.json rebuilt from 374f505 with today's code; Track A, B and the trio re-scored on the new snapshot (Tyranids, exam), old snapshot kept so every past number reproduces. Before T-673 phase 2 measures Built (5 Oct): snapshot 8eb69bc7af with the data kept as at eb3590a, inputs hash a20dbd2c3316 (old lock kept, LEDGER_INPUTS_LOCK); Drukhari on their nine; Track A Tyranids 79.3 → 79.1, exam 59.1 → 59.0; reports/tiers/2026-10-05-refreeze-engine.md.

Built 4 Oct, on the branch (not on beta: no beta push for now): docs/bestmatch.js, a 🎯 Best matchup menu beside the attacker's list chip: Into <defender>, then vs Hordes, Infantry, Elites, Monsters, Vehicles, Heavy vehicles (stand-in targets under a pseudo-army, the rankings' five plus a monster T10 Sv2+ W12). It searches the squad's legal wargear (Loadout.solve against the target, in the mode played), the leader and support characters (Legends left out) and their wargear, the army's detachments greedily up to 3 DP (the player's own kept where nothing beats them) and every rule option (detachments', characters', the unit's own), scored by the calculator's dice engine on common seeded rolls (600 trials; wounds taken off the target, overkill not counted). Keeps size, mode and situational switches. app.js: recompute's volley building is now attackPlan(), shared. Under a second on a phone-class search. Round 2 (4 Oct): (1) bsdata.js reads which chapter a detachment is for (BSData hides it unless the main catalogue is that chapter's) into detachments.json only; 37 Space Marine detachments are a chapter's and 9 of the Aeldari's are the Drukhari's; Best matchup offers only what the army may take (the Detachment picker is unchanged). (2) Conditional effects (taken on trust: after charging, when Battle-shocked, vs the Oath target) count half in the search, so it no longer chose Rage-Cursed Onslaught for its "+1 A when Battle-shocked". (3) Fixed in the calculator: a joined character's gun read as melee in detInPlay (it isn't on its squad's datasheet) and took melee-only effects (a Judiciar's bolt pistol got +1 A after charging). (4) A character joins once. (5) The menu rises over the swap button on a phone. Round 3 (Jordan, 4 Oct: "hide other chapters' detachments in the picker too"): app.js detPickable/detLegal: the Detachment part, a list's and Army vs Army's pickers offer only what the army may take (Space Marines 16 of 53; Blood Angels their own and the Codex ones); a saved or linked one of another chapter no longer applies (detsOf, fitDets); findDetachment still knows them all for imported lists. Not changed: unit pages' best detachment (tools/build_rankings.js, a scoring change). tests/browser/bestmatch.test.js; screenshots desktop and 390px, light and dark. Open: the defender has no Best matchup; a leader's squad-wide manual buffs are the calculator's as before.

Per unit, our letters across its legal squad sizes (each size at its best detachment, the army cut as today); a reviewer's letter inside that span scores 1 ÷ the number of letters spanned, outside 0. Reported beside the strict pairwise score in tools/exam.js and the Tyranid headline, per army and pooled, with intervals; a placebo (spans of the same widths placed at random) beside it. Changes no ledger value; dials must hold on both yardsticks

Built 4 Oct, on the branch (not on beta: no beta push for now): docs/bestmatch.js, a 🎯 Best matchup menu beside the attacker's list chip: Into <defender>, then vs Hordes, Infantry, Elites, Monsters, Vehicles, Heavy vehicles (stand-in targets under a pseudo-army, the rankings' five plus a monster T10 Sv2+ W12). It searches the squad's legal wargear (Loadout.solve against the target, in the mode played), the leader and support characters (Legends left out) and their wargear, the army's detachments greedily up to 3 DP (the player's own kept where nothing beats them) and every rule option (detachments', characters', the unit's own), scored by the calculator's dice engine on common seeded rolls (600 trials; wounds taken off the target, overkill not counted). Keeps size, mode and situational switches. app.js: recompute's volley building is now attackPlan(), shared. Under a second on a phone-class search. Open: (1) BSData files chapter detachments (Rage-Cursed Onslaught, Unforgiven Task Force…) under Space Marines, so a plain Marine squad can be given another chapter's detachment, as the Detachment picker already allows; needs a chapter tag on detachments.json. (2) Check one result that looked high: Intercessors + Judiciar + Ferren Areios in Rage-Cursed Onslaught into five Terminators at 14.3 of 15 wounds. (3) A browser test; screenshots at 390px and desktop, both themes; the defender side has no Best matchup yet.

Per unit, our letters across its legal squad sizes (each size at its best detachment, the army cut as today); a reviewer's letter inside that span scores 1 ÷ the number of letters spanned, outside 0. Reported beside the strict pairwise score in tools/exam.js and the Tyranid headline, per army and pooled, with intervals; a placebo (spans of the same widths placed at random) beside it. Changes no ledger value; dials must hold on both yardsticks. Built 5 Oct (local commit): tools/spanmatch.js and tools/exam.js --span (byte-identical without it). Pooled 14 armies span / strict / placebo: A 25.2 / 25.2 / 18.9, B 26.5 / 26.8 / 19.2, trio 26.1 / 26.3 / 19.3; Tyranids 36.5 / 36.7 / 22.3 (A). Span equals strict (−0.1 [−1.4, +1.1] pooled on A): one graded unit in seven has a span. reports/tiers/2026-10-05-spanmatch.md

One yardstick step, no ledger value moves: the Tyranid headline scores the three 11th-edition transcripts (Auspex, Hivemind, Into the Hive Mind), with the five-list number beside it (Maelstrom and Astrategas are 10th edition, March and April 2026); every army's panels marked 11e or 10e by date (11th edition from June 2026); Leagues of Votann rejoin the exam's pool on Jordan's 11th-edition Auspex list (29 Aug), its 10th-edition lists beside. Benchmarks re-stated on both; tools/exam.js, ledgerstep.js and the front door follow. After T-687's rebuild. Built 5 Oct (waits for review): tools/edition.js; Tyranid headline on the three (A 82.4, five 79.1); the exam pools 15 on 11e lists (A 59.1, trio 61.9, +2.8 [+0.4, +5.4]; without Votann +2.0 [−0.4, +4.3]); APART removed; reports/tiers/2026-10-05-headline11e.md

No rebuild. Per army of the 16: which detachments the ledger builds forms for (against detachments.json, the matched-play list and chapter legality), and for each detachment its rules, enhancements and stratagems as dice, partly or noted; then two or three detachments per army hand-checked: a unit's Kill in that detachment worked by hand from our effects data and compared with the ledger's form. A one-page table per army; every mismatch a line with its cause. Found already: Drukhari built with no detachment (detfx key under Aeldari) and Genestealer Cults missing Infestation Swarm, both folded into T-687. Built (5 Oct): tools/detaudit.js, reports/tiers/2026-10-05-detachment-audit.md: 15 of 16 load every matched-play detachment (Drukhari none; Infestation Swarm is Boarding Actions, rightly out); 40 hand checks reproduce the ledger exactly, 35 read the rule right; rolls, ladders and once-a-battle picks kept all game (Emperor's Children, Space Wolves, Ordo Xenos, Orks), Wrath of Khorne on Epic Heroes, checkable conditions written as vouched; a ×1.065 on every unit for noted rules picks the winner in seven armies; no enhancements or stratagems. Waiting on the supervisor: which fixes go into T-687

Each army's army rule as dice where our data can say it (armyfx.json; 0% dice in 11 of 16 armies today), and the units that switch it on or carry it credited the way Synapse carriers are: order-givers (Astra Militarum), Cabal psykers (Thousand Sons), Pain (Drukhari), Waaagh! (Orks), Contagion (Death Guard), Cult Ambush (Genestealer Cults), Blessings of Khorne (World Eaters, T-672's armyPick) and the rest. Game-wide dials at 0, a placebo beside each, measured held out by army; likely where much of a character's worth runs (T-673). Our own words; after T-687's rebuild. Phase 1 built (5 Oct): tools/armyrules.js catalogues each army rule of the 16 armies, its shape, its enablers with the reviewers' misses and a plan (tools/armyrules.json; reports/tiers/2026-10-05-army-rules.md; design/ledger.md section 38). Found: the ledger applies no army-rule dice in any army (Oath of Moment never reached the Marine ledgers); enablers the reviewers rate above us (Cabal casters +29, officers +13, Ork bosses +11). tools/armyrules-draft.json: four armyfx.json entries, to merge after T-694. Phase 2: build and measure the eight dials (armyMarks, armyRounds, armyStates, armyAura, armyEnabler, armyOrders, armySpawn, armyMove) one at a time after T-687, predictions in the report. Phase 2 built and measured (5 Oct): the four armyfx.json corrections merged and the ledger re-frozen (d8b5a1bb14, data at eb3590a, hash c5e7d85b43f8; Death Guard 53.4 → 54.6, nothing else moves). Five dials in ledger.js, all 0 (armyMarks, armyRounds, armyStates as Burst variants from tools/armyburst.js; armyEnabler, armyOrders as credits), measured by tools/armymeasure.js. armyEnabler is the one above its placebo (+0.3 pooled; Thousand Sons +4.9); armyOrders is small (+0.1); the other three stay at 0. armyAura, armySpawn and armyMove were not built. reports/tiers/2026-10-05-army-rules-measured.md. Waiting: the cascade decides on armyEnabler (and armyOrders).

soakfx-rules files as Tyranids and Space Marines have them (T-599, T-681), built with tools/soakfx.js from our effects data; today their soakfx files are empty. Expected gain small (Space Marines: 0 in T-681). Ledger-own files, no re-freeze; after T-687

On the rebuilt snapshot: vary the uncertain pieces of Kill within plausible ranges (melee landing scale, target-choice sharpness β, the enemy field's class mix) and report how far each unit's rank moves; steady units solid, swinging units flagged "uncertain" (for T-697's pages). Fix the burst stage switching between ranged and melee that gives Mephiston 4× in one detachment (T-690 audit; 9 cases), as a correction measured before and after. Measured alongside the other cards after T-691. Built (5 Oct, snapshot c5e7d85b43f8): the mode is chosen by Burst (step 45: Mephiston 4.0× → 1.14×, Tyranids 82.4 unchanged, exam 59.2 → 59.4); tools/killrobust.js, 41% of 733 units uncertain (Tyranids 13%), lands the main driver; reports/tiers/2026-10-05-kill-robustness.md and .json

(1) Choices that are really rolls, ladders or once-a-battle picks (Coterie of the Conceited, Saga of the Great Wolf, Ordo Xenos Mission Tactics, Madcap Meks, Dread Mob, Khorne Daemonkin) get a tag the ledger reads and count at a share of the game, not their best case; the calculator still lets a player pick. (2) A noted (non-dice) detachment rule's multiplier reaches only the units the rule names. (3) ledger.js detRulesOf reads choice options' unit keywords (Idols of Khorne). (4) Data: Wrath of Khorne excludes Epic Heroes; Born Soldiers' and two Drukhari rules' target-keyword conditions, Dark Age Arsenal by weapon, the three S-above-T rules by sVsT, Blood Tithe's Feel No Pain written checkable. Our own words; the ledger's frozen detfx is the pre-dataslate one plus these corrections Built (5 Oct): 8eb69bc7af (data, ledger mixing, scoping, notTargetKw/notUnitKw); in the ledger through T-687's re-freeze; not stamped (pending).

A switch the cascade searches: rank each army by Value per 100 points (today) or by a unit's total worth in a list (Value × points ÷ 100), and blends between. Front door open question 10: total worth lifted 14 armies +1.5 and cost Tyranids −2.9 (4 Oct). Searched in the cascade from World Eaters on

Add tournament list share (tools/popularity.js, T-693, grimstat-corpus CC BY 4.0, 11th edition only) to Track A's Value as an experiment and measure agreement per army and pooled, held out, with a scrambled control. If agreement leaps toward the reviewers' ceiling, the gap is what players take rather than our maths; if not, something structural is off. Popularity never enters a published letter. Measured 5 Oct (tools/popshare.js, the exam's post hook): Value × (1 + p × z) held out +12.5 ± 3.2 (scrambled +0.6); exam at p 2 59.1 → 72.2, +13.1 [+8.9, +17.2], 14/15 armies; popularity with Track A breaking ties 73.0; World Eaters 83.2 (reviewers 82–85), Space Marines 80.0 (91). The gap is mostly what players take. reports/tiers/2026-10-05-is-the-maths-wrong.md

Every knob free (rung (c)'s per-feature slopes, T-662) fitted on World Eaters' three 11e lists, and the same fit on scrambled letters (several seeds), and on the other lists held out (fit on two lists, score the third): how high it goes, and how much of that memorising produces. A report. Measured 5 Oct (tools/wefit.js, 136 knobs): 67.5 → 94.3 in sample, scrambled letters 94.3 too (5 seeds); held-out list 85.5 (the other two reviewers' consensus 89.3); held-out units 64.4 against Track A's 67.3. All memorising. reports/tiers/2026-10-05-is-the-maths-wrong.md

For every army: the units players take far more than our Value says, and the ones we rate high that nobody takes (11th-edition list share, tools/popularity.js, T-693; grimstat-corpus CC BY 4.0), each with what its lines credit and a short guess at the missing ingredient, grouped into kinds that recur across armies. A report; popularity never enters a letter. Built 5 Oct (tools/poppointer.js; reports/tiers/2026-10-05-popularity-pointer.md and .json): 15 armies (Agents skipped, 1 list), 6 underrated and 6 overrated each on Track A. Underrated units take 20% of Value from non-Kill lines, overrated 9%. Kinds by armies (lift over the base rate): like-job rival 15 (×1.24), Deep Strike 13 (×1.26), leader 11 (×2.1), fitted multiplier 11 (×1.35), durable 11 (×0.81), enabler 10, forward deploy 10 (×1.6), transport 9; sibling datasheet 6 (×3.1). Every kind but indirect fire has a dial, and the dials measured close to nothing game-wide. Jordan's Tyranid notes: Gargoyles, Winged Hive Tyrant and ranged Warriors found alone (with the rivals he named); Leapers, Carnifexes and Toxicrene not

From the full 11th-edition transcripts (Tyranids' three, and any other full ones), each graded unit's stated reasons as short tags in our own words (screen, scorer, unlocks a squad, durable, delivery, damage into X, overcosted, competing sibling, army-rule engine), never quoting; per unit and per reviewer; then which tags go with which letters. Feeds T-704's variables. Built 5 Oct (tools/reasons.js; reports/tiers/2026-10-05-reasons.md and .json): 27 tags (positive, negative, context), each stated or inferred, from our why notes, the older panels' tags and the source tables' tier names and notes (no transcript opened, no text copied); 24 11e panels, 928 graded units, 290 tagged. The Tyranid transcripts were read for grades, not reasons: 22 of 156 units give anything taggable, one a role reason. Stated tags (883 units): leader-unlock +1.0 letter, sibling-better −0.6, overcosted −0.26, detachment-dependent level. Gaps with no dial: situational, copies, unreliable dice, indirect fire. Jordan's six: only the Carnifexes have a stated reason (one, led by Old One Eye); the letters put his named rivals higher. Next: reasons written into the panels' why in our own words, unit by unit from the transcripts (Tyranids first), then a re-run; that needs the transcripts in hand (Jordan)

One model on all 16 armies (about 730 units): about 25 variables a player recognises (Kill by target class, Soak, OC, speed, Deep Strike, forward deploy, Lone Operative or Stealth, unlocks a squad, army-rule enabler, Synapse, transport, points, and the like), each army a shrunken adjustment, fitted on reviewers' consensus letters (ordinal), tested on whole armies held out; output: each variable's value relative to Kill with uncertainty, and where armies differ. Second target, discovery only: 11th-edition list share (never in a letter). Built 5 Oct, version 1 (tools/readable.js; reports/tiers/2026-10-05-readable-model.md and .json): 595 graded units, 9,354 consensus pairs, pairwise logistic with army deviations shrunk by cross-validation; the variables are a swappable table for T-707's list (version 2). Held out by army 60.1% against Track A 61.9 (15 without Tyranids 59.5 against 60.1), Kill alone 58.7, scrambled 50.7 (20 seeds); beside Track A +0.2. Relative to Kill: Epic Hero 0.8, OC per point 0.8, Psyker 0.7, Deep Strike 0.6, Move 0.6, enabler 0.5, points 0.4, Fly −1.0; placebo 0.16 [−0.30, +0.74]. Players weigh OC per point about 3× reviewers. Nothing adopted. Version 2, 5 Oct (tools/readable.js, --v1 keeps version 1; reports/tiers/2026-10-05-readable-model-v2.md and .json): design/jobs.md's priorities 1 to 25 (all built; the five partly ones as small proxies), unlocks a squad as its own column, slot competition among siblings, five interactions and seven saturation ranks, 42 columns. Held out by army 59.8 against version 1's 60.1 and Track A's 61.9; scrambled 50.2; interactions and saturation add nothing held out; version 1's Epic Hero and Psyker added back give 61.9 (61.1 against 60.1 without the Tyranids): jobs.md lacks a named-centrepiece variable. Reviewers: anti-tank, anti-elite, reserves, enablers, Hidden, CP up; Fly and the army's cheapest bodies and action-doers down; the leader package +0.01. List share (grimstat-corpus, CC BY 4.0): version 2 61.2 against version 1's 58.6, players take the squads leaders lift (+0.10). Nothing adopted

From the full 11th-edition transcripts (Tyranids' three, and any other full ones), each graded unit's stated reasons as short tags in our own words (screen, scorer, unlocks a squad, durable, delivery, damage into X, overcosted, competing sibling, army-rule engine), never quoting; per unit and per reviewer; then which tags go with which letters. Feeds T-704's variables

design/jobs.md: per variable, what players mean (plain words), why it matters in 11th-edition missions, a measurement recipe from our data (ledger lines, unitfx/leaderfx/armyfx kinds, the charge model, mission notes), the data missing, and confidence; built on the existing jobs work (T-524, T-537, T-626), mission and rules notes, the popularity pointer (T-703) and reasons tags (T-705). Community understanding in our own words only. Feeds T-704's variables (version 2) Written 5 Oct (design/jobs.md; summary reports/tiers/2026-10-05-jobs.md): 30 variables in six groups, each with what players mean, why 11e missions pay for it, a recipe naming our fields (ledger form fields, effects kinds, build/units.json, the charge model, mission notes, deployments.json), what is missing, confidence and the existing dial. Priority list for T-704: 1–25 (20 buildable today, 5 need a small field or script), 26–30 wait for terrain, variance or a moving opponent. Hard ones with proxies: screening per unit (the 9" coherency cap makes the 8" arrival bubble about 345 sq in whatever the size), zoning and tarpits, unlocking a squad (the joined synergy as its own column), army-rule engines (marginal coverage, as synapseAdd), hiding, reliability. T-705 tags mapped to the variable keys

A leader is worth what it adds to the squads worth leading, over the best alternative leader for that squad (the Kâhl on Hearthguard leaves Grimnyr, the Iron-master and the Champion without a squad worth leading; the same for Space Marines' Phobos and Reiver Captains and Lieutenants). Sharpens leader-unlocks-a-squad. A game-wide dial at 0 as an exam post step, measured held out with a placebo; the wall units (reports/tiers/2026-10-05-solution-cascade-walls.md) reported. Built 5 Oct (tools/leadercomp.js): doesn't hold out (every fold picks 0; pooled −0.6 to −2.0, no better than its placebo); the engine's synergy picks the reviewers' preferred leader less often than chance, so the leader effects need an audit first; nothing adopted (reports/tiers/2026-10-05-leadercomp.md)

A leader is worth what it adds to the squads worth leading, over the best alternative leader for that squad (the Kâhl on Hearthguard leaves Grimnyr, the Iron-master and the Champion without a squad worth leading; the same for Space Marines' Phobos and Reiver Captains and Lieutenants). Sharpens leader-unlocks-a-squad. A game-wide dial at 0 as an exam post step, measured held out with a placebo; the wall units (reports/tiers/2026-10-05-solution-cascade-walls.md) reported

Its own guns and toughness plus the delivery of riders that are slow, valuable and have no other carrier (the Hekaton for Votann's exosuit infantry); who may ride what from tools/transports.js. Sharpens transports per army. A game-wide dial at 0, held out, placebo, wall units. Built 5 Oct (tools/exclusivecarry.js, an exam post step; reports/tiers/2026-10-05-exclusivecarry.md and .json): not above its placebo game-wide (held out +1.33 ± 1.80 against +0.54; exam at 0.5 +0.7 [−0.4, +2.0] against +0.9; 5 armies better, 7 worse). Hekaton 10th → 5th and Sagitaur 14th → 4th of 22 (Votann +10.5, placebo +7.6); Drukhari +4.3, Emperor's Children +2.6; Agents −2.2, Orks −1.5, Tyranids −0.5 (Tyrannocyte 48th → 23rd). Nothing adopted; an army-specific candidate for the next cascade at 0, 0.5 and 1

Its own guns and toughness plus the delivery of riders that are slow, valuable and have no other carrier (the Hekaton for Votann's exosuit infantry); who may ride what from tools/transports.js. Sharpens transports per army. A game-wide dial at 0, held out, placebo, wall units

How many scoring units a unit (or its transport) puts on objectives: squad splitting (a Sagitaur splits ten Hearthkyn into two fives, one at home, one to the expansion), objectives kept after leaving; beyond OC per point. A game-wide dial at 0, held out, placebo. Built 5 Oct (tools/objpresence.js; reports/tiers/2026-10-05-objpresence.md): not a game-wide dial (held out +0.00, every fold picks 0; placebo −0.46; pooled −0.2 at 0.5); splitting and stickiness only, with the split's gain on its transport too, holds out +0.61 (placebo −0.06) on Votann's one list (Sagitaur 14th → 7th): an army-specific cascade axis at 0, 0.5, 1, and a lead for T-710

How many scoring units a unit (or its transport) puts on objectives: squad splitting (a Sagitaur splits ten Hearthkyn into two fives, one at home, one to the expansion), objectives kept after leaving; beyond OC per point. A game-wide dial at 0, held out, placebo

Burst delivered by Deep Strike, Rapid Ingress, strategic reserves or a transport after the enemy has moved (Thunderkyn, Hearthguard) counts more than Burst that must walk into range; the sharper version of arrivalKill. A game-wide dial at 0, held out, placebo. Built and measured (5 Oct), nothing adopted: tools/surefire.js (post step, dial sureFire); held out +2.7 ± 0.6 (placebo 0; without strategic reserves +3.5), Tyranids +0.2 at 0.5; moves melee walkers down more than Thunderkyn and Hearthguard up. For the next cascade at 0.25 and 0.5. reports/tiers/2026-10-05-surefire.md

Done as a pilot (steps 44 and 44b, nothing adopted): the catalogue tools/stratfx/<army>.json and core.json (every detachment by slug, each dice stratagem as engine effects in our words, no names), tools/stratuplift.js (each unit's Burst or Soak with one use added, the ledger's own dice and field), tools/stratagems.js (10 CP a game spent by points per CP on a typical list by Value; credits; the post step; the cross-army fit). Points per CP at the margin by detachment: Tyranids 0 to 26, Votann 6 to 22; the Swarmlord's 4 CP buy +106 points a game in synaptic-nexus, +9 in subterranean-assault where the ledger ranks it. Face value: Tyranids −0.1, Votann +9.5 to +12.4 (one list; placebo credits +4.7 to +7.2); the cross-test fails its rule. Report reports/tiers/2026-10-06-stratagem-pilot.md. Rollout: T-742

T-709 judged leaders by what our engine says each adds to a squad, and that number looks wrong: the Apothecary's healing measures up to 6,113 per 100 points and wins ten squads; on Hearthguard Ûthar measures 2,730 against the Kâhl's 1,594; in 129 squad cases where reviewers separate the candidate leaders, our best leader holds the best letter 30% of the time (random 37%). A report like T-690: per army, hand-check two or three leaders' joined forms against leaderfx.json and the dice engine (heal, re-rolls, Lethal or Sustained, Feel No Pain, Deep Strike for the squad), find the cause (data, heal pricing, stacking), list the fixes. No rebuild until Jordan approves the fixes; then T-709 is re-tested. 5 Oct (the builder): the dice are right, the pricing is wrong: a leader's own command-point, healing and Synapse multipliers scale the whole squad (57% of the measured synergy), Kill is read on two scales (Burst alone, both phases joined; 27%), Support characters compete with Leaders, joining effects are divided by the leader's points; eight fixes proposed, none applied. reports/tiers/2026-10-05-leader-audit.md

Each unit a vector of measured job scores per point from design/jobs.md's buildable recipes; a unit loses its slot to a same-army unit at least as good per point on every job it is good at (Pareto dominance; multi-role units escape it); archetypes found by archetypal analysis on all armies' profiles (each unit a mix of pure types), the future role labels; rival pairs checked against list co-occurrence (tools/colist.js: substitutes rarely share a list) and Jordan's notes. Replaces T-682's likeness matching; a post step at 0, scored on Tyranids, Votann, Thousand Sons, then all

Each unit a vector of measured job scores per point from design/jobs.md's buildable recipes; a unit loses its slot to a same-army unit at least as good per point on every job it is good at (Pareto dominance; multi-role units escape it); archetypes found by archetypal analysis on all armies' profiles (each unit a mix of pure types), the future role labels; rival pairs checked against list co-occurrence (tools/colist.js: substitutes rarely share a list) and Jordan's notes. Replaces T-682's likeness matching; a post step at 0, scored on Tyranids, Votann, Thousand Sons, then all

(1) How much of its army's bonus package a unit can receive: the army rule, the detachments winning lists run and the army's auras, by the keywords each needs (PSYCHIC attacks, PSYKER, INFANTRY, the army keyword) — Rubrics and Scarab Occult collect them, generic engines don't; (2) casters credited for making the hard rituals succeed (Magnus +2 and two attempts, Ahriman +1) rather than for filling one of four slots. Post steps at 0, scored on Thousand Sons first, then all, with placebos Built 5 Oct (tools/bonusshare.js, an exam post step; reports/tiers/2026-10-05-bonusshare.md): neither dial holds out (bonusShare held out −1.22, pooled −1.2 at 1, placebo −2.0; bonusCaster ±0.0); Thousand Sons alone gains from the share (38.2 → 46.6 at 1, placebo 39.5), by pushing down units that receive nothing rather than lifting the Psychic infantry. Nothing adopted

From reports/tiers/2026-10-05-leader-audit.md: (1) a leader's army-wide multipliers act on its own share only; (2) one Kill scale for solo and joined forms; (3) Support characters as Support, beside a Leader; (4) healing scoped and counted once; (5) Lone Operative on a joined form only when every member has it; (6) the leader's dice gain priced apart from joining; (7) the missing grants (Deep Strike from Teleport Crest, the Judiciar's Fights First, +1 OC banners), pre-dataslate sense; (8) alone at the joined form's loadout. Data fixes need a re-freeze (approved with the fixes). Then rebuild, report Track A before and after, re-test T-709 and every leader toggle, and feed the next cascade. Built (5 Oct): all eight applied, re-frozen at 8dcd24032d (hash dcd477d8a78c), every ledger rebuilt; Track A 59.37 → 59.32 (Tyranids 82.45 → 81.61); leader check 25.8% → 50.9% by role on the dice lent (chance 38.7%); T-709 penalty half holds out +0.58 (placebo 0); no leader toggle holds. reports/tiers/2026-10-05-leader-fixes.md

T-716's 7 archetypes miss them because the 20 jobs describe what a unit does, not how: add melee-or-shooting share, speed, body type, engagement range, a cost band and a rough board position; run clustering (dense groups, about 10–14) beside archetypal analysis (extremes); durability also compared across armies, not only within; Jordan's groups as the test set (Genestealers, Leapers, melee Warriors, Necron Wraiths together; Haruspex and melee Steeljacks; Barbgaunts, Termagants, ranged Warriors and shooting Steeljacks; Maleceptor and Dreadnoughts). Built 5 Oct: tools/clusters.js, 16 groups; two of Jordan's four types emerge; the groups are kinds, not slots (reports/tiers/2026-10-05-clusters.md)

Burst values a form's activation in its one natural mode (tools/burst.js), so a unit that shoots then charges gets only the larger phase: Tyranid Warriors with Ranged Bio-Weapons measure about 97 ranged Kill a turn at β 6 but rank on melee Burst alone. Measure how many forms lose a large second phase, and test a two-phase Burst (shooting then fighting in one turn, the second phase against what the first left) as a correction, before and after on every army

Why: the 5 Oct weekly report (reports/analytics/2026-10-05.md): 13,285 impressions in 7 days at position 8.7 but a 1.0% click rate; /best/anti-tank/ 115 impressions, 3 clicks; the home page alone earns 14%. Searches are "<unit> 11th edition", "<unit> datasheet", "<unit> points", "best <army> detachment", "<unit> loadout". What reads badly today (tools/build_pages.js): unit titles are a keyword list ("Killa Kans 11th Edition: Points, Tier, Damage"); descriptions pack shorthand Google shows raw ("A tier, 13th of 58 Orks units; best detachment Dread Mob (+56%)", "Best loadout: 1 × Siege cannon"); filler at the end ("Free, no sign-up."); army descriptions cut off mid-name ("Top pick: Ironkin Steeljacks with Melee…"); /best/ pages name surprising leaders without context ("Cthonian Beserks… lead the game" for anti-tank). Do: (1) a gallery first (an Artifact, before and after as Google would show them: title ≤ 60 characters, description ≤ 155, desktop and phone) for each page kind: home, army, unit (with and without a loadout choice), detachment, /best/, /meta/, /meta/patch/, /hill/; Jordan picks; (2) then build_pages.js writes them: plain sentences, the searcher's words first (the unit's name, "11th edition", points), one clear number at most, nothing cut mid-word (trim at a word and drop a list item rather than end on "…"), no filler; (3) never promise what we don't host: no "datasheet" in a title (no GW rules text on our pages); (4) the weekly report gains a CTR-by-page-kind line so we see whether it worked (measure 2 to 4 weeks after, Search Console runs 3 days behind). Our words only. Static pages only: the app's own title (index.html) stays unless Jordan picks a change in the gallery.

T-723 reads BSData's "cannot have both" errors per model; most of the 20 are squad-wide (Thunderkyn, Yaegirs, Cthonian Beserks, Lychguard, Immortals' gauss/tesla, Aggressors, Space Wolves and Vanguard Veterans' kits; Grey Knights' at most 2 heavy weapons; Blood Angels' one pistol swap; Recon Troopers), and loadout.js's squads can still mix them across models. Do: read those shapes from BSData (the error rules' conditions: atLeast/greaterThan on entries with scope the unit) into a squad-level rule (same kit for every model of a kind, or a count across kinds), enforce it in Loadout.squads and the Weapons sheet, test on each named unit. The other ~220 error rules (squad size and "1 per N models") are checked against limitAt (design/wargear-limits.md) in the same pass; list any it misses.

Built 5 Oct: tools/dialinventory.js and tools/dial-inventory.json: 161 dials (the page's 118 slider keys, 13 rule multipliers, 4 letter cuts, 24 post dials over 10 exam post modules and gradeBy, the feature family, the popularity diagnostic) plus 35 constants that could be dials; --check fails when a new slider key, rule kind or post module is missing. Each dial tested live on Track A on all 16 armies (snapshot dcd477d8a78c): 145 live, 11 inert at the test value (7 of them live once a sibling is set); cascade2 searched 26, left 119 live dials out (supportMeasured and synapseMarginal among them, though asked for). Duplicates: prem = wKill exactly; only the weights' ratios matter; smallPiece = pointsExp with the sign turned; scarceAnswers ≈ scarcity off (ρ 0.997); objPresence ≈ screenScore in direction (0.963); joinedShapley ≈ joinedMarginal at half strength; typicalW a shorthand. Removal candidates for Jordan: prem, pointsExp or smallPiece, typicalW, r.arrival, killMargin, armyPick, charsJoined, profileDials, popshare; bonusShare's use of list shares is his call. Next search proposed: a space-filling screen of every live dial (about 4,550 settings, 2–3 h) then a full factorial on what passes (0.5–4.7 h). Report reports/tiers/2026-10-05-dial-inventory.md. Nothing removed or adopted.

Built 5 Oct: tools/heldback.js (cascade2.js extended with options, its Track A check unchanged): the 87 dials cascade2 held back (every remaining ledger slider and post step; the leader-share switches leadersLeading, joinedMarginal, joinedShapley and leaderCredit among them), two values each, added one at a time to the main chain's 213 and the clean chain's 240 survivors, scored as cascade2 with its scrambled seeds. Stopped by design after 1 h 35 min (Jordan's OK): superseded by the dial-inventory screen (T-726), then pairs, then one sampled search. Finished: Dark Angels (125 values, all survivors) and jailW and stealW in every army. Dark Angels falls to single dials that beat their scrambled control (arrivalKill 1.5, r.buff 2.12, charPsychic 1.5: up to 119 survivors past 60), unchecked on the other armies; the leader-share switches cost it; jail and steal are noise-sized. reports/tiers/2026-10-05-heldback-partial.md

1a done 5 Oct (the builder): tools/everydial.js, 95 factors covering every live dial of the inventory (exclusions written in the report), each alone from Track A on all 16 armies against three scrambled letter sets (4.9 min): 36 pass on the fair-test seven; top preferredTargets C16, attachChars, sureFire 0.5, lifeKill, smallPiece 0.2; the leader credits, killByJob, the screens' area and block, scarcity off cost most; Dark Angels best +4.3 (sureFire 0.5nr), Agents past 60 under r.heal 1, supportMeasured 3, charPsychic 1.5. Under the stricter bar (the scrambled gains' 95th percentile) no single level survives on the fair-test seven. 1b stopped by Jordan's call (random settings cost about 7× the estimate, about 22 h; the Plackett–Burman 192 that replaced it stopped before scoring); in its place ten hand-built candidates on cascade2's headline: none clears every bar; C1 + arrivalKill 1.5 best (all 16 69.2 against C1 68.3 and Track A 61.9; Dark Angels 59.7); preferredTargets and attachChars cost Adeptus Mechanicus; Agents at most 59.6. Stage 2 done (Jordan's go): the 2^7 factorial on C1 (1.7 min): nothing beats C5 cleanly; best all-16 C5 + charPsychic 1.5 + attachChars (69.5, fair-test seven down to 73.5); with sureFire 0.5 too, 2 bars missed (Adeptus Mechanicus, Emperor's Children) and both walls past 60 (Dark Angels 60.1, Agents 60.5); in sample. reports/tiers/2026-10-05-every-dial-screen.md

tools/bonusshare.js weights each detachment and aura bearer by its share of tournament lists; rebuild it with rules-only weights (every detachment equal, or the army's best), so no list share feeds a letter. Until then it is measured only, flagged. Then re-score it in the next search.

Jordan supplied a Necron tier list written by Google Gemini from community sources (reports/tiers/panel/2026-10-05-necrons-gemini-aggregate.json; 29 units, reference only, reliability low). Necrons have no ledger yet, so it scores nothing. Two parts: (1) build the Necron ledger on the frozen snapshot (tools/ledger-all.js chain), with its effects coverage checked; (2) before any GEMINI AGGREGATE list joins a yardstick, calibrate one on armies with several human lists (Tyranids, World Eaters): it earns a place only if it agrees with the human lists about as well as they agree with each other; until then AI aggregates are kept apart from reviewer consensus.

Calibration (design/decisions.md, 5 Oct): Gemini agrees with human lists 3-8 points less than humans agree with each other. Add the 25 GEMINI AGGREGATE panels (reports/tiers/panel/2026-10-05-*-gemini-aggregate.json) to the 16 ledger armies' yardsticks at weight 0.5: a deliberate re-freeze adding only the panels (tools/ledger-inputs.js), the ledger merge reading them as reviewers with a weight, and the exam, cascade2 and everydial scores counting each list's pairs by its weight (consensus pairs: a pair agreed by the humans and Gemini counts fully; Gemini's own pairs at half). Report every army's agreement before and after, today's model and the C5 setting. The 9 armies without a ledger keep their Gemini lists as reference until they get one. Built (6 Oct, overnight; brief amended: no re-freeze, no rebuild): tools/yardstick.js reads the panels at scoring time by unit name, behind a flag (LEDGER_YARDSTICK=half for cascade2 and everydial, tools/exam.js --gemini 0.5); the rule is written in its header; without the flag every score is as before, to the pair. 15 ledger armies have a panel (Emperor's Children none). Consensus score barely moves (Track A 61.9 → 61.7, C5 69.2 → 69.2 on 16); the exam's list mean loses 1 to 2 (Track A 59.3 → 58.4, C5 66.7 → 64.9 on 15). Jordan to pick which is the headline. [yardstick-exam](reports/tiers/2026-10-06-yardstick-exam.md)

Report 6 Oct (reports/tiers/2026-10-06-death-guard-checks.md, tools/dgchecks.js; frozen snapshot dcd477d8a78c, Track A; nothing adopted). (1) Biologus: the dice are fine. The gain is small because 11e Plague Marine weapons already have Lethal Hits (+7–10% on the all-melee brick, +36–56% into vehicles); what's missing is two-leader forms and leader credit. (2) Fire Support: noted in unitfx.json, not counted. It's worth about +26 per 100 Rhino points the turn a boltgun brick unloads, shooting only; the Rhino's A is delivery (carry weighted 0). (3) Poxwalkers: the dice are modest; the heal kind's ×1.805 on their whole Value lifts them from 15th to 2nd of 36. (4) T-723/T-724: the Helbrute's (Death Guard) and the Thunderkyn's (Votann) best forms are illegal (next legal 959 and 674, lower bounds). Waiting on Jordan: the Fire Support data patch in the report (a kindfx.json lend, the unitfx status), not applied.

Internal, never shown: grimstat-corpus's listhammer/ folder read for model-building only (anonymized, list names dropped; data in the git-ignored build/tournaments/). tools/sources/listhammer.js (header: internal use), tools/sources/merge.js (Listhammer added; a record-only list matches an earlier source's on event, army and record; within one source two lists never merge; lists after the 1 Oct dataslate marked and kept apart; --without, --out), tools/unitoutcomes.js (per army and unit: share in winning lists, an outcome score with an empirical-Bayes shrink, and Spearman against the reviewers' consensus and Track A's Value). Numbers stay in the internal report (reports/tiers/2026-10-06-listhammer-outcomes-internal.md, never rendered in the Lab: build_pages.js skips -internal.md) and design/decisions.md. Nothing adopted. Waiting on Jordan: whether internal aggregates may stay committed, and which results yardstick (if any) the model should be judged on.

Internal model use only: data in the git-ignored build/tournaments/, never committed, published or shown, fed to no ledger, popularity file or yardstick. Found with Gemini (15 grounded calls), each source vetted by hand (robots.txt, terms, what's public; tools/sources/check.js now knows 13 more platforms and searches GitHub, Hugging Face, Zenodo). Acquired: MiniHeadQuarters direct (tools/sources/mhqsite.js: standings and lists, +24 lists the corpus lacks, a W/L/D record on 651 of 653 lists) and Tabletop Herald's public pages (tools/sources/tabletopherald.js: 119 German, Austrian and Spanish events since 20 June, 2,402 players, 1,930 armies; field only, its API not called). Merged (tools/sources/merge.js; event name + date within 10 days + army + placing): 653 lists and 153 events since 20 June, against the corpus's 629 and 33; all European. Not read: grimstat-corpus's listhammer/ folder and Lexmechanic's relay of it: the read was refused by the session's permission check, so Jordan's own call; bot checks (Longshanks, Hutber, Goonhammer), BCP, Reddit (robots.txt), Spikey Bits and shop blogs (terms), New Recruit (robots.txt), app-only platforms; no open 11th-edition dataset exists. Report: reports/tiers/2026-10-06-tournament-sources-internal.md; table in design/sources.md. Off in tools/sources.json (internal: true). Next: Jordan decides whether to allow the listhammer/ read and how the set is used

tools/yardexam.js. Held out (15 exam armies, 3 seeds × 3 folds, picked on 10, scored on 5; leave one out; paired bootstraps; both yardsticks): the best of Track A, C1, C5, #3 beats Track A +6.6 [+3.5, +9.8] but C1 by +0.0 ± 0.8; C1's game-wide part alone +2.7 on the 10 armies its choice never saw. Weights solved to hit Kill/Soak/scoring/support shares (a) 30/25/20/15, (b) 50/25/25, (c) 70/15/15, wKill fixed, on Track A and on C5: every one below its base (on C5 −1.8 to −4.9), never picked held out. Discovery only. Next if Jordan wants it: cascade2's game-wide choice re-run by folds from its stored records (minutes). [yardstick-exam](reports/tiers/2026-10-06-yardstick-exam.md)

The roles: Anvil (objective anchors, tarpits), Hammer (primary strike), Heavy anti-armour and artillery, Action units (secondary scorers), Screens and chaff, Force multipliers (buffers, command engines), Disruptors (debuffs, Battle-shock, precision), Transports. Generic names, no GW text. Map them onto T-716's 7 archetypes and T-718's 16 clusters; assign each unit a primary role (and a second where it has one) by rules from design/jobs.md's measured jobs, never from Gemini's examples (those only to check). Then: (1) rank within role and test whether reviewers' gaps shrink when units compete only inside their role (slot competition, T-708's replacement idea); (2) list the roles we measure badly (Anvil needs T-720's tarpit value, Disruptors the debuff auras, Action units the secondary scoring) as the build list; (3) the role names for the public tier pages (T-697). Discovery first; nothing adopted.

Twelve armies have one 11th-edition human list in the yardstick. Searched overnight 6 Oct (YouTube search and watch pages, Reddit through pullpush, 4 Gemini search questions; window 1 Jun to 30 Sep 2026; Space Wolves on pre-codex rules): 7 new candidates, all verified (Orks 4: Auspex Tactics, Art of War, Secondary Objective, The Daily Krumper; Dark Angels: Grimdark Breakdown's buy-first ranking; Agents: Brother Tobias, as allies for Ultramarines; Death Guard: a Reddit picture list); none for the other eight, Space Wolves included. YouTube refused every caption request, so one panel only: reports/tiers/panel/2026-08-22-orks-auspex-tactics.json (Gemini draft checked against the video's chapter list, reliability low-medium; Orks' only human list, Sprues & Brews being retired). Four Gemini drafts wait for captions (build/gemini/t733/, git-ignored, with the tools). Nothing added to a ledger, the frozen inputs or a yardstick. Jordan: use the Orks panel (after a caption spot-check?); transcribe the other two Ork lists; whether a buy-first list, an allies list or a picture list counts. Report: reports/tiers/2026-10-06-second-lists.md.

tools/recipestep.js (held out on the 15 exam armies, 3 seeds × 3 folds, paired bootstrap; leave one army out; Gemini at half; shuffled letters; Tyranid three-list consensus; the keep rule written before scoring). Step 41, the stable layer (Track A + charEpic 0.5 + aircraftBoard 1 + typicalSize 0.25): kept as Track A2 (candidate), held out +1.2 [−0.4, +2.6], 11 of 15 not falling, shuffled about 0; tools/ledger-benchmarks/2026-10-06-step41-stable.json. Adoption as the published benchmark is Jordan’s call. Speed: tools/movecheck.js first (Move is speed masked by unit type, +1.8 [+0.1, +3.5] over the ledger beside type controls, but −0.9 per 100 points); step 42, Reach as briefed (tools/reach.js, board share by turn 2 per 100 points against the army’s median): fitted wReach 0 in every fold, reverted; step 42b, Reach against its own kind (declared before scoring): +0.6 [−1.7, +2.7], 8 of 15, reverted. Report reports/tiers/2026-10-06-recipe-steps-1-2.md. Next: step 3 (durability), checked with movecheck.js first.

tools/breakdownpage.js writes design/handover/2026-10-06/ledger-breakdown.html ("Ledger Breakdown by Army", the 4 Oct page's look) from the frozen ledger (dcd477d8a78c; build/ledger/ and docs/lab/ledger/), in about 10 s. Every unit under two models, Track A (step 34b) and Track A2 (step 41, its typical-size post step), each through the exam's path (recipestep runsOf: wCarry 0, post applied, re-sorted): rank and Value under both, our letter under both cut at the reviewers' tier shares, the human reviewers' letters (11e lists first, 10e after a bar, dimmed, not counted), the GEMINI AGGREGATE letter in its own column ("Gemini aggregate, half weight"; not in any figure), the Track A2 line bar with the rule bonus hatched, what its damage lands on, role chips; the tier board switches between the models. Agreement per army, both models, in plain words: "Pairs all the reviewers agree on" (cascade2 lettersOf/pairsOf; one list: its pairs) and "Each list on its own, averaged" (the exam's measure), with a "how to read the numbers" note; the Tyranids' old five-list figure beside, marked as the old measure. Tyranids: 89.5 → 90.4 agreed pairs (583), 81.6 → 82.6 each list, old five-list 78.8 → 79.4. Known issues flagged beside their rows, not fixed: Poxwalkers, Neophyte Hybrids and both Acolyte Hybrids (a heal rule ×1.8), the Death Guard Helbrute and Brôkhyr Thunderkyn (illegal wargear in the best form). Role chips are a reconstruction (the 4 Oct page had no generator; rules in the script's head). Screenshots 1200 px light and 390 px dark, no page-wide horizontal scroll. Not published by the builder: the main session publishes it

Internal (Listhammer-derived lists; aggregates only, per-list data in the git-ignored build/listshape/). tools/listshape.js: --bands (his six Toughness bands with our exact dice, frozen snapshot dcd477d8a78c, Track A), --lists (stage 1), --unitfeats; tools/statlearn.js's shape features and --shape-md; tests/unit/listshape.test.js. Stage 1 on the winners' lists: his 3 / 4 / 6 shape replicates, a valley near 115 and none at 200, losing lists in whole fields share the shape, and the damage quota depends on the reading (the numbers are Listhammer-derived: in the internal report only, kept off the Lab board, T-744). Stage 2: no feature beats the ledger out of sample (bands hurt and coverage +1.0 [−1.4, +3.4] on 15 armies; anchor ratio −0.7; tier −0.2; within-tier rank +0.2). Nothing adopted; none declared. Idea for Jordan: the shape as a list checklist in My army (our words, our dice; it describes lists, not winners). Report reports/tiers/2026-10-06-list-shape-internal.md

Built 6 Oct, on beta for review: a transport whose passengers re-roll wound rolls against the unit it hit is a lend in docs/data/kindfx.json (rrWound all, our words; shooting only, the Falcon's for the turn; "got out of it this turn" a manual condition; the target the Marked chip) and partly in unitfx.json with a cant. Read on the 11th-edition pages, the same rule on 13 datasheets: Death Guard Chaos Rhino; Space Marines Razorback and Relic Razorback (every chapter through Space Marines); Coronus Grav-carrier; Skorpius Dunerider; Falcon; Manta (Aggressive Deployment); Goliath Truck; Crassus and Valkyrie Sky Talon (Astra Militarum and Genestealer Cults); Grey Knights Relic Razorback. Not the same rule, left noted: the Chaos Space Marines', Space Marines', World Eaters', Emperor's Children's, Sororitas' and Grey Knights' Rhinos (none has it), Thousand Sons' Rhino (Sorcerous Support, psychic +1 hit and wound), Taurox Prime (re-roll hits). In the calculator: the Army part's Nearby pick (Chaos Rhino for a Death Guard unit) gives a ⚡ chip, in play once the defender is Marked. Tests: unit and browser nearby; suite 603 passed, 2 failed as known (matrix killDP bound T-606, the Windows clipboard step in share). The rankings and the frozen ledger don't read it. docs/ regenerated (T-723's and T-688's pages, metatrack's detachment spelling, the Lab's new reports); T-743's Listhammer-derived stage 1 numbers taken off this card so the Lab board doesn't show them

Built 6 Oct: (1) rules that bring slain models back to a unit (44; unitfx.json returns: true) leave the heal kind's ×1.805 for their own kind, "Returns slain models" (r.return, × 1; the Spawn line's measured ones stay measured); (2) T-723's one-model wargear pairs via the re-freeze, T-724's squad-wide rules enforced in the ledger's Auto-equip (SQUAD_SAME: Thunderkyn, Beserks, Yaegirs, Aggressors, Headtakers; the rest still T-724). Re-frozen at b3c416933e, hash dcd477d8a78c → 1b88e955b9b3 (unitfx.json, docs/bsdata.js, build/units.json moved); every ledger rebuilt; the merge keeps panels that join no yardstick out of the comparators. Track A exam 59.3 → 59.7 (Agents +7.1, GSC −6.3; Tyranids unchanged); Poxwalkers 2 → 17, Neophytes 9 → 22; Helbrute 11 → 9 and Thunderkyn 5 → 4 (legal kits score higher). Step 41 still passes (+1.1 [−0.3, +2.7], 12 of 15): Track A2 is the benchmark. reports/tiers/2026-10-06-bugfix-snapshot.md

T-745 took the rules that bring slain models back (unitfx.json returns) out of the heal kind; they count × 1 (r.return) until measured. Write each army's spawn rules (tools/spawn.js type: "return", cost tables, our numbers: Curse of the Walking Pox per model its attacks slay, Cult Icon up to D3 a Command phase, the Medi-packs, Narthecium beyond the Marines, Rebind Rubricae, Fleshcraft, Rage Eternal, Healing Balms), rebuild the chain (spawn is a ledger stage, no re-freeze), and score on Track A2 with tools/recipestep.js. Predicted: the Genestealer Cults recover part of their −6.3. Built and measured (6 Oct), reverted (hibernated): nine armies' rules files (tools/spawn-rules-<army>.json), nine ledgers rebuilt on 1b88e955b9b3 (no re-freeze: live files); held out +0.0 [+0.0, +0.0] over step 41, 15 of 15 not falling, every fold picks the base, so the keep rule's "positive gain" fails. Returning units gain 15 to 37 Value (Poxwalkers 814 → 831, Neophytes 28th → 27th); the leaders' rules (Slaughterbound, Exalted Sorcerer, Haemonculus, Wolf Priest, Ravenwing Command Squad) land on joined forms only and move nothing. The Spawn line's per-army median scale is why: carded as a question in the report. Files kept, read with LEDGER_SPAWN_RETURNS=1. reports/tiers/2026-10-06-spawn-returns.md

Stage 1, a mockup for Jordan (nothing in docs/ changes): design/mockups/2026-10-06-calculator-stratagems.html, screenshots beside it (phone 390 and desktop, light and dark; no horizontal scroll). A side's Detachment part gets a Stratagems block under its detachment chips: this unit's dice stratagems from the detachments picked (keywords checked; the rest a faint count), in our words with their CP ("Re-roll 1s to hit and wound · 1 CP", "−1 Damage · 2 CP"), grouped Shooting, Fight, Defence; a group out of play is faint and names its toggle. Tapped, one joins the Modifiers line as a teal ⚡ chip with its cost; every one starts unused. The CP total: one number in the block's heading, "CP this matchup" (a defence one counts once per enemy phase it covers), nothing on the result, no budget. Examples from the catalogue: Tyranids Hive Tyrant in Invasion Fleet, Death Guard Plague Marines in Virulent Vectorium, Termagants in Synaptic Nexus. Also proposed: the 282 "Stratagems, by name only" notes in docs/data/detfx.json (1,382 names) rewritten in our words from the catalogue (154 detachments covered, 297 dice stratagems; 128 get a count only), so no stratagem name stays in site data. Stage 2 built on beta (Jordan approved, 6 Oct, "Yes"): tools/stratcalc.js writes docs/data/stratfx.json (296 dice stratagems in 136 detachments and the core re-roll; our words, no names); docs/detfx.js strats/stratEffects; docs/stratui.js draws the block, the Modifiers line's teal ⚡ chips and "CP this matchup"; flag "strats": "beta" (the beta site and local copies; ?strats=1 anywhere). Beyond the mockup: a stratagem whose versions are true alternatives (Lethal Hits or Sustained Hits; the core re-roll's hit or wound) is a chip per version with "or" between, one use. The 282 notes rewritten in a separate commit (151 from the catalogue; 131 a count, the catalogue's empty entries counted as not covered); a unit test keeps names out. Waiting for Jordan's look on beta; main untouched. Handoff: reports/handoff.md (6 Oct, T-749 stage 2)

Built 6 Oct: all five reverted; Track A2 stays the benchmark, no Track A3 candidate. tools/sheetlayer.js (a post step chained after the stable layer: sheetSpeed, sheetEpicPsyker, sheetInfantry, each 0 = today) and tools/sheetstep.js (tools/recipestep.js's protocol, one dial per step on a small grid chosen on the training folds, three shuffled controls through the same fit; keep = held-out gain > 0, low end above −0.5, 9+ of 15 not falling, above the shuffled controls' mean). Each prediction committed before its score (ledger-steps rows 46 to 50). Held out over step 41: 46 speed within its kind +1.1 [−0.6, +2.7], 10 of 15 (k 1 in every fold; the shuffles pick 1 too, mean +0.3; fails the floor); 47 Epic Hero or Psyker −0.3 [−1.2, +0.5], 8; 48 Infantry −0.2 [−1.0, +0.7], 8; 49 the Soak weight ×2/×4 −0.1 [−0.3, +0.0], 7; 50 Lone Operative 2.5/3 +0.0, 15 (only the Orks move). The five together (a diagnostic) +1.3 [−0.6, +3.1], 9. Movers at speed 1: Land Speeders 29th → 6th and 37th → 14th (S), Helbrute 11th → 23rd (C), Wulfen and Wolf Scouts up, Logan Grimnar down. Report: reports/tiers/2026-10-06-datasheet-steps.md. Next: more human lists before speed is tried again; Toughness against the army's median as a flag (T-748's fallback, not run).

Confirmed by the rule frozen beforehand (ledger-steps row ensemble-confirm); nothing adopted. T-736's declared ensemble (ledger Value rank + datasheet-model rank), re-fitted on snapshot 1b88e955b9b3 with Track A2 (tools/ensconfirm.js; statlearn.js gains --bench/--out and applies a setting's post step; the re-implementation equals statlearn's fit to the digit). Over Track A2: the 11 held-out human lists (the T-733 Orks candidate and each list of Tyranids, World Eaters, Space Marines and Genestealer Cults held back from its own fit) +3.9 [+1.3, +6.6], 9 up / 2 down; GEMINI AGGREGATE +5.3 [+1.8, +9.1] (already seen, weaker); the Orks list alone +1.6 [−7.8, +9.8]; without the Genestealer Cults +2.1 [+0.3, +3.9]. Leave one army out it shrinks to +2.4 [−0.8, +5.6] on 15 (Track A2's charEpic already holds part of it). Winners' list share (internal) as a diagnostic only. Proposed, for Jordan: five one-dial recipe steps on step 41, in order: speed within kind, Epic Hero and Psyker, Infantry, Soak's weight (toughness and wounds), Lone Operative (not built). Report: reports/tiers/2026-10-06-ensemble-confirm.md

tools/kindlayer.js (a post step chained after the stable layer: Value × exp(kInfantry, kMonster, kVehicle, kFly, kEpic, kPsyker on the datasheet's keywords) × (Move ÷ its kind's median)^kSpeed) and tools/kindstep.js (recipestep.js's protocol over a 2,916-candidate coarse grid, fitted on each training fold; base step 41). Reverted: held out +0.2 [−1.6, +1.9], 7 of 15 not falling; Fly −0.3, Epic +0.3, Psyker +0.3, kSpeed 1 stable, Infantry, Vehicle, Monster split; shuffled letters gain as much. Report reports/tiers/2026-10-06-recipe-step-43.md. Nothing saved as a benchmark.

tools/statlearn.js: one feature table (75 facts × 733 units at Track A: lines, Kill by class, datasheet, keywords, leading, support, jobs; human 11e letters, GEMINI AGGREGATE letters apart, list share as a diagnostic only), then 34 structurally different models fitted leave one army out on the human letters, each against 20 scrambled letter sets, bootstrapped against the ledger by army. Result: every re-fit of the ledger's own information (logistic L1/L2, ordinal, trees, neighbours, roles, value over replacement, leaders joined) lands within 2 of the ledger (61.9; 60.0 on 15 without Tyranids); facts it doesn't use do better: the declared ensemble (ledger rank + datasheet-model rank) +3.9 [+0.4, +7.3] on 15, the datasheet-only model +3.2, ranks of every fact +4.0, and on Gemini's never-trained-on letters +6 to +7 with intervals clear of 0. Reviewers value Move, Epic Hero, Psyker, Lone Operative, Infantry, durability (Soak about level with Kill, against the ledger's 85:3); Fly, debuff rules, transports, vehicles down; within-role scoring loses 4 to 5. Nothing adopted. Next: a confirmation run of the ensemble on unseen human lists | reports/tiers/2026-10-06-statlearn.md

Built 2 Oct (local commit, not pushed): tools/tiertest.js switch r7 and --r7json <file>: (1) best-only grading, score = best allowed job + V7C.BONUS 0.25 × each other allowed job's points above V7C.BAR 60, at most 100 (a weak job never lowers a unit; letters by quota as before); (2) Feed the Swarm lent to a Harvester at most one squad's aura worth (V7C.REGEN_UNITS, 38 pts): Pyrovores Banner 89 → 62 (B → D), Ripper Swarms 94 → 83 (B → C); the Tyrannocyte's cargo set down once (deliver's drop): Banner 91 → 21 (A → D); (3) yardsticks for every panel: ρ with SE, strict on our ruler (the panel re-cut at our quota), raw, within one, and shuffle baselines (2,000 permutations). Numbers (6b → 7): Tyranids ρ 0.39 → 0.50 (SE 0.12), strict on our ruler 19 → 20 (chance 10.3), raw 12 → 12, within one 27 → 29 (chance 20.4), Tyranid list share 0.32 → 0.39, every unit's list share 0.171 → 0.164, Space Marines −0.03 → −0.05, Orks −0.16 → −0.13; 291 of 1,161 letters move (150 up, 141 down). Up: Hormagaunts, Norn Assimilator, Tyrannofex, Gargoyles, Winged Tyranid Prime to S, Norn Emissary B → A; down: Neurotyrant, Psychophage, Venomthropes B → C, Lictor A → B. Report: reports/tiers/2026-10-02-tyranids-round7.md; scoring.md (V7C, a changelog line). Open: the healed squad's own Anvil doesn't count Feed the Swarm yet.

Why: round 6 (T-557) counted a Command Point at 0 in the tier test's letters; since round 6b it is a flat 30 pts (V6C.CP_PTS, Jordan, 2 Oct) until a CP has a measured worth (abilities that give, save or tax CP: the Hive Tyrant's, the Swarmlord's, the Lictor's and others, tierfx.json cp). What to build (tools/tiertest.js, a report; nothing on the site): (1) For each army and each of its detachments, list the stratagems a unit can use: names and our own one-line description only, never GW's wording (Wahapedia's 11th-edition faction pages, curl -sS https://wahapedia.ru/wh40k11ed/factions/<army>/, the errata on the same page; plus the core stratagems: Command Re-roll and the rest). Keep them in a data file of our own words, e.g. docs/data/stratfx.json { army: { detachment: [{ name, cp, phase, who (keywords), effects (detfx.js's mods: rrHit, rrWound, lethal, ap, fnp, inv, …), note }] } }, with the effects in the same vocabulary as detfx.json so ev.js can play them. (2) For each unit in each detachment, take the best stratagems it can use (its keywords against who) and work out with the engine what one CP buys it: the low end is a Command Re-roll on one attack roll or one failed save (ev.js's one-die re-roll, rrOneHit / rrOneWound, or one save re-rolled), the high end a re-roll-hits or similar stratagem on its best volley, both into the five targets (enemy points destroyed, step g's ppw) and against the six attackers (own points saved). The CP's worth for that unit = the expected gain per CP of the best stratagem it can use, in points; a unit with nothing better than a Command Re-roll gets the low end. (3) Use it in Banner where tierfx.json's cp gives or saves CP (the CP goes to the army's best user: the median of the army's top units, or the co-listed squads as variable 5 picks them) and where an enemy-CP tax costs the enemy (the enemy's median). (4) Re-run round 6 (--round6) with it as a switch and write the yardsticks against round 6 (reports/tiers/<date>-tyranids-round7.md or a section), and update design/scoring.md (V6C.CP_PTS replaced, a changelog line; tests/unit/scoringdoc.test.js names any new constant). Inputs: build/units.json, the BSData checkout, the round-5/6 command (reports/handoff.md, T-557's entry). | Carded 2 Oct (T-557's round); not started

The Visual workflow (.github/workflows/visual.yml, T-396/T-491) has been red on every beta push since 1 Oct: its baselines are only refreshed by hand (a manual run with mode "update" commits them to the branch). Decide: the workflow refreshes its own baselines on a push to beta whose commit message carries a marker, or the builder of any UI card triggers the update run. For now the design session triggers the refresh by hand after T-554. visual.yml unchanged so far.

Built 2 Oct, on beta: build_rankings.js reads the coverage files' heal rules (to itself, each Command phase) and lifts hits to destroy by ev.js's healLift, the tier test's closed form, on the turns alive without the heal; rankings.json keeps def bare and adds hl and hr; unit pages' Defense table and the app's Rankings use def × hl, with a note on the page. 50 rows lift (49 Necron, Old One Eye); 19 pool letters change (7 Necrons up, 12 elsewhere down a band at an edge). Not counted: kill and fight heals, heals from other units (Technomancer, Ghost Ark), heals without numbers. Doubt: the lift reaches ×2 (Skorpekh Lord); a cap would be one constant. Report: reports/tiers/2026-10-02-defense-heals.md

11th edition's core rules (Wahapedia, 05.02.01, and Attacking Attached Units): attacks on a unit whose models have different T use the highest T among its models on the battlefield (the bodyguard models' when a character is attached). Built 2 Oct for the live rankings, on beta (Jordan's go, 2 Oct): build_rankings.js unitT, the highest T among bsdata.js models; 13 rows take a higher T (Decimus and Aquila Kill Teams 4 → 6, Traitor Enforcer 3 → 6, Talonstrike 4 → 6); 7 pool letters change (5 up, the Artillery Team down at the B/C edge). Black Spear Task Force's tMajority is a detachment rule, which Defense doesn't count. Still open: the calculator (seedDefence) and ev.js take the first statline; app.js was another builder's lane. Report: reports/tiers/2026-10-02-defense-heals.md

Child of T-523 (Tier system v2); carries on T-343's batches until every army is covered. For each army: every datasheet's abilities (non-Legends first, then Legends) in data/unitfx.json, leaderfx.json for what a leader gives its unit, armyfx.json for army rules; every detachment's rule and enhancements in detfx.json (enhancements as per-detachment upgrades, scored later and never in the letter yet), stratagems by name only in a note. Our own words read on Wahapedia's 11th-edition pages, never rules text. Each rule records a status (modelled, partly, noted), a kind for what isn't dice (arrival, move, enemy, shock, mortal, spawn, heal, cp, aura, mark, synapse, overwatch, chosen, once, oc, lead, list) and, where it would touch the dice, why it can't yet; rare or once-a-battle effects carry off: true and start switched off in the calculator. One coverage report per army, reports/tiers/<date>-<army>-coverage.md (rendered in the Lab), with the vocabulary gaps counted. One commit per army. Order (Jordan, 2 Oct, via the supervisor): Tyranids (T-541, first), then Necrons, Adeptus Custodes, T'au Empire, Dark Angels, Emperor's Children, Orks, Chaos Daemons, Death Guard, Adeptus Mechanicus, Astra Militarum, Aeldari, then the rest by share. The corpus's count for reference (top-quarter lists, metatrack.json June to September, 150 lists; non-Legends datasheets in our BSData build): Adeptus Astartes all chapters 21 lists (14%; the Space Marines' 87 datasheets plus each chapter's own: Space Wolves 21, Blood Angels 16, Dark Angels 16, Black Templars 19, Ultramarines 11, Deathwatch 10), Necrons 15 (10%, 55), T'au Empire 12 (8%, 46), Adeptus Custodes 11 (7%, 34), Emperor's Children 9 (29), Adeptus Mechanicus 9 (37), Tyranids 8 (59), Death Guard 7 (42), Chaos Space Marines 6 (61), Thousand Sons 6 (41), Adepta Sororitas 6 (36), Aeldari 6 (79), Orks 6 (58), Chaos Daemons 5 (80), World Eaters 5 (36), Leagues of Votann 5 (25), Astra Militarum 4 (75), Grey Knights 3 (29), Genestealer Cults 2 (100, allies included), Imperial Knights 1 (27), Drukhari 1 (39), Chaos Knights 1 (27), Agents of the Imperium 1 (32), the Titanicus lists 0 (4 each). About 1,400 non-Legends datasheets in all. Done so far: Tyranids (T-541); Necrons (2 Oct: 52 of 55 datasheets, 186 abilities with 44 modelled, 11 partly, 105 noted, 26 unread (the three Crucible characters; the six crypteks' "Support" noted since); 12 detachments, 42 enhancements; Reanimation Protocols in armyfx.json; reports/tiers/2026-10-02-necrons-coverage.md); Adeptus Custodes (2 Oct: 31 of 34 datasheets, 86 abilities, the three Crucible characters unread; Martial Ka'tah in armyfx.json; their 9 detachments are BSData's (T-543 found the build skipped the Custodes' plural "Detachments" entry; fixed, so the calculator offers them))); T'au Empire (2 Oct: reports/tiers/2026-10-02-t-au-empire-coverage.md; For the Greater Good in armyfx.json)); Dark Angels (2 Oct: reports/tiers/2026-10-02-dark-angels-coverage.md; their own 19 datasheets and 8 detachments; the Space Marine datasheets they share come with the Space Marines)); Emperor's Children (2 Oct: reports/tiers/2026-10-02-emperor-s-children-coverage.md); Orks (2 Oct: reports/tiers/2026-10-02-orks-coverage.md); Chaos Daemons (2 Oct: reports/tiers/2026-10-02-chaos-daemons-coverage.md); Death Guard (2 Oct: reports/tiers/2026-10-02-death-guard-coverage.md); Adeptus Mechanicus (2 Oct: reports/tiers/2026-10-02-adeptus-mechanicus-coverage.md); Astra Militarum (2 Oct: reports/tiers/2026-10-02-astra-militarum-coverage.md); Aeldari (2 Oct: reports/tiers/2026-10-02-aeldari-coverage.md; the Drukhari detachments in BSData's Aeldari list wait for Drukhari); Chaos Space Marines (2 Oct: reports/tiers/2026-10-02-chaos-space-marines-coverage.md); Thousand Sons (2 Oct: reports/tiers/2026-10-02-thousand-sons-coverage.md); Adepta Sororitas (2 Oct: reports/tiers/2026-10-02-adepta-sororitas-coverage.md; Acts of Faith in armyfx.json, noted: Miracle dice aren't in the maths); Blood Angels (2 Oct: reports/tiers/2026-10-02-blood-angels-coverage.md; their 27 datasheets and 8 detachments); Grey Knights (2 Oct: reports/tiers/2026-10-02-grey-knights-coverage.md; Gate of Infinity in armyfx.json); Drukhari (2 Oct: reports/tiers/2026-10-02-drukhari-coverage.md; their 9 detachments under BSData's Aeldari list; Power from Pain in armyfx.json, Pain abilities set by hand as Empowered); Leagues of Votann (2 Oct: reports/tiers/2026-10-02-leagues-of-votann-coverage.md; Prioritised Efficiency in armyfx.json as a pick of footing); World Eaters (2 Oct: reports/tiers/2026-10-02-world-eaters-coverage.md; Blessings of Khorne in armyfx.json as a pick of the dice blessings); Ultramarines (2 Oct: reports/tiers/2026-10-02-ultramarines-coverage.md; four of their sheets aren't on Wahapedia 11e and stay unread); Imperial Knights (2 Oct: reports/tiers/2026-10-02-imperial-knights-coverage.md; Code Chivalric and Bondsman in armyfx.json); Space Wolves (2 Oct: reports/tiers/2026-10-02-space-wolves-coverage.md; their 7 detachments; Curse of the Wulfen in armyfx.json); Space Marines (2 Oct: reports/tiers/2026-10-02-space-marines-coverage.md; the 161 shared datasheets, 16 Codex detachments, Oath of Moment in armyfx.json); Black Templars (2 Oct: reports/tiers/2026-10-02-black-templars-coverage.md; Templar Vows in armyfx.json); Chaos Knights (2 Oct: reports/tiers/2026-10-02-chaos-knights-coverage.md; Harbingers of Dread in armyfx.json); Genestealer Cults (2 Oct: reports/tiers/2026-10-02-genestealer-cults-coverage.md; the allies copied from the Astra Militarum and Tyranids; Cult Ambush in armyfx.json); Deathwatch (2 Oct: reports/tiers/2026-10-02-deathwatch-coverage.md; Black Spear Task Force; Mission Tactics in armyfx.json); Agents of the Imperium (2 Oct: reports/tiers/2026-10-02-agents-of-the-imperium-coverage.md; Assigned Agents in armyfx.json); Salamanders, Raven Guard, Imperial Fists, Iron Hands and White Scars (2 Oct: their own sheets and one detachment each, a report each); Adeptus Titanicus and Titanicus Traitoris (2 Oct: the four Titans for both lists, no detachments; reports/tiers/2026-10-02-adeptus-titanicus-coverage.md and -titanicus-traitoris-coverage.md). Next: none left in the order: every army in BSData's build has its coverage report. Unread on purpose: the Crucible characters and the sheets Wahapedia 11e doesn't have (each army's note lists them). The engine gaps the reports name are in reports/handoff.md's last T-542 entry (reports/handoff.md has the method).

Child of T-523 and the first batch of T-542. Units: every Tyranid datasheet in BSData's catalogue (61 of 64; the three Crucible organisms aren't on Wahapedia's 11th-edition page, so unread) in data/unitfx.json, each ability with its status, kind and reason; the leaders' abilities for the unit they lead in leaderfx.json (the Broodlord's Hypnotic Gaze, the Hyperadapted Raveners' Alpha Invader, new). New: an effect with off: true starts switched off in the calculator (app.js fxOff): the damaged brackets' -1 to hit, Battle-shocked and below-half conditions, the Harridan's Frenzied Metabolism. Detachments: all 10 matched-play detachments and the 4 Boarding Actions ones, each rule's status and kind, each enhancement as an upgrade in detfx.json's enhancements (effects where our vocabulary has them; never in the calculator or the letter yet) and the stratagems by name in a note. Report: reports/tiers/2026-10-02-tyranids-coverage.md, with the vocabulary gaps by how many units need each, and the tier test's Tyranid table with the data switched in. Supersedes the T-540 list's data side (T-540's tier-test kinds stay in tierfx.json, round 5). Built 2 Oct: 151 abilities (30 modelled, 11 partly, 74 noted, 36 unread: the Crucible organisms); 28 detachment rules; 41 enhancements. tools/coverage.js writes the report; tiertest.js --own-out measures the units' own abilities (one letter moves, ρ 0.38 unchanged). The detachments' movement rules are written under move, not round 5's tier: read as tier they move 15 letters and ρ falls to 0.28, so their constants (tunnel distance, regeneration credit, OC share) come first. Waits on the supervisor's read.

Child of T-523 (Tier system v2), from T-524's Tyranid table; nothing built yet, and each rule is modelled one at a time under Jordan's Tyranids-first rule. The rules Auspex rates units for and V4 doesn't play out, each with a proposed shape in our effect vocabulary and the job it feeds (the full table is in reports/tiers/2026-10-02-tyranids.md, "Tyranid rules to model"): Biovores' Spore Mines as a new spawn kind (Runner, Banner); Raveners' Death From Below and the Red Terror's Subterranean Hunter as rearrive (Runner and Hammer; the Red Terror's also cuts exposed turns); the Red Terror's healing as heal (turns alive); the Neurolictor's forced Battle-shock and its aura as shock plus an enemy-side aura (Banner); the Maleceptor's −1 to hit within 6" as an enemy-side aura (Anvil, Banner); the Norns' chosen target or objective as a chosen condition (Hammer or Anvil); the Hive Tyrant's CP discount as cp (Banner, a new constant) and its Assault and Lethal Hits aura in armyfx's shape at its real lift (Banner); a leaderfx entry for the Hyperadapted Raveners. Our own words only, never rules text. Modelled 2 Oct in round 5 (T-524, V5): spawn, rearrive (as arrival), shock, the enemy-side auras (enemy), chosen, cp and the Hive Tyrant's aura at its real lift, in docs/data/tierfx.json (our words; the tier test only). Not yet: the Red Terror's healing (heal), the re-deploy and Rapid Ingress stratagems, and the detachment movement rules (Subterranean Assault's tunnels, Vanguard Onslaught's charge after an advance, Crusher Stampede's OC, Assimilation Swarm's regeneration, Talons of the Norn Queen's swap and invulnerable upgrade). The tier test reads those from a detfx.json rule's tier key (shape in design/scoring.md, V5 item 7) once the Tyranid coverage card writes them. Engine side (2 Oct, a builder sub-agent on the supervisor's brief): the kinds the coverage files record in words now count, one commit each. The numbers live in new docs/data/kindfx.json, keyed like the coverage files (file, army, owner, rule), until the coverage builder writes them on the rule itself (the proposed shape, which the engine already prefers: heal: { n, per: cmd/kill/fight, models, to: self/unit/near, who, weapon, off } on a rule of kind heal; detfx.js withNums). 1. heal: heals are chips of their own on the side's Modifiers line and play in To the death turn by turn (its Command phase first, a kill heal after its blows); the answer says how many wounds came back a fight on average and the round strip says who healed how many; armyfx.json's Reanimation Protocols reaches every Necron unit whose datasheet lists it; ev.js healLift is the closed form (k = (W − h) ÷ (D − h) of 5 rounds), not in the live rankings yet (they read no unitfx rule); the tier test's --kinds uses it for turns alive and Anvil in place of ×1.15 where the data has a heal. Tyranids: ρ 0.38 → 0.38, Old One Eye A → S, the Tervigon's Termagants +140% durable in Banner. 2. mortal: mortal wounds outside attacks (shape mortal: { n, on, d, pm, when, range, vs, near, max, v }) are chips and a "weapon" of their own in the volley (a bullet per mortal wound, one damage, no save, Feel No Pain applies, spilling over), "+N mortal" on the funnel's wound gate and the answer; the tier test's Hammer reads them in place of mortalfx.json where the data has them (5 Tyranid units, the same numbers, nothing moves), mortalfx.json kept for the 101 others. Not yet: the defender's mortals in its strike-back. 3. aura: a coverage rule's aura object (range, to, not) with its effects (the rule's own, or aura.effects in kindfx.json for one noted in words) reaches a joined character's squad in the calculator, keywords checked, range taken as met; enemy-side auras come with their bearer; a rule leaderfx.json already gives isn't given twice; the tier test's variable 5 reads them in place of tierfx.json's (the same squads and lifts, nothing moves). Left for later: the unit pages' aura worth and tools/banner.js (still its proxy); the defender's mortals in its strike-back; rearrive and spawn (already in V5 through tierfx.json, variables 2 and 8; the coverage files hold no numbers for them); the live rankings' Defense with heals (a decision: it lifts every Necron).

A design rule for Tier v2 (T-523), written into design/scoring.md §6. The letter is the best legal context (loadout, delivery, its army's best detachment for it, the Current meta lens and the meta's disposition mix); leaders don't inflate a squad's letter. One line under the letter names the context. The floor (no detachment, alone, Even lens) shows as a range, "B–S", and the tier list sorts by the ceiling with a toggle for the floor. Axes are shown one at a time, never crossed: per detachment (precomputed) and per disposition (recomputed in the browser); the same cells give "best units for <detachment>" lists on the detachment pages. Cost measured 2 Oct: 24,999 detachment cells, 8,805 disposition and 21,132 archetype cells at 6 + 6; build 28 s to about 40 s; rankings.json 356 KB to under 400 KB gzipped. Builds only when v2 does.

The bundle rule (05:28Z), delivery modes (05:38Z) and the round-3 fixes (05:44Z), as V3 in tools/tiertest.js, report-only. Built 2 Oct: walk, Deep Strike, Strategic Reserves and the Dedicated Transport bundle (tools/transports.js reads who may ride what from BSData at run time); the standard table of distances from the 11th-edition rules; fixes (a) mortal wounds (reports/tiers/2026-10-02-mortals.json, 34 abilities read on 11e datasheets, our words), (b) joiners aren't Runners, (c) Battle-shock below half, (e) Indirect Fire from turn 1. (d) transport capacity in Banner lowered every yardstick and is out. Result: ρ with list share 0.164 (V1 0.174, V2 0.127, V2b 0.087); Space Marines' order −0.18 (the least wrong of every system), Orks 0.18; Mortarion A, Ghazghkull B, the first new system to rate both. Decisions taken alone: Dedicated Transports only; characters aren't bundled. Doubt: the transport's guns are 57% of a bundle's damage at the median, so a weak passenger's letter partly measures its ride. Report: reports/tiers/2026-10-02-round3.md. Waits on Jordan's read.

Child of T-523; report-only. Built 2 Oct: tools/dispositions.js reads the 11th-edition mission deck's 25 primaries (Wahapedia, our own words and numbers). The pairing comes from the mission generator: each disposition has five primaries, one for each opposing disposition. It sorts each primary's VP by the job that earns it and weights a disposition's five by how often the field plays the opposing disposition. Coverage: about a quarter of lists name a disposition (77 in Aug and Sep; none in June). Reconnaissance 30%, Priority Assets 23%, Take and Hold 21%, Purge the Foe 14%, Disruption 12%. Demand: Anvil earns 50% to 87% of every disposition's primary VP. Purge the Foe asks for the most Hammer (29%), Reconnaissance the most Runner (41%). The lens gives each job half today's S and A split plus half the demand. 73 units move one letter between the Take and Hold and Purge the Foe lenses (troops up under Take and Hold, big killers up under Purge the Foe). The check fails: the lists that play each disposition don't carry what its primaries pay for (Anvil ρ −0.70, Hammer −0.40, Runner +0.20); an army can only pick the dispositions its detachments offer. Recommendation: no disposition lens on the letters yet; keep the demand table as a teaching aid, and rerun once twice as many lists name one. Report: reports/tiers/2026-10-02-dispositions.md.

Child of T-523, started now. Jordan: "are we keeping track of all the factors that go into how we score? Could you show me the math behind the scenes if I asked? Is there a dev page on the website that explains it in plain English, every factor? Maybe there should be." Built 2 Oct: design/scoring.md, rendered at /lab/docs/scoring/: the one-attack rule and the neutral table, with the reason for each assumption; every target and attacker (key, profile, stand-in, weight, where in the code); Offense, Defense, Value, Utility's parts and traits, Meta, today's letter with the meta lift; the effects files with their counts, and the loadout solver with its real limits (400 kits, 200,000 squads); Tier system v2 marked proposed: the four jobs, the composite and quotas, V2b's delivery model with every constant, army rules, Lenses, the Banner method; the known gaps, and a dated changelog. Linked from /about/'s "How the scores work" (a new line) and every "How we score this" (method.more: "Every formula and constant"). tests/unit/scoringdoc.test.js fails when the code has a target, attacker, Utility part, trait, job or delivery constant the doc doesn't name. The CLAUDE.md line (added in this commit; the design session can reword it): "design/scoring.md is the canonical spec of the maths (T-535)… A change to tools/build_rankings.js, tools/targets.js, the effects files (detfx, leaderfx, unitfx, armyfx) or the tier tools updates scoring.md in the same commit, with a changelog line; tests/unit/scoringdoc.test.js fails when a target, attacker, Utility part, trait, job or delivery constant in the code isn't named there."

Child of T-523; report-only until T-524 is back and Jordan has read it. A Monday paragraph in the weekly analytics report and a block on /meta/ and /lab/reports/: three units our maths rates high (A or S by job) while their share of winning lists is low (below their army's median), with the numbers behind each (the job, the composite, damage before death or the Banner multiplier, the best loadout and target) and one line on why lists might be missing them. Gated: on the site only once the calibration score (T-533) is above a bar Jordan sets (proposed: 70% within one tier); until then in the Lab only, marked "not yet public". Outcomes tracked: when a past Sleeper's list share rises, say so ("called 6 Oct, now in 18% of lists"); the hit record is the point. The mirror list, Workhorses (low letter, high share), stays in the Lab as our to-do list of what the maths misses, never published as advice (Mortarion is one, T-524).

Child of T-523; report-only until T-524 is back and Jordan has read it. Makes T-524 repeatable. The panel: 3 to 5 armies' reputable, text-based public tier lists, each recorded as unit → tier plus a one-phrase paraphrase of the reason (our words only), with source URL and date, refreshed when the source updates, in reports/tiers/panel/ (the first entry exists: reports/tiers/panel/2026-10-02-space-marines-tistaminis.json, Tista Minis). tools/calibrate.js scores our current letters against the panel: agreement, mean tier distance, and the per-unit disagreements, each in a diagnosis bin (missing rule / utility we don't measure / consensus likely wrong / acceptable variance / data error). A bin set once stays set until the unit's numbers change. In CI on every change to build_rankings.js, the effects files (detfx, leaderfx, unitfx, armyfx) and the archetypes, as a non-blocking report: the number goes into reports/analytics and onto /lab/reports/ as a line over time ("agreement 58% → 71% since 1 Oct"), each change's delta attributed to the commit that moved it. Rule: a change to the maths that lowers agreement needs a reason written in its card. Plus a coverage line: how many of our units the panel grades.

build_rankings.js's leaderLift (T-062) reads only BSData's Leading links (rec.leads), so 11th edition's Support characters (48 of them: the Apothecary Biologis, for one), who join squads through Supporting links (rec.supports), get no lift in Utility's support part on the tier list and unit pages. Score them the same way (their effects on each squad they can support), check which have leaderfx.json entries, rebuild the rankings and report the letters that move. T-527's report tool already does this. On beta with the next rankings build.

Child of T-523; design now (in T-529's report), mockup after T-524. Jordan: "if the meta shifts to all monsters we change the weighting on the back end… a toggle for skews… units that are S-tier in one meta and D-tier in another… reweight what enemies they're coming across and the calculator… all the pros would come to us for it. Data is cheap and compute is cheap: more archetypes, stress-test every unit against them, toggle the weighting by the current meta." Precompute wide, weight late: rankings.json keeps every unit's damage into each target and hits-to-destroy from each attacker for the archetype set T-529 recommends; a lens is a weight vector, and Offense, Defense, the jobs, the composite, the quotas and the letter recompute in the browser (a dot product and a re-percentile; measure the file's growth and the time on a phone, target under 100 ms). Built-in lenses: Current meta (the default, from winning lists' points by target class and weapon class, refreshed daily; the static pages and Google see this one), Even (today's), Monster mash, Horde, Elite infantry, Armour, Mortal wounds heavy, Last month's meta; each with a line and its weights on a tap. Custom lens: sliders, or "from these lists" (paste opponents' lists or pick winning lists or a tournament); saved per device (hre.lens.v1, into CLAUDE.md's key list when built); carried by links (?lens=). A candidate supporter perk later (our software); free while memberships are off. Where it applies: the tier list and faction pages (letters re-rank live, with a lens chip and a line like "S in the current meta · B against hordes"), unit pages (job bars, the Banner table), the calculator's stand-ins (decide: fixed or the lens's top targets). Static HTML always shows Current meta. Lens page: /meta/lens/ or a section of /meta/: the current weights and their change since last month ("monsters up 6 points"), a Monday paragraph. Risks: moving letters (chip and line), SEO (one canonical lens), file size and CPU, the job quotas being lens-dependent too (from the same lists). Design in T-529's report (2 Oct): storing the recommended set adds about 25 KB gzipped to rankings.json's 343 KB (12 targets and 8 attackers, about 66 KB). A lens recompute for 1,241 units takes 35 ms in Chromium at 4× CPU slowdown (target: 100 ms). Seven test lenses move 590 units one letter and 263 two, but none from S to D: a target lens only re-weights Offense, half of Value. A meta lens should shift the attackers too, and the mockup should use V2 letters. Proposed: the calculator's stand-ins stay fixed; the default lens is the one that best predicts what wins (the meta weighting lowered agreement in this test). Mockup after T-524. Decided 2 Oct (Jordan, 1 Oct (Pacific), via the design session): the custom lens is an eventual supporter perk; the built-in lenses stay free forever. Until launch (T-187) it ships free, behind the same supporter gate as the other perk candidates and labelled "Free while we're in early days". When it goes behind the perk: design/kofi-tiers.md (T-186) and the Ko-fi text for Jordan.

Child of T-523; report and data, no site change (the calculator's chips come later under their own card). We model detachments (detfx.json), leaders (leaderfx.json) and units' own abilities (unitfx.json) but not army rules. armyfx.json in the same shape and our own words: each army rule as dice or stat effects with its condition (in range of a Synapse unit, Battle-shock re-rolls and the like) and who grants it. A Synapse creature's aura then counts in its Banner score at the 2-units-in-range assumption, and Leadership re-rolls count in Anvil's Battle-shock resilience and Runner's action eligibility. Tyranids first as the pilot (Jordan recalls a Strength bonus and extra dice on Leadership: read the 11th-edition army rule on Wahapedia, never copy its wording). Then the 36 armies' rules with a one-line "how we'd model it / can't yet" each, and the order to write them (by share of winning lists). Report plus the Tyranids file; wired into T-524's V2 numbers if time allows. Done 2 Oct (report and pilot): docs/data/armyfx.json with Tyranids written (Synapse, Shadow in the Warp), and tools/tiertest.js --armyfx. Report at reports/tiers/2026-10-02-armyfx.md, with a one-line plan for every army's rule (surveyed on Wahapedia, our words) and the order to write them. Wired into V2, it lifts ρ from 0.127 to 0.146 but takes Tyranid S letters from 6 to 25. Lesson: army rules go into letters only once every army's are written; Battle-shock weighs too much in Anvil, so damp it. New engine vocabulary needed: target Toughness −1, S>T and S≤T conditions, Rapid Fire-only, a save capped at 3+, a single-die re-roll. Waits on Jordan's read. Checked 2 Oct on Jordan's question (11th edition, not 10th): every page read was the 11th-edition one. Oath of Moment as it stands there: every Adeptus Astartes army re-rolls hits against the Oath target; +1 to wound only with a Codex: Space Marines detachment and no Blood Angels, Dark Angels, Deathwatch or Space Wolves units. The errata dropped Black Templars from that list, and Black Templars armies take Templar Vows instead. A leaked future change isn't on the page; re-check at the next balance update.

Child of T-523; a report, no site change. Today: GEQ, MEQ, TEQ, a light vehicle (T10 W12 3+), a heavy vehicle (T12 W16 2+); small arms, special, plasma, elite, anti-tank; equal weights; the neutral table. Jordan: "are we oversimplifying, are we missing anything?" Test with the real data, reporting the units that change letter under each and the agreement with the community list: (1) a big target with an invulnerable save (T11-12, W18-20, 3+, 4++: Knights, Daemon Princes, wraith constructs, big monsters); (2) a tough horde (T5, 5+ or 6+, W1-2); (3) a mortal or devastating-wounds attacker (saves ignored, Feel No Pain counts) and a precision attacker (character sniping), so FNP, invulnerable saves and Lone Operative count in Defense; (4) meta weights: each target weighted by the points share of winning lists' units in its class (unitType and stats), each attacker by the share of the weapons winning lists carry in its class (from their loadouts), refreshed with the corpus; the weights and their effect against equal weights; (5) how much cover and half range move the letters. Recommend a set (5 to 7 targets, 5 to 7 attackers, weighted or not) with reasons, noting the cost of more columns on the unit pages and the calculator's five stand-ins (app.js STAND_INS must stay in step). reports/tiers/<date>-archetypes.md. Done 2 Oct (report): reports/tiers/2026-10-02-archetypes.md, with tools/archetypes.js. The best single change is a mortal-wounds attacker (ρ with list share 0.119 → 0.136). The lists field big targets with a 4++ or 5++ (15% of points) more than plain tanks (8%). Weighting by the meta makes agreement worse (0.088): keep equal weights. Cover on lifts agreement (0.134); half range doesn't. Recommended: six targets (the heavy vehicle swapped for a big 4++ target, plus a tough horde) and six attackers (plus mortal wounds), equal weights: ρ 0.147, 295 letters changed. The cost: a column more on the unit pages, and app.js STAND_INS and tools/targets.js changed together, as a build card once Jordan picks.

Child of T-523; mockup-stage, after T-524. Jordan: "this extra metadata is super interesting to math nerds and should be on full display when someone clicks a unit's page… land on the Tyranid Prime and recognise: attached to each squad it can lead, here's the damage multiplier, here's the anticipated damage output, for each squad against each of our five enemy types; and it's still a real beatstick." Mockup as an Artifact, 390px and desktop, both themes, the Tyranid Prime as the example. (1) Under the letter and job tag ("A · Banner"), a "Why this letter" block: the four job bars with each one's raw ingredients in a line (Offense 71 · survives 2.4 turns → damage before death 84; Defense 55 × OC 2/pt × Ld pass 72% → Anvil 48; …) and which job earned the letter. (2) For characters, the Banner table: a row per squad it can lead, a column per target; each cell "without → with (×1.6)"; per row, per 100 pts of the character and "beats N more bodies: yes/no"; the best squad highlighted and named ("best with Termagants ×20"); defensive effects as a second compact set of rows (hits to destroy without → with); its own attacks as "and on its own: Hammer 63, a real fighter" with the melee numbers. (3) Army-rule and detachment contributions as labelled lines (T-530), each a chip that explains itself on a tap, in our words. (4) Everything also in plain text for Google, a "How we score" link, no statlines or profiles (the kill switch rule stands): only our derived numbers. Stop at the mockup for Jordan's yes.

Child of T-523; a report, no site change. Generalises T-062's leader lift into the Banner job. For each character and each squad it can lead (BSData's Leading links): the squad's damage into all five targets with the leader's effects (leaderfx.json) on and off (Offense's rule, best loadout), and its hits to destroy from the five attackers with the defensive effects on and off; the leader's own attacks count (it fights with the squad). Added value per point: the damage and durability gained, each in Offense's and Defense's currencies, over the character's points. Better than bodies: against spending those points on more models of the same squad (up to the datasheet's maximum); a Banner earns the job only if it beats bodies, and the ratio is reported. The score is the best squad's result (or the mean of its top two), percentiled; the squad is recorded ("best with Intercessors ×10"). Auras assume 2 units in range, detachment- or army-wide effects 3; transports a proxy (the carried squad's Hammer × a modest factor); a CP valued once as the average worth of the core stratagems we can model; the report says which are modelled and which are proxies. Coverage first: characters with effects in leaderfx.json (offensive, defensive, both, neither) and the leaders taken in winning lists that have none yet (the next hand-writing batch, like T-343). Output reports/tiers/<date>-banner.md: every character's Banner score, the top and bottom 20 with best squad and multiplier, Mortarion's aura, agreement with the community list on characters; its numbers feed T-524's V2 Banner job. Built 2 Oct: tools/banner.js, report at reports/tiers/2026-10-02-banner.md (/lab/reports/tiers/2026-10-02-banner/). Coverage: 451 non-Legends characters; 184 have dice effects (127 offensive, 44 defensive, 13 both), 129 an entry without dice effects, 138 none; 291 lead or support a squad we could score (Support characters added on 2 Oct after the public list showed them missing). 203 of those beat bodies. ρ with list share among characters is 0.060, against 0.052 for today's support part. Gap list: 85 characters taken in winning lists with no dice effects yet (Logan Grimnar, Lucius, the Coldstar Commander, the Dawneagle Shield-Captain and the Swarmlord head it): the next hand-writing batch. Fed into T-524's V2 (--banner), it lifts V2's ρ from 0.113 to 0.127 and Mortarion from C to B. Proxies stated: auras, transports. Army-wide effects and CP aren't modelled. Waits on Jordan's read.

Child of T-523; a report, no site change. An independent 11th-edition tier list on GitHub that reads the same BSData: Monte Carlo damage, damage and survivability per 100 pts with a "melee tax", a utility score, min-max normalisation, percentile tiers (README in Russian). Read their scoring code (src/tier/, src/combat/): survivability on their bounded scale, the melee tax, the utility flags, the 2,000-point cap, Legends. Compare with ours on 30 shared units: where we disagree and who's right by the tier test's community list. Note what's worth adopting (as our own implementation, never their code) and what we think is wrong. List what we have that they don't (jobs, leaders, detachments, meta kept separate, the calculator, the Lab) for the Method page and a future Reddit post. Output reports/tiers/<date>-stcrafter.md, linked from /lab/reports/. Done 2 Oct (report): reports/tiers/2026-10-02-stcrafter.md, with tools/compare_stc.js. Their code was read at e8298cf and their output built offline (939 shared units). They edge us on list share (ρ 0.154 against our Value's 0.140) and are more often right on the big disagreements, because they credit cheap units with Scouts, Infiltrators or Deep Strike (our V2 Runner is the fix). We're right where their squad sizes break (Terminators, Sternguard and Eradicators scored as one model). The report lists five ideas to take as our own (targets from the data, a floor term, a tier-stability test, price-band durability, once-a-battle shown as a difference), their rules errors, and what we have that they don't. Waits on Jordan's read.

First child of T-523; a report, no site change (no change to rankings.json or any page). Built 2 Oct: tools/tiertest.js gives every unit today's letter (Value lifted by the meta), the maths-only letter (Value, fixed bands) and the proposed one (Hammer = Offense; Anvil = Defense's hits-to-destroy × the unit's OC, ranked, a product so no weight to tune; Banner = Utility's four parts weighted and ranked over every unit; composite 0.75 × best + 0.25 × mean; S 7% / A 15% / B 28% / C 30% / D quotas, S and A split by the jobs' share of the winning lists' points). Report at reports/tiers/2026-10-02-space-marines.md, rendered at /lab/reports/tiers/2026-10-02-space-marines/ and linked from /lab/reports/. Findings: 264 units wear S today (80 by Value alone; the quota holds 81); job split 37 / 40 / 22% (S quotas 30 / 33 / 18); fitted Banner weights board control 0.7, reach 0.2, support 0.1, action economy 0, ρ with list share 0.174 against 0.153 equal and 0.113 Value (all weak); Leaders and Auras twice as common among units players take that we grade C or D (Azrael D in 22 of 23 lists); global quotas leave Space Marines almost no S or A. Blocked: the public tier lists (goonhammer.com, reddit.com, tabletopbattles.com, tistaminis.com, spruesandbrews.com, belloflostsouls.net, spikeybits.com) are denied by this environment's network policy, so the agreement tables, the 15 biggest disagreements each way, the count of cited reasons and the test of the fitted weights on that list wait; a stand-in (one review's 11 best-in-role picks, names and roles only, through a search summary) is in the report. To finish: allow one of those hosts, then node tools/tiertest.js --community <file> (this report: add --named Mortarion --named-note reports/tiers/2026-10-02-mortarion-note.md --flip-note reports/tiers/2026-10-02-flip-note.md --picks reports/tiers/2026-10-02-space-marines-picks.json --summary reports/tiers/2026-10-02-space-marines-summary.md) (names, letters, our paraphrase of each reason). Jordan's "rank 62" example is Mortarion (design session, 04:09Z): S today by the meta, B on maths, B under the proposal (Anvil 92, 110th of 341 Holders, S quota 33); the report's "acid test" section sets out what we miss on him (Host of Plagues' mortal wounds: a rule we don't model; Lord of the Death Guard's buffs: a synergy we don't model; the contagion aura: counted only as one aura) and proposes Utility v2's first two parts (passive damage as a hand-written effect; lift to nearby units); Death Guard is the faction to test once a public list is readable. All 44 meta-lifted S units with a Value in the 60s are listed too. Amended 2 Oct, 04:21Z (Jordan, via the design session): two versions side by side. V1 is the three domains above. V2 is four jobs from how a game is won: Hammer = damage before death (damage per turn × turns alive under typical fire, at most 5); Anvil = Defense per point × OC per point × the chance to pass Battle-shock × 1.15 for healers; Runner = reach, units per 100 pts, footprint and Leadership; Banner = a Leader's lift, auras, Transport and revives per point. Same composite and quotas. Offense and Defense stay the published raw pair under both. V2 result: job demand 49 / 18 / 17 / 16% (S quotas 40 / 15 / 14 / 13); ρ with list share 0.113 against V1's 0.174; 835 units change letter and 664 change job; V2 rates characters (25 of its 82 S units, none in V1) but overshoots cheap leaders through Runner; Mortarion is C under V2, B under V1. Recommendation in the report: V2's Hammer and Banner, V1's Anvil, and Runner only for units that act alone, tested against the community list once one can be read. Community comparison done 2 Oct (Jordan opened the network): Tista Minis' 11th-edition "Best Space Marine Units" (22 Jul), 30 units, ranks mapped to letters. Mean distance: today 1.40, maths 1.43, V1 1.43 (equal weights 1.47), V2 1.67. None agrees well, and V2 least. They rate close-range melta and flamer units, mission units, transports and support characters higher; we rate the slow, expensive efficient-on-paper units higher. Additions to the shopping list: Overwatch, melta within half range, delivery, support synergy, a price on slowness. The comparison also showed the Banner tool skipping Support characters, now fixed (T-527). Goonhammer and Tabletop Battles answer with a bot check, and Reddit refuses. Round 2 done 2 Oct (05:14Z brief): the yardstick within the army (rank order, and letters re-cut inside the army), V2b (Hammer as damage delivered before death), and a second panel list, Sprues & Brews' 11th-edition Orks codex review (22 Aug, 45 units, its verdicts graded by strength; worth about half a ranked list). A third could not be read: the candidates are behind bot checks or are videos. Both panel files are in reports/tiers/panel/. ρ with the list's order, Space Marines / Orks: today −0.31 / 0.24, maths −0.31 / 0.25, V1 −0.27 / 0.22, V2 −0.23 / 0.12, V2b −0.24 / 0.06. Answer: the fairer yardstick helps partly, and V2b doesn't help; V1 fitted is best overall. Mortarion and Ghazghkull go opposite ways (V1 holds Mortarion and drops Ghazghkull to C; V2 the reverse). Only today's meta-lifted letter rates both highly. Write-up: reports/tiers/2026-10-02-round2.md (/lab/reports/tiers/2026-10-02-round2/). Round 3 done 2 Oct (T-538): V3, with delivery modes, the Dedicated Transport bundle and four fixes. ρ with list share 0.164; Space Marines −0.18; Orks 0.18 (reports/tiers/2026-10-02-round3.md). Waits on Jordan's read. Round 3, V2c (2 Oct, a builder sub-agent on the supervisor's brief, with Jordan's refinements): V2c is V2b with six steps, each measured on top of the last: (a) mortal wounds from abilities (docs/data/mortalfx.json, 83 datasheets, our numbers; Devastating Wounds were already in ev.js); (b) Support characters can't be Runner or Anvil alone, Leaders can, but Runner counts survival (reach, turns alive and Leadership, plus cheapness and footprint at half weight; Lone Operatives' survival doubled); OC 0 can't be Anvil; (c) Battle-shock weighted by the share of the game spent below half strength; (d) Banner as beats-bodies per point for everyone (Leader multiplier, auras, transport capacity); (e) Indirect Fire from turn 1 (no effect); (f) the diagnosis: V2b multiplied per-point damage by absolute survival, so big units won on size. Turns alive now come from durability per point, a unit is exposed only on the table outside a transport, and a unit rides only where a Dedicated Transport can carry it and the pair beats both parts per point (Jordan's bundle test). Numbers: Space Marine ρ with the public list −0.24 → −0.08 (mean distance 1.57 → 1.43), ρ with list share 0.087 → 0.137, Orks 0.06 → 0.01, Tyranids (Auspex Tactics' list, the third panel file, reports/tiers/panel/tyranids-auspex.json) 0.07 → 0.21 (Value 0.33, today 0.65); almost all the Space Marine gain is durability per point. Mortarion C → S (2nd of 36). The first session's V3 (above) scores −0.18 / 0.164 / 0.18: V2c is better on the Space Marine list, V3 on list share and Orks, and both reach 0.21 on Tyranids; both are in the report. Verdict: partly. The test cases still miss for reasons that are rules, not dice: Biovores (Spore Mines), the Venom (split squads) and Eradicators (the target average). The open questions are how to price size and Runner for big durable models. Report: reports/tiers/2026-10-02-space-marines.md, "Round 3". Constants and rules in design/scoring.md. Waits on Jordan's read. Round 4 done 2 Oct (a builder sub-agent on the supervisor's brief, with Jordan's step g and Tyranid section): V4 merges the strands (V3's arrival modes and the bundle with the beats-both-parts test; V2c's durability per point, exposure on the table, mortal wounds, Battle-shock damping, the Support/Leader rule, Banner per point, Indirect Fire), adds no charge after an advance (11th-edition core rules), Runner's points gate (1 up to 75 pts, 0 at 260), solo characters' turns alive × 0.5, and step g (Hammer as enemy points destroyed, ppw, weighted by the meta's target classes, peak plus breadth, tagged anti-tank / anti-elite / anti-chaff); every part a switch, each measured by leaving it out. Numbers: Space Marine ρ 0.04 (first positive; V2c −0.08, V3 −0.18), distances 1.33; Tyranids 0.19 (both strands 0.21); Orks −0.19 (V3 0.18); list share 0.104 (V2c 0.137, V3 0.164). Mortarion is no longer a Runner (B · Hammer); the Lieutenant with Combi-weapon keeps C; Eradicators D → C (anti-tank), Hive Guard S; the Chaplains stay B or A (Banner carries them now). Panel ρ has a standard error of 0.15 to 0.19, so most single-panel differences are noise. Verdict: partly. Lessons: merging didn't add the strengths; the gate exposes the size question (Ghazghkull C, Wazdakka D); the Chaplains are a Banner problem (lift credited on squads nobody fields). Tyranids against the Auspex list: every graded unit, the 20 biggest disagreements diagnosed, a plain paragraph; reports/tiers/2026-10-02-tyranids.md. Report: reports/tiers/2026-10-02-space-marines.md, "Round 4". Waits on Jordan's read; no round 5 until then. One army until the variables are found (Jordan, 2 Oct, via the supervisor): "For the purposes of ironing this out, stick to Tyranids until we can identify all the variables." The tier work now iterates on Tyranids alone, judged by the Auspex panel list, Tyranid list share and Jordan's own reading (he plays Tyranids, so he can say when a number is wrong); each missing variable is named and modelled one at a time until the Tyranid table is explained. The Space Marine and Ork panels run only as a check at the end of a round, never to steer it. 2 Oct, every domain shown (Jordan: "are we not scoring all domains anymore?"): reports/tiers/2026-10-02-tyranids.md now shows, for every Tyranid row, the four V4 job percentiles, raw Offense and Defense per 100 pts with their percentiles, turns in reach, turns alive and the arrival mode. It adds five-turn profiles, every arrival mode and the cost of each Hammer term for Raveners, the Red Terror, the Neurolictor, Biovores, Hormagaunts and Von Ryan's Leapers. Raveners' and the Red Terror's Hammer is sunk by turns alive (living all five turns would make each an A), not by step g. The Neurolictor misses A in Runner by 0.1. The rules list became T-540. Round 5 done 2 Oct (a builder sub-agent on the supervisor's brief, Jordan's eight variables, Tyranids first): V5 = V4 plus (1) survival absolute, (2) arrival rules, (3) a mortal-wound attacker with the attackers weighted by the meta's incoming fire (small 8 / special 20 / plasma 37 / elite 7 / anti-tank 22 / mortal 6%), (4) enemy debuffs and Battle-shock as Banner, (5) buff auras and Synapse through the engine on the squads co-listed in winning lists (tools/colist.js), (6) leader pairs shown, (7) detachment context with Singular Purpose and the floor letter, (8) one-use units, CP at 15 pts, Biovores' spawning; plus (9) Banner's smooth start, found this round. The non-dice rules are in docs/data/tierfx.json (our words, not loaded by the site). Each switch was measured alone and stacked on the Tyranid units against a frozen pool. Numbers: ρ with Auspex 0.19 → 0.38, same letter 14 → 16 of 44, within one 26 → 31, ρ with Tyranid list share 0.12 → 0.24 (today's letter 0.65 / 21 / 37). Check: Space Marines 0.04 → −0.01, Orks −0.19 → −0.12, list share 0.104 → 0.129. Norns C → S, Hive Guard S → A (not a Sleeper), Biovores D → C, Hive Tyrant and Neurotyrant C → B, Ripper Swarms A → C. Verdict: partly. Still unexplained: Raveners, Hyperadapted Raveners and the Red Terror (re-deploy and Rapid Ingress stratagems, and detachment movement rules not yet in detfx.json); the support monsters' worths (CP, Battle-shock, debuffs: stated guesses for Jordan to set); the Tyrannocyte (V2c's capacity credit). Report: reports/tiers/2026-10-02-tyranids.md, "Round 5". Waits on Jordan's read. Detachment movement rules (T-541, the supervisor's decision, 2 Oct): written in detfx.json under move, not tier. Read as written, they lower agreement until their worths are set (tunnels, Crusher OC, Feed the Swarm: V5's ρ 0.38 → 0.28, 15 letters move); the worths are Jordan's to set, so round 5's result stands. Coverage re-run (2 Oct, after T-542): V5 with every kind and every Tyranid unit's own abilities: 1 letter against the last V5 + kinds run (Venomthropes C → B, Foul Spores), 5 against V5; ρ with Auspex 0.39 → 0.39, same letter 17 → 18 of 44, within one 30, list share 0.24 → 0.23. Sitewide 0 letters move: the tier test reads no other army's coverage (own abilities and kinds are Tyranid-only, --armyfx reads only the Synapse pilot's shape), so the frozen-pool caveat stands; --armyfx as it is double-counts Synapse and lifts 26 Tyranid letters, so it stays off. Report: reports/tiers/2026-10-02-coverage-rerun.md and the Tyranid report's "Coverage re-run". Next: the tool re-scoring every army with its coverage (another builder's), then Jordan's constants (CP, Battle-shock, debuff share, movement rules). Every army scored (T-552, 2 Oct): with every unit carrying its own abilities, kinds, army rules and best detachment (--every), Tyranids against Auspex ρ 0.39 → 0.37 (same 17 → 13, within one 30 → 23), Tyranid list share 0.24 → 0.28, Space Marines −0.01 → −0.05, Orks −0.12 → −0.14, every unit's list share 0.129 → 0.156 (0.173 before detachments); 423 of 1,161 letters move by army (Space Marines 45 up, Tyranids 27 down). reports/tiers/2026-10-02-tyranids.md, "Every army scored".

Parent card; nothing under it builds until Jordan says so. From the brainstorm with Jordan: three job domains per unit, each a percentile over all non-Legends units: Hammer (today's Offense), Anvil (durability weighted by objective control per point; plain Defense stays a shown number), Banner (today's Utility: board control, action economy, reach, support). Composite = 0.75 × best domain + 0.25 × mean of the three; the unit's job is its best domain, a second job when another is 80 or more. Letters by quota on the composite's rank, not fixed cut-offs: S top 7% (about 85 units), A next 15%, B 28%, C 30%, D the rest; the S (and A) quota split across jobs in proportion to how much of a winning army each job makes up (points share of top-quarter lists by job), so each job's S is as scarce as armies' demand for it. Meta leaves the letter entirely: a pixel crown with list share, and a one-word read where they disagree (Safe pick, Sleeper, Workhorse, Pass). Utility's part weights fitted to list share given Hammer and Anvil. Children: T-524 (the test, first; Jordan wants its result before committing to the redesign, and before the mockups). 2 Oct, 04:21Z (Jordan): two versions are tested side by side (T-524): V1, the three domains, and V2, four jobs (Hammer as damage before death, Anvil, Runner, Banner). Offense and Defense stay the published raw pair under either design ("quite solid math… more data is better"), shown on every unit page and Rankings row with their percentile chips. The jobs are built from them and never replace them. Damage before death becomes a third shown number if V2 is adopted. The letter and the job tag are what count. Names (Jordan, 2 Oct, via the design session, 04:29Z): the four jobs are Hammer (hitting), Anvil (holding), Runner (running the secondaries) and Banner (enabling others). These are our own words, not GW keywords. A unit's tag reads "S · Hammer" or "A · Banner", and code uses hammer, anvil, runner and banner. Jordan's aim (1 Oct (Pacific), via the design session), in his words: "my dream is that our calculator accounts for so many scenarios, interactions and rules that when people come up with consensus tier lists, our rankings map closely; where there's discordance there's a good reason or acceptable variance. Then we'll find things others don't, and they'll look to us for leads." The calibration score (T-533) measures the first half; Sleepers (T-534) the second. One army until the variables are found (Jordan, 2 Oct, via the supervisor): "For the purposes of ironing this out, stick to Tyranids until we can identify all the variables." The tier work now iterates on Tyranids alone, judged by the Auspex panel list, Tyranid list share and Jordan's own reading (he plays Tyranids, so he can say when a number is wrong); each missing variable is named and modelled one at a time until the Tyranid table is explained. The Space Marine and Ork panels run only as a check at the end of a round, never to steer it.

Built 2 Oct: (1) Patch detection, tools/patches.js: the daily refresh now builds the BSData commit the site was on beside the new one, ranks both with today's code, and adds the update to docs/data/patches.json: per unit its points at the smallest size before→after, the *names* of the fields that changed (a stat's letters, <weapon>: AP, +/- a weapon, size, keywords, abilities; never values), our Value score and tier before→after, and the units added and removed. 15+ units with points or profile changes (Legends aside, a unit shared by armies once) is a balance update. Backfilled from 24 Aug: the 5 Sep points update (BSData 46d8cc5→074eabc) is a balance update, 145 units (128 points, 62 profiles; 5 added, 24 removed, the Legends cut); 19 Sep 13 profile fixes; 27 and 30 Sep nothing that moves a unit. (2) Search demand, tools/demand.js (Search Console helpers shared with the weekly pull in tools/gsc.js): each day's searches, three days behind (the last three pulled again), and the live site's matchups per unit and pair from the data Worker's new GET /tests?day= (names and counts only), into reports/analytics/demand.json, 90 days rolling; daily by .github/workflows/demand.yml (14:37 UTC, 07:37 Pacific, [skip ci] like the weekly report). Searches are matched to our unit names at read time (whole name, name without "Squad", a long first word only it starts with; a phrase two units share finds neither; an army's word is never a unit; a Legends unit needs two words), so 26 of the weekly pull's 30 searches find their unit; the other four name none (two calculator searches, "centurion", which two squads share, and "hunter clade"). Seeded from the weekly pull's 28 days until daily days exist. (3) The pulse, tools/pulse.js → reports/analytics/pulse.json: patch (1 per 10% points, 1 per 5 points of score, ½ a tier step, ½ a profile change) + search spike (last 7 days against the 28 before, smoothed by 5; a level until 14 days are kept) + the same for tests; top 20, each with its three most tested opponents over 28 days, else its best and worst standard targets; a top unit and its first opponent is a suggested clash page (with no tests yet, its best standard target, marked stand-in). (4) Report: a "Patch pulse" section in tools/report.js (so /lab/reports/) and a Monday paragraph in the weekly analytics; names and numbers only, the searches stay in reports/. Tests: pulse.test.js (a made-up update through the detector, the matcher on real searches, the pulse ranking a moved and searched unit with its tested opponents), the Worker's /tests in dataworker.test.js. First real pulse (2 Oct): last balance update 5 Sep, 145 units; top movers Warbuggies (80→70 pts, tier D→A), Painboy (90→45), Wolf Guard Headtakers (profile: size and invulnerable save), Zodgrod Wortsnagga (80→50), Warboss in Mega Armour (80→125, A→B), Bannernob (50→35), Big Mek in Mega Armour (80→90), Squighog Boyz (profile), Hunta Rig (125→165, S→A), Mek Gunz (45→55); 15 of the top 20 Orks (their faction pack came with that update). Searches: the seed only; tests: none yet. On beta (2 Oct, main frozen): the Worker's /tests, the refresh's patch step and the daily demand job only run from main, so they start when beta goes to main with Jordan's OK; search spikes from about 14 days after that.

A unit name with pages in more than one army: the home army's page (build_pages.js homeRank, the rule exact copies already use) keeps the plain name, each other army's page says "{unit} ({army}) 11th Ed: …". Pages stay self-canonical (their scores differ by army rules); a build check that no two indexable pages share a title. Built 6 Oct, on beta for review: 226 unit pages name their army (exact copies already canonical elsewhere included) ("Chaos Rhino (Death Guard) 40k 11th Ed: Points & Best Loadout"); the 14 detachment pages whose name has a page in two armies (Drukhari's and their Aeldari copies) say "Skysplinter Assault (Drukhari): Best Units & Meta" (det.titleArmy). Sitemap pages sharing a title: 49 groups (120 pages) → 0; build_pages.js warns if any come back

Falls back to "{unit} 11th Ed: Points & Best Loadout", then "{unit} 11th Ed: Points, Loadout"; units without loadout choices "… Points & Tier". "11th Ed" in every step, "Damage" dropped. Was "{unit} 11th Edition: Points, Best Loadout, Damage" with a fallback that lost "11th Edition" on 28% of pages. T-721's description rewrite and gallery stay open. Built 6 Oct, on beta for review: unit titles without "11th Ed" 299 → 1 (a 52-character name), with "40k" 0 → 1,016 of 1,083; none over 60

stamp_assets.js writes each copy; Built 6 Oct, on beta for review: /trends/ and /rankings/ name /meta/ and /factions/ as canonical (and og:url) and leave the sitemap (1,397 → 1,395 URLs); on /army/ and /lists/ their screen's heading is the h1 ("MY ARMY: RATE YOUR 40K LIST", "WINNING 40K TOURNAMENT LISTS") and the calculator's becomes an h2; the headings and their one-line intros are reworded on every copy, so the screens read the same whichever address opened them. Not done: /matchup/ (the review suggests canonical to /) and a crawlable index of the 85 winning-list pages on /lists/ (the review's H5, second half)

h1 "40k Damage Calculator (Mathhammer) for 11th Edition"; the brand stays the site name; links to the tier lists, /best/ and /mathhammer/. Built 6 Oct, on beta for review: the logo is a span (.brand-wm, as the static pages have it), the h1 sits above the introduction, which names "40k calculator" and "mathhammer" and links /meta/, /factions/, /best/ and /mathhammer/; layout.js still moves both below the calculator, so the screen opens as before. The tabs' copies lose the brand h1 too (T-772)

1,000 rows sorted by impressions for queries and pages, a query × page pull, devices; the report gains "high impressions, CTR under 2%", "position 5 to 20" and "queries with two or more of our pages" tables. Plausible devices too. Moving demand.yml's schedule to main stays Jordan's call. Built 6 Oct, on beta for review: Search Console has no sort, it sends rows by clicks, so the pull asks for its most (25,000) and keeps the most seen: 1,000 queries, pages and query × page pairs over 28 days, 250 over 7, and devices; the report adds "Seen often, under 2% clicks" (20+ impressions), "In reach of the first page: positions 5 to 20", "Searches two or more of our pages share" and devices; Plausible adds devices and the pages visits from Google land on (visit:entry_page, source Google). --from latest.json renders the report again with no keys (checked on the 5 Oct pull and a made-up one; the live APIs are first called by the next Monday run, which only runs from main)

GitHub Pages can't 301: a small page with a canonical to the army's page and a link on, out of the sitemap. Built 6 Oct, on beta for review: Legacy of Grace is a Blood Angels detachment (the 3 Oct data stopped offering it to Space Marines, and Blood Angels have no detachment pages), so the old address names /factions/blood-angels/ as canonical and goes there at once (meta refresh, which search engines read as a redirect); not noindex, so the redirect carries. build_pages.js MOVED holds such addresses, skipped if the data makes the page again. Already 404 on the live site since main took the 3 Oct data

Not yet: only detachments (detfx.json) and joined characters (leaderfx.json) change the dice; a unit's own datasheet abilities don't. Plan: unitfx.json, the same effect fields in our own words read from Wahapedia's 11e datasheets (never their wording), most-played units first (the corpus's top units, then each army's); always-on abilities apply by themselves, conditional or once-a-battle ones (a Plasmacyte's boost, charging, below half strength) as chips on the unit's Modifier tab, off by default; rankings and ev.js read them the same way Batch 2 (1 Oct): the next 38 most-taken units in data/unitfx.json, read on Wahapedia and written in our own words: 17 change the dice (Crisis Fireknives and the Riptide ignore hit modifiers and re-roll, Hekaton, Hearthguard, Jain Zar against characters, Morvenn Vahl's Miracle attacks, Wardens, Sacresants and Scarab Occult −1 to wound, the winged Slaanesh Prince −1 Damage, the Khorne Prince's Devastating charge, Exalted Eightbound +1 Damage into monsters and vehicles, Eightbound +1 to hit, the Nurgle Prince's cover, the Lord of Virulence's re-rolls, the Neurolictor's +1 to wound, the Defiler's Daemonforge), 21 noted as not touching the dice. 78 units in all. Batch 3 (1 Oct): the seven whose Wahapedia address differs, as ten entries (both Bloat-drones, both armies' Manipulus, both Terminator Sorcerers): the Enforcer Commander's weapon support system ignores hit modifiers, the Chaos Sorcerer's Death Hex gives +1 AP and the Thousand Sons one's Marked by Fate +1 to hit against the unit picked, the Thunderkyn's conversion beamers score critical hits on 4+ beyond 12"; the rest noted (once per battle, movement, Stratagem costs; their leading abilities are leaderfx.json's). 88 units in all. Batch 4 (1 Oct): each army's next two most taken (in two or more top lists), 48 units: 17 change the dice (Be'lakor re-rolls 1s to hit, Angron ignores hit modifiers in melee, the Canoness with Jump Pack's and the Captain's once-a-battle +3 attacks with Devastating Wounds, Bladeguard's pick of +1 to hit or −1 to be hit, Assault Intercessors, Custodian Guard and Purifiers re-roll wounds (all of them on an objective), Corsair Voidreavers the same for hits, Death Company with Jump Packs re-roll hits in melee, Deathwing Knights −1 Damage, Wolf Guard Terminators −1 to wound against stronger attacks, Cawl's Machine Vengeance re-rolls and Shroudpsalm cover, Krieg's +1 to hit and wound as they fall, the Dreadknight's re-rolls into monsters and vehicles, the Beastboss's +1 to hit, Hyperadapted Raveners' Sustained Hits 1), the rest noted. A Space Marine chapter's list now finds the Space Marines' own units' entries (detfx.js), as its unit list does. 136 units in all. Batch 5 (1 Oct): every unit taken in four or more top lists once the chapters' lists count toward the Space Marines' own units (the Intercessor Squad was in 13), 30 units: 6 change the dice (Company Heroes −1 to wound while a character leads them, the Phobos Lieutenant's objective re-rolls, the Lokhust Heavy Destroyers' wound re-rolls of 1, the Silent King's Triarch ability as a pick, Boyz' once-a-battle +1 to hit when shooting and Lethal Hits on the charge), the rest noted. Hail of Bolts (+2 attacks for the Intercessors' bolt rifles) waits on effects for one weapon only, carded as T-516. 166 units in all. Still to read: the units taken in three or fewer (380)

Every weapon family in build/units.json (keywords and name families, ranged and melee) with a proposed effect each (particles, count, colours, spread, duration, muzzle/impact, a one-line feel); Jordan: flamers "way more flames"; bio-spray cannons and alien torrents "lots of effects and be purple in colour"; melee its own set (slashes, sparks, arc flashes, shockwave rings, impact bursts, bites); "the more toggles the better": a switch per family under Weapon effects with a master switch; colour from the faction palette except bio-weapons (purple). Deliver design/weaponfx.md (the table, match rules, counts, leftovers) and a preview gallery (2–3 frames each) for his phone; no change to shootout.js beyond a sandbox. Our own drawings only Proposed 30 Sep: design/weaponfx.md (30 families, 21 shooting and 9 melee, with counts from build/units.json, match rules in order, the 130 leftovers, where it would live and three questions) and the live gallery https://claude.ai/artifact/7sFr4pH868w6k8pZagNMMg (each family animated with its own switch and a master switch, army colours or natural, a 3-frame view; a copy in design/weaponfx-preview.html). Nothing in shootout.js changed. Waits for Jordan's picks Round 2, 30 Sep (Jordan, 30 Sep, reviewed with the design session): the catalogue is approved as the plan; the gallery went back and round 2 is at the same link (the battle's scale and figures, natural colours with Army colours as a toggle, dithered pixels instead of soft glows, the Tyranid split into eight families, dark light, rail and sniper, lasguns apart from lascannons, whips and hammers, crackle, hit-stop, weapons in hand, bites with jaws; 41 families). The rules moved to tools/weaponfx.js with tests/unit/weaponfx.test.js (the Fire Prism and Blastmaster fixes and each family's oddest members); design/weaponfx.md and the preview copy updated. The build is T-458 to T-463 once Jordan approves round 2 Round 3, 30 Sep (Jordan's review of round 2): most families approved as they were; new shotgun, grenade and bolter families; bio-sprays, plague, stranglers, venom and bio-plasmic cannons, plasma (straight through, burn marks), lasguns, gauss, rail and sniper, helfrost, warp (the dark ball), missiles, cannons, chain teeth, plague and burning blades and whips redone (44 families; design/weaponfx.md has the list and the readings chosen). Same link Round 4, 30 Sep (Jordan's review of round 3): melta, gauss, arc and lightning, helfrost, shotguns and bolters approved; flames curl up at the end; spinefist, spine-bank, shuriken and splinter spikes stay stuck; bio-plasma slimes; plasma stutters through each model; lasguns the lascannon's beam, thinner; rail and sniper through everyone with holes, a shock-coned dart and a longer trail; warp a trippy cluster of coloured orbs that spins and shrinks the target; missiles straight and snappy with wavy smoke and a debris crunch; rotary guns spray an area; bolters shake the target; all melee 1.5 times the size, twice the particles, shake and a longer hit-stop, accelerating swings; bigger bites with follow-ups and a monster's crunch; whips wind up and snap Round 5, 30 Sep (Jordan's notes on round 4): the rail and sniper dart slowed enough to see, a melee-style stutter at each model, smaller holes that fade, a spray of sparks at each hit, a longer linger; every target that stood still now flinches at least a pixel when hit (contact measured from each family's drawing) Round 6, 30 Sep (Jordan's notes on round 5): flames and bio-plasma widen to the tip; webs corkscrew; helfrost grows twice and shatters, leaving frost; the venom slug stutters and rips out the back, leaving slime; plague showers; lasguns one solid line; pulse sprays; the rail charges, then fires like lightning with 45-degree shock waves; warp proposed as an eye in a rift; missile smoke only rises; melee winds up slow and comes down fast; weapon effects run all the time; whips two long, heavy strokes; the monster bite shows Round 7, 30 Sep (Jordan's notes on round 6): melee rests at 30° on a clock face, a slower backswing to 315°, a strike to 120° over a frame or two with a smear, a slow return; chain teeth slower; bolters clear before the loop; artillery a six-shell burst in front, behind and on top with one big dust cloud; the missile's warhead flashes harder and its smoke stops short; warp charges and opens a big rift and four small ones, shaking the target; the rail's line burns and drips; lasguns two longer shots; bio-plasmic sludge; the venom slug passes right through and slimes the ground behind Round 8, 30 Sep (Jordan's notes on round 7): every family fades back to neutral at the end of its run (burning and dripping weapons keep going); the rail sticks in the first model for about a second, then rips through, leaving big molten holes and drips on the models only, one two-pixel colour for the line; warp charges in the hands and knocks the model's ghost out of its body, leaving it grey; the missile's flash stays inside its blast; melee strikes throw white, red and grey specks; whips add a third, heavy stroke with three hit bursts; the particle sliders (T-474) are in the gallery, all and per family. The rail (2.2 s) and whip (1.8 s) run past the volley's 1.4 s cap, a call for the build Round 9, 30 Sep (Jordan: "we're almost there"): the rail's pause in the first model halved (the run 1.8 s); the warp's spirit leaves the body plainly: a full, detailed ghost tethered to the body, rising, holding, then dissolving pixel by pixel into nothing (the run 1.7 s). Same link, and on the site at /lab/effects/ (T-465); waits for Jordan's sign-off

Reshaped 2 Oct (Jordan, 1 Oct (Pacific), via the design session): /meta/patch/ is the live page and the canonical, always the newest balance update; older ones archived at /meta/patch/<date>/ and listed at the bottom of the live page. T-519's data still feeds it. Winners and losers grouped Up / Down / New / Gone with our values before→after, and a faction toggle like /meta/'s (All / Imperium / Chaos / Xenos, then an army). At the top, the patch's top 5 units (the biggest winners by our score) in a King of the Hill: Jordan's words: "like the normal damage calculator where the attacker attacks the defender starting with shooting or melee. A queue of sprites of the units waiting their turn, bobbing up and down, five in waiting. On a podium or the top of a literal hill the current King stands with a crown on his head or a count over it. Each fight uses the calculator settings: both units at optimal loadout, To the death, fight back enabled. When the attacker kills the defender he moves to the defender slot and a new enemy moves in. When the defender wins the attacker goes to the back of the line. If the defender fails to kill the attacker, the attacker wins. Just automatic but real calculator output and funnel." Spec: the King (defender slot) on the hill with a crown sprite and a reign counter (bouts survived); up to 5 challengers at the foot, idle-bobbing in order (our figures, hero sprites where they exist). Each bout a real run of the engine: Auto-equip's best loadout for both, To the death with fight back, the challenger opening with Shoot if it has ranged weapons, else Melee; the funnel compact beside the hill and the pixel volley played on the hill. The unit that dies goes to the back of the queue at full strength; a stalled fight (no death within the engine's turn cap) is the challenger's win; the winner takes or keeps the hill. Runs on its own while in view, pauses out of view, one bout at a time at the volley's pace, Skip and Pause; reduced motion shows the standings only. Under it the standings (longest reign this run, each unit's wins and losses) and "Run this bout yourself" into the calculator on the current pair. Seed: the top 5 by score change; a shuffle button. The same component on /meta/ with the top 5 meta units, in place of T-518's daily Clash strip. Amended 2 Oct (Jordan, via the design session, 02:34Z): (1) the crown is a pixel crown in figures.js's style (a few tones, crisp at whole pixels), never an emoji; the reign digits, the queue's places and Pause/Play are our pixel glyphs too (pause and play join icons.js; Skip and Shuffle use its skip and swap). (2) Two hills, same layout, a tab each: Shooting (volleys only, alternating, challenger first, no melee at all; seeded by the top 5 by our ranged score) and Melee (the charge and the fight only, no shooting, not even an opening volley; seeded by our melee score). A unit strong in both is on both; a unit with no weapons in a lane never enters that hill. Stall rule: no death by the turn cap goes to whoever dealt more damage (ties to the challenger). Default tab: the lane with the bigger total score swing in the update (5 Sep: ranged 722 points of percentile score moved, melee 572, so Shooting); Shooting on /meta/; the last tab remembered per device (a small new key, hre.koth.v1, into CLAUDE.md's key list when built). A mixed hill was considered and left out: Jordan chose two clean lanes (a shooting unit stuck in melee "beating its head to do zero damage" is boring). Amended again 2 Oct (Jordan, via the design session, 02:40Z): weight classes, like boxing (a cheap unit "won't hold a candle to a Titan"): by the points a unit fights at, cut for roughly equal thirds of our 1,106 units (non-Legends rankings rows): Light up to 75 pts (363 units), Middle 76 to 130 (395), Heavy 131 and up (348; wide, 135 to 3,500 pts, median 180, 22 over 500). The design session's first cuts (120 / 250) would have split 707 / 283 / 116. The class is a second selector beside the Shooting / Melee tabs (pixel glyphs: one figure, a squad, a walker), six hills in all, one on screen. Default class: the one the update moved most (5 Sep: Middle, 660 points of lane score, against Light 582 and Heavy 302); Middle on /meta/. A unit enters only its own class; bouts run at each unit's real points. Seeding per hill: the update's top 5 risers in that class and lane, among units scoring 50 or more in the lane (so a tank's tracks don't make it a fighter); a hill with fewer than 3 fills from the meta's units of that class and lane. Standings show each unit's points and its wounds dealt per 100 pts. The last hill and class remembered per device (hre.koth.v1). Rejected: stacking cheap units up to the King's points (three squads against a Titan): the engine fights one unit a side, and stacking hides what the hill is for. Layout settled 2 Oct (Jordan, via the design session, 02:50Z): three pages, one component. (1) /hill/, King of the Hill's own page (title "King of the Hill: 40k units fight to the death, 11th edition"), the one people share: lane tabs, class selector, the hill, standings, the calculator; ?seed=patch or ?seed=meta. (2) /meta/patch/ stays its own page (title, date, Article): at the top a compact "On the hill now" strip (one bout of the default hill, no selectors, "Watch all six hills ›" to /hill/?seed=patch), then winners and losers with the faction toggle, then the archive. (3) /meta/: under the podium, a card "Last balance update: <date> · N units changed · biggest winner X, biggest loser Y ›" to /meta/patch/ (5 Sep: Warbuggies, our Value 12 → 78; Squighog Boyz, 85 → 48), and the same compact strip seeded by the meta, to /hill/?seed=meta; Meta's own sections as in T-518. The hill is illustrative, the calculator demonstrative (Jordan: "a fairly static picture of the unit with the slightly larger heroic sprite on top of the hill, the queue slowly ascending the hill and trailing off it; as they fight there is also a calculator, just like on the calculator page, that populates the full unit"): the King's hero sprite (T-378's where the army has one, else its figure a step larger) on the summit under the pixel crown, idle breathing only; one figure per waiting unit walking up the slope, the challenger at the brow, the rest trailing off the left edge; the loser walks down and off, the winner steps up; no damage on the hill. Amended 02:56Z (Jordan): the queue climbing the hill is hero sprites too (T-378's, in their four-step walk at the hero's normal scale), not the battle figures; the King is the same hero a step larger under the pixel crown. Gaps: every look (23) and every army already has a hero, so none is missing; but there is one hero per army, so a hill of five Ork units shows five identical Ork heroes (the name tags tell them apart; on a phone only the King's and the challenger's show), and vehicles, monsters and riders walk as their army's hero on foot. Proposed follow-up, not drawn: a hero per figure slot (vehicle, monster, walker, rider, flyer) for each look. Below, the calculator page's own result card for the bout: both units at full size, the funnel, the pixel volley with weapon effects, the To the death round strip with fight back, the result; Skip/Pause in place of Simulate; "Open in the calculator" takes the pair to /. Weapons at their most effective: each side's loadout solved against this opponent (most expected kills on it, not the all-rounder), the best profile per target, every free modifier that helps (the lane's own abilities, unitfx); one line under the result: "Both at their best loadout against each other." Selectors and standings beside the hill on desktop, between it and the calculator on a phone. Article with dateModified; linked from /meta/ and each changed unit's page. Mockup first (390px and desktop, both themes), then stop for Jordan's yes. Mockup 2 Oct, waiting on Jordan: https://claude.ai/artifact/FR8sqwMYA6nx6qKhRsmnKv (/hill/ and /meta/patch/, the settled layout; two hills × three classes; e.g. Light shooting: Warbuggies, Weirdboy, Mek, Warbikers, Warlock Skyrunners; Heavy melee: Battlewagon, Breaka Boyz, Beastboss on Squigosaur, Khorne Berzerkers, War Dog Karnivore; the pixel crown; bouts from our expected-value engine, the real one rolls dice; winners and losers with the group and army filter; the archive). Built before the reshape (2 Oct, on beta, 81b9d7ba): a page per update at /meta/patch/<date>/ with an index at /meta/patch/; the grouped tables, the /meta/ line, the unit-page line, the Article and test unit/patchpage carry over; the live page, the faction toggle and King of the Hill are the new work. Built on beta 2 Oct (Jordan: "yes, build it on beta"): /hill/ (six hills: Shooting and Melee × Light, Middle and Heavy; Patch and Meta seeds; the King's hero sprite a step larger under our pixel crown, the queue walking up as hero sprites, pixel digits; standings with points, wins, losses, longest reign and damage per 100 pts; Pause, Skip, Shuffle; the last hill, class and seed in hre.koth.v1) and under it the calculator's own result card, a real run each bout through the calculator in a frame (/?hill=1, TRHill.bout: each side's loadout solved against its opponent in the lane, To the death with fight back, the volley and funnel; no counts or analytics from the frame). /meta/patch/ is the live page (the newest balance update; older ones at /meta/patch/<date>/ under "Earlier balance updates"), with the "On the hill now" strip, winners and losers in Up / Down / New / Gone and the group and army filter; /meta/ has the update's card and the meta's strip. The strips show one bout from our expected values (illustrative), the full hill rolls dice. Lane scores per update (ls in patches.json) come from tools/patches.js. With Legends and Crucible out, the classes hold 333 / 372 / 339 units. Stall rule as built: no wipe goes to whoever destroyed the larger share of the other (ties to the challenger), the share rather than raw damage, so a cheap unit isn't punished for its foe's wounds. Tests: unit/hill, browser/hill, unit/patchpage. Waiting on Jordan's look at beta.

Mockup 2 Oct, waiting on Jordan's yes: https://claude.ai/artifact/PAJhgKypz3b2gCt1WtS5YP (the /meta/ page, Old One Eye's page and notes; phone and desktop, light and dark). (1) The Clash strip near the top of every static page: our own pixel figures fighting the calculator's real result, one line of real numbers under it, "Run it yourself" opening the calculator on that matchup; plays once in view, again on a tap, still with reduced motion; loaded after the page in a fixed box. /meta/: an epic hero pair a day, factions alternating (today Lion El'Jonson deals 7.7 of the Swarmlord's 10 wounds, 4.8 back); with an army picked, its hero against a rotating rival. Unit pages: best and worst common matchup (Old One Eye: 5.6 of 10 Termagants; 7.7 of a Land Raider's 16 wounds). Faction pages: its hero against a rotating rival. (2) Meta: a podium of the top three armies (Necrons 13%, Custodes 10%, AdMech 8%) with their figures, a Riser of the week (Space Wolves, none to 6%), army bars with glyphs, Test it on each unit row; every sentence kept, explanations moved down. (3) The drawers keep their questions, each with a small visual: a funnel (15 events → 71 lists → 1,241 units), dice score against meta share for three units, the last and next refresh. One epic hero per army, from the data, is in the mockup's notes for Jordan to override (the Tyranids' is the Swarmlord, 7 lists; Jordan named Old One Eye, 2). Open: the count of lists before the top-quarter cut isn't kept yet 2 Oct (Jordan, 1 Oct (Pacific), via the design session): the /meta/ Clash strip gives way to King of the Hill (T-521); settled 02:50Z: on /meta/ a compact "On the hill now" strip (Middle shooting, the meta's best shooters at 76 to 130 pts, to /hill/?seed=meta) and, under the podium, the last balance update's card (to /meta/patch/); the full hill lives on /hill/. Earlier plan: two hills: Shooting with the 5 units in the most winning lists that shoot best by our score (Inquisitorial Agents, Inquisitor Draxus, Rubric Marines, Paragon Warsuits, Chief Librarian Tigurius), Melee with the 5 that fight best (Deathwatch Veterans, Emperor's Champion, Celestian Sacresants, Logan Grimnar, Death Company Marines with Jump Packs); with Tyranids picked, its own; the podium, Test-it rows and the rest kept; the same mockup link, updated. Amended 2 Oct, 03:21Z (Jordan, 1 Oct (Pacific), via the design session, from his phone review of /meta/): (1) the three main tables become tabs, "Armies · Detachments · Units", under the faction row, swapping the table in place; swipe left or right on touch; the hash follows (#armies, #detachments, #units, each linkable); all three stay in the HTML, hidden with [hidden], so search engines still read them; the same control on desktop; the army card that opens on a tap stays as it is. Already there: since T-312 a smaller switch inside "This month's meta" swaps the three, with no hash or swipe, and with an army picked its detachments and units show one under the other; the build turns that switch into the tabs. (2) The faction row takes our pixel glyphs, the unit picker's (icons.js shield, flame, alien) in the group's colour, glyph above the word, count under it, and a new "All" glyph (four squares). Checked: T-476's glyphs only reached the group sheets' army tiles on /meta/; the row was text only. (3) Pictures: army rows the army's glyph (T-375) and its hero sprite (T-378) at 24px at the row's start; detachment rows the army's glyph only; unit chips in "Most taken units" (and the Units tab's rows, 20px) the unit's role figure at 16px (figures.js pick from the stub's keywords); rows stay one line at 390px, a long name truncates with "…", never the number. (4) Cut: "Two lists, head to head" leaves Where to next (Jordan: Meta visitors are browsing, not holding two lists, and "Winning lists: open one, then test it against yours" covers it); three cards remain: Tier list, Winning lists, Test a matchup. Amendments mockup 2 Oct, waiting on Jordan: https://claude.ai/artifact/KHkzFiNE9icfDse7xXa7pG (the real beta /meta/ with the four changes, clickable: Armies with an army opened, Units, Where to next at 390px, Detachments on desktop; light and dark).

Why: our tiers ranked armies by where their lists finished at the ~20 mostly French events MiniHeadQuarters covers (3 months; Orks 21 lists); the public win-rate tables (Stat Check, Listhammer) had Orks among the top armies and AdMech, GSC and Death Guard among the weaker ones, where we had them S, S and A (their figures, Listhammer-derived, were taken off this card: T-750). The method is fine: finish percentile tracks win rate within 1–2 points on the same data. Done 28 Sep: tiers off (ARMY_TIERS_ON in build_pages.js): gone from the Meta hub (site and app), /factions/ lists armies by their units with a note and links to Stat Check and Listhammer, armytiers.json has no tiers. Next (Jordan, 28 Sep: "I don't want to email them. Let's just wait until more events release"): no email. The tiers stay off until our own data can carry them: our source adds ~170 lists a month (~10 events, mostly France), ~5 per army, so ~40 lists per army over 3 months is a long way off unless MiniHeadQuarters grows. Monthly check (first 28 Oct): lists per army over the last 3 months, and our finish order against the public win-rate tables (Stat Check, Listhammer, via web search); back on (per army, those with ~40+ lists) only when both hold. For reference, the corpus's listhammer/results-*.json already holds every player's faction and win–loss record from BCP and Tabletop Herald events (checked locally, not published; the figures were taken off this card, T-750). If that ever changes: win rate per army over the last 4 weeks (singles, 5+ rounds, 16+ players; RTTs out), S ≥55%, A ≥52.5%, B ≥49%, C ≥46%, D below, fewer than ~40 players unranked, credited to Listhammer on every tier; weekly with the data refresh. Force Disposition tiers (T-318) are off too (Jordan, 29 Sep: "Yes"), same switch; the per-army counts stay. (Listhammer's data needs their OK; not asked, Jordan's call.) Jordan, 30 Sep: the rule stays as it is (last 4 weeks, singles, 5+ rounds, 16+ players, RTTs out; S 55%+, A 52.5%+, B 49%+, C 46%+, D below; under ~40 players, no tier). A tier switches on per army only when the army clears that floor AND our order matches the public tables within a couple of points, checked monthly; the sample size shows beside each tier. The public tables (Stat Check, Goonhammer 40kstats, Listhammer's /stats, GW's Metawatch) are a cross-check only: nothing of theirs on the site, not even a link (the paused note's links to Stat Check and Listhammer came out 30 Sep); the monthly comparison is logged in the report

grimstat-corpus's listhammer/ folder: undefeated and one-loss lists from GTs and RTTs on Best Coast Pairings and Tabletop Herald, with records instead of placings, and every event's full results (each player's faction, detachments, Force Disposition, record). Not under the corpus's licence: "on": false in tools/sources.json, and nothing of it is published until Listhammer says yes (Jordan is deciding whether to email them, 30 Sep; template in T-073). Built, one flag away: tools/sources/listhammer.js; build_lists.js adds per-army win rates to inclusion.json (winrates, only when a source has results) by T-332's method: the last 4 weeks, singles, 5+ rounds, 16+ players, RTTs out, ~40 players to be tiered, S 55%+, A 52.5%+, B 49%+, C 46%+, D below; an event both sources carry keeps the corpus's lists and takes Listhammer's results; its spellings added ("Imperial Agents", "Space Marines (Astartes)"). Local test (corpus 27c1ea7, 30 Sep, not published): win rates and list counts read from the listhammer/ folder with the source switched on locally; Listhammer-derived (Best Coast Pairings and Tabletop Herald results), so their numbers were taken off this card (T-750) and stay out of anything shown. Its lists have no placing, so they feed the tracker, inclusion and Meta score but not the "Recent winning lists" panel until that shows a record (a follow-up once it's on) Jordan, 30 Sep: send the one email; nothing from the folder is published until Listhammer agrees. Why ask rather than read it ourselves: the facts are free, but Listhammer's data comes from Best Coast Pairings (whose terms forbid automated reading) and Tabletop Herald, and the folder is their compilation, so their permission is the clean route to the US events. Email for Jordan to send (from hello@tacticalreroll.com; his wording, 30 Sep; the address in design/sources.md): "Hi there, I'm Jordan, and I run [Tactical Reroll](https://tacticalreroll.com), a free mathhammer calculator for 40k: you pick a unit and a target and it works out the damage, with a little pixel battle on top. I've been a fan of Listhammer for a while; the site is the best read on the competitive scene I know. I'm writing to ask a favour. I'd love to use your event results (which armies played and how they did, nothing about individual players) to give our [unit rankings](https://tacticalreroll.com/rankings/) a 'what's actually winning' column and a fairer sense of where each army stands. We're not a lists or results site and don't want to be one: anywhere we showed a number from your data we'd credit Listhammer by name and send people to you for the lists and the events themselves. The corpus on GitHub (grimstat-corpus) already relays your feed, so reading it there would be the least work for you, but whatever route or terms you're comfortable with is fine by me, including none at all. If our own numbers (per-unit damage, loadout comparisons) would ever be useful to Listhammer, they're yours. Thanks for reading, and for the site. Jordan"

Blocked: BSData has no stratagem text, and publishing GW's wording is an IP risk. Needs a data source we can use