Game-story copy issues
Case 1b858313 m31 (8/6pk/5p1p/3Q4/8/7P/6PK/4q3 w): boards for the position, what Qd4 does (Qe5+ forks king and queen, forced trade, lost pawn ending) and what Qc4 does, today's story text, rule hits
Experiment: DecodeChess explanation catalogue (59 types from 32 scraped pages) vs the 58 pending moments — DecodeChess-style facts computed for every case, verdict per case, what we can copy and what needs their engine farm
Experiment: plain board rules (passed pawn, king cover, open file, trapped piece, perpetual check...) run over all 58 pending moments in Node only — 34 concrete hits, 11 of 14 hand-checked are right or fair, honest coverage about 27 of 58, full table with every case
Pending case 3 (Node-only fixes): room 1f4f58e2, move 1 (Rc2) — the stronger move Qe4 threatens mate in one, but three replies stop it; why every rule stays silent, and three fixes that need no engine and no Python change (chess.js mate-in-one check, three defenses for a mate threat, the fork that wins nothing)
Pending case 2: room 1a93804a, move 4 (Rb8) — a rook-sacrifice attack where the reply rule and the gave-up rule both fail; the forcing-line rule that would tell it, and the count of the rest (13 forcing, 17 long quiet, 35 no material)
One pending case in full: room 0b5acbb6, move 2 (c4) — what the generator does, why every candidate reply is rejected, the text shown today, and the text the same facts can give (the line black gave up)
Analysis: one-line stories in Akshat's format — where it works, where it fails, counterexamples, and the generator changes needed; numbers from 676 mistake moments in 120 regenerated stories (round r27)
Prototype: arrows on the board, focused — the starting move only: red arrow = the move you played and the reply it runs into, green arrow = the right move; tap an arrow to follow it; after both arrows, the takeaway; production wording only (round-3 Kg2 case)
Prototype: arrows on the board, focused — the Kxh4 moment: the opponent's gxh4+ plays first, then green arrow = the right move (Kg2), red arrow = the move you played (Kxh4); the red arrow leads to a second screen with all seven of their attacking replies as arrows, each one followable; the takeaway after all seven; master wording for the moment itself, engine-checked lines with plain move sentences for the seven attacks (round-3 Kg2 case)
Prototype: arrows on the board, all branches — every master branch point incl. the opponent's moves and your chances; tap an arrow to follow that line, legend under the text says what each arrow is; all 57 steps (round-3 Kg2 case)
Prototype: hard stop + follow-up questions (round-4 Nc2 case)
Prototype: hard stop + follow-up questions (round-3 Kg2 case)
Prototype: branch explorer — straight to the moment, pick lines, step back (round-3 Kg2 case)
Prototype: branch explorer, minimal intro — only the essentials, then straight to the choices (round-3 Kg2 case)
Reference: exact master story — production wording and lines, all 57 steps in order, no pause, no questions, nothing added (round-3 Kg2 case)
Prototype: master story collapsed into branches — production wording and lines only, grouped into choices, nothing added (round-3 Kg2 case)
Loading…
Loading…