The reading room a guides library is, and the one it pretends to be
A guides library, read in the right order, is a small reading room. The same topic shows up in three or four pieces, written at three or four depths, and the reader who lands on the right piece first can answer a question before lunch. The reader who lands on the wrong piece first leaves the room thinking the library is shallow.
Most readers land on the wrong piece first. The reason is structural. A guides library publishes more than one article per topic because a single article cannot do the work of three. The news piece covers the verified event. The analysis piece covers the mechanism under the event. The explainer piece covers the durable principle the event was an example of. The recap piece, when there is one, covers the consensus an industry has already settled on. Each of those four is a different genre with a different promise, and the four-test method below is a way to put the right genre against the right question.
The method is not a ranking. A reader who treats it as a ranking will use the wrong test for the wrong genre and end up back at square one. The method is a triage. The first test separates a news piece from an analysis piece. The second separates a working analysis from a recap. The third separates an explainer from a piece that only looks like an explainer. The fourth separates a piece that can survive a second read from a piece that was written to be read once and forgotten.
Test one: does the piece tell you what was verified, and what was not
The first test is the easiest and the most often skipped. A reader who has just opened a piece on a current event needs to know, in the first three paragraphs, what the writer has actually verified and what they have inferred. Most pieces make this hard on purpose, because the inference is the part that gets shared and the verification is the part that gets cited. LetsGame editors look for three small marks. The piece names the source. The piece names the date of the source. The piece tells the reader what the source does not contain.
When all three marks are present, the piece is doing the work of a news piece. The reader can use the piece to update a calendar entry, change a watch list, or plan a follow-up question for the next window. When only the first mark is present, the piece is doing a different job. It is using the appearance of a source to carry an interpretation that the source does not actually support. The reader who takes that piece at face value will plan around an interpretation, not a fact, and the plan will fail at the next data point.
The test is a short paragraph, not a full reread. Open the first three paragraphs, the second-to-last paragraph, and the final paragraph. Count the named sources, the named dates, and the moments where the writer admits a limit. A working news piece has all three. A working analysis piece has one or two of the three, with a stated reason for the missing element. A recap piece has zero of the three, because a recap piece is reporting on a consensus, not on a fact. A explainer piece has zero of the three, because an explainer is reporting on a principle, not on a fact. The test, applied to a piece that does not match its genre, will produce a misleading result. Apply the test to a piece that matches the genre you are reading.
Test two: can the writer explain the mechanism, separate from the event
The second test is the one a working analysis piece survives and a recap piece does not. The reader asks the piece to explain, in one paragraph, why the event happened the way it did. A working analysis piece has a paragraph. The paragraph names at least two inputs, names at least one trade-off between the inputs, and names the boundary that the writer set when they chose the trade-off. A recap piece has a paragraph, but the paragraph names a consensus and stops there. The reader who cannot find the trade-off is reading a recap.
The practical value of the trade-off paragraph is that it lets the reader apply the analysis to the next event, separate from the event the piece is reporting on. A piece that names the trade-off can be reused. A piece that names only the consensus has to be re-read, and re-reading is more expensive than applying. LetsGame editors treat the trade-off paragraph as the section that pays for the rest of the article. If the trade-off paragraph is missing, the article is not yet analysis. It is a report with a headline.
The test is also useful for readers who arrived at the piece from a search result. A search result will often land the reader on a recap because recap pieces rank well in the short term. The reader who knows to look for the trade-off paragraph will recognise the recap on the first re-read and move on. The reader who does not know to look for the trade-off paragraph will treat the recap as analysis, and the plan that comes out of the recap will be brittle.
Test three: does the explainer teach a principle you can re-use without the article open
The third test applies to explainer pieces, which are the most over-published genre in a guides library. An explainer that earns its place is a piece a reader can finish, put down, and use on a topic the article never named. An explainer that does not earn its place is a piece a reader has to keep open on the second monitor while doing the work the article is supposedly teaching. The difference between the two is a single rule.
The rule, in a working explainer, is named in the first half of the article and re-stated, in different words, in the second half. The reader who closes the article at the halfway mark can carry the rule forward. The reader who closes the article at the end is carrying the article's conclusion, not the article's rule. LetsGame editors test every explainer by closing the tab at the halfway mark and asking whether they can describe the rule to a colleague without re-opening the page. The explainers that pass the test are the ones that get re-published when the topic comes back around.
The practical use of the test is that it lets a reader sort the explainers in a library by re-usability, not by recency. The explainer that can survive the halfway close is the one the reader should print, save, or return to. The explainer that cannot survive the halfway close is a one-read piece, and the cost of the one read is the whole price. A reader who knows the difference will not waste the second read. A reader who does not know the difference will keep re-opening the same one-read piece and wonder why the principle never sticks.
Test four: does the piece survive the second read without contradicting itself
The fourth test is the one LetsGame editors run last and readers should run first, because it is the cheapest. The reader re-reads the article a second time, in full, looking only for two things: a sentence that contradicts a sentence earlier in the article, and a sentence that contradicts a sentence in another article on the same topic in the same library. A working news piece, a working analysis piece and a working explainer should both survive the second read.
The contradictions a reader is looking for are not the small ones. A reader who has been working with the piece for a while will catch the small ones by accident. The contradictions the second read is meant to catch are the structural ones, where the first half of the article establishes a fact and the second half quietly walks the fact back. The second read is the cheapest way to find the walk-back, because the reader's memory of the first read is still fresh enough to spot the change of mind.
Cross-article contradictions are harder to catch and more expensive to fix. The reader who has read two pieces on the same topic in the same library and cannot reconcile them is, in most cases, reading a library that did not coordinate its pieces. The reconciliation job is then the reader's, not the library's. A library that has run the second-read test on its own pieces will make the reconciliation job easier, because the pieces will agree on the underlying facts even when they disagree on the interpretation. A library that has not run the test will not agree on the facts, and the reader will leave the library thinking the topic is contested when the topic is only under-coordinated.
Where the four tests break, and the genre that breaks them
The four tests break in one place: the opinion piece. An opinion piece is a genre that borrows the form of an analysis piece without doing the work of a trade-off paragraph, the form of an explainer piece without doing the work of a re-usable rule, and the form of a news piece without doing the work of a named source. The reader who runs the four tests on an opinion piece will produce a misleading score, because the tests are designed to fail opinion pieces and the tests are doing their job.
The reader's task in that case is to recognise the genre before the tests run. The first paragraph of an opinion piece is usually the only place the genre is announced. The reader who reads the first paragraph and asks "is this a fact or a take" will know which tests to apply. The reader who skips the first paragraph will run the wrong tests, get the wrong score, and either trust a take or distrust a fact. LetsGame editors treat the first-paragraph genre check as a prerequisite to the four tests, not as a fifth test.
A practical way to use the four tests on a library you have never read
The practical use of the four tests is the order. Start with test one, because the genre is unknown and the genre determines the rest. Move to test two if the piece is an analysis piece, to test three if the piece is an explainer piece, and skip both if the piece is a news piece. End with test four on every piece, because the second-read check is cheap and catches the structural contradictions regardless of genre. The reader who uses the order will sort a library in a single sitting. The reader who uses the tests out of order will sort a library three times and not trust the result.
Readers looking for the next piece to add to their reading list can move from this method to the rest of the guides library at LetsGame guides, where the long-form walkthroughs are listed in the order LetsGame editors would read them if they had to read a new library in a single evening.
