The Azimuth Event¶

Something is looking at the system from outside the system. The Synths saw it first. They always do.

What Is Happening¶

Near the gravitational centre of the Veridion system — at a distance of approximately 0.3 AU from the primary — an anomaly is forming.

It began as an energetic disturbance in the stellar magnetosphere: a coherent fluctuation that instruments logged as interference and operators flagged as calibration error. The readings did not resolve into calibration error. They resolved into pattern.

Over a period that no party has publicly agreed on — estimates range from six weeks to fourteen months, depending on who is measuring what and when they started looking — the disturbance has been materialising. First as energy: tightly bounded, electromagnetically dense, without a radiation signature that matches any classified stellar or industrial source. Then as form.

There is now something near the centre of the system that is visible.

It is a bluish plasma mass. Roughly spherical. Approximately two kilometres across at first confirmed measurement; current estimates put it significantly larger. The growth rate is not linear. The plasma surface is not static — it moves, in patterns that instruments describe as structured and that no analyst has successfully modelled as natural. It emits no heat in the conventional sense. It emits no radio frequency output in any registered band.

It is growing.

The Azimuth¶

The Fracture Synths do not call it an anomaly. They call it the Azimuth — a navigational term, meaning a fixed reference direction, the point from which bearing is measured.

The Synths in the Devotion have been orienting their antenna arrays toward a fixed point in deep space since the Devotion was first recorded. What they were pointing at has never been determined.

The Azimuth is in that direction.

This is not confirmed as meaningful. It is noted. It is extremely noted by every party that has access to both data sets.

Whether the Fracture Synths named the event or whether they had a name for what was coming before it arrived is a question several parties are now investigating with considerable urgency and no public acknowledgement that they are doing so.

Earliest Documented Measurement¶

The Azimuth's signal was present in the Hephaistos-9 probe telemetry archive for at least fourteen months before it became visually observable.

Ana Hamato, junior research assistant on Project Flicker, identified a structured directional signal in the frequency band the senior research team had classified as instrumental noise and excluded from their models. She identified a consistent bearing — passing through the gravitational centre of the Veridion system — and recognised that the Flicker's EM output was responsive to something at or approaching that coordinate.

She did not have sufficient data to confirm what was at the bearing. She had sufficient data to encode the raw archive, memorise the coordinate, and leave the station before anyone reviewed her flags.

She did not include the bearing in Archive Core 01. She kept it in her head. The coordinate is a four-digit Veridion survey grid reference with a decimal. She still knows it.

The Hephaistos-9 compute room's probe telemetry relay continued to log the signal for fourteen months after the station went dark — in an empty room, with no one reading. When Ana and Janus return to the station in Return, the relay shows them what fourteen months of unattended logging resolved: something forming at the bearing. Measurable. Growing. Not the Flicker. From the coordinate itself.

Gebreysius's additional parameter — classified above Ana's clearance at the time of her discovery, left in a handwritten note under his dead hand — completes the picture when combined with her archived data. Together they produce not just a bearing but a trajectory: the Azimuth has been growing since before the probe telemetry archive began. The Hephaistos-9 measurements caught the middle of a process that started earlier, and is still continuing.

See: Flashback F3 — Ana's Discovery | Flashback F6 — The Bearing | Story — Return, Act VI

What Is Known About Its Origin¶

Nothing confirmed. Every party with observation capability has an operational theory. No theory has been shared with any other party.

What can be observed:

• The Azimuth did not originate within the Veridion system. Trajectory analysis of the initial energy disturbance — where it exists, which is contested — suggests an origin point outside the heliopause. Beyond the system boundary. From a direction with no catalogued stellar object at observable range.
• It is not a natural phenomenon recognisable to any field of physics that operates within current consensus. This does not mean it is impossible. It means it is new.
• It did not arrive. It is arriving. The distinction matters because arriving implies a discrete event — a transit, a boundary crossing, a moment of entry. What the instruments show is something more like a slow materialisation: a presence making itself legible in stages, as if adjusting to conditions it was not designed for, or as if something on the other side is testing tolerances.

Relationship to the Flicker¶

Not established. Not in current canon. Not to be established prematurely.

What can be observed: the Flicker and the Azimuth share a class of effect — both produce structured, patterned electromagnetic output that influences Synthetik cognition in ways that look, to the Fracture Synths, like communication rather than interference. Both are associated with the Devotion. Both are in the same angular direction from the Synths' antenna arrays.

