Back to Blog
Insights

Caught by Paper, Never by Motive: 5 Rules for a Mystery You Can Solve Fairly in 90 Seconds

Every free 90-Second Case on this site is built to one design table, five clauses long: exactly one statement contradicted by a document; every other statement corroborated by a document rather than by another witness; the tell readable on one screen inside ninety seconds; caught by paper and never by motive; years redacted.

Read together, those five lines are a definition of a fair mystery, and a stricter one than many mysteries use. On this definition, a mystery is fair when its answer is on the page: you can reach it from what you were given, and once you have it, you can point at the line that proves it. Here is what each rule is for, what each one costs, and why the same idea runs through the printable case file, the party game and, as it happens, the way I read a log file.

Rule 1: Caught by Paper, Never by Motive

Start with a mystery that is not one of ours. A laptop goes missing from a shared office on a Friday evening, and three people were there late: the office manager, a contractor and an intern. The manager has been asking for a new machine for months. The contractor is still waiting to be paid. The intern lost an argument about the project that lives on that laptop.

That is three motives, and they settle nothing. Any of the three can be written up as the obvious suspect, and a reader who picks one is picking a character, not reading evidence. A motive can make someone look guilty, but it cannot show that they did it, and a mystery that leans on it turns into a guessing game about who seems the type. It also leaves the writer a trapdoor: one more reason revealed in the last paragraph, and the reader who guessed right never had a way to know it.

A time written on a document is different. It either agrees with what someone said, or it does not. That is the first rule in one sentence: whatever decides the answer has to be something that could have come out the other way.

The rule does not ban motive from the story. A suspect can have every reason in the world to have done it. The rule is that no reason ever settles the answer.

Rule 2: Every Other Statement Is Backed by a Document, Not a Witness

Now give the three a statement each. The manager says she left at ten to six for an appointment across town. The contractor says he drove home at half past five. The intern says she was the last one out and locked up at seven.

The easy way to support a statement is with another person: the intern saw the manager leave. It is also the way that quietly ruins the puzzle. If one witness vouches for another, clearing the manager means trusting the intern, and the question becomes whom you believe, which is motive again with an extra step. Witness against witness turns the puzzle into who you trust instead of what is true.

So the second rule backs every true statement with paper instead. The clinic's front desk checked the manager in at 6:20. The alarm company logged the office as armed at 7:02. Neither record cares who took the laptop, and each one either agrees with the statement beside it or does not. Here, both agree.

Rule 3: Exactly One Statement Does Not Survive

Then the contractor. He drove home at half past five, he says. The garage under the building stamped his car out at 6:48. That is the lie, and in a case built this way, the lie is the answer.

The case page says the rule in one line: “One statement does not survive the paper.” Exactly one, because both other numbers break something. With no contradiction, the answer is not on the page and the reader is back to guessing. With two, there are two suspects, and whatever breaks the tie has to come from outside the documents, which in practice means motive, the thing the first rule just ruled out.

One contradiction turns the answer from a judgment into a finding. There is one name, and one line on the page you can put your finger on to defend it. It is also what makes a clock honest: a case with one lie has a right answer that can be graded, while a case with two plausible readings can only be argued about.

The test every statement faces

A statement is a claim. A document is the evidence it has to survive. Every statement but one survives, and the one that does not is the answer.

Rule 4: The Tell Fits on One Screen, Inside Ninety Seconds

The fourth rule is the one the format is named for. The tell, the place where a statement and a document disagree, has to be readable on one screen inside ninety seconds. The page's own instruction is the method in miniature: “Read everything once. Then name the liar.”

Short and fair pull in the same direction. A long mystery can bury its answer in volume and call that difficulty. A ninety-second case has nowhere to bury anything, so the contradiction has to sit in plain view, and the only way to make a case hard is to make that contradiction quiet rather than hidden. The length limit and the fairness rule end up enforcing each other: if the answer has to be findable on one screen, it cannot depend on something the screen does not show.

