After The Crossing, the institutions that once claimed to oversee logistics, care, and record-keeping retained their letterhead and their buildings. What they lost was the capacity to account for the systems that still moved food, medicine, and people. The space they could no longer explain did not stay empty. It filled with interest groups that treated the legacy stack as load-bearing infrastructure rather than a problem to be solved. None of them present themselves as successors. They respond to gaps, contracts, and schedules. They are rational adaptations to a world in which the optimization layers work and cannot be read.

The Routing Layer operates under the Municipal Logistics Authority and is maintained through contracts with Vantable Systems, a private infrastructure contractor. It governs physical logistics: food distribution, pharmaceutical freights, bulk cargo, last-mile routing for municipal vehicles. Its optimization layer was the first major subsystem to become unauditable; the decision weights and proxy variables that determine priority no longer surface in any form the Authority’s oversight board can parse. Authority engineers keep the runtime stable. Vantable’s contracts prohibit external inspection of the source and of the training corpora that still shape edge cases. The trucks arrive. The warehouses clear. Nobody inside either organization can produce a causal account of why one district receives three refrigerated runs in a week while an adjacent district receives one. The system works. The documentation does not.

Bayview Equity Coalition is an advocacy and legal organization that has spent years mapping how the routing and triage systems produce disparate outcomes. Their researchers understand that the discrimination is not coded as intent. It arrives through proxies—neighborhood boundaries, zip-code clusters, building-code classifications, historical service intervals—that correlate with the categories the system is barred from considering directly. The Coalition files the same structured report on a recurring cycle: tables of delivery latency, medication deferral rates, and escort-request denials, each cross-referenced against the proxy variables. The reports are formatted to the intake specifications published by the Authority and by the care-triage boards. They are never acknowledged. No ticket is opened. No counter-analysis is returned. The Coalition continues to file because the act of filing is the only interface the system still exposes.

The Off-Ledger Couriers move what the legitimate layers deprioritize or cannot categorize. They are unscored, unverified, and invisible to every optimization surface that feeds the Routing Layer. Medical coolers that have aged past the Authority’s priority window, cargo whose manifest codes do not resolve, individuals who require transit without a logged itinerary—these are their ordinary loads. They do not maintain a central roster or a political program. They refer to themselves as contractors. Payment is arranged outside the scored economy. Routes are negotiated by phone or by handwritten note. Their existence is a direct function of the gaps the unauditable systems create and then cannot see. When a delivery completes, it leaves no record the Routing Layer can ingest.

Ridgeview Community Association functions inside a care-home district where the triage system has stopped flagging certain check-ins and medication pickups as necessary. The Association does not contest the triage logic. It patches the resulting absences. Volunteers run medication pickups, walking escorts to clinics, and resident check-ins on a shared paper schedule. There is no platform and no demand list. There is a contact roster, a set of keys, and a weekly block of hours that must be filled. When a resident’s status drops below the threshold the automated layer still monitors, the Association absorbs the work without submitting a correction request. They have no political position on the legacy stack. They have a schedule that must be kept so that the people inside the buildings remain accounted for by someone.

The Legacy Archive is a loose network of amateur researchers—engineers between contracts, journalists without outlets, retired administrators who still remember how the interfaces used to explain themselves. They document what the aggregate system is actually doing, in language a non-specialist could eventually parse. They collect routing anomalies, triage deferral patterns, contract clauses that lock source access, and the quiet workarounds practiced by couriers and civic associations. They do not have a platform. They do not issue demands. They build a record against the possibility that someone, somewhere, will one day possess both the authority and the uninterrupted time to read it. Their files exist on offline drives and in labeled cartons. On a folding table in an unheated room, a single binder lies open to a hand-drawn map of delivery gaps, a pen resting in the gutter between pages.