Open Questions

Living document. Updated as installments are drafted. Two sections: Open Questions (narrative threads awaiting resolution) and Continuity Notes (quirks, misalignments, and decisions that need resolving before production).

Questions marked 🔒 are spoiler-protected — do not surface to narrators or playtesters until the relevant story beat is reached.

Part 1 — Open Questions by Theme¶

Janus — Personal History¶

What happened at Cinder-7 (2843)? Janus was team leader. A forced decision under time pressure: innocent lives or his team. Three team members did not come back. The Corps classified it as routine. What specifically were the conditions? What made it unsolvable?
When did Janus leave the Vanguard Corps, and under what circumstances? The separation carries no punitive classification on record. The gap between correct decision and Corps exit shortly afterward is its own kind of statement.
Why does Janus have a Fabric protocol patch on the TAP-7? He added it himself at some point between leaving the Corps and arriving at Hephaistos-9. He has not examined this decision. The story eventually will. [See also: Continuity Note C4]
Why did Janus recognise the Fabric relay frequency? He knew it deliberately — "I knew what frequency it was." This implies prior Fabric contact, which predates the Hephaistos-9 contract.

The Cinder-7 Survivors¶

Three confirmed survivors hold Janus responsible. A fourth survivor's position is not stated. Where are they now? How close are they?
The leader — former second-in-command — made the patient choice at the time: let Janus go, wait for a better moment. Four years have passed. Is this the moment they have been waiting for?
🔒 Do they know Hephaistos-9 is dark? They tracked Janus to his last known contract. The station going silent is either a news event or a sign. How do they interpret it?
🔒 What happens when they find Janus mid-operation — with the android already shadowing him, the nanotracker transmitting, and the data module in his pocket? They do not care about any of that. Neither does the situation.
🔒 The confrontation is not primarily about whether they can hurt him. It is about whether he has anything to say to them that is not I was right. Does he?
🔒 The fourth survivor — the one whose position is unstated. Are they with the group, estranged from it, or somewhere that makes them relevant to Janus's current situation in a different way?
Is there any version of the confrontation in which the survivors become temporary, grudging operational assets rather than adversaries? Their skills, Janus's situation, the right pressure point — all the conditions exist. Whether the motive can be set aside is a different question.

Ana Hamato — Whereabouts and Intentions¶

Where is Ana now? She departed the short-stay block approximately ten weeks before Janus arrives at it. Her dead-drop note gives a second address encoded as a Fabric routing cipher. That meeting date has passed.
Did the supply transport from Hephaistos-9 reach its destination without incident? Ana left three days before the kill team arrived. Whether Praxis tracked the transport manifest is not stated.
Does Ana know Hephaistos-9 is gone? She has no way to know unless someone told her — or unless she has Fabric contacts who monitor station incident logs.
Does Praxis Biomechanica consider Ana a loose end? She left the station before the incident. She had access to the probe telemetry archive. She filed a flag. Whether Praxis knows she understood what she filed is not established.
Ana's dead-drop note says come alone and don't use your real name. Does she have a verification method at the second location? She wrote the note for an unknown recipient — she cannot rely on face recognition alone.
How does the Fabric know about Ana? The Fabric node has a partial record including her alias and short-stay address. Did she contact the Fabric deliberately, or is she already inside the network?
The thirty-day window she gave Janus has long expired. What is her contingency plan for no-show?

The Data Module¶

What, precisely, did Ana find in the probe telemetry? A recurrent signature in a frequency band the senior team categorised as instrumental noise. What does it represent? [Not stated in current canon — this is the central mystery.]
Did Ana understand the full significance, or only enough to be afraid? Her departure was fast and careful. Her note says "I don't know. Exactly." — technically true, deliberately incomplete.
What is the military-grade encryption on the module's index layer? It uses Vanguard Corps classification standard from the Outer Ring Disputes. Why does a Praxis Biomechanica research archive use Vanguard Corps encryption?
Who, currently, has the capability to decrypt the module? Janus has the TAP-7 — a Vanguard Corps intrusion device — but decryption of the index layer is not the same as reading twelve petabytes of optical lattice data.

Kirk Vasquez¶

🔒 What frequency did Kirk set on the comms panel, and who received the transmission?
🔒 Was Kirk extracted by the black ship willingly or under duress? He said "I'm sorry" before losing consciousness. What does he know?
🔒 Does Whisper know the data module exists? Kirk observed that Janus concealed something in the foam. Did he report this before losing consciousness?
🔒 Kirk's secondary transmitter — the device Janus saw on day one of the drift. What was it? What did it send?
🔒 "I don't even know why I'm here" (Echos in the Cold, page 8) and "What am I doing here?" (page 9) — both are true in a way Kirk did not rehearse. After eighteen months undercover, how much of the cover has become the person?

