Reading and reveal order

A fictional example for documenting route order, narrator spans, chronology, and reveal boundaries.

This is a compact, fictional example. A private project version should cite the real scenario IDs, unlock data, and runtime evidence.

Purpose

Use player-facing order rather than filenames or extraction order. This authority prevents an editor from assigning the wrong narrator, using knowledge from a later reveal, or reviewing a route before its prerequisites are understood.

Chapter order

OrderChapterUnlock requirementNarrator / POVTimeReader knowledge at entry
1P0 — Arrivalnonedeliberately unidentified first personpresentThe narrator knows the harbor but has no displayed name.
2A1 — Fog SignalP0Mina Kurosepresent“The Courier” is only a title; no civilian identity is known.
3X1 — Ten Years EarlierA1unidentified witnesspastThe witness's later identity must remain hidden.
4B1 — Low TideA1 + X1Ren SaegusapresentThe player may connect two aliases, but Ren has not.

If routes unlock in parallel, record both the engine's requirement graph and the editorial tie-break order used by the project.

Narrator ledger

Chapter / rangeNarrator statusEnglish person and numberEvidenceAvoid
P0:0001–0068unknown by designsingular Iexplicit ; solitary actionsAdding a gendered self-description.
A1Mina Kurosesingular Iname box, internal monologue, scene continuityTreating blank speaker cells as neutral narration.
X1unresolved witnesspreserve local ambiguitysubject omission and hidden faceImporting the identity learned in B1.
B1Ren Saegusasingular I; institutional we only when explicitroute header and faction dialogueNormalizing every 我々 or omitted subject to “we.”

Reveal boundaries

FactFirst suspectedFirst confirmedTranslation rule before confirmation
The Courier has a civilian nameA1:0210B1:0144Use the title or source pronoun; never insert the name.
The X1 witness survivesX1:0090B1:0302Preserve uncertainty and evidential language.
Two organizations share a founderA1:0331B1:0418Keep their names and ranks distinct until the source connects them.

Working rules

  • Read and review in this order, even when archive names sort differently.
  • Identify the narrator from scene evidence, command rows, and route context—not from the current English draft.
  • Later knowledge may explain an earlier ambiguity to the editor, but it does not authorize an early reveal.
  • Recheck every English I/we/my/our form after the full story map exists.
  • Record unresolved narrator spans explicitly; “unknown” is a valid controlled state.

Sign-off

  • Engine unlock graph checked: [date / evidence]
  • Editorial order checked: [date / reviewer]
  • Narrator spans audited: [count / result]
  • Reveal-sensitive terms cross-referenced to terminology authority: [version]