DECISION SUMMARY

BFT entered Round 5 at 3-0-1 in second place, playing the first-place team (RLD, undefeated at 4-0-0). A third team (Team Alberta) was 3-0-1 sitting third, 13 battle points behind BFT. From BFT’s seat, the round was a tiebreaker arithmetic problem: win, and win by enough that Alberta couldn’t leapfrog. From RLD’s seat, the round was a closing-out problem — ideally win the event, but a tie at the round combined with a modest Alberta result would still take it.

Two captains entered the round with very different process shapes. BFT had a singular pairings captain (Riley) with a technical captain (François) advising — a clean one-person-decides structure. RLD had a coach plus two co-captains all participating in pairings, which Nick later diagnosed as the team’s “too many cooks” problem.

Across the round’s two pushes and the scrum, four distinct captain-craft plays surfaced. Three were BFT’s — Riley defending himself to bait Ridvan out of the scrum, François up into CSM as a feint expecting rejection into Recon, and Kasra up into Recon as a feint expecting rejection into GSC. One was RLD’s — Nick defending his own Tau hoping to bait BFT’s EC attacker into a counter-trap. The Riley-as-bait play worked exactly as designed. The Kasra rejection-engineering routed Kasra into the intended matchup. The François gambit got called — RLD’s CSM player championed François rather than JB, but not because RLD’s matrix viewed the cell the way BFT’s matrix did. The Nick-Tau-bait was burned by friendship-channel intel before it could fire.

The team won the round 93–67 — six games to two. Riley’s own retrospective: “I thought we got outpaired in the scrum.” Nick’s own retrospective: “I would approach pairings differently.” Both captains, on reflection, name the pairings as a process loss — the result went BFT’s way through player skill on the day, not through either captain winning the craft. That’s the round’s central observation, and it’s unusual material for the Archive: most entries record a captain winning the craft or losing it cleanly. This one records both captains feeling they lost their own craft, and the games carrying the team to a 6–2 win anyway.

THE TEAMS

Blunt Force Trauma (BFT). Pairings captain: Riley (Thousand Sons). Technical captain: François (Emperor’s Children).

• Astra Militarum, Grizzled Company — JagAll-comers, stable first defender that gets positive matchups based on table pick. The recurring first defender in 4 of 5 rounds.
• Chaos Space Marines, Renegade Raiders — Tim4 Rhinos with Vindicators — blunting attacker.
• Necrons, Starshatter — DevinTurbogreed Triple C’tan with King; built as a “Princess” to be slotted into a good matchup.
• Deathwatch, Black Spear Task Force — Kasra5 Kill Team brick (Sweden List variant); targets infantry-focused builds, scores stably. Coming off a 20–0 loss to Tyranids the prior round.
• Genestealer Cults, Outlander Claw — Stu“Aussie Mad Max” 20-Bike Triple Grinder — stable blunter that smashes any T3 army.
• Thousand Sons, Warpforged Cabal — RileyTriple Prince Triple Defiler Sandstorm — the captain’s own list. The main problem presented to opponents in pairing to force matchups.
• Drukhari, Spectacle of Spite — JBTriple Scourge Spectacle with Mandrake unit, built to attack light boards.
• Emperor’s Children, Coterie of the Conceited — FrançoisDouble Defiler Double Prince — the technical captain’s list. Aggressive list that needs to be respected in pairings.

Red Lizardy Dragons (RLD). Team captain: Nick. Pairings Process: Team of 3 (coach and 2 co-captains).

• Space Marines, Blades of Ultrimar — CodyLennon Blades (community list).
• Genestealer Cults, Biosanctic Cult — DanNas’ Biosanctic.
• Necrons, Awakened Dynasty — Josh20 Warriors with C’tan.
• T’au Empire, Mont’ka — NickTriple Riptide with Broadside unit. Nick himself.
• Drukhari, Spectacle of Spite — Ridvan2 Scourge, 10/5 Helion. The player BFT’s matrix flagged as the four-soft-target threat.
• Chaos Space Marines, Renegade Raiders — CowanDouble Defiler Raiders.
• Emperor’s Children, Coterie of the Conceited — WillDouble Defiler Coterie. Pre-event pivot — the player didn’t have much practice going into the event on this list.
• Astra Militarum, Recon Element — ZachRecon Guard, body-count list.

THE STRATEGIC PICTURE · BOTH SIDES

BFT’s read going in. Four BFT priorities: neutralize (Ridvan), shelter (Kasra), cash in (the Recon and Marines soft pins), and a recurring captain choice (Jag as the permanent first-defender slot).

RLD’s read going in. Nick had a correct read of the Push 1 BFT defender (Guard / Jag) but the team prepped against TSons — the “too many cooks” problem in operation. He correctly identified BFT’s TSons-and-Deathwatch priorities — but his read of them came at the strategic level (TSons-for-big-score, Deathwatch-to-shelter) while BFT was operating at the structural level (TSons as a threat-piece to force matchups, Deathwatch as a list to route into a sympathetic cell).

