Detect a timeline whose dates cannot all be true at once

Chapter by chapter the dates look fine, but taken together the war ends before it starts or the heir is born after the funeral. Here is how your AI turns your story's time statements into something it can test, and which part it points at.

Why this works

Dates in a story are promises about order and distance, and promises can contradict each other even when each one is fine alone. Treating every statement as a small rule, then looking for a ring of rules that cannot all hold, shows exactly which statements to give up.

When not to use it

Skip it when your story plays with time on purpose, such as dreams, visions, parallel worlds or time travel, where events are allowed to contradict. There, keep a separate timeline for each strand and check each one on its own.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 39 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Detect a timeline whose dates cannot all be true at once" (read_entry story-timeline-that-cannot-be-true) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP