THE LEEPER ARCHIVE
Archive 002 / Chapter 18 / Current canon
Revised · 28 September 2026

Night of Three Orders

Three instructions collide over a grain convoy. Crews publish technical state and act locally; a held UNKNOWN request and a later custodial notice keep the political problem open.

Read revised chapterRead 26 September canon studyDownload structured canon

Evidence basis. These findings cite the current novel by paragraph. The earlier canon study remains available as a dated record of the first edition. Some identities, motives and claimed authorities remain unresolved in the story.

What changed / what remains open

  1. The revised text records an actual split of four transports, preserving who approved flight changes and who controlled ground conditions. ¶231 ¶285 ¶287 ¶290
  2. The held UNKNOWN request narrows the evidence to attempted access; its author and any later defence acceptance remain open. ¶156 ¶158 ¶160 ¶373

People, places and evidence

Character · A2-CHAR-ARUN

Arun Vey

Refuses to turn incompatible instructions into a single engineering order, publishes local technical states, and preserves the held UNKNOWN request without claiming a battery accepted it.

Visual cue: Live state board with local crew entries.

Evidence ¶42 ¶49 ¶70 ¶79 ¶160 ¶417

Character · A2-CHAR-ROOK

Commander Rook

Controls airborne spacing and approves updated landings as depot capacity changes while ground crews maintain their own safety decisions.

Visual cue: Aircraft plan annotated by receiving field.

Evidence ¶231 ¶263 ¶285 ¶287

Character · A2-CHAR-KORR

Eda Korr

Works from weather, fuel, berth count and unloading figures while the four transports share one western corridor.

Visual cue: Flight table with weather strips and fuel figures.

Evidence ¶1 ¶9 ¶30 ¶231 ¶286

Character · A2-CHAR-NARA

Nara Venn

Keeps receiving requests tied to actual labour and lift capacity and warns that shared technical coordination also needs public accountability.

Visual cue: District request beside changing berth figures.

Evidence ¶91 ¶99 ¶349

Character · A2-CHAR-MARIAN

Marian Vale

Issues a non-recognition notice about disputed identity authority over weapons and routing; it is not a technical battery order.

Visual cue: Succession-office notice next to battery log, as separate documents.

Evidence ¶20 ¶107 ¶120

Records · A2-OBJ-THREE-INSTRUCTIONS

The Three Instructions

Custodial routing, Marian’s non-recognition notice and district receiving requests have different scopes. The actual operation is preserved alongside each original instruction.

Visual cue: Three distinguishable documents, not one composite command.

Evidence ¶20 ¶24 ¶25 ¶42 ¶287

Record · A2-OBJ-STATE-BOARD

The Corridor State Board

Stations publish firing-path, tracking, berth and service conditions, then coordinate through visible local information without giving the board command power.

Visual cue: Public board with time-stamped local states.

Evidence ¶70 ¶79 ¶82 ¶83 ¶91 ¶99 ¶417

Record · A2-OBJ-HELD-UNKNOWN

Held UNKNOWN Readiness Request

UNKNOWN requests a battery readiness review, repeated twice; the local identity freeze holds the request before authority translation. No accepted defence command is shown.

Visual cue: Hold strip visibly distinct from an accepted order.

Evidence ¶156 ¶158 ¶160 ¶373

Place · A2-PLACE-WESTERN-BELT

The Western Defence Corridor

The four transports use a weather corridor across defence installations while local crews inhibit firing paths and retain needed tracking functions.

Visual cue: Crew at controller and physically inhibited firing path.

Evidence ¶9 ¶79 ¶181 ¶196

Event · A2-EVENT-FOUR-LANDINGS

The Four Grain Landings

The actual distribution is two central, one Lower East and one Lower South, reached through changing capacity and local support rather than a permanent allocation rule.

Visual cue: Four flight paths with separate landing notes.

Evidence ¶231 ¶285 ¶286 ¶290 ¶291

Record · A2-OBJ-UNAUTHORISED-NETWORK

The Coordination Notice

Custodians challenge inter-station coordination and publication of operational states; crews continue logging local conditions because suppressing the board would hide service dependencies.

Visual cue: Formal notice pinned beside new state entries.

Evidence ¶349 ¶375 ¶417

Continuity boundaries

  1. The three public documents differ in legal and operational scope; their overlap does not merge them into a common command. ¶20 ¶24 ¶42 ¶287
  2. Marian’s non-recognition notice is not a technical order to batteries. ¶20 ¶107
  3. The state board displays local conditions; flight command stays with Rook and operating responsibility remains local. ¶70 ¶79 ¶231 ¶287
  4. Two UNKNOWN readiness requests are held; the chapter shows attempted access, not successful defence control. ¶156 ¶158 ¶160 ¶373
  5. All four aircraft land: two central, one Lower East and one Lower South. The distribution is an operational result. ¶285 ¶286 ¶290
  6. The notice challenges the coordination network’s accountability while the network continues to report local states. ¶349 ¶375 ¶417

Companion records

Game design candidates

Untested ideas. Costs, rarity, timing and rules have not been approved; this canon update does not change the live game.

Record · Infrastructure, Knowledge

Corridor State Board

Share a visible local system state that another player may use without making the board an order.

Based on A2-OBJ-STATE-BOARD

Record · Knowledge

UNKNOWN Request — Held

Show an attempted authority use halted before acceptance.

Based on A2-OBJ-HELD-UNKNOWN