Answerdle / Krillion Archive: What Past Days Do and Don't Tell You
Krillion Archive: What Past Days Do and Don't Tell You
How the Krillion archive works, what past days can and cannot tell you, and how to turn old prompts into better rare picks today.
The archive is the part of the game most players misunderstand, so it is worth being precise about what it is: a record of earlier days, not a key to today's.
What the archive is
The game keeps an archive of earlier days at its own address (/archive), separate from the daily dive and from the unlimited mode. It exists so that a run you missed is not gone forever — the same reason every daily puzzle game eventually grows one.
What the archive is not is a published answer key. Today's seven prompts are only visible inside your own run and they change every day, so any page claiming to list today's Krillion answers before you have played is inventing them.
Why past answers do not transfer
This follows directly from how scoring works. Rarity is decided per prompt: each prompt has its own answer set, built by aggregating dictionaries, wiki pages and encyclopedias, and every accepted answer is scored against a familiarity database of how often that word or name turns up in what people read and write. Some prompts are scored with model help and a human pass instead.
So the rare answer you found for name a cheese is not a rare answer for name a country with a coastline. It was scored against a different answer set with a different frequency curve. Memorising yesterday's winning picks gives you close to nothing.
What does transfer is the shape of the problem: which kinds of answers sit at the common end of a curve, and which kinds are unusual but still real enough to be in the answer set at all.
What the archive is genuinely good for
- Calibrating difficulty. Read a week of prompts and you see how often the game reaches for geography, food, sport and animals. That tells you where to prepare.
- Building the third-idea habit. Old prompts are a free question bank. Cover the answers, give yourself twenty-five seconds, and force out your third idea instead of your first.
- Spotting your own blind spots. If you freeze on the same category every time it appears, the archive makes that obvious in a way a single daily run cannot.
- Reading the room. When a prompt repeats a theme, your old third idea is still a decent starting point — not because the answer set is the same, but because the category is.
How to practise with it in ten minutes
- Pick five prompts from past days. Do not read any answers first.
- Set a twenty-five second timer for each, exactly as in the game.
- Write down your first idea but do not use it — use your third idea.
- After each prompt, ask the only question that matters: was that answer real, and was it unusual?
Real but common means you need a different map. Unusual but not real means you were being clever rather than right. That distinction is the whole game, and it is also why a rejected answer hurts more than a boring one: a common answer still earns a little depth, an invalid answer ends the prompt at zero.
The archive and the rarity curve
One more thing worth knowing before you dig. Rarity is a property of the answer, measured against a familiarity curve rather than a vote from the day's crowd. An answer that was genuinely uncommon last month is still roughly as uncommon today; an answer that has since gone mainstream has drifted toward the common end.
Which is the useful way to read an archive: not as a list of past winners, but as a record of how fast certain answers went from obscure to obvious.
Try it on a live prompt
Reading is not practice. The five-minute dive on our home page gives you seven prompts, twenty-five seconds each, and scores you on how few of today's players picked the same option — the same reflex the archive is meant to train. For the mechanics in one place, the scoring guide covers the clock, the rejection rules and the rarity curve; for volume rather than one run a day, unlimited mode is where to grind.
Checked against the game's own pages and its developer FAQ before publishing. If a rule has changed, say so on the contact page and it gets fixed.