Timelines across POVs and flashbacks

Two orders run through every story: the order events happen, which is story order, and the order the reader meets them, which is publication order. With one viewpoint and straight chronology they are the same line, and almost nothing can go wrong. Add a flashback or a second viewpoint and they diverge. Continuity errors live in the gap: the character who is in two cities on one day is almost always a story-order mistake wearing a chapter-order disguise (see the seven continuity errors).

One spine, in story order

Keep the master timeline in the order events happened. Every scene gets a position on that spine, whatever chapter it appears in. Chapter order is a presentation choice; the spine is the truth of the world. When you plan chapter fifty, the question to ask is not "what has the reader read by now" but "what has happened by now", and only the spine can answer it.

Three ways to anchor an event

Not every event needs a date, but every event needs a position. Three anchors cover everything:

1. Absolute: the fourth of March, year 1024. Precise, and what you want for court intrigue, alibis, and any mystery where two people cannot be in one room.
2. Relative: three days after the festival, the night of the attack. This is how stories naturally speak. Chain relatives carefully: each link inherits the looseness of the last, so tie relative chains to absolute points now and then, or drift compounds silently.
3. Pinned: no date at all, but fixed between neighbors: after the duel, before the coronation. Unknown dates are fine; unknown positions are not. An event whose place in the order is known can stay dateless forever.

Flashbacks carry two timestamps

A flashback has a when-told and a when-happened, and the timeline cares about the second. Record both:

• Story date: where the flashback's events sit on the spine, back in the past, next to the events that surrounded them.
• Frame chapter: where it is told, which decides what the reader knows when they reach it.

Two rules keep flashbacks honest. First, a flashback narrates the past; it does not modify it. Whatever it shows must fit the states characters were in at that earlier time, so a flashback showing Kai acting on the King's secret before he learned it breaks continuity exactly as a present-day scene would. Second, respect the knowledge ledger: a flashback informs the reader directly, and informs only those characters who were actually there.

Multiple viewpoints multiply threads

Each point-of-view line is its own sequence of scenes on the same spine. Interleaving them across chapters is presentation; the spine keeps them straight. Three collisions recur:

• Same-day overlaps: two viewpoint characters in the same market on the day of the attack. Some overlaps are the point of the structure. The spine shows you which overlaps you designed and which you merely failed to notice.
• Travel math: each line carries its own location thread, and the distance between the lines bounds what next chapter can do. "She rode through the night" pays for one impossibility, once.
• Information bleed: when the lines meet, each character knows only what their own chapters showed them, not what the reader has assembled from all of them. This is where timeline discipline and point of view discipline turn out to be the same discipline (see choosing point of view).

Backstory is timeline too

Historical events belong on the same spine at their own dates. The war thirty years ago, the founding of the order, the day the dragons left: backstory that floats free is backstory that contradicts. Ages hang off these anchors, and "how old was he during the war" is a question readers really do ask. A grudge that predates the founding of the guild that supposedly caused it is a classic deep-cut contradiction, and a spine with backstory on it catches it in seconds.

The pre-scene check

Before writing any scene, four questions from the spine:

1. What is the story date, or the anchor?
2. Who is where at that moment, across every thread?
3. What has happened by now, in story order?
4. What does each character present know by now?

If any answer requires remembering instead of checking, the spine is stale, and the fix is the same as everywhere else in continuity: record the event at its story position the day you write it.

How Kanonara approaches this

The timeline in Kanonara is maintained as a chronological record alongside chapter order, and it supports absolute dates, relative dates, events with unknown dates, flashbacks, multiple viewpoints and historical backstory. When two events cannot both be true, the conflict surfaces as an alert with the evidence on both sides, and the author decides what happens next. See how Kanonara works.