Nick’s pre-round trap intent. Nick was defending himself in Push 1 with the intent of luring BFT’s EC (François) into attacking him, expecting RLD could exploit the Tau-vs-EC matchup. The trap relied on BFT’s EC player following a matrix expectation that Tau-vs-EC was good for EC.

Why the trap got burned — cross-friendship intel flow. BFT held François back from attacking Nick’s Tau not just because the matchup math (a defender Tau is a different matchup than an attacker Tau) but because the BFT side had Nick’s trap intent in advance.

Riley’s Discord-quoted aside — “It was François in my ear saying Nick isn’t going to play that game the same” — now reads as François flagging both the matchup math and Nick’s trap intent to Riley during the call. The “François in my ear” line is doing more work than the original parse credited it for.

PUSH 1 · FIRST DEFENDERS, BOTH SIDES TRYING TO BAIT

Each team puts up a first defender; the other team puts up two attackers; the defending team picks one to champion in.

BFT first defender: Astra Militarum (Jag). RLD attackers were Will (EC) and Cody (Marines, Blades of Ultrimar). RLD championed Will. Game went 20–0 to Jag.

RLD first defender: Tau, Mont’ka (Nick himself). BFT attackers were Tim (CSM) and Devin (Necrons). RLD championed Tim. Game went 14–6 to Tim.

Nick’s retrospective on the Tau-as-defender call: he disagreed with his own team’s call to defend with Tau. The “too many cooks” process produced a defender choice Nick would not have made if running pairings solo. He wanted Tau as an attacker — held in reserve for the Riley/TSons defender slot if it surfaced.

Three captain-level observations from RLD on the AM championship (Will into Jag): Will’s matrix view of his own matchup was likely wrong; Will’s aggressive playstyle didn’t fit a contingency-tolerant attack into Guard; and the Tau defender choice cascaded forward into the AM champion choice — if Tau had been an attacker, RLD’s attacking options against Jag would have been Tau + CSM rather than EC + Marines, a different (probably better) pairing landscape.

Nick’s retrospective on his own pairing (CSM championed into Tau, not Necrons): Nick wanted Devin (Necrons) championed into his Tau; RLD’s pairing process produced Tim (CSM) instead. Nick explicitly names this “a big pairings blunder.” The team-captain who would play the game disagreed with the team’s captaining of the game.

Riley’s reasoning on holding François (EC) back — in retrospect, both for matchup math and because the BFT side had intel on Nick’s Tau-attack trap. The matchup specifically wanted to lure François; François being elsewhere meant the trap couldn’t fire.

Riley’s resolution on the “bigger score into EC” line: Jag’s preference between his two possible attackers, not BFT’s read on RLD’s championship choice — “With table pick, Jag felt like he could get more differential against the EC compared to the other option. Was too early for prediction the champion.”

PUSH 2 · RILEY AS BAIT, MARINES DEFENDER, AND ONE BLUNDER EACH SIDE

BFT second defender: Riley himself (Thousand Sons). RLD attackers were Ridvan (Drukhari) and Josh (Necrons, Awakened Dynasty). BFT championed Rid into Riley — exactly what Riley defended himself to engineer. Game went 13–7 to Riley.

RLD second defender: Marines (Cody, Blades of Ultrimar). BFT attackers were Devin (Necrons) and JB (Drukhari). RLD championed Devin. Game went 12–8 to Devin.

The Push-2 BFT defender call is the round’s signature captain move:

Captain-as-bait: Riley used his own slot as defender to commit Ridvan into a known matchup rather than leaving him free in the scrum, where four of BFT’s eight players were in the orange/red zone against him. BFT’s matrix called Riley/Ridvan as −1; the alternative was leaving Ridvan as a scrum wildcard. The secondary benefit was table craft: defending Riley constrained the table pool, allowing Kasra to avoid a specific table he didn’t want. Captain work runs two levels deep — matchup grid and table seeding — and Riley’s call paid in both.

Nick’s retrospective on the Marines championship (Devin into Cody): the choice was a coin-flip from RLD’s seat (both attackers had matrix arguments). The retrospective regret is one level up — Nick now sees that championing Drukhari instead would have removed JB from the scrum pool, denying BFT the Drukhari-vs-Recon scrum pairing that eventually delivered Recon a loss. Captain craft at the meta level — not just “which matchup is best on this push” but “which championship choice constrains the opposing captain’s scrum options most favourably.”

Riley clarified one Discord ambiguity on form-fill: “Sadly we lost Devon in the scrum” referred not to losing Devin’s game (Devin won 12–8) but to losing the option of using Devin for the final scrum pairing, where BFT’s matrix viewed him as particularly strong. Push-2 committed Devin to Cody, so by the scrum he was off the board.

THE SCRUM · THREE BFT PLAYS AND ONE CAPTAIN NOT PLAYING THE MATRIX

After the two pushes, four pairings remained to set in the scrum. Three captain-craft plays were running on BFT’s side. RLD’s championship choices in the scrum were driven primarily by player comfort, not matrix arithmetic — and that asymmetry is where the round’s central methodology observation lives.

BFT Gambit A — François into CSM, expecting rejection into Recon. RLD’s CSM player went up as the third defender. BFT attacked with JB (Drukhari) and François (EC). From BFT’s matrix:

• JB into CSM read as +1 (good) for BFT.
• François into CSM read as 0 (even) for BFT.

Under matrix-optimal play, RLD champions the cell worse for BFT — François × CSM at 0 over JB × CSM at +1. That logic puts JB into the scrum pool, which is exactly where BFT wanted JB headed (Recon was the destination, per the rejection-engineering plan). The plan was a feint.

Two reads of the same outcome, then. Matrix-optimal RLD play arrives at the championship BFT engineered (François); RLD’s actual logic per Nick (Cowan’s player-comfort into EC) arrives at the same championship. The gambit fires either way — either because the matrix prescribed it, or because Cowan picked the matchup he wanted. The rejection-engineering doesn’t depend on either path; it only depends on RLD not championing JB, which neither lens recommends.

The game went 3–17 to RLD. Riley stands by the BFT EV math:

BFT Gambit B — Kasra (Deathwatch) into Recon, engineered for rejection into GSC. Parallel logic in the same scrum.

Kasra was put up as an attacker into the Recon defender (Zach), expecting RLD to reject him — because Kasra into Recon was unfavourable for the Recon-defender side — routing Kasra into Dan’s Biosanctic GSC, his preferred matchup. The rejection-engineering worked: Kasra landed in GSC as planned. The game then went 4–16 to Dan:

The pairing-engineering worked exactly as planned. The game then went sideways inside the engineered matchup, on a positioning trap Kas’s teammates had specifically warned him about.

BFT Gambit C — championing Stu away from CSM, accepting Stu into Necrons. With the scrum resolving, Stu (BFT’s GSC player) ended up championed against RLD’s Necrons in the residual scrum pairings. BFT’s matrix viewed Stu/Necrons as −2 (Stu’s “least favourite matchup”). Riley walked Stu through the matchup on the fly:

Game went 14–6 to Stu. The captain’s player-over-matrix read paid off; the in-round coaching was real captain-craft work, not just a pairing call.

The matrix recalibration in Riley’s own game. Riley vs Rid played out as the final captain-level lesson of the round.

The matrix predicted Riley/Rid as −1 for BFT; the actual game played as an even matchup. Riley won 13–7 through skill on an even cell, not by winning a disfavoured cell. Live captain-level recalibration of the matrix during the captain’s own game.

RESULT

Final round score: BFT 93, RLD 67 (BFT 6 wins, RLD 2 wins). The table below is the partial matrix view — the eight realized matchup cells with BFT’s pre-round matrix read. The other 56 cells of BFT’s 8×8 matrix are surfaced in the OVERVIEW tab’s full matrix view.

▸ BFT MATRIX VIEW values are BFT’s pre-round read on the WTC −2 to +2 scale (−2 = very bad / ≈30% win · −1 = bad · 0 = even · +1 = good · +2 = very good / ≈70% win).

Riley’s per-game one-liners, in his own voice:

• JB vs Zach (13–7):“Was marked bad to try and avoid in pairings; on the table it plays as a game of Warhammer where both sides have opportunities to kill the opponents’ stuff.”
• François vs Cowan (3–17):“The first few dice rolls decided who won big.”
• Devin vs Cody (12–8):“The bad guys were unable to kill the good guys.”
• Kasra vs Dan (4–16):“The one thing that could go wrong went wrong. Don’t let 5 units get engaged when you only have 5 units.”
• Riley vs Rid (13–7):“My matrix wasn’t real. TSons Crabs means a −2 is actually a 10–10 game. Elves played an extremely technical game of Warhammer while crabs and princes killed all the elves.”
• Stu vs Josh (14–6):“The bug things got over their fear of toasters and shoved into them.”
• Jag vs Will (20–0):“Jag did his thing. Defiler EC is volatile.”
• Tim vs Nick (14–6):Riley defers to the Editor (RLD captain) for the game-level narrative.

Nick’s read on the round outcome:

The Will-vs-Jag 20–0 and Nick’s own 14–6 loss were the “predicted big wins → 0s” Nick refers to. In a close-round calculus where RLD only needed a tie, two of the games swinging hard the other way meant the round was unrecoverable.

BACKWARD-INDUCTION COMPARISON · SOLVER vs RILEY