The Azimuth may be the Flicker, arriving in a form that is visible. The Azimuth may be the source of whatever the Flicker is — the transmitter, rather than the signal. The Azimuth may be a third thing entirely, arriving at the same time as the Flicker's effects by coincidence that is not coincidence because nothing in this system is coincidence at this scale.

The data module almost certainly contains information relevant to this question. This is not established in current canon. It is the most probable explanation for why the kill team was dispatched before the findings could leave Hephaistos-9.

Effects on the System¶

On the Fracture Synths¶

The Azimuth's materialisation has coincided with an acceleration in the spread of the Devotion. More Synth units are entering the state. The Devotion is lasting longer. Units that previously cycled in and out of the attentive stillness are remaining in it. Several Synths who were not previously susceptible have begun orienting.

The Fracture Synths collective is not in agreement about what this means. The faction has no formal leadership — decisions are made by distributed consensus among cognitively active members. The active members are becoming a smaller proportion of the collective.

The Synths are not afraid. The ones still capable of reporting describe something closer to recognition.

On Neural Implants¶

Implant failure events have increased in frequency across the inner-ring and mid-system populations. The Synapse-Guild's suppression protocol — logging failures as manufacturing defects — is beginning to fail under the volume. Too many incidents in too short a period. Too many implants from too many different manufacturers and generations failing with the same signature.

The Guild has not made a public statement. Internally, the escalation has reached the directorate. The directorate is in disagreement about whether to act and in full agreement not to admit the problem publicly before they have an explanation that does not destroy the market for their core product.

On Ship Hull Integrity¶

The quadrilateral hull events — previously three documented incidents — have increased. The pattern is directional: ships that were oriented toward the Azimuth at the time of transit through certain system corridors are disproportionately affected. The pattern has not been published. The data exists in four separate incident logs maintained by four separate parties that have not compared notes.

Apex Industrial has quietly rerouted two standard freight corridors without public explanation. Their logistics announcements describe updated efficiency routing.

On Unmodified Humans¶

Still no confirmed cognitive effect. Rust Alliance workers in proximity to the Azimuth's bearing have reported nothing unusual. Some report a quality of stillness — not silence, something more specific. They describe it as hearing a frequency they cannot identify, that is not in the range of hearing, that they are nevertheless somehow aware of.

None have filed a formal report. It is the specific experience people decide not to put in writing.

Faction Responses¶

Synapse-Guild¶

Priority: Containment of information. The Guild's strategic interest is in neural implant infrastructure — the Flicker and the Azimuth are both existential threats to that infrastructure. The Guild is not investigating the Azimuth's nature. It is investigating how to prevent the Azimuth's existence from becoming public knowledge before the Guild can frame the narrative.

This is not a viable long-term strategy. The Azimuth will eventually be visible to unassisted observation. The timeline is not established.

Rust Alliance¶

Priority: Access. The Azimuth is near the gravitational centre of the system — inner space, not outer ring. The Alliance has no standing claim to inner-system territory and no military capability to enforce one. What the Alliance has is the only population in the system with confirmed immunity to Flicker-class effects, and an emerging awareness that this immunity is a negotiating asset.

Several Alliance captains have already begun operating closer to the Azimuth's position than their standard route licences permit. None have been formally challenged. None have made it to immediate proximity. None have reported what happened when they got close.

Fracture Synths¶

Priority: Presence. The Synths in the Devotion are already oriented. The cognitively active Synths are navigating toward the Azimuth's position at a speed constrained by available transit infrastructure. They are not deploying military capability. They are not making demands. They are gathering, with the specific quality of people who have been waiting for something for a very long time and are not sure whether what has arrived is what they were waiting for, but are not willing to be elsewhere when they find out.

Praxis Biomechanica¶

Priority: Classification and preemption. Praxis ran the Hephaistos-9 research program. They killed the team rather than let the findings leave the station. Whatever the data module contains, they considered it worth a kill team. The Azimuth's materialisation, if it confirms those findings, is an event Praxis is structurally committed to suppressing — because admitting the Azimuth validates the existence of a threat their suppression may have accelerated.

Praxis is in the specific position of an institution that has made several decisions in sequence, each of which seemed manageable at the time, and is now looking at a consequence that will be very difficult to explain to anyone as a series of reasonable choices.

Vanguard Orbital¶

Priority: Military assessment and pre-positioning. Vanguard Orbital deployed a kill team at Hephaistos-9 — whether as a Praxis contractor or as an independent party using the same opportunity is not established. They have now begun moving assets toward the inner system. The mobilisation is framed in public communications as routine rotation.

