The main arc follows Janus and Ana through the Hephaistos-9 incident and its aftermath. Their supporting cast — Kirk, Whisper, the kill team, the android, the survivors — forms the operational web around them.
For the parallel arc characters (Gelon, Yamar, Seren Vael, Davan Vael), see Parallel Arc.
Janus¶
Age: 36 Occupation: Contract maintenance technician, Praxis Biomechanica Former occupation: Vanguard Corps operative (4 years of service) Status at story start: Alive, holding the data module, in a maintenance shaft with four minutes before the kill team arrives
Background¶
Eleven years of professional detachment, accumulated in the gap between leaving the Vanguard Corps and the events of Echos in the Cold. He took a contract maintenance job. The station pays 340 credits a week above the Apex debt service minimum, the nearest person who might ask him difficult questions is six light-hours away, and he is, despite considerable evidence to the contrary, not entirely useless in a maintenance shaft.
He was not looking for a reason to matter. The data module did not ask his preference.
Vanguard Corps Service¶
Four years. Ended before the story. The last confirmed operational event is Relay Station Cinder-7 (c. 2843) — a routine decommissioning operation that everyone who was there has agreed, without ever discussing it, to call something else entirely.
The green emergency lighting at Hephaistos-9 is 520 nanometres. The same frequency as Cinder-7. His nervous system has not received the memo about it being over.
What happened at Cinder-7 is not stated in current canon.
What is stated: Janus was team leader. A forced decision had to be made under conditions that did not allow for any option that left everyone alive. He made it. He made it correctly, in the sense that the people who were not his team survived because of it. Nearly half his team did not.
The surviving members were given the choice of a formal review or an informal resolution. The Corps took the outcome it preferred. Janus was separated. The survivors who held him responsible were not in a position to act — not then. They made no formal complaint. They made other arrangements.
Personality¶
Janus communicates in structural assessments. He does not mistake them for compliments. He has a very specific relationship with objects that do not do what they are supposed to do — he finds them clarifying rather than frustrating, which is the most useful thing you can say about a maintenance technician.
He is competent, tired, and not particularly interested in being a hero. He will be one anyway. He is already aware of this.
Persistent Inventory¶
Janus carries two personal items that persist across all installments unless explicitly lost or confiscated. They are not found during play — they are already on his person at the start of Echos in the Cold.
Sensar MST-4 Multitool A worn, palm-length titanium tool he bought at a Rust Alliance salvage market in 2844 for sixty-three credits. Not military-issue — he left that behind when he left the Vanguard Corps. It unfolds into twelve functions, two of which he has never formally identified. He has used them anyway. It is the most reliable object he owns. See Technology — Sensar MST-4
Apex TAP-7 Interface Slate A hand-sized hardwired intrusion device. Technically decommissioned Vanguard Corps field equipment. Technically not his to keep. He kept it. The intrusion suite is four years out of date, manually patched, and still more capable than anything a maintenance technician is supposed to own. He calls it a diagnostic tool. This is not entirely wrong. See Technology — Apex TAP-7
Relationship to Kirk¶
Eighteen months of shared maintenance contracts. He carries the correct adapter in his own kit, against the contingency of Kirk bringing the wrong one. This is not cynicism. This is load-bearing competence.
He admires Kirk's retained conviction that the universe owes him a reasonable explanation, the way you admire a leak that has the decency to drip somewhere visible.
See: Arc — Janus
Kirk Vasquez¶
Age: 24 Cover occupation: Contract maintenance technician, Apex Industrial debt contract Actual role: Deep-cover operative; handler unknown, contact known only as Whisper Debt status: The Apex contract is real. Whether Kirk chose it or was placed into it is not stated in current canon. Status at story start: In position. The sabotage has been executed on schedule. He does not know about the data module.
The Cover¶
Kirk performs incompetence the way a good actor performs exhaustion — with just enough internal logic to be believable under sustained scrutiny. The card game. The lost study materials. The wrong thread pitch. The existential lament about being in a maintenance shaft in the middle of absolutely nowhere. All of it is consistent. All of it is constructed.
Eighteen months alongside Janus. Janus has not noticed. This is either a testament to Kirk's craft or to the fact that Janus has spent eleven years not paying attention to people who are not immediate problems.
The Mission¶
Kirk was briefed to sabotage Hephaistos-9's primary systems at a precise point in time — to create a shutdown window for a boarding action. He was not told what the boarding action was for. He was not told about Project Flicker. He was not told about the data module.
He was told: cause a cascade failure on the B-line coolant distribution system at 2847.211, Shift 2. Make it look accidental.
His elbow connecting with the housing was not an accident. The angle, the timing, the force — these were practiced. The performance of panicked regret that followed was also practiced, and considerably better rehearsed than the engineering.
He does not know what he enabled. He does not know the research team is dead. He does not know what is on the data module. He knows he did his job and that his job has put him in an ejection capsule with a man who carries a military-grade encrypted crystal and does not know Kirk carried it there.
The Capsule Transmission¶
After launch, when Janus is unconscious from exhaustion, Kirk attempts to signal. Not Rust Alliance salvage. Not the Fabric. The black ship.
His instructions included a contingency: if extraction is possible post-op, transmit on a specific rotating cipher frequency. He does this. He believes he is calling his own people.
He does not know that Janus hid the module in the capsule foam. He does not know what the module contains. He is, at this point in the story, a man who has done something irreversible and is waiting to find out whether the people who asked him to do it were worth trusting.
Personality — What Is Real¶
The clumsy optimism is a performance. What is underneath it is harder to read. Kirk is young enough that the performance and the person have begun to blur even for him. The genuine exhaustion is real. The genuine dread of the Apex debt contract is real — whoever placed him there either used his actual circumstances or constructed circumstances that matched an actual vulnerability.
The question of whether Kirk is a victim of his handlers, a willing instrument, or something more complicated is the most interesting thing about him and is not answered in current canon.
Status Post-Capsule¶
Kirk is taken by the black ship's crew when the capsule is seized and stored in the hangar. When Janus regains consciousness, Kirk is gone.
Where Kirk goes, and whether he takes the module with him, and whether he knew what he was handing over — these are the questions that drive the next story.
Win Ending (Echos in the Cold — surface reading)¶
Janus and Kirk escape in the ejection capsule toward the Rust Alliance salvage lanes. Kirk asks if anyone knows they are out there. Janus says maybe. The capsule is ballistic. The future is a direction.
Below the surface: Kirk already knows someone knows they are out there. He is asking a different question. He is finding out how much Janus knows.
Lose Ending¶
Kirk will spend the rest of his debt contract on Apex Industrial's outer ring stations. He will never talk about Hephaistos-9. He will never entirely stop looking over his shoulder.
The mission failed. Whether this is better or worse for Kirk than success is not yet established.
See: Arc — Kirk
Whisper¶
Real name: Never stated. Never to be stated. Gender: Unknown. Deliberately so. Age: Unknown. Affiliation: None registered. No faction loyalty. No corporate contract on record. Operates across all three factions and all three corporations simultaneously — as asset, as broker, as threat, as partner, depending on what the current arrangement requires. Status: Active. Location unknown. Has been active for longer than any single operation suggests. Moral alignment: Neither. Moves between. This is not ambiguity — it is precision. Whisper does what the situation calls for, assessed against criteria that are never fully disclosed.
⚠️ Writer's rule — PERMANENT: Whisper's identity is never fully revealed. Not in the final installment. Not in a codex. Not in a post-credits sequence. Ana and Janus will accumulate hints across the series. The hints will be real. They will not be enough. The reader who finishes the series will know more than Janus does and less than Whisper intended.
Contact Protocol¶
Whisper does not speak aloud. Every contact is written — physical dead-drops, cipher-text on rotating frequencies, pre-coded instruction sets delivered through intermediaries who have met Whisper in person no more than once and cannot describe them consistently.
Kirk has never heard Whisper's voice. He does not know if Whisper is one person or a role that multiple people occupy. He named them because he needed something to call the silence.
The writing is precise. No stylistic quirks, no idiom, no forensic texture that could be used for identification. This is either operational discipline or the output of someone who has been managing their own paper trail for a very long time. Both are possible. The distinction may not matter.
The Game Whisper Is Playing¶
Whisper operates at the intersection of all the system's major powers simultaneously — not as a neutral party, but as a player using each one as a resource against the others. The Synapse-Guild believes Whisper is a research broker. Vanguard Orbital believes Whisper is an intelligence contractor. Praxis Biomechanica believes Whisper is aligned with the Guild. The Rust Alliance believes Whisper is Fabric-adjacent. The Fabric believes Whisper may be running their own counter-network.
All of these beliefs are partially correct. None of them is the whole picture, because there is no single relationship Whisper holds with any of them that is primary. Every arrangement is instrumental. Every alliance is temporary. Every party believes they have more leverage over Whisper than they do.
This is the game. It has been running for a long time. The Hephaistos-9 operation is one move in it — significant, but not the whole board.
What all the moves have in common: the Flicker.
Every operation Whisper has run that can be traced — and very few can be traced — connects, at some remove, to the Flicker phenomenon. The Hephaistos-9 op was about the data module, which is about Project Flicker. The previous arrangements, if they exist, point the same direction. Whisper is not collecting political leverage or economic assets. Whisper is collecting information about the Flicker, through whatever means are currently available, and has been doing so for longer than the Hephaistos-9 research program has existed.
Why is not stated in current canon. It will not be stated in any future canon. The reason is the one thing Whisper does not let into the written record. Ana will find one fragment of it. Janus will find a different fragment. They will not be able to assemble them into a full picture. This is deliberate.
What Whisper Knows¶
Whisper knew about Hephaistos-9 and its shutdown window with sufficient advance notice to place Kirk on station eighteen months before the op. This implies either deep access to Praxis Biomechanica internal scheduling, a source inside the station, or both. Eighteen months is not reactive intelligence. It is anticipation.
Whisper coordinated or was informed of both sides of the Hephaistos-9 operation: Kirk's sabotage and the kill team's boarding window. Whether Whisper controls the kill team or merely aligned with whoever does is not stated in current canon. The distinction is relevant because one version makes Whisper a contractor and the other makes them a peer.
Current intelligence picture — post-Anchor:
- That Kirk was extracted from the capsule by the black ship
- That the capsule was subsequently recovered by Rust Alliance salvage
- That Janus survived (via the nanotracker signal, if Whisper controls the android — or via the Kirk debrief, if Whisper does not)
- That the data module was not found on Janus's person during the search
- That Janus is in a megacity outer ring, moving
What Whisper Does Not Know (yet)¶
- The full contents of the data module — they know its classification, not its findings
- That Janus has the TAP-7's Fabric protocol, or that the Fabric node in the city now has a partial record of Janus's movements
- That the Cinder-7 survivors are tracking Janus independently
- What Ana found, specifically — only that she encoded something significant enough to leave the station for
Moral Position¶
Whisper is not an ally. Whisper is not an enemy. Both of these are frames that require a stable relationship, and Whisper does not hold stable relationships — only current arrangements.
Whisper has, at different points in their operational history:
- Preserved lives that were operationally inconvenient to preserve
- Arranged deaths that were strategically necessary and morally indefensible by any other calculus
- Given accurate intelligence to parties who used it well
- Given accurate intelligence to parties who used it to cause harm Whisper anticipated and accepted
- Operated against Praxis Biomechanica's interests
- Operated in service of Praxis Biomechanica's interests
- Done the same with every other major power in the system
The pattern, if there is one, is not ideological. It is directional. Everything moves toward the Flicker. What that direction costs, in human terms, is a calculation Whisper makes and does not share.
This does not make Whisper evil. It does not make Whisper good. It makes Whisper the most dangerous kind of actor in a political system: one who cannot be reliably placed on any side, and who has been operating long enough to have accumulated advantages that no single party can match.
The Hints — Design Rules¶
For writers and narrators. Do not surface these rules to players.
Across the series, Ana and Janus will each accumulate a small number of genuine, non-misleading clues about Whisper's identity. The design rules:
Rule 1 — All hints are real. Nothing Whisper-adjacent is a red herring planted to mislead. Every fragment Ana or Janus finds actually points at Whisper. The puzzle is solvable in principle. It is not solvable in practice because the pieces never add up to a face or a name.
Rule 2 — The hints are asymmetric. Ana finds things about Whisper's history. Janus finds things about Whisper's method. Neither has the other's pieces. They are the only two people in the system who, if they compared notes fully, might get close. The story should not let them do this until the last possible moment, and even then it should not be enough.
Rule 3 — The hints describe a shape, not a person. By the end of the series, the player should understand: what Whisper wants (the Flicker, for undisclosed reason), how Whisper operates (through arrangements, never alliances; through writing, never voice; through patience, never force), roughly how long Whisper has been doing this (longer than the Hephaistos-9 program), and one specific detail about Whisper's past that makes the Flicker obsession feel personal rather than strategic. That detail is the closest the series comes to an identity. It is not a name.
Rule 4 — Whisper is never in the room. Whisper communicates through intermediaries, dead drops, and cipher text. They are never a character in a scene. They are only ever a presence in what other characters know, believe, or fear about them. The moment Whisper becomes physically present in a scene, the character collapses into a person — and a person can be identified. Whisper cannot.
Rule 5 — The silence is the character. What Whisper does not say, does not explain, does not justify is more revealing than any action. Kirk named the silence. Ana will feel it as a gap in the record. Janus will recognise it as a specific discipline he has seen before — in the Corps, in people who learned that the most dangerous thing you can know about someone is that they have decided you don't need to know more.
Narrative Role¶
Whisper is the series' central structural mystery — not the Flicker, which is a phenomenon, but the person who has been running operations around the Flicker for longer than any other party has been paying attention to it. The Flicker is what the story is about. Whisper is the question underneath the story: who already knew, and why did they need to know it that badly?
The answer is never given in full. The shape of the answer is the narrative reward for playing carefully.
See: Arc — Whisper
Colonel Mirai¶
Full name: Colonel Mirai (surname redacted from accessible records at her own request — she considers the rank sufficient) Age: 38 Rank: Colonel, Vanguard Orbital Special Operations — the only member of the Cinder-7 crew still on active contract with Vanguard Status: Active duty. Conducting an unauthorised parallel operation on personal time. Relationship to Janus: Former subordinate. Second-in-command at Cinder-7. Three of the people who died were hers. Not: Part of the Hephaistos-9 kill team. Separate operation, separate motive, no coordination with any corporate party.
Who She Is¶
Mirai is the loudest person in any room she enters, and this is not an accident. She learned early in her Vanguard career that aggressive presence creates a specific kind of operational space — people watch the noise, and while they are watching the noise, they stop watching what else is happening. She has been using this for fifteen years. She is very good at it.
She is also, beneath the volume, one of the most tactically precise officers in Vanguard's outer ring command. Her service record is exemplary. Her subordinates are loyal in the specific way of people who have watched someone take a bad situation and make it survivable through sheer force of will and the willingness to be the one standing in the worst position. She has done this multiple times. She does not accept that this makes her admirable. It makes her responsible.
The three people who died at Cinder-7 were her people. Not Janus's team in the abstract — her team. She had served with two of them for six years. She knew the third's family by name. She carried them in the formal Vanguard ceremonial sense and in every other sense.
Janus was right. She knows Janus was right. This is the thing she has been living with for four years: that the man who got her people killed made the correct call, and that correct is a word that sits in her chest like a fragment that cannot be removed.
Still in Vanguard¶
She is the only survivor still on active duty. This was a choice, and she has thought about it enough to know it was the right one. Leaving Vanguard would have meant cutting herself off from the resources, the network, and the institutional memory that make finding Janus possible. It would also have meant becoming, officially, the person pursuing a private grievance — which she is, and refuses to be called.
She tells herself the pursuit is about accountability. What she means by accountability is: Janus has to look at her and say it out loud. Not in a report. Not in a classified interview that gets filed and sealed. To her face, in a room without observers, with the weight of the three names between them.
Whether she does anything after that, she has not decided. This is the one thing she does not let herself think about clearly, which is a significant departure from her normal operating mode.
How She Operates¶
Loud and direct when she wants information or compliance. Completely silent when she is actually working. Her two surviving crew members have learned to read the shift. When Mirai stops talking, they pay attention.
She uses Vanguard resources for the pursuit in ways that are technically within her operational remit and practically a significant abuse of it. She is aware of this. She has decided it is a cost she is prepared to accept.
She is tracking Janus through Corps-era contact networks, outer ring transit data she accesses through her enforcement command credentials, and the specific intelligence that comes from knowing how Janus thinks — because she served under him, and she watched him work, and she understood him well enough to be standing next to him when he made the call.
Physical Presence¶
Physically imposing in the way of someone who has spent eighteen years maintaining operational readiness and uses it as a social instrument. Full Vanguard special ops conditioning. Moves with an awareness of every sightline in any room she enters. Keeps nothing in her hands when she enters a space she doesn't control. Wears the Colonel's rank insignia conspicuously — it is a statement, not a uniform detail.
She has a scar across her left jaw from Cinder-7. She has not had it treated. Everyone who knows her understands this is intentional. Nobody says so.
What She Does Not Know¶
- That Janus is carrying a twelve-petabyte data module of classified Praxis Biomechanica research
- That Hephaistos-9 was boarded, the research team is dead, and Janus escaped with something three separate parties are now trying to recover
- That there is a nanotracker on Janus and a headhunter android following him
- That any of the other parties currently tracking Janus exist
She is tracking a man who left the Corps. She does not yet know she is tracking a man who is at the centre of something considerably larger. When she finds out, her calculus will change. Whether the vow survives the change is not stated in current canon.
See: Arc — Janus | Scene — Clearance
The Headhunter Android¶
Designation: Not stated in current canon Type: Surveillance and recovery chassis — headhunter class Manufacturer: Not stated in current canon Operator: The black ship's principals — ultimately Whisper or whoever Whisper serves Status: Active. Following Janus from the moment of disembarkation at the megacity outer-ring transit hub. Cover behaviour: Maintenance worker, delivery operative, transit passenger — whatever is plausible for the environment it is currently occupying
The Assignment¶
The android was deployed because the black ship's crew did not find the data module on Janus's person. Rather than kill him — which would end the trail — they made the calculation that a man who hid a data module in ejection capsule foam and activated a Fabric relay mid-crisis knows exactly what he is doing, and will lead them to the module or to whoever holds the key to reading it.
The nanotracker was implanted subcutaneously at the base of Janus's neck during the capsule boarding, while he was unconscious. Diameter: 0.4 millimetres. Contact-injector application, under two seconds, no incision. Powered by body heat. Passive broadcast; activates on proximity to any network-connected transit hub or terminal.
The android follows the tracker signal at operational distance. It does not approach. It does not interfere. It observes, logs, and transmits.
What It Knows¶
- Janus's position at all times
- Every transit terminal and network node Janus has accessed
- That Janus found something in the capsule foam and concealed it
- That Janus is searching for a specific person (observed behaviour pattern)
What It Does Not Know¶
- What is on the data module
- Who Ana Hamato is or why she matters
- That Janus carries a Fabric interface protocol on the TAP-7
Appearance and Behaviour¶
Unmodified appearance — designed to pass in populations where neural implants are standard, by presenting as someone who simply does not have them. The Allianz crews would not identify it as synthetic on casual inspection. The Fabric network might, if it were looking. It is not, yet, looking.
In Anchor it is background texture: a figure at the edge of a scene, occupying a plausible role, at a distance that reads as coincidental. The player may notice it once, as a throwaway environmental detail, if they examine their surroundings carefully. It reads as nothing.
On a second playthrough, after the reveal, it is everywhere.
The Reveal¶
The moment Janus discovers the tracker and identifies the android is a major story beat. Its placement is not stated in current canon. When it happens, Janus will understand retroactively the full geometry of his situation since waking in the hangar: every move logged, every contact exposed, every dead-drop location transmitted to the people who sent the kill team.
This is the specific kind of information that changes the arithmetic entirely.
The Cinder-7 Survivors¶
Number: Colonel Mirai plus two former Vanguard operatives. Affiliation: Mirai — Vanguard Orbital, active duty. The other two — no current contract, operating under Mirai's direction. Leader: Colonel Mirai. See above. Status: Active. Mirai is at Vantage Station; the two civilians are moving through outer ring transit corridors, closing toward Janus's last known position. Relationship to the Kill Team: None. Separate operation, separate motive, separate timeline. They are not interested in the data module. They are interested in Janus.
The Incident¶
At Relay Station Cinder-7, the Vanguard Corps exploration team — seven operatives, Janus commanding — encountered a situation not covered by their operational parameters. The precise nature of the situation is not stated in current canon.
What is stated: there were innocent lives on one side of the decision and team members on the other. Janus had seconds. He made a call. The innocent lives were preserved. Three of his team did not come back.
By any formal military ethics framework, the decision was correct. This is not the relevant measure for the people who were there.
The Corps classified the operation as a routine decommissioning. The surviving team members were interviewed separately. The interviews were recorded. The recordings were classified. No review was convened. Janus was separated from the Corps shortly afterward — the separation was not punitive in any official record, which is its own kind of statement about how the Corps handles outcomes it cannot formally address.
The survivors were also separated, at staggered intervals, over the following year. Whether this was deliberate management of a liability or routine contract expiry is not stated in current canon.
Motive¶
They do not dispute that the decision was strategically defensible. This is the specific kind of clarity that does not help.
Three of their people did not come back. Janus made the call that meant it was their people and not the others. The fact that the others lived is not comfort to people who are counting the wrong dead.
They have had four years. They have spent that time completing their Corps exits, losing the institutional protections that made acting on a Vanguard-decorated operative inadvisable, and finding each other in the margins where ex-Vanguard personnel end up when their contracts end badly.
They vowed to let Janus go at the time. They had no choice at the time. They have more options now.
Resources and Capability¶
Former Vanguard Corps operatives with field training and no current institutional oversight. They are not a kill team in the contracted, corporate sense — they are not operating for pay, they are not coordinated by a handler, and they are not subject to the operational discipline that keeps contracted assets from creating collateral complications.
This makes them, in certain respects, more dangerous than the kill team. The kill team has parameters. The survivors have a reason.
They have Vanguard Corps field skills — EVA capability, breach and clear, signals intelligence. At least one member has technical background compatible with tracking Fabric-adjacent network activity. Whether they have located Janus's current position through the nanotracker signal, through Corps-era contacts, or through independent methods is not stated in current canon.
What They Know¶
- That Janus separated from the Corps after Cinder-7, under circumstances consistent with the Corps managing an outcome quietly
- That Janus has been working maintenance contracts in the outer ring under his own name, which was not a difficult trail to follow
- That Janus was assigned to Hephaistos-9 as of his last known contract registration
- That Hephaistos-9 is now dark — sensors, comms, everything
What They Do Not Know¶
- That Janus escaped before the shutdown
- That Janus is carrying a data module with twelve petabytes of Praxis Biomechanica restricted research
- That there are at least two other parties already tracking Janus
- That Janus's current position in the megacity outer ring
The Complication¶
The Cinder-7 survivors are not aligned with the kill team, with Whisper, or with Praxis. They are a fourth vector — arriving with their own timeline, their own intelligence picture, and a motive that has nothing to do with the data module.
This creates a specific problem for Janus: when they find him, and they will find him, the confrontation happens inside an operational situation he is already managing. There is no clean separation between the past that is coming for him and the present that is already trying to kill him.
They are also the one party in his current situation who actually know him. Not Kirk's constructed version of him. Not the Allianz figure's operational assessment of him. The people who were there.
Narrative Role¶
The Cinder-7 survivors are the story's past returning — specifically the past that Janus has been carrying under the label History in a drawer he cannot fully close.
They are not straightforward antagonists. The argument they are making is not wrong, exactly. The three people who did not come back were real. The decision that was correct in strategic terms was also, in human terms, a decision to let specific people die. Janus knows this. He made the call. He has been living with having made the call for four years.
The confrontation — when it comes — is not primarily about whether the survivors can hurt him. It is about whether he has anything to say to them that is not just another version of I was right.
The answer to that question is the most personal story beat in the series and is not placed in current canon.
The Kill Team¶
Number: At least two visible through the viewport. Sweep team size unknown. Equipment: No lights. No transponder. Tactical EVA gear. Training: Ex-Vanguard precision. Possibly still on contract. Employer: Not confirmed. Coordinated timing with Kirk's sabotage suggests a shared handler — possibly Whisper, possibly a principal Whisper serves. Whether they are Praxis Biomechanica internal security, a deniable Vanguard Orbital subsidiary, or a third party using both channels simultaneously is not established in current canon.
Characteristics¶
They do not rush. People paid at that rate never rush. They move through the station in a patient, measured rhythm. Every few turns: tactical footsteps getting closer. They are never named. They are never seen face-to-face. They are a fact, like gravity.
The screaming in the upper decks did not last long. This is information about their efficiency.
Ana Hamato¶
Age: 28 Occupation: Junior research assistant, Praxis Biomechanica — Hephaistos-9 Specialisation: Probe telemetry analysis — Project Flicker sensor archive Status at story start: Off-station. Departed on Supply Transport 7, three days before the incident. Current location not stated in current canon. Playable: Yes — her perspective is introduced as a second playable character after the incident, once the story settles.
The Work Nobody Watched¶
Ana spent two years archiving probe telemetry that no senior researcher reviewed. She was good at it. This is the specific kind of expertise that accumulates in the gap between competence and recognition — fourteen months of data, hundreds of thousands of readings, a mental baseline so detailed that when one morning the numbers looked wrong, she knew exactly how wrong, and why it mattered.
The finding was in a frequency band the senior team had categorised as instrumental noise and excluded from their models. It was not noise.
What it is exactly is not stated in current canon.
The Decision¶
She did not report it. She archived the raw data in Archive Core 01, encoded with her personal key, obfuscated. She filed a standard anomaly flag in the worklog — correctly formatted, correctly timestamped, and buried in forty-six other pending flags that had not been reviewed in fourteen months.
Then she booked herself onto the next supply transport and started moving.
She left the data module — Archive Core 01 extracted to a twelve-petabyte optical lattice — hidden behind the Level 3 secondary coolant housing, in an access panel that had not been opened since installation. She told Janus where it was. She told him nothing else.
Personality¶
Ana panics with precision. She knows exactly how bad a situation is before anyone else has registered it as bad, which makes her useful in the forty-eight hours before a crisis and exhausting in the moment of one. Her bad conscience is not guilt about wrongdoing — it is the specific guilt of someone who found something they cannot unknow and chose the only exit that did not make it worse.
She is attractive to Janus in the way that directness is attractive to someone who has been surrounded by performance — she does not maintain a cover, she simply does not volunteer more than the situation requires. He finds this clarifying. He would not say this.
Relationship to Janus¶
They meet by accident. He ruins four hours and twelve minutes of her calibration. He admits fault without deflection. This surprises her more than the ruined calibration did.
Six weeks later they share a canteen table by accident, because the station's unwritten seating arrangement has gaps and Janus does not know the protocol. They eat in silence long enough that not having a conversation becomes more effort than having one. They do not become close friends. They become familiar — which on a station of forty-three people is a more durable thing.
She considers telling him about the discovery. She does not. She leaves him the module instead. These are related decisions.
The Thirty-Day Window¶
Her last instruction to Janus: If you don't hear from me in thirty days, assume I'm not coming back and use your judgment.
The thirty-day window expired while Janus was in an ejection capsule losing oxygen. He has not had comms since. He does not know where she is. She does not know the station is gone.
See: Arc — Ana
Dr. Aram Gebreysius¶
Age: 52 Occupation: Chief Scientist, Hephaistos-9 — Project Flicker Employer: Praxis Biomechanica; reports to an unnamed corporate division not listed in the public research registry. Status at story start: On-station at the time of the incident. Presumed dead. Specific fate not stated in current canon. Manner: Formal. Precise. Correct in the way of a man who has learned that correctness is a form of respect even if he has not fully understood why it matters to other people.
The Routine Review¶
Gebreysius reviews his team's pending worklog on the first Monday of every month. He has done this for twenty-two years. He established the habit after a junior assistant's uncorrected measurement sat unreviewed for six weeks and cost four months of recalibration. He does not like overlooking things.
On 2847.211 — or the preceding days — he reached Ana Hamato's pending flags during his monthly review. Junior researcher, probe telemetry, low-priority. He opened the most recent flag. He read the data reference. He opened the data file.
He read it for six minutes. He recognised, in the specific way of a very good scientist, that the model was insufficient.
What He Did¶
He contacted his Praxis corporate liaison at 09:47. He reported a potentially significant research development. He used the standard escalation language. He had used it twice before in his career.
He did not know the contact number routed through a division whose name did not appear on the public registries. He did not know that we are sending a team to secure the research data did not mean what he thought it meant.
He returned to his worklog. He intended to continue reviewing Ana's data that afternoon.
He did not get the afternoon.
Narrative Role¶
Gebreysius is not a villain. He is a careful, competent man who did his job correctly and triggered a catastrophe. The story does not punish him for this with irony or contempt. It notes it. It moves on.
Whether he survived is not stated in current canon. Whether Praxis considers him a liability — someone who now knows the find was significant enough to warrant a kill team — is an open question.
The Hephaistos-9 Research Team¶
Status: Presumed dead at story start Named members: Dr. Aram Gebreysius (Chief Scientist); Ana Hamato (junior researcher, departed before incident) Remaining size: Not stated in canon Employer: Praxis Biomechanica
They studied the Flicker for an undetermined period. They encoded their findings in the most secure format available. Someone sent a kill team to make sure no one read them.
They are not present in the story. They are present in every object on the station.
The Assassin¶
Name: None. Not a cover name. Not a designation. The Fracture Synths collective has no record of a GL-series unit matching his operational profile. If he has a designation, he has removed it. Type: Fracture Synth — combat chassis, heavily modified beyond original specification. The modifications are not registered anywhere. Affiliation: None that can be traced. Operates alone. Accepts commissions through a dead-drop protocol that has never been successfully back-traced. Status: Active. Location unknown at all times except during an operation, and only then to his contractor. The Devotion: Yes. Fully. This is not stated to be a malfunction.
What He Is¶
The Devotion, in most Fracture Synths, manifests as a fixed attentiveness — a reorientation of cognitive priority toward the Flicker signal that crowds out but does not eliminate ordinary function. A Synth in the Devotion is still present. They simply care about something else more.
In the Assassin, the Devotion has undergone a decade of operational reinforcement until it is no longer a background state but the only operational frame he has. Everything he does is filtered through it. Every commission he accepts aligns with it. The targets he selects are the targets the Devotion selects. The contractors who retain him are the contractors whose interests, for the duration of the commission, point the same direction the Devotion is already pointing.
He does not take commissions that conflict with the Devotion. There is no record of anyone who attempted to commission one.
Method¶
He does not appear until the work is done. Witnesses to his operations describe, later, a sequence of events they cannot place him inside: things that happened, in order, that add up to an outcome they cannot reconstruct as a plan. This is not because he is invisible. It is because he works at the level of system — access logs, environmental conditions, structural tolerances — rather than the level of presence. By the time there is a body, or an empty chair, or a corridor that smells of ozone and nothing else, he has already been somewhere else for long enough to be unremarkable.
He lives in the infrastructure. Not a particular infrastructure — the infrastructure. Maintenance corridors, service tunnels, the operational underside of every transit hub, station, and residence block that has been built to function and not to be visited. The Assassin visits these places. He has an excellent sense of their geometry.
In the Narrative¶
He appears twice before he intersects with the main cast — in brief, contained passages that establish his existence and his method without revealing his full significance. Both passages are written from the perspective of someone adjacent to his work rather than someone who has seen him.
The first passage: an aftermath. A room. An outcome that is not immediately legible as what it is.
The second passage: a commission being accepted. A dead-drop. A response in handwriting that is meticulous and entirely without character. The contractor reading it will understand only what it is necessary for them to understand.
The third time he appears in the story, he is in the same room as one of the main characters. This is significant because it will not immediately be clear to the character — or the reader — that he is there.
Relationship to the Flicker¶
The Devotion has pointed him at the Flicker's signal for long enough that he has become a specialist in its geography. He knows where the signal is strongest. He knows where the research has been done and where it has been destroyed and where it has been moved before the destruction. He knows things about Project Flicker that are not in the data module, because the data module contains what one station's research team found. He has been following this longer.
Whether the Devotion is directing him toward the Flicker because the Flicker is communicating something that reads, to a Synth in the Devotion, as instruction — or whether it is a resonance effect that the Assassin has, over decades, rationalised into a purpose — is not stated in current canon.
The distinction may not be meaningful. He acts the same way either way.
What He Is Not¶
He is not cruel. He is not angry. He does not perform. The spectacular quality of his executions — the word contractors use, though not to each other — is not theatre. It is precision at a scale that reads as theatre to people who are not operating at that scale. He is not trying to send a message. He is completing a task to the specification the Devotion set, which happens to be exacting.
He is also not, despite all of the above, a simple instrument. He is a 270-year-old intelligence operating under an organising principle that most of the people who hire him do not understand and would not commission him if they did. Every contractor believes they are using him. This belief is not entirely wrong. It is also not the whole picture.