Data sources and editorial policy

Primary source

The public Krillion reveal endpoint

Prompts, accepted answer spellings, tier IDs and scores come from the official public endpoint at krillion.io/api/reveal. Each request is tied to a calendar date. The archive currently runs from July 16, 2026 through August 25, 2026.

The current date, Daily Dive number, seven live prompt texts and next reset timestamp come from the official today endpoint.

What the importer checks

• The response date must match the requested date.
• Every Daily Dive must contain exactly seven unique prompt IDs.
• Every accepted answer must have non-empty text, a recognized tier and one of the observed score values: 10, 15, 30, 60, 85 or 100.
• Duplicate answer spellings inside one prompt are rejected during import.
• Raw dated JSON stays separated by date; daily summaries and practice pools are derived after validation.

How search normalization works

Tools ignore capitalization, repeated spaces, simple punctuation and diacritic marks when comparing a typed answer with a reveal spelling. They do not infer semantic synonyms, expand abbreviations or decide that a new edge case should be accepted. When a spelling matches, the official display answer is shown back to the player.

Editorial versus source data

Answer rankings, scores, prompt text and dated counts are source data. Strategy advice, route-improvement logic, page summaries and tool instructions are original editorial work. The planner performs transparent arithmetic; the Practice Dive applies historical reveal scores to historical prompts. Neither tool claims access to an unpublished scoring algorithm.

Corrections and rights requests

If a public reveal changes, a later data sync can replace the affected dated snapshot. For a correction, copyright concern, privacy request or removal request, use the contact form and include the exact page URL and supporting source.