Three overlapping instructions, a held UNKNOWN defence request, live corridor state and the accountability problem created when lateral coordination succeeds.
Historical canon pack: these claims and numbered evidence links document the 26 September 2026 text. The novel has since been revised. A “revised passage” link appears only when the cited wording survives in the revised chapter; other claims await editorial verification.
Established story material
A2-CHAR-ARUN · Character
Arun Vey
Refuses to turn three overlapping public instructions into one engineering command. He publishes live system state instead, keeps technical responsibility local, and later refuses to shut down the shared state network merely because the custodians call it unauthorised.
Use the Spine state board, station calls and public operational logs; avoid depicting Arun as a central commander issuing orders to every system.
A2-CHAR-ROOK · Character
Commander Rook
Retains command of aircraft in flight while relying on ground engineers, receiving depots and local state reports. He accepts a held UNKNOWN request as evidence of risk without treating it as an accepted defence command, and splits the convoy by live capacity and weather.
Flight map and corridor display rather than combat action; emphasize decision under incomplete ground information.
A2-CHAR-KORR · Character
Eda Korr
Turns political demands into operational questions: number of supported fields, fuel, timing and actual landing capacity. Her pressure for useful numbers keeps the convoy plan tied to what aircraft and ground crews can do.
Route strips, fuel notes and receiver traffic; no decorative command pose.
A2-CHAR-NARA · Character
Nara Venn
Prevents the Lower City receiving request from becoming a claim of jurisdiction simply because the convoy later uses Lower City depots. She also warns that lateral engineering coordination can itself become unaccountable power if it hardens into command.
Public state board and depot-capacity notes; avoid victory-rally imagery.
A2-CHAR-MARIAN · Character
Marian Vale
Issues a non-recognition notice rather than a technical counter-order: disputed estate, MASTER or succession-derived identity cannot by itself establish lawful authority over weapons or military routing. She does not command the batteries or aircraft.
Legal notice beside the live system board; no command seal or military imagery.
A2-CHAR-VOSS · Character
Halden Voss
Pushes for central accountability and initially treats the engineering state network as a dangerous parallel command structure. After the convoy succeeds, his office issues a notice against unauthorised inter-station coordination and summons Arun to the Council House.
Postmortem table and formal notice; avoid caricaturing him as simply anti-engineer.
A2-CHAR-ELIZA · Character
Eliza Marr
Preserves the three instructions, the actual operational deviations, and the two held UNKNOWN readiness requests as separate evidence. She refuses to reduce the outcome to a winner or a single obeyed command.
Three public documents beside the actual system timeline and deviation log.
A2-CHAR-PERA · Character
Pera Sol
Publishes receiving capacity, system states, timing notes and the final distribution caveat. Her records make coordination observable without turning the public board into a command authority.
Public board with timestamps, depot capacities and caveats; no central dispatch throne.
A2-OBJ-THREE-INSTRUCTIONS · Authority records
The Three Public Instructions
The custodians seek confirmed battery safe state and central warehousing; Marian's office refuses to recognise disputed identity authority over military systems; receiving courts ask for Lower City landings based on capacity. Their scopes overlap but they are not identical kinds of authority.
Three visibly different documents with distinct source and scope fields.
A2-OBJ-NONRECOGNITION · Legal position record
The Non-Recognition Notice
States that registry acceptance of disputed estate, MASTER, preservation-office or succession-derived identity does not establish lawful authority over weapons or military routing. It explicitly does not command any defence system.
Legal notice with the sentence THIS NOTICE DOES NOT ITSELF COMMAND ANY DEFENCE SYSTEM.
A2-OBJ-STATE-BOARD · Coordination record
The Live Corridor State Board
Publishes local technical states, capacity and hazards without issuing commands. Stations use it to coordinate and ask one another for help, while each local crew remains responsible for its own operating decision.
Multi-station state board with status lines and timestamps; do not style it as a command dashboard.
A2-PLACE-WESTERN-BELT · Infrastructure zone
The Western Defence Belt
The only usable weather corridor crosses legacy defence systems whose authority pathways are still under the identity freeze. Crews physically isolate firing paths while preserving tracking and weather functions.
Night corridor map and local battery status lights; avoid weapons glamorisation.
A2-OBJ-HELD-UNKNOWN · Disputed authority request
UNKNOWN — Readiness Review Held
UNKNOWN twice requests a readiness review from Battery Two. The local identity freeze holds both requests before authority translation. This is evidence of attempted access to a defence-related controller, not successful defence control.
Local acceptance log with REQUEST: READINESS REVIEW and STATUS: HELD.
A2-EVENT-RESERVE-TRANSFER · Coordination event
The Six-Minute Reserve Transfer
A pumping-station engineer publishes spare reserve capacity and temporarily supports Lower Depot South's beacon without a central citywide order. The transfer stays within the station's operating minimum and ends before the next pump cycle.
Three linked local-state entries—water reserve, beacon demand, central capacity—not a heroic switch pull.
A2-EVENT-FOUR-LANDINGS · Supply event
The Four Grain Landings
Four grain transports ultimately split two to central warehouses, one to Lower East and one to Lower South. The distribution emerges from live lift, berth, beacon, weather and fuel conditions rather than a pre-agreed political allocation.
The custodians declare inter-station coordination and public operational-state sharing outside recognised central channels pending review. Stations continue publishing because removing the shared state would make operations slower and less visible, even if nothing collapses immediately.
Places three overlapping authority claims face up; none automatically overrides the others, and effects resolve only within each source's actual scope.
Open design question: Avoid requiring legal interpretation mid-game; use clear printed scopes.
Records an attempted high-level request that is stopped before permission translation. It may support later investigation but grants no active authority.
Open design question: Ensure held requests cannot be exploited as free activation triggers.
Lets several Places share visible state and make bounded local choices without creating a central controller; later authority effects may challenge its legitimacy.
Open design question: The card should enable coordination without becoming a stronger central command by another name.
Chapter 18 follows the partial identity freeze of Chapter 17. UNKNOWN remains locally disabled and under review.
No defence system is established as having accepted UNKNOWN. Battery Two receives readiness-review requests that are held before authority translation.
Marian's non-recognition notice is not a technical order to batteries and does not make her commander of defence systems.
The three public instructions are different in scope and authority; the chapter's tension comes from operational overlap, not from pretending they are legally equivalent.
Rook retains flight command once aircraft are airborne. Ground crews and receiving depots retain their local safety and capacity responsibilities.
The live state board publishes system conditions and hazards but is not itself a command authority.
Battery crews isolate firing paths while preserving needed tracking/weather functions. No battery fires during the convoy.
The Lower City receiving request is based on unloading capacity and does not become permanent jurisdiction simply because two Lower City depots receive grain.
The six-minute reserve transfer stays within the pumping station's operating margin and is locally documented.
The four transports land successfully: two central, one Lower East and one Lower South. No air battle occurs.
The final distribution is explicitly labelled as a result of live capacity and flight conditions, not a permanent allocation rule.
The two UNKNOWN readiness requests are preserved as evidence of attempted access, not successful control.
Arun does not issue a citywide order replacing the three authorities. Local stations act within published technical limits and coordinate laterally.
The custodians' morning notice challenges the legitimacy/accountability of the engineering coordination network and sets up Chapter 19; it does not physically shut the network down.
Chapter 19 must inherit the accountability problem: coordination worked, but distributed technical power still needs a defensible governance structure.
Existing Chapter 9 artwork, Chapter 5 notes, Archive 001 content and live game rules remain unchanged.