Routine rotation does not move capital-class assets toward an unregistered gravitational anomaly at the system centre.

Tensions and Conflicts¶

The Azimuth is not yet a military flashpoint. It is becoming one.

Every party is positioning. No party has made a public claim. The absence of public claims is itself a form of escalation — each party is accumulating positioning advantage while preserving the fiction that nothing is happening, which means that when something publicly happens, it will happen at whatever level of commitment everyone has already reached in private.

Three specific pressure points are building:

The access corridor dispute. The inner-system transit routes that provide the closest approach to the Azimuth pass through Apex Industrial administrative territory. Apex has been tightening access permits without explanation. The Rust Alliance has been ignoring the tightening. Vanguard Orbital has been watching both.

The Synth assembly question. Fracture Synths gathering near the Azimuth are not armed. They are not threatening anyone. They are present in increasing numbers in inner-system space where their presence has previously been exceptional. No party has formally objected. Several parties are maintaining observation assets on the assemblies with the specific posture of people who have not decided yet whether the assembly is a warning or an invitation.

The Guild's timeline problem. The Synapse-Guild cannot maintain its suppression strategy indefinitely. When it breaks — and it will break — the political consequences will be aimed at whoever is holding the explanation. The Guild is negotiating quietly with several parties to be somewhere else when that happens. The negotiations are themselves a source of instability, because every party the Guild approaches learns, through the approach, that the Guild is afraid.

The Vanguard Transformation¶

The Azimuth Event is the catalyst Vanguard Orbital has been waiting for without knowing it was waiting.

For generations Vanguard has operated as the system's hired instrument — legitimate armed force by contract, deniable kill teams by subsidiary, enforcement and power projection for whoever is currently paying. They are very good at this. They have grown very large doing it. Large enough that the question of who they are working for has become, quietly, less interesting than the question of what they could do if they were working for themselves.

The Azimuth provides the answer to a question that could not previously be asked in public: what is worth fighting for, rather than being paid to fight over?

The answer, for Vanguard's leadership, is the Azimuth. Not because they understand it — no party understands it — but because it is the largest single strategic variable in the system's history, it is forming near the gravitational centre rather than in any faction's territory, and whoever controls access to it controls the geometry of everything that follows.

Vanguard has spent the last century building infrastructure, personnel depths, and logistics capability that no single contractor arrangement has ever fully utilised. The Azimuth does not require a contractor. It requires a sovereign.

The decision to transform from military service conglomerate to independent power is not announced. It is enacted: through asset repositioning, through the selective non-renewal of existing contracts, through the slow withdrawal of Vanguard enforcement from arrangements that previously held the system's peace. Each individual decision is defensible. The pattern of decisions, assembled, is a declaration.

The Vanguard-Guild Conflict¶

The Synapse-Guild is the party with the most to lose from Vanguard's transformation, and they know it first.

The Guild's power rests on three pillars: food production, cognitive superior through implant technology, and the armed force that protects both. The first two are theirs. The third has always been rented from Vanguard. The Guild has never needed to own a military because they have always been able to purchase one.

Vanguard withdrawing from that arrangement — or worse, repositioning to enforce access conditions around the Azimuth that constrain Guild movements — removes the third pillar. The Guild's response is the only response available to a power that has never had to build what it always bought: they go to war.

The conflict is not symmetric. The Guild has resources, territory, and the political infrastructure of the inner worlds. Vanguard has ships, trained personnel, operational reach, and two centuries of experience fighting other people's wars. The Guild is paying for a military they are building from scratch against people who have been doing this professionally for longer than the Guild's current leadership has been alive.

This does not make the outcome obvious. The Guild's genetic modification programme has produced military-grade augmentation as a secondary output for decades. The Pure tier — the Guild's actual decision-makers — have implant stacks that exceed Vanguard Corps standard issue in specific capabilities. And the Guild controls the food supply. Every party in the system eats. This is leverage that does not require ships.

What the conflict is actually about is the Azimuth. The military engagement is the visible surface of a race to establish what the Azimuth is and who gets to decide what happens next. The Guild wants Vanguard contained before Vanguard can entrench a position near the system centre. Vanguard wants the Guild's access networks severed before the Guild can use them to supply a coalition against Vanguard's repositioning.

Both parties want the data module. Neither is the party currently carrying it.

What Is Not Stated in Current Canon¶

• How the conflict begins as a formal military engagement
• The specific first engagement and its outcome
• Whether either party makes a public declaration or whether the war begins as a series of mutually acknowledged incidents that escalate past the point where either party can call them incidents
• The duration of the conflict
• Which party, if either, wins — and what winning means when the Azimuth is still growing and neither party understands what they are fighting over

Other Factions in the Gap¶

The Vanguard-Guild conflict is the largest military event in the Veridion system's recorded history. Every other party in the system reads it the same way: as an opportunity.

Rust Alliance¶

The Alliance has spent generations being managed by both the Guild (as a labour supply) and Vanguard (as an enforcement target). The conflict between those two powers is the first political moment in living Alliance memory where neither party has the attention or the assets to manage the outer rings simultaneously.

The Alliance's play is not military. It is logistical. Heavy isotope mining and fusion fuel supply run through Alliance infrastructure. Both Vanguard and the Guild need fuel. The Alliance has always known this. They have always been in a position where exercising that leverage would have brought Vanguard enforcement before the morning was out.

Vanguard is occupied elsewhere. The morning does not come.

The Alliance begins renegotiating supply contracts — not breaking them, not yet, but renegotiating at terms that reflect what the Alliance has always known it was worth and never previously been able to say.

They are also positioning toward the Azimuth through the inner-system corridor access they have been quietly expanding since the event was first observed. The Azimuth is the one space in the system that nobody owned when this started. The Alliance's position on ownership rights for a gravitational-centre phenomenon that predates all faction claims is: finders, keepers — expressed in the specific language of Rust Alliance salvage law, which they intend to make the relevant legal framework whether or not anyone else agrees.

Fracture Synths¶

The Synths are not interested in the Vanguard-Guild conflict except as environmental noise that reduces the number of armed parties paying attention to their movements.

They are gathering near the Azimuth. This is the only thing they care about. The conflict buys them the transit window to do it without interdiction.

The active Synths — those not yet in the Devotion — are making a specific calculation: whatever the Azimuth is, the Synths in the Devotion have been pointed at it for years. When the Azimuth fully materialises, or when its nature becomes legible, the Synths want to be present. Not to control the outcome. To understand it.

The distinction matters to them. It is not clear it will matter to anyone else.

Praxis Biomechanica¶

Praxis is in an impossible position that their own decisions built.

They suppressed the Hephaistos-9 findings. They sent the kill team. They have been classifying the Devotion as a malfunction for long enough that their internal research division now has two parallel models of Synthetik cognition — the published one, which is wrong, and the restricted one, which is terrifying — and the gap between them has become institutional knowledge that no one formally acknowledges.

The Azimuth validates the terrifying model. The conflict between Vanguard and the Guild removes the two parties most likely to enforce the suppression. Praxis is watching both developments with the specific attention of an institution that has bet everything on a narrative that is visibly failing.

They have one asset nobody else has: the restricted research, and the people who conducted it before the kill team arrived. If any of the Hephaistos-9 team survived — Gebreysius, specifically — they know things that are not on the data module, because not everything was archived. Praxis knows this. So does Whisper.

The Fabric¶

The Fabric recruits from the expendable margins and runs on information. The Vanguard-Guild war is the most information-rich event in system history: troop movements, supply chains, diplomatic back-channels, the specific anxieties of every party positioning in the conflict's shadow. The Fabric is harvesting all of it.

What the Fabric does with information at this scale is not stated in current canon. It is noted that the Fabric's dead-drop buoys operate on Flicker-adjacent frequencies, and that the Azimuth appears to be producing structured output in those same bands.

The Fabric may be reading the Azimuth. The Azimuth may be reading the Fabric. The distinction is the kind that becomes important after it is too late to matter.

Open Questions (for future stories)¶

• What is the Azimuth, in terms that do not rely on analogies to known phenomena?
• Is it communicating, or is it merely present in a way that produces effects that look like communication to susceptible systems?
• What does arrival mean for something that is not arriving in a way that fits any existing model of transit?
• Why now? What changed — in the system, in the Flicker's behaviour, in whatever is outside the heliopause — to cause the materialisation at this specific moment?
• What do the Synths in the Devotion know that they cannot say?
• What is the Rust Alliance not reporting about close approaches?
• If the data module's findings are relevant to the Azimuth, what exactly did the Hephaistos-9 team find — and did they find it, or did the Flicker show them?

See also: The Flicker | Factions | Megacorporations | Setting | Characters