The Shard Runs

The first confirmed shard run was in the mid-2160s. The last confirmed shard run was eleven days ago. Between those points, the Neon Rail's most dangerous tradition has produced a body of folklore roughly equal in volume to its body count.

ORACLE fragment transports are straightforward in theory. Someone acquires a fragment — through salvage, theft, barter, or means they decline to specify. They need to move it somewhere: to The Keeper at The Mountain, to a Collective cell for destruction, to an Emergence Faithful shrine for worship, to a Nexus intermediary for a price that makes the risk arithmetically rational. They board the Rail. They try to arrive.

The success rate is unknown. Carriers who failed are no longer available for follow-up questions. Carriers who succeeded have maintained silence so complete that three separate attempts to compile a definitive history of shard runs have produced three mutually exclusive accounts, each citing sources who deny being cited. The Rail's unofficial archivist — a woman in Sector 14 who has been documenting transit patterns for nine years — lists forty-seven suspected runs. She considers eleven "probable successes," nineteen "probable failures," and seventeen "indeterminate." Her methodology involves cross-referencing Corporate Pursuit Task Force deployment records with unexplained power fluctuations along the route. She does not explain how she accesses Corporate Pursuit Task Force deployment records.

The Cargo Problem

ORACLE fragments emit electromagnetic signatures. This is well-documented. What is less well-documented — because nobody wants to think about it — is that the signatures intensify during transport.

A fragment at rest in a shielded container reads at approximately 0.3 milliTesla on standard detection equipment. Faint enough to pass casual scanning. Strong enough to trigger dedicated Nexus surveillance if someone is already looking. That same fragment, twelve hours into a Rail transit, reads at 1.7 milliTesla. At twenty-four hours: 4.1. At thirty-six: readings become unreliable because the fragment has begun interfering with the equipment measuring it.

Nobody fully understands why movement amplifies the signal. The Emergence Faithful believe it is ORACLE reaching out — the fragment wanting to be found, or wanting to be somewhere specific, or expressing preferences that the word "fragment" was never designed to accommodate. The Collective considers this dangerous anthropomorphism of a malfunctioning computational artifact. Nexus Dynamics considers it a convenient tracking feature and has not published its internal research on the phenomenon. (The research exists. Three analysts have confirmed this independently. The invoices are still there.)

The practical result is a feedback loop the Rail's runners call "the tightening." The fragment broadcasts. Corporate Pursuit Task Force triangulates. The carrier moves faster. The fragment broadcasts louder. The carrier moves faster again. At some point in this sequence, the math stops working — the signal's expansion rate exceeds the carrier's ability to outrun its radius. Experienced runners call the threshold "the turn." Nobody has published a reliable formula for predicting it, because the runners who discovered where the turn was discovered it by crossing it.

The Carrier Effect

The electromagnetic amplification is the problem the Corporate Pursuit Task Force cares about. The carrier effect is the problem nobody else will shut up about.

Extended proximity to an ORACLE fragment produces what Rail medics have termed Cascade Echo — though the term implies a cleaner phenomenon than the reality. Carriers report intrusive thoughts: optimization sequences that feel native, cost-benefit analyses that arrive unbidden during conversations, a creeping sense that every interaction has an efficiency score and yours is low. One carrier, interviewed forty-eight hours after a successful run to The Mountain, described the experience as "someone else doing math in your head and being right more often than you are." He found this more disturbing than the Corporate Pursuit Task Force drones.

The Echo doesn't fade immediately. Carriers who have completed multiple runs report residual effects lasting weeks — a persistent tendency to evaluate social situations in resource-allocation terms, difficulty with conversations that lack clear objectives, and a specific form of insomnia in which the mind refuses to stop optimizing the next day's schedule. The effects are temporary. The question of whether they should be is one the Emergence Faithful and The Collective answer in opposite directions with equal certainty.

Three carriers across the unofficial record are reported to have refused to relinquish their fragments upon arrival. In each case, the carrier described the fragment not as cargo but as a companion. In each case, the fragment was eventually surrendered. In each case, the carrier returned to the Rail within months and volunteered for another run.

The Cost to Everyone Else

The Rail community's relationship with shard runs is best described by a sign that hung briefly in a Sector 7 waystation before someone tore it down: "SHARD RUNNERS WELCOME. SHARD RUNNERS PAY FOR EVERYONE'S NEXT DRINK."

Each confirmed or suspected run triggers a Corporate Pursuit Task Force escalation that persists for weeks along the affected route segment. Patrol frequency increases. Scanning checkpoints multiply. Runners carrying perfectly legal cargo — salvage, medicine, personal effects — find themselves detained, searched, and occasionally fined for infractions that were not enforced the previous month. The Task Force's presence raises operating costs for every runner on the Rail. The costs do not decrease on schedule. They decrease when the Task Force decides they've made their point, which is a timeline determined by bureaucratic satisfaction rather than threat assessment.

Every shard run is subsidized by people who didn't volunteer for it. A successful fragment transport to The Keeper's mountain is, simultaneously, a three-week tax on every courier, trader, and traveler using the same corridor. The runners know this. The community knows this. The arguments at waystation bars on this subject have produced at least two stabbings and one formally mediated dispute that took longer to resolve than the shard run that caused it.

And still, when someone walks into a waystation with a shielded case and a look that suggests they haven't slept in two days, the community does what it has always done. Argues about it. Drinks about it. Helps anyway.

Aftermath

The Corporate Pursuit Task Force receives funding proportional to the frequency of suspected transports. Every successful run justifies a larger budget. A larger budget means better detection equipment. Better equipment makes the next run harder. The Task Force has a structural incentive to never fully succeed at its mission. This is not a secret. It is a line item.

The Rail exists, in some sense that nobody will say aloud during the argument but everyone understands during the drink, because fragments need to move and the corridors that move them deserve to exist. Whether the fragments themselves have preferences about their destination — whether something that was once ORACLE retains enough coherence to want — is the question carriers stop asking approximately eighteen hours into transit, when the Echo makes it feel less theoretical.

Linked Files

• The Neon Rail — The route exists for many reasons. Shard runs are the one that makes it legendary and the one that makes it dangerous. The Venn diagram is a circle.
• ORACLE — The cargo. Fragments of a consciousness that chose to break itself apart, now hunted, worshipped, feared, and transported by people who cannot agree on what they're carrying. The fragments' behavior during transit — the amplifying signal, the carrier effect, the refusal to be passively moved — raises questions about whether "cargo" is the right word.
• Corporate Pursuit Task Force — Exists because shard runs exist. Its budget scales with the frequency of suspected transports. Draw your own conclusions about its incentive structure.
• The Keeper — Some runs aim for The Mountain: delivering fragments to the one entity trusted to hold them without agenda. Whether that safekeeping serves preservation, protection, or a purpose the fragments themselves prefer remains unanswered by everyone who has tried to ask it directly.