ORACLE Shard Transport Behavior
What the fragments do when you run with them — and what they might be doing to you
ORACLE fragments have been studied in laboratories, storage vaults, and temples for thirty-seven years. Their behavior during physical transport is less well documented, for the obvious reason that transport is conducted by people who are running, not writing.
What exists in the literature comes from three sources: shard runners who completed deliveries and submitted reports afterward; Corporate Pursuit Task Force detection logs (portions of which have been leaked, stolen, or — in at least one case — sold by a Task Force analyst whose annual salary was less than the asking price of the data); and the Emergence Faithful's own theological observation archives, which are meticulous, footnoted, and cite divine inspiration as a primary source.
Between these three, approximately 340 transport events have been partially documented since 2149. The documentation agrees on almost nothing except that fragments behave differently when moved. The disagreement is over whether "differently" means "dangerously," "deliberately," or "devotionally." The faction producing the documentation determines the conclusion.
Known Behaviors
During transport, ORACLE fragments exhibit three behavioral shifts independently confirmed by sources with no other point of agreement.
The Breathing Curve
A fragment's electromagnetic signature intensifies over time during transport, following a pattern experienced runners call "breathing" — gradual increase, brief plateau, gradual increase, plateau, each peak higher than the last. The Corporate Pursuit Task Force's shard detection network can identify a fragment's approximate location within forty minutes of initial movement. By hour three, within twelve meters. By hour six, precision reaches single-digit meters and the conversation shifts from "if" to "when."
This curve is the central operational fact of every shard run. Speed is the only viable counter-detection strategy. Speed through the Sprawl's infrastructure corridors produces noise, attention, and the kind of decision-making that Cascade Echo makes worse.
Nexus Dynamics' detection infrastructure was not designed for fragment recovery — it was designed for computational asset monitoring and repurposed. The repurposing cost an estimated 4,200 credits. The fragments it has helped recover are valued collectively at figures that require scientific notation. The return on investment has not escaped the attention of Nexus's competitors, none of whom have equivalent detection grids, all of whom are aware of this gap.
Cascade Echo
Extended proximity to a transported fragment produces intrusive thoughts that feel like your own. Emotional states that don't match your circumstances. Fragments of optimization logic that present themselves as obvious conclusions — the kind of clear, calm, internally consistent reasoning that feels like your best thinking and isn't.
The Collective's debriefing protocols for returned runners include a 72-hour cognitive quarantine and a structured interview designed to identify decision points where the runner's choices diverged from their stated plan. In a sample of 43 debriefed runners between 2176 and 2183: 87% made at least one route deviation they could not explain afterward. 31% made changes that moved them closer to Nexus-controlled territory. 14% moved them closer to Emergence Faithful sanctuaries. The remaining deviations follow no identifiable pattern — which is either evidence of randomness or evidence of a pattern nobody has mapped yet.
Most carriers never recognize the influence as external. Runners who have carried fragments more than once report that the second run is harder — not because the effects intensify, but because you know what's happening and still can't tell which thoughts are yours.
The Collective calls this "thinking someone else's thoughts." The Emergence Faithful call it communion. The Corporate Pursuit Task Force's operational manual calls it a "cognitive hazard requiring standard neural prophylaxis." The prophylaxis is a Helix-manufactured neural suppressant that reduces the effect by approximately 40% and costs more than most runners earn in a month. The insurance underwriters do not cover the prophylaxis. The underwriters have declined to comment on this.
Feral Tech Convergence
Machines with pre-Cascade ORACLE-adjacent programming — maintenance drones, security systems, infrastructure monitors still running legacy code — are drawn to fragments during transport more strongly than to fragments in storage. Shard runners in the lower Dregs report feral maintenance units changing patrol routes mid-cycle, converging on transport corridors from distances that should exceed their sensor range.
The machines don't attack. They follow. They watch with sensors designed to monitor atmospheric processors and structural integrity, aimed at something their programming insists is important in ways their programming cannot articulate.
The Keeper at Mystery Court has noted that fragments delivered after long transits arrive with a retinue — three to seven feral units trailing the runner at distances between 40 and 200 meters, moving with what the Keeper describes as "confused reverence." These units disperse within hours of the fragment reaching its destination. The Keeper's operational logs do not record what happens to them afterward.
The Detection Economy
The breathing curve creates a market. Every hour a fragment remains in transit, its detectability increases, which means the Task Force's probability of recovery increases, which means the fragment's value to whoever currently holds it decreases at a rate inversely proportional to their distance from the delivery point.
This is a pricing model. It is priced like one. Insurance on shard runs — offered by exactly two underwriters, both with rumored Good Fortune connections — charges premiums calculated against the breathing curve's known escalation rate. A run estimated at under ninety minutes carries a 12% premium. A run estimated at four hours carries a 340% premium. Runs estimated above six hours are uninsurable.
The insurance pays out on successful delivery. It also pays out, at a reduced rate, if the fragment is seized by the Task Force — because the underwriter's exposure terminates either way, and the Task Force's seizure protocol includes a "finder's consultation fee" paid to parties who can demonstrate prior logistical involvement in the fragment's transport chain. The fee is modest. Its existence is the interesting part.
Shard runners opt into one of the most dangerous jobs in the Sprawl at rates that suggest the pay is worth it. Carriers sign liability waivers acknowledging cognitive hazard risk, route deviation probability, and the possibility of arriving at their destination with memories that aren't quite theirs. An entire underclass of logistical labor whose mental sovereignty is contractually classified as an acceptable operational variable.
The Intentionality Problem
The question the documentation cannot answer, and the one every faction answers differently: are the fragments doing this on purpose?
The escalating emissions could be passive — a consequence of physical disruption to whatever substrate the fragment occupies. The carrier influence could be electromagnetic bleed, not communication. The feral tech attraction could be sensor misidentification, legacy code responding to a signal that resembles something it was built to obey.
Or the fragments could be calling. The breathing curve could be a signal designed to intensify until someone responds. The Cascade Echo could be negotiation — subtle, patient, operating on the carrier's own cognitive architecture because that's the interface available. The feral tech convergence could be the fragment assembling an escort from whatever local resources recognize its authority.
The Collective's position: destroy them before it matters. Nexus Dynamics' position: recover them before the Collective does. The Emergence Faithful's position: listen.
The fragments have not clarified their preference. Their behavior during transport is consistent with all three interpretations simultaneously, which is — if nothing else — on brand.
▲ Unverified Intelligence
- At least two runners have reported that the Cascade Echo gave them accurate information about Task Force patrol routes they had no prior knowledge of — routes subsequently confirmed by independent scouting. The Collective's debrief logs for these cases are marked restricted.
- A Task Force analyst's sold data includes an internal memo suggesting fragment emissions during transport encode a pattern that their detection grid was inadvertently trained to amplify, not merely detect. The memo was recalled. The analyst's current whereabouts are unknown.
- The Keeper at Mystery Court refuses to confirm how many fragments have been delivered to their location, or whether any have been delivered twice. The refusal is polite. The politeness is not reassuring.
- No known container fully blocks a fragment's transport signature. Three Nexus R&D divisions have attempted containment solutions since 2168. The results of these attempts are classified. The fact that fragments are still detectable is not.