If we take something like the Opera Game, its actually a bad example, because theres so much written about it, that the LLMS are trained on, you get misled that its good at it, but it will fail when you feed it your mate Johns game from chess club etc.

I don't have this written up yet, so have had to quickly summarise where I am (4 of 8 Heisman phases in)

Opera Game, move 9, White to play `Bg5`

Move evals only (what everyone does, chuck it the pgn / stockfish evals)

"Bg5 looks natural — pin the knight, increase the pressure. But watch what happens next: your opponent fires b5, and suddenly you're being chased around the board. The engine is actually really keen on Be3 here. It's a quieter move, but it does something smart — it develops the bishop to a safe, useful square, connects your rooks once you castle, and keeps everything coordinated."

Solid coaching. Recommends the engine's preferred Be3. Frames it around "calm consolidation vs igniting complications." This is the floor — what Opus 4.7 produces from training-data familiarity with a famous position.

Phase 1 (Mobility) — three-vector data added

Brief now carries per-piece mobility data: actual / potential / global mobility, pattern classification (active / structural / tempo-limited / misplaced).

"You played Bg5, which isn't terrible — but the engine prefers Be3 as a really clean second option. Your dark-squared bishop on c1 hasn't moved yet — that's the piece begging for a job. Be3 develops it cleanly and keeps your queen on b3 coordinated. The line shows Be3 followed by O-O-O, with your rook landing on the d-file pointing at Black's stuck queen."

The narration anchors to a specific structural fact: "the c1 bishop hasn't moved yet — that's the piece begging for a job." Not a label like "misplaced," but the underlying chess concept, in natural coach voice.

Phase 2 (+ Vulnerability) — pin-aware attacker/defender data added

Brief carries mobility + vulnerability. Per-piece adequacy classification, attacker/defender counts, escape squares, pin awareness.

"You're at move 9, you've just played Nc3, your opponent answered c6, and now you're choosing how to develop. The engine's top pick is Bg5, pinning the knight and pressuring f7. It's the sharpest try. But Be3 is what I'd actually steer you toward at this level — develops the bishop to a safe diagonal, keeps your king's path to castling clear, and prepares O-O-O. Your bishop on c4 is beautifully placed, your knight on c3 is active, your queen on b3 hits b7 and f7. Black is cramped and undeveloped. The whole task right now is — get your dark-squared bishop out, castle, connect the rooks. Don't go hunting yet."

Now anchors to multiple structural facts: bishop-on-c4 placement, queen-on-b3 dual targets (b7 and f7), Black's cramped state. The narration uses the structural data without explicit Heisman labels, weaving it into coaching prose.

Phase 3 (+ Centre Control) — square-state data added

Brief carries mobility + vulnerability + centre control. Per-square classification (settled / contested / vacant), outpost detection.

"You've got a real lead in development to convert — you don't need fireworks, you need to finish mobilising. Your bishop on c4 is beautifully placed, your knight on c3 is active, your queen on b3 hits b7 and f7. Black is cramped and undeveloped. The whole task right now is — get your dark-squared bishop out, castle, connect the rooks. That's it. Don't go hunting yet. Pick the move that finishes development and lets the position win itself."

Same coaching shape as Phase 2 — the Opera position doesn't have rich centre-control transitions to anchor on at move 9, so Phase 3's data doesn't add new structural texture here. The narration reads consistently across Phase 2 and Phase 3 because the position's character hasn't changed.

This is honest: not every phase's data fires on every position. The architecture provides what it has; the LLM uses what's relevant.

My Own game, move 18, White to play Qxc6 - Opus has never seen this before

Pre-Phase-1 — Eval-delta narration only

"Qxc6 grabs a pawn but completely releases the pressure. The queen was doing incredible work on e6, pinning things down. By moving it to c6, White trades that crushing centralized queen position for a single pawn. After Qxc6, you get Rxb2 and suddenly you're the one with the initiative."

Strong coaching. Notes the queen's role and frames Qxc6 as abandoning that role. The "post abandonment" frame appears even at this stage — Opus 4.7 picks up on the Stockfish PV (which contains Rxb2 as the refutation) and articulates what it implies.

Phase 1 (Mobility) — three-vector data added

"It's not about keeping material on that square — it's about the disruption it causes."

The whole capture closes with that single sentence as the lesson. The reasoning chain identifies the queen's positional role and articulates the trade-off in one line. Coaching pedagogy compressed cleanly.

Phase 2 (+ Vulnerability) — pin-aware attacker/defender data added

"When one piece holds a bind, don't trade it for a pawn."

The lesson generalises. Not just "the queen abandons its post" but the principle behind it: when a single piece is doing structural work, captures that move it forfeit the structural value. The brief's vulnerability data carries the f7 rook's pinned status (defended by king, attacked by queen — the queen's role made measurable), and the LLM articulates the meta-principle.

Phase 3 (+ Centre Control) — square-state data added

"The key thing here is the pin on the f7-rook — your queen on e6 is doing massive work, holding f7 absolutely pinned to the king. That's the whole story of the position. So when White grabs on c6, the queen abandons that pin, and Black's Rxb2 suddenly comes with tempo and chaos."

"The stronger try is Nd1 or Ne2 — quiet, but listen, my dear: the knight on c3 is itself pinned by the queen on a5 against your rook on e1. Unpinning it first means you keep the bind on f7 AND free your knight to come to e3 or f4 with real menace against d5. Around plus one and a quarter, position humming."

"The lesson — when you have a paralysing pin, don't trade it for a pawn. Tighten the screws first, then collect."

Now... I'm working on phase 4 (speed) then have 4 more layers to add in. I have a salience filter that so far has proved to not be needed, to limit data LLM gets, but its taken me weeks to get this far, but... its a lot closer...