Whisper¶

⚠️ Permanent open question. Whisper's identity is never fully resolved. The questions below are narrative threads, not promises of answers. The shape of the answer is the reward — not the answer.

Whisper has been running Flicker-adjacent operations longer than the Hephaistos-9 program has existed. How much longer? What were the earlier operations?
Every faction and corporation believes Whisper is aligned with someone else. None of them are fully wrong. What is the actual structure of Whisper's arrangements across the system?
The reason Whisper is obsessed with the Flicker is never stated. Ana will find one fragment of it. Janus will find a different fragment. Neither will be enough. What do those fragments point at?
Whisper communicates only in writing, only through intermediaries. The writing has no forensic texture. This is either discipline or something else. What does something else mean?
🔒 Whisper controls or is aligned with the black ship operation. The distinction matters: one version makes Whisper a contractor, the other makes them a peer to whoever sent the kill team. Which?
🔒 Does Whisper now know Janus is alive? Via the nanotracker signal (if Whisper controls the android), or via the Kirk debrief (if not)?
🔒 Whisper knows the data module was not found on Janus. They do not know what Ana found specifically. When they learn — and they will — does the arrangement with the kill team principals change?
One specific detail about Whisper's past makes the Flicker obsession feel personal rather than strategic. It is the closest the series comes to a name. It is not placed in current canon.

The Nanotracker and the Android 🔒¶

🔒 Janus does not know the tracker is there. The tenderness at the base of his neck (Anchor, Page 1) is attributed to hypoxia. When does he find it?
🔒 When Janus finds the tracker, he will understand the geometry retroactively: every dead-drop location, every Fabric node access, every contact since the hangar has been logged and transmitted. What is the blast radius of that realisation?
🔒 The android has observed that Janus found something in the capsule foam. It has not reported what the object is. What happens when the principals instruct the android to retrieve rather than observe?
🔒 Does the Allianz figure know the android is in the city? The Allianz are unmodified and Fabric-adjacent. They may be watching for tails as a matter of practice.
🔒 Does the Fabric node operator detect the android? The Fabric's operational security may include sweep protocols for surveillance hardware in node-adjacent areas.

The Allianz Figure¶

The Allianz figure chose not to log the TAP-7. Why? What is their relationship with Praxis — or with the Fabric?
They gave Janus a sealed contact cipher card on disembarkation. For what purpose and under what conditions is it intended to be used?
They told Janus about the Fabric node in the city. This is either genuine assistance or operational positioning. Which?
Does the Allianz figure know about the data module? They noticed Janus found something in the capsule foam and did not ask. Silence can be courtesy. Silence can also be patience.

The Factions — Strategic Layer¶

When did the Flicker's effects first become publicly documented? The neural implant failures are being logged as manufacturing defects. How long has Praxis been suppressing this?
Who first identified the Rust Alliance immunity to Flicker effects? Did Praxis identify it? Does Praxis consider it a threat or an asset?
What is the Fabric's operational history and who built it? It predates the Hephaistos-9 incident. It has reach into transit hub infrastructure across at least one major city.
What is the Fracture Synths Devotion? Some Synthetik units are turning antenna arrays toward a fixed point in deep space. The data module may have information relevant to this. [Active connection to the central mystery.]
Did Gebreysius survive the incident? If he did, Praxis now has a senior scientist who knows the anomalous finding was significant enough to trigger a kill team response. That is the specific kind of knowledge that makes a person a liability.

Part 2 — Continuity Notes¶

These are misalignments, ambiguities, and decisions that need resolving before a scene goes to production.

C1 — Anchor Epilogue Arithmetic¶

File: story-anchor.md — Epilogue Page

Issue: The timing stated in the epilogue does not fully cohere.

The established dates: - Ana departs Hephaistos-9: 2847.208 - Ana arrives city: 2847.214 (6 days transit) - Ana stays 17 days: departs room ~2847.231 - Note gives meeting date ~6 weeks from room departure: ~2847.273 - Incident: 2847.211 - Janus unconscious 4 days: wakes ~2847.215 - 3-day barge passage: arrives city ~2847.218

At arrival (~2847.218), the meeting date (~2847.273) is 55 days away — roughly 8 weeks in the future, not 5 weeks in the past.

The epilogue states: "That date was five weeks ago." This requires either a much longer period of unconsciousness/passage (~105 days total) or the meeting date to be much earlier (~2 weeks from room departure, not 6 weeks).

Resolution needed: Decide whether Janus is weeks or months behind Ana. Current prose says "three months" between her departure and his arrival, which would place the meeting date in the past — but then the barge passage timing (4 days unconscious + 3 days passage) needs reconciling with "three months."

Suggested fix: Either make Janus explicitly unconscious for a much longer period (weeks, not days), or change "five weeks ago" to "one week ago" / "the date is in five days" to give the pursuit more urgency. The "one week behind" framing in the epilogue title is strong — consider anchoring everything to that and adjusting the dates.

C2 — Flashback F3 Narrative Perspective¶

File: story-before-the-incident.md — Flashback F3

Issue: F3 is tagged to surface during Drift's prologue (Janus alone in the capsule). But F3 contains Ana's internal reasoning about her discovery — information Janus does not have and could not have.

The flashback is written in omniscient third person (narrator knows Ana's thoughts) while the main story uses second-person / Janus's POV. This is a deliberate structural choice but it needs an explicit framing device — otherwise the player receives information Janus has no basis to know, which undermines the logic of the investigation in Anchor.

Resolution needed: Either (a) frame F3 explicitly as the narrator's omniscient voice, clearly distinguished from Janus's POV, or (b) split F3 — surface the observable facts from Janus's perspective (she left, she hid the module, she sent the message) in Drift, and reserve the full discovery scene for Ana's own playable section in a later installment.

C3 — Hangar Location Resolved Without Story Beat¶

File: story-drift.md — Open Questions; story-anchor.md — Setting

Issue: The Drift open questions include: "Where is the hangar — ship or structure? Whose?" — framing this as unresolved.

But story-anchor.md's Setting section definitively states: "A Rust Alliance salvage barge or deep-ring platform." This resolves the question in the writer's notes without a corresponding story beat that reveals it to the player.

Resolution needed: Either (a) remove the open question from Drift since it's answered, or (b) keep the question and ensure the answer is delivered as an explicit in-story moment in Anchor's prologue (Janus seeing the exterior, or the Allianz figure naming the vessel). Option (b) is preferred — the question landing in-story is more satisfying than being quietly resolved in the lore.

C4 — TAP-7 Fabric Protocol Origin — Untagged Gap¶

File: story-anchor.md — Transit Hub Third Level Down; story-before-the-incident.md

Issue: The TAP-7's Fabric protocol is presented as a manual patch Janus added himself, but the pre-incident arc (which establishes Janus's full history at Hephaistos-9) never mentions Fabric contact. The gap between Corps service and contract work is unaccounted for.

The text says "Janus added this himself. He has not examined when or why he decided to add it." This is intentional narrative deferral, but it is currently untagged as a canon gap.

Resolution needed: Add a canon gap marker in the before-the-incident arc noting the undocumented period between Corps exit and the Hephaistos-9 contract. This is the window where Fabric contact likely occurred.

C5 — Ana's Real Name in Transit Logs vs. Alias in Housing¶

File: story-anchor.md — Transit Hub Public Level; Transit Hub Third Level Down

Issue: The public transit terminal search (SEARCH FOR ANA HAMATO) returns Ana's arrival record by real name. But the Fabric node reveals she used an alias for her short-stay housing registration.

If she was cautious enough to use an alias for housing, why is her real name in the transit arrival logs? Transit logs are public Apex Industrial infrastructure — more exposed than a private housing registry.

Possible resolutions: - She was not yet cautious when she arrived (the decision to use an alias came later, after she assessed the city). Transit arrival was unavoidable; housing was a choice. This is psychologically coherent — she arrived, assessed her situation, then went to ground under a second name. - Explicitly state this logic in the transit hub scene: the real-name arrival record is the last trace before she switched identities.

Preferred resolution: The first option — and making it explicit in the prose. The transit record is the seam between the public Ana and the hidden one. Janus would recognise this.

C6 — Nanotracker Pings vs. Fabric Node Operational Security¶

File: story-anchor.md — Writer's Note; story-drift.md — Writer's Note

Issue: The nanotracker is described as pinging on "proximity to any network-connected transit hub or terminal." The android's knowledge includes "every transit record Janus accessed via the TAP-7."

But the Fabric node (third level down, eastern transit hub) is described as deliberately unlogged, undetectable infrastructure — "you would not find it without knowing what to look for." Its operational premise depends on being invisible to standard network surveillance.

If the nanotracker pings on all network-connected terminals, it would expose the Fabric node location to whoever is receiving the tracker signal — which breaks the Fabric's operational security model and has major plot implications.

Resolution needed: Define whether the Fabric node is air-gapped (the TAP-7 connects via hardwire only, no network ping triggered) or whether the tracker does compromise the node location. The second option is dramatically richer but requires the Fabric to react — either by detecting the tracker, sweeping the node, or burning it.

C7 — Drift Score System — "Survive to Unconsciousness" as Player Action¶

File: story-drift.md — Score System

Issue: The score table lists "Survive to unconsciousness (oxygen zero) +1" as a scored action. Unlike the other four scored actions (which are explicit player choices), this is a passive outcome — the player cannot choose not to reach oxygen zero given the narrative structure. Every playthrough receives this point.

Resolution needed: Either replace this with an active final choice (e.g., a last action before losing consciousness — leaving a Fabric message, hiding the module again, choosing not to confront Kirk about the frequency) or remove it and cap the score at 4. The current maximum of 5 is preserved more elegantly if all five require player agency.

C9 — Whisper Hint Asymmetry — Placement Not Yet Defined¶

File: characters.md — Whisper / The Hints — Design Rules

Issue: The hint design rules are now defined (Rule 1–5), but no specific hints have been placed in any installment yet.

The architecture: - Ana finds fragments of Whisper's history - Janus finds fragments of Whisper's method - The one personal detail that makes the obsession feel personal (Rule 3) is not placed in current canon

Required before production of any installment beyond Anchor: - Decide which installment surfaces Ana's first Whisper history fragment — and what it is (without naming or gendering Whisper) - Decide which installment surfaces Janus's first Whisper method fragment — candidate: the writing style of Kirk's dead-drop instructions, which Janus reads via the TAP-7 in a future installment and recognises as the output of someone managing their own paper trail - Decide what the personal detail is, even if its placement is deferred to a late installment. It needs to exist in the writer's room before it can be foreshadowed correctly

Hard constraint: Whisper is never physically present in a scene. Any hint must arrive as text, as absence, as something another character says about Whisper, or as the specific gap where explanation should be and isn't.

C8 — Kirk's Secondary Transmitter — Missing Examine Action¶

File: story-drift.md — Page 3 (Prologue); Interactive Section

Issue: The secondary transmitter Kirk uses on day one is a significant narrative element — it is the device Janus observes and files. But in the interactive section's available actions, the only action involving it is ASK KIRK ABOUT [device/frequency/hands] — which Kirk deflects.

There is no EXAMINE DEVICE, LOOK FOR DEVICE, or SEARCH KIRK'S SUIT action available to the player. Given that the prologue specifically draws attention to the device (Kirk putting it into "the inner pocket of his suit"), players will likely try to find it.

Resolution needed: Add an action for the interior: EXAMINE SUIT POCKET or LOOK FOR DEVICE — which returns a result of either (a) the pocket is zipped and it would be a significant boundary crossing to open it, or (b) Kirk has moved it. This preserves player agency while keeping the device inaccessible. A narrative flag is fine; a hard invisible wall is not.

Part 3 — Open Questions Introduced by Return¶

The Sentence¶

🔒 What does the Flicker say? The sentence must be disturbing (not threatening), must be a question, observation, or statement (not a command), and must be the last line of the series. This is the author's sole decision. Not to be speculated in any lore file.
🔒 The response arrived in 0.3 seconds. The dead ice planet is six light-minutes away. The signal was already here. Where, precisely — inside the station, the compute room, or something that entered with the team?
🔒 Has anyone received this sentence before? The Hephaistos-9 team had fourteen months of live data on the stack. Did the signal ever respond to them? Is there a record they did not live to read?

The Railgun¶

🔒 The black ship stopped mid-charge. The Flicker destroyed its targeting hardware. Why this moment — the Flicker has not intervened in any prior human conflict. Was this protection, patience, or something with no human analogue?
🔒 The ship went quiet but did not leave. What did the crew experience during the compute room sequence? What do they do when the effect clears?

Gebreysius¶

He addressed his note to the next researcher — not to anyone specific. Did he have reason to believe someone would come back, or was this faith?
The additional parameter was classified above Ana's clearance. How long had he known it changed her numbers? Did he withhold it deliberately, or did he only connect it to her work in the last morning of his life?

The Cinder-7 Confrontation — After¶

🔒 The leader let Janus go at Cinder-7. They let him go again at Hephaistos-9 for operational reasons. Is there a third time, and does it follow the same logic?
🔒 Janus answered the leader's question in the corridor. The question and answer are not stated in current canon. Was the answer enough — for the leader, or for Janus?
🔒 The Cinder-7 survivors hold the corridor while the kill team boards through the outer sections. What happens there is not shown. Who is still standing when the compute room sequence ends?

Who Directed the Survivors Here¶

🔒 Someone with inside access to unregistered nav data gave the survivors the station's coordinates — hoping Ana and Janus would be neutralised before reaching the compute room, with clean deniability. A Whisper-adjacent move is the most consistent explanation. But Whisper's interest is the Flicker, not neutralising Janus. Something does not fully resolve.

After the Series Ends¶

Ana and Janus now know more about the Flicker than any living party in the Veridion system. What do they do with it?
Whisper is still operating. Kirk is unresolved. The Fabric has fourteen months of adjacent-frequency Flicker data logged. The sentence ends the series. It does not end the world.
The Fracture Synths in the Devotion — antenna arrays pointing at the dead ice planet for months. Did they receive the sentence before Ana did?