Publishing methodology
One answer, proven before publication.
Every ClueAxis case is both a short story and a formal constraint problem. The story is not the proof: the solver is.
Unique-solution verification
Each event and clue is translated into a machine-readable constraint: fixed position, excluded position, before, immediately before, or exact distance. A deterministic solver checks every possible ordering. Publication stops unless exactly one ordering satisfies every clue and that ordering matches the stored answer.
Logic diversity
Changing character names does not create a new puzzle. We calculate a structure signature from the answer-relative positions and relationships in each case. The twelve-week catalog must contain at least twelve materially different signatures, and no single signature may account for more than 12.5% of published cases.
Readable clues and progressive hints
The plain-English clue must express the same relationship as its stored constraint. Hints point first to an anchor or tight relationship, then become more specific. The closed-case explanation is kept separate from the playable deduction.
Corrections
If a clue is ambiguous or a record behaves incorrectly, the affected case is held or corrected. The full case date and title identify the version. The contact page provides the reporting route once the production domain mailbox is connected.