Sixty Minutes, Five Lines, Zero Engine Checks: A Ledger Audit of the Najdorf Update

Sixty minutes. Five line clusters. Twelve minutes per cluster. That number of twelve appears nowhere in the review I am reading — I derived it by dividing the declared runtime by the declared cluster count. The most reliable part of any review is the part it does not state but can be counted.

The review in front of me has no author. No publication date. No outlet. Not a single engine check, not one model game cited, not one database count — how often this line has been played, at what rating band, up to which year. And after all of that, it makes a recommendation. This is not unusual. Almost every informal review of a chess training product is written this way: from experience, without verification, and without saying which date the experience belongs to.

What interests me is not the product. What interests me is how a sixty-minute video claiming to update five lines of the Sicilian Najdorf circulates without a date — and how the reader accepts it.

Context: what this product actually is

The identity is simple. The line is ChessBase's FritzTrainer series, volume Power Play 18, author GM Daniel King. English language, one-off downloadable video, sixty minutes, with a companion FritzTrainer database. Subject: a Black repertoire in the Sicilian Najdorf, five branches reopened in this update.

One thing needs stating clearly, because the review does not state it. This is not a new book. It is a maintenance release of the same author's earlier Najdorf repertoire. The older DVD is referred to as being "from last year" — and there the first crack appears. Which last year? There is no year anywhere in the review. This is not a small omission. For a product whose entire value proposition is currency, the absence of a date removes the one piece of information without which everything else is moot.

Some technical background is necessary. 1.e4 c5 2.Nf3 d6 3.d4 cxd4 4.Nxd4 Nf6 5.Nc3 a6 — the structure spans roughly B90 to B97 in ECO classification. Its distinguishing feature within chess theory is that it is one of the most heavily analysed branches in the game: hundreds of new lines every year, re-examined at every top-level tournament, and every published repertoire is an invitation for White-side counter-preparation. The review itself calls it dynamic, popular and constantly developing. That phrase reads like praise. In fact it is testimony against the product. An opening that is constantly developing will render a one-off update stale at the same rate.

Core: the five clusters, one by one

Cluster one: 6.h3 e5 7.Nde2. The Adams Attack, named for Michael Adams. White's intent is explicit — avoid the Nb3/Nf3 congestion, prepare g4/f4, bring Be3 and Ng3. Black answers with ...Be6, ...d5, ...Nbd7, ...b5. At elite level this is one of the two principal modern tests. The cluster is mandatory. A Najdorf repertoire that does not address 6.h3 is incomplete.

Cluster two: 6.Bc4, with Be3 and f3 ideas. A Fischer–Sozin-type hybrid — the Bc4–Bb3 battery, then transposition into English-Attack structures via f3/f4. Medium frequency at elite level, meaning not primary but not skippable. This is a completeness entry, not a frequency entry.

Cluster three: 6.Be3 e5 7.Nb3, with Black's ...a5 plan. This is the English Attack, and by volume the single most-played White setup. White: f3, Qd2, 0-0-0, then g4/g5. Black: ...Be6, ...Be7, ...Nbd7, and a queenside fixation with ...b5/...a5. Also mandatory, and technically the heaviest of the five.

Cluster four: 6.Be2, including 9.Re1. The Opocensky Variation — slower manoeuvring, Re1–Bf1, Nd5 ideas, positional squeeze instead of the g4 race. Medium frequency, classical branch, required for completeness.

Cluster five: 5.f3. An anti-theory sidestep. White delays the normal Nc3 development pattern, aims for a big-centre English-Attack-like structure, and steps out of the mass 5.Nc3 theory. Low frequency at elite level. At club level it is a practical weapon. Its inclusion in a Black repertoire is a market decision rather than a frequency decision — club players play it, and club players are the buyers.

Seen together, the structure is sound. Clusters one and three are precisely the two highest-frequency White tries at elite level. Clusters two and four are correct completeness items. Cluster five is a low-frequency oddity included to close the repertoire. The line selection contains no obvious error. The problem is not selection. The problem is depth.

The arithmetic of sixty minutes

Twelve minutes per cluster. That number settles the difference between two things: orientation and currency. In twelve minutes you can convey plans — which piece goes where, which idea runs through which structure, which move-order trap exists. In twelve minutes you cannot convey move-by-move currency, because 6.h3 and 6.Be3 are among the heaviest branches in all of chess theory and their present state runs to hundreds of pages.

This fixes the user segment automatically. The product is for the club and intermediate player, roughly 1500 to 2100, who needs direction — which branch to enter, where not to get stuck. It is not a pre-tournament briefing for a 2400+ player. The review does not state this distinction, and that is its largest practical omission.

The second thing the review does not state: the video is one-directional. No interactive trainer, no spaced repetition, no drilling. Whether what was watched is retained has no mechanism inside the product. Stability is high for the material as presented, low for the user's memory of it — unless the user drills a database independently. The correct comparison is against products that ship MoveTrainer-style systems, and against that comparison a linear sixty-minute video is behind.

And the largest gap is the one that cannot be counted: the verification layer. Not one engine check. Not one model game. Not even a statement of which Black setup is recommended against which White system. No technical claim in the product is verifiable from within the review.

Contrarian: a product that admits it is perishable is more trustworthy

The first awkward claim is that the missing date is not the review's error but the product's condition. The entire economy of maintenance releases depends on nobody counting how old the previous edition is. The moment a date is printed, a decay rate becomes measurable — and a measurable decay rate makes the buyer wait for the next update. In my own work I apply the same rule: a document without a date is not evidence, however honest it looks.

The second claim is more uncomfortable. The most credible sentence in this entire review is not a recommendation. It is the caveat: the earlier DVD is not strictly required, but it would help, because these lines form part of a complete repertoire. The sentence is commercially self-serving, and that is true. But it is the only sentence that admits dependency. The rest of the text praises the product; this one sentence states its limit. In my experience, a product that states its own limit is more trustworthy than one that claims permanence.

Third: the word "popular." It arrives without a denominator — no sales figure, no download count, no user rating, no platform ranking. It is decoration, not evidence. I have watched such claims for years and not one of them could produce a number afterwards.

Fourth, and most important: the 1500–2100 band is not a consolation prize, it is the actual market. Measuring this product on the elite-currency scale is using the wrong scale. The right scale is orientation value per minute. On that scale, for a player who has never built a plan against 6.Be3, twelve minutes of one cluster is worth more than hundreds of pages of database. That is the product's strength, and measuring it in the name of currency does it an injustice.

Takeaway

I have no complaint against the product. I have a complaint against how it is sold — without a date, without a rating band, without an engine version, without a database cutoff. When I was converting 4,300 games into PGN in 2026, we flagged 380 as unrecoverable rather than guessing. The same discipline applies here. Silence in the record is still a data point.

Ask three questions before buying. First — what is the release date of this video, and which engine version was in use at that time? Second — up to what date does the database run? Third — for which rating band was this written? A product that cannot answer all three should be called a memory, not an update. And in the metadata of the next maintenance release, those three lines should be written first. Everything else comes after.

The scoreboard is a summary. The ledger is the story. In this case the ledger does not exist — and that is the whole story.