The Archive’s WTC sequential solver — a backward-induction game-theoretic model that plays out the captain dance assuming both sides optimize from the matrix — gives us a quantitative baseline for what the matrix recommended at each captain-craft moment. The comparison below is editorial complement to the account-based narrative above: the matrix prescribes one path, Riley chose another, the table delivered a third. Where they diverge is where the captain craft shows up.

Three readings sit inside this comparison. First: Riley’s Push-1 defender choice (Jag) was matrix-suboptimal by 2 EV against François. Jag’s selection paid off because RLD didn’t play matrix-optimally either — they offered Will instead of Cowan, and Will’s volatile list lost 20–0. The solver’s math assumes both sides optimize; reality is sloppier. Second: the Push-2 captain-as-bait call cost 1 EV against the matrix, but its real value is in a register the solver doesn’t model — committing Ridvan to a known matchup and constraining the table pool for Kasra. The matrix is a tool, not the answer. Third: BFT was outpaired by 8 EV in pure scrum-allocation terms, but BFT’s actual scrum sat 3 EV better than RLD-optimal because the Kasra rejection-feint engineered Kasra into Dan (+1) instead of Zach (−2). The Kasra gambit was the scrum’s load-bearing captain-craft moment, and it shows up cleanly in the math.

Solver runs against BFT’s matrix as captured at intake; RLD’s matrix is unknown to the Archive and may give different recommendations from the RLD side. The comparison reflects what BFT’s pre-round model would have prescribed, not the joint matrix-optimal play under both sides’ actual matrices.

POST-MORTEM

Four captain-level signals from the round.

The captain’s matrix is a tool, not the answer. Three scrum calls — championing Stu away from CSM, accepting JB into Recon as the residue of the François gambit, and Riley defending himself into Ridvan — all asked the captain to override his own team’s predictive cell colour. All three paid off. The matrix quantifies the team’s collective best read; the captain knows which player can be coached through a bad spot, which player will outperform a flat cell, which player’s preference is more load-bearing than the rating.

Rejection-engineering is captain craft worth naming. Two parallel gambits — François into CSM expecting rejection into Recon, Kasra into Recon expecting rejection into GSC — both relied on the opposing captain making the championship choice the matrix would predict. The Kasra play worked exactly as engineered. The François play was called by the opposing captain making a non-matrix choice that produced the same outcome.

A gambit’s robustness is the count of opposing-side logics that fire it. This is the round’s central methodology observation, and the version of the matrix-versus-narrative callout that v2 and v3 of the entry circled around without quite landing. BFT’s François-into-CSM gambit fires under at least two distinct RLD logics: matrix-optimal play (RLD champions the cell worse for BFT — François × CSM at 0 over JB × CSM at +1) AND player-comfort logic (Cowan wants EC, worries about Drukhari, picks the matchup he wants to play). Under either logic, RLD champions François; under either, JB drops free for the scrum and routes into Recon as BFT engineered. The gambit-setter wasn’t bidding against a specific RLD logic — they were bidding against any logic that prefers cells with known BFT-side weakness.

The corollary is operational: gambits in pairings get robust by surfacing under multiple opposing-side logics. A gambit that only fires under matrix-following play breaks the moment the opposing captain runs on player comfort, list-tool calculus, or table-seeding. A gambit that fires under all of them is structurally stronger. BFT’s François-into-CSM gambit had this multi-logic robustness; whether Riley built it intentionally that way or whether the matrix values happened to line up matters less than the practical lesson — the most resilient gambits are the ones that don’t require the opposing side to think in any particular way.

Both captains’ process losses produced the same game result. Riley: “I thought we got outpaired in the scrum.” Nick: “I think this was a big pairings blunder on our part” (Push-1 Tau defender call); “Yes, I would approach pairings differently.” Riley felt RLD outpaired BFT. Nick felt RLD outpaired itself. The 6–2 round result came from BFT’s players overperforming on the day, not from either captain winning the craft.

Two captains’ lessons.

Riley’s Day 2 self-management shift. Riley’s account names a structural piece of captain self-management — the shift from maximize-my-own-score-each-round to use-myself-as-the-team’s-skill-versus-skill-insulator-against-the-opposing-team’s-best-players, even-at-the-cost-of-my-own-points. Round 4 (“The Captain’s Sacrifice”) is where that switch happens; this round refers to it from one push past the origin.

Nick’s RLD-side lessons. Three lessons stacked: matrix accuracy is the load-bearing input (Nick echoes Riley’s “my matrix wasn’t real” line from a different vantage); singular pairings authority beats distributed pairings authority (RLD’s “too many cooks” diagnosis, held up against BFT’s clean Riley-runs-pairings-with-François-advising structure); experience beats meta-chasing (the EC defiler pivot the week before the event that left a player under-practiced on his list all weekend).