What the clock does not promise

The rule is about the page, not the player. A case is designed to be readable on one screen inside ninety seconds; nobody is promised they will find the tell in that time. Finding it is the game.

Rule 5: Years Redacted

The fifth rule belongs to the world the cases live in. Every case page carries the same archive line, “From the research archive of the podcast THE COLD LEDGER.” It carries the same note about dates, too: “Years redacted per release agreement.” The framing is not decoration. A true-crime podcast's research folder is a place where a police report, an insurance file and a forensic re-examination can plausibly sit side by side, which is exactly what a mystery built on documents needs.

Inside a file, dates are relative. The printable case file's start page begins “Fifteen years ago tonight,” not with a year, and the script that builds each case page refuses to build one if a four-digit year appears in its text.

For fairness, what that buys is modest and real: it takes the calendar out of play. A full date invites checks against the world, such as what weekday it fell on or what was in the news that night, and a puzzle that can be solved, or broken, by a fact from outside the page is less fair to the reader who only has the page. Without the year, a date in a file answers to the rest of the file. It also keeps a case from being pinned to the year it was written, though that is a smaller claim than it sounds, since a story can show its age in plenty of other ways. What it will not do is hand you a year to check it against.

The Same Rule at Three Sizes

The core of it is not special to ninety seconds, which is what makes it a design rule rather than a product note. The paper rule scales.

The Orpheum File is the same idea at seventeen exhibits, for one or two readers. Its start file makes the promise on page one: “Everything you need is in these pages. Nothing is missing. Some of it is lying.” A few lines later it tells you how to read them: “Every exhibit either gives you a time, contradicts a time, or connects two documents.” That is the paper rule, written as an instruction to the reader.

The Hundredth Episode is the same idea with eight to twenty people in a room. Partway through the evening every player reads a statement aloud, verbatim and on the record, and when the round ends the host tells the room: “Those statements are on the record. The evidence will agree with almost all of them.” More suspects and a longer night, and underneath it the same test: what people said on one side, paper on the other. How the rest of the evening runs is in Four Killers in One Box, and which of the three to start with is in 3 Ways to Play a Mystery.

Testimony, Not Proof

It is a rule I trust in software, too. A log line that says something succeeded is testimony, not proof. It is evidence that something ran; it is not proof the result happened.

The Failures That Log Success is about exactly that gap: a system that finishes cleanly, writes a reassuring line and did not do the thing. The fix there has the shape of the second rule. A test that keeps its own copy of a list agrees with whatever it copied, a witness vouching for a witness. The test that counts reads the source of truth, the schema itself, and lets the code survive it or not.

And It Passed for the One Input I Happened to Give It is the first rule seen from the testing side: a green result is only evidence if you know what would have made it red. Motive can never come out red. Paper can. That is the whole reason to build a case, or a check, on it.

Five Rules Worth Stealing

For anyone writing a puzzle of any length, here are the five as a checklist:

  1. Decide the answer with a record, never a reason. Give the suspects all the motive you like, and let none of it settle anything.
  2. Back every true statement with paper, not with another witness. Witness against witness is a test of trust, and trust is not what the reader came to test.
  3. Allow exactly one contradiction. None leaves the answer off the page; two send the reader back to guessing.
  4. Size the tell to the time you give. If the clock is ninety seconds, the contradiction lives on one screen, in plain view.
  5. Take out whatever the reader could check outside the page. Redact the year, date things relative to each other, and keep the argument on the page.

None of the five is clever, and together they make a mystery you can lose fairly: when you name the wrong person, the line that proves it was on the screen the whole time, and when you name the right one, you can point to it. That is what makes a solution feel earned.

Try the Rules on a Case

The 90-Second Case: four exhibits, three statements, one lie, ninety seconds. Free, in your browser.

Open a Case
BW

Brandon Wigley

Founder of Wigley Studios. Building developer tools since 2018.

Previous: 3 Ways to Play a Mystery All Articles