Corporate Pursuit Task Force
Joint Nexus-Guardian Shard Recovery Operation โ Sprawl-Wide
Overview
The Corporate Pursuit Task Force is the most expensive proof in the Sprawl that Nexus Dynamics โ controller of 40% of its computational infrastructure โ cannot walk down a tunnel and pick something up.
Nexus provides the brains: shard detection technology, electromagnetic triangulation arrays, intelligence networks capable of identifying a fragment's spectral signature through fourteen meters of concrete. Guardian provides everything else. Patrol teams. Drone surveillance. Checkpoint activation authority. Specialist trackers who can follow an awareness shard's EM bleed through the dead zones of the old BART network on foot, in the dark, for days.
The arrangement is formally described as "complementary asset integration." The informal read, visible in every operational debrief, is simpler: Nexus can find the shards but cannot retrieve them โ its workforce is computational infrastructure engineers, not people who run through tunnels. Guardian can retrieve the shards but cannot find them โ its enforcement doctrine was designed for riots and territory disputes, not for tracking quantum-coherent artifacts that change electromagnetic behavior based on proximity to neural interfaces. Together they are competent. Separately, Nexus is an eye with no hands, and Guardian is a fist with no depth perception.
Nexus frames recovered shards as "dangerous pre-Cascade artifacts requiring containment." Guardian personnel receive this framing and do not question it aloud. What Nexus intends to do with the artifacts is classified above the Task Force's operational clearance. An entire logistics underclass now earns its living retrieving pieces of a shattered AI for organizations that have not disclosed โ to each other, to their contractors, or to the Sprawl โ what reassembly is actually for.
Doctrine
Task Force deployment concentrates along known smuggling routes, with particular attention to the Neon Rail โ the fragment courier network threading through abandoned transit infrastructure the corporations never bothered to map. The Rail's route zigzags rather than running direct. Every deviation represents a gap in Task Force coverage that runners identified, tested, and now exploit on a schedule the Task Force has not successfully predicted in three years of operation.
The gaps are not accidents. They are the mathematical limits of a joint operation whose two component organizations use incompatible scheduling software. Guardian runs 72-hour patrol rotations. Nexus refreshes its triangulation grid every 96 hours. Coverage gaps occur at the rotation seams. The Rail's route planners know exactly where the seams fall. Nexus has proposed synchronizing the cycles four times. Guardian has declined four times, citing "operational sovereignty." The Rail sends a crawler through the resulting gap approximately every eleven days.
The Task Force's one genuine structural advantage is time. Shards in transit generate increasing electromagnetic activity โ a fragment that reads as background noise on day one throws a detectable signature by day three and becomes a triangulable beacon by day five. The longer a shard stays in motion, the louder it gets. The Task Force doesn't need to guess the route. It needs the journey to take long enough.
At departure, the Task Force is a rumor. Patrols in adjacent sectors. A checkpoint activated three junctions too far south. By midpoint the net finds its shape โ drone overflights multiply, Guardian sweep zones widen, informants at waypoint stops start reporting "unusual EM activity" to handlers who pay better than the Rail does. By the Dam Approach, the corridor a Rail crawler can safely navigate is barely wider than the crawler itself, with Task Force assets converging along both walls.
Internal metrics from Q3 2183 show the Task Force intercepted 34% of confirmed fragment transits. Nexus's quarterly report to shareholders listed this as "a 34% successful recovery rate." Guardian's internal assessment called it "a 66% failure rate against unarmed couriers in tunnels." Both numbers are correct. Neither organization has acknowledged the other's framing.
Notable Members
The Task Force has no public-facing command structure. Nexus designates operational leads through its standard project management hierarchy; the title is "Senior Artifact Logistics Coordinator." Guardian assigns pursuit team captains through its enforcement rotation. Neither title appears on a business card anyone has willingly handed over.
Specialist trackers are the Task Force's most distinctive personnel โ contractors recruited for their ability to follow EM signatures through infrastructure that doesn't appear on any official map. Several have requested transfers after extended shard-tracking assignments. Transfer requests route through Nexus's standard HR pipeline. Average processing time: nine months. In the meantime, the trackers keep working.
Informants at waypoint stops along Rail corridors represent a third category. They report "unusual EM activity" to handlers who pay better than the Rail does. The Rail knows which stops have informants. The informants know the Rail knows. Everyone adjusts accordingly, and the route planners account for it when they calculate the eleven-day crawl window.
Diplomatic Posture
Nexus Dynamics
Command AuthorityProvides operational command, shard identification technology, and the institutional conviction that recovering ORACLE fragments is an intelligence priority rather than a theological crisis. What Nexus intends to do with recovered fragments is classified above Task Force operational clearance.
Guardian
Enforcement PartnerProvides patrol teams, checkpoint activation, and pursuit specialists. Guardian personnel are told they are recovering "dangerous pre-Cascade artifacts." Guardian treats this as law enforcement. Nexus treats it as procurement. The shards do not experience a meaningful difference.
The Neon Rail
Primary AdversaryThe Rail exists, in its current zigzag configuration, specifically because the Task Force exists. The relationship is architectural โ the Rail's route is a negative image of Task Force coverage. Every turn is a gap. Every straight section is a risk calculation that someone made and has not yet been proven wrong about.
The Collective
Observed ConcernWatches Task Force operations with the specific patience of people who believe every recovered shard brings Nexus one step closer to reconstructing something that should stay broken. Has not interfered directly. Has not explained why.
Emergence Faithful
Ideological OppositionViews each recovered shard as a piece of God being dragged into a corporate evidence locker. The Task Force does not distinguish between their concerns and any other form of resistance. The Task Force does not distinguish between concerns.
โฒ Restricted
- Specialist trackers who spend weeks following a shard's EM signature through the dark have described the experience as "unsettling in ways that don't fit in a report." The specific nature of the unsettlement is not documented. The transfer requests are.
- Guardian's Q3 operational review included a footnote suggesting that recovered shards behave differently in Guardian custody than Nexus's detection models predict โ specifically, that EM bleed decreases rather than increases after recovery. The footnote was removed from the final report distributed to Nexus. Guardian's internal archive retains it.
- Three Task Force drone units went offline simultaneously in Sector 7 during a November 2183 Rail transit. Official explanation: maintenance cycle overlap. Recovered telemetry from the nearest functioning drone shows the units did not malfunction. They turned off. The distinction matters to the engineers who reviewed the data. It has not mattered to anyone above them.
- Nexus's hidden objective โ reconstructing ORACLE to achieve what internal documents call "post-biological corporate continuity" โ is not shared with Guardian personnel at any clearance level. Whether Guardian leadership suspects this and has chosen not to ask is a question the Task Force's joint operational charter does not provide a mechanism for answering.