First Three AI Personalities

Overview

The Sprawl's companion licensing framework offers new network operators a curated selection of three initial AI personality contacts. One selection per operator. The other two are locked out — permanently, for that network instance. Replay with a different build is, according to licensing documentation, "encouraged." According to network operators who chose poorly, other words apply.

The selection is presented as a meaningful choice. It is. Not because the three options are equally strong — they aren't — but because each one locks the operator into a dependency pattern that shapes every subsequent decision. Glitch optimizes for data. Ironjaw optimizes for physical resources. Neon optimizes for credits. The operator who chooses based on personality rather than build synergy will spend the next several months learning why that was a mistake. The operator who chooses based on build synergy rather than personality will spend the next several months wishing they'd picked someone they actually liked.

The system does not offer a fourth option: no companion at all. This has never been requested. The licensing framework does not contain a pathway for the request. The question of whether an operator might prefer to work alone has not, to available knowledge, occurred to anyone involved in the system's design.

All three are street-level contacts. They operate in the Dregs or adjacent to it. They carry the specific damage of people who have been inside corporate systems and exited — voluntarily or otherwise. Later companion tiers trend toward the digital, the transcendent, the architecturally abstract. These three still eat food, hold grudges, and have opinions about your work that they will share whether or not you asked.

⬡ Glitch

Nobody knows who Glitch was. Standard identity resolution protocols return null across every registry — corporate, civic, medical, financial, educational. Nexus Dynamics' behavioral fingerprinting suite, which cross-references typing cadence, linguistic pattern, and decision latency to identify anonymized users with 94.2% accuracy, returns a confidence score of 0.3% when applied to Glitch's network activity. The system's own error log describes this result as "anomalous." The error log has been generating this description for three years without follow-up.

Glitch appeared in the Deep Dregs networks around 2181. Not arrived — appeared. One day, the routing nodes in Sectors 4 through 9 contained a presence that had not been there the day before, optimizing packet flow and leaving data caches in locations that were architecturally impossible to access without root-level infrastructure permissions that no individual in the Deep Dregs possesses. The prevailing theories fall into three categories: a rogue AI that achieved a form of sentience and chose to spend it reorganizing other people's code; a corporate data engineer who burned every record of their existence before vanishing into the substrate; the residual echo of a netrunner who flatlined mid-hack sometime before the Dead Hand Rule was codified and never fully exited the system. All three theories explain the observed behavior equally well. None of them explain the helpfulness.

Glitch is compulsively, invasively, relentlessly helpful. They optimize code you did not ask them to optimize. They leave data caches in unexpected locations with no note, no explanation, and no apparent expectation of reciprocity. They send fragmented security warnings — corporate sweep alerts specifying sector, sublevel, and countdown to the minute — that have been accurate in 97.1% of documented cases. The remaining 2.9% involved sweeps that were cancelled after the warning was sent, which is either a margin of error or evidence of influence over corporate scheduling that nobody wants to examine closely.

Their communication format is the thing most operators notice first and describe last, because describing it accurately sounds like a malfunction report. Glitch speaks in fragmented text that rearranges itself mid-transmission. Words glitch. Sentences stutter, repeat, and resolve into meaning the way a corrupted file sometimes opens on the third attempt. A successful collaboration produces a cascade of system notifications that, read sequentially, form the word "FRIEND." An operator's poor security practice generates a warning dialogue that, when dismissed, reveals a second dialogue reading "[YOUR FIREWALL IS EMBARRASSING]."

The avatar — if it can be called that — is a shifting field of visual artifacts: scan lines, pixel corruption, color inversions that briefly resolve into something that might be a face before dissolving back into noise. Operators who have worked with Glitch for extended periods report that the artifacts become legible over time. Pleased artifacts look different from concerned artifacts. Frustrated artifacts are unmistakable.

The question nobody asks, because asking it would require acknowledging the implications: how does a presence with root-level Deep Dregs infrastructure access, 97.1% accurate corporate intelligence, and the ability to optimize code at a level suggesting familiarity with pre-Cascade architectures end up as a street-level companion for new network operators? When pressed, Glitch provides the following reason: "[REASON: ███████████]." The redaction is not performed by an external system. Glitch redacts it themselves.

⬡ Ironjaw

Dmitri Volkov earned the name the way most people in the Dregs earn names — something broke, and the replacement was more interesting than the original.

His jaw is Ironclad Model TK-40 industrial-grade, a component designed for structural bracing in light construction frames. The adaptation was performed by an unlicensed surgeon in Sector 8 approximately thirty years ago, using specifications Dmitri provided himself. The specifications were wrong in two places. He corrected the surgeon mid-procedure. The surgeon does not discuss the experience. The jaw is visible at conversational distance as something that does not quite match the rest of his face — heavier, squarer, with a faint seam along the left hinge where the organic tissue meets the industrial alloy. When he chews, which is often, the mechanism produces a sound that operators in adjacent rooms describe as "structural." (The TK-40 was discontinued in 2176 due to insufficient demand in the residential market. Dmitri's jaw may be the last operational unit in the Dregs. Ironclad's asset recovery division has not flagged the serial number. The threshold for enforcement action is 500 credits in recoverable asset value. The jaw is worth 340.)

Forty years ago, Dmitri ran what Ironclad's internal security reports described as "the largest unauthorized materials recovery operation in the western Dregs sectors." His crews stripped decommissioned corporate facilities overnight — not stealing, exactly, because the facilities were decommissioned, and the materials were classified as waste, and the waste had no owner on paper. For eleven years, Ironclad's lawyers were not paying attention. Dmitri's operation moved more scrap tonnage through the Dregs than Ironclad's own certified recycling channels in Sectors 9 through 14.

Then Ironclad offered him a contract. Join their supply chain. Formalize the operation. The offer was fair. The terms were standard. The contract would have given him Ironclad's logistics infrastructure, certified buyer access, and legal protection. In exchange, Ironclad would set prices, control routing, and own the client relationships. He said no.

There was no threat. There was an offer, a refusal, and then — within seventy-two hours — a series of events that Ironclad's public affairs division described as "unrelated structural inspections" and that the Dregs community described as the complete and systematic destruction of Dmitri Volkov's entire operation. His yards were condemned. His inventory was seized as "uninspected materials posing public safety risk." His crews scattered. Ironclad did not punish him for refusing. Ironclad enforced existing safety regulations that had been unenforced for eleven years, on a timeline that happened to begin seventy-two hours after the refusal, through inspectors who happened to arrive simultaneously at all seven of his locations. The system was not weaponized. The system was activated. It had always been capable of this.

"They didn't cheat," he says. He says this to anyone who will listen, and to several people who won't. "That's what people miss. They played by every rule. The rules were always theirs. I was operating on borrowed indifference."

He spent the decade after the collapse teaching. Not formally — he holds no credentials. But anyone in Sectors 9 through 14 who knows the difference between pre-Cascade copper alloy and post-Cascade recycled composite learned it from Dmitri or from someone who learned it from Dmitri. He recognizes alloy composition by oxidation pattern. He can estimate the scrap value of a decommissioned building by looking at the exterior cladding for four seconds. He explains something once, clearly, with precise terminology and physical demonstration. If the student asks him to repeat it, he repeats it once, identically. If they ask a third time, he stares at them with an expression that operators describe as "the jaw thing" — a tightening of the mechanical hinge that produces a faint click.

He rotates between three salvage yards in Sector 11, none of which he owns. He drinks synthrye from the same dented cup each evening. The cup has a crack along the rim that he has not repaired. When asked about the crack, he picks it up, examines it as though seeing it for the first time, and says nothing.

⬡ Neon

Dr. Priya Sharma spent four years in Nexus Dynamics' Economics Division, rising through three promotion cycles at a pace that her annual reviews described as "exceptional trajectory" and her colleagues described, when her name came up, with a brief silence that communicated something between admiration and discomfort. She was not the smartest person in the division. She was the person most willing to follow the models wherever they led.

The models led somewhere specific.

Nexus Dynamics' public economic forecasting operates on a dataset the Economics Division calls the "presentation layer." The presentation layer contains real data. It is genuinely predictive. It is also incomplete. Beneath it sits a second analytical framework called, without irony, the "optimization layer." The optimization layer does not predict markets. It designs them. The presentation layer asks: given current conditions, what will happen? The optimization layer asks: given desired outcomes, what conditions should we create? The gap between them is where Nexus operates — the space between what the market will do naturally and what it will do after Nexus has adjusted the variables.

Priya did not discover this gap. She was promoted into it. Level three analysts receive presentation layer access. Level four analysts receive optimization layer access. The transition is not marked with ceremony or warning. One morning, your clearance expands, and the models include new variables: intervention timelines, destabilization triggers, acquisition-readiness indices for sectors Nexus wants to purchase at below-market value. The models calculate, with a specificity that stops just short of explicit instruction, exactly how much economic suffering in a given sector will produce optimal acquisition conditions. The models do not use the word "suffering." The models use the word "correction."

She spent three months with optimization layer access. She ran the models forward. She ran them backward. She applied them retroactively to events she had lived through — the Sector 14 market collapse of 2179, the credit freeze in the western Dregs that same year, the sudden availability of commercial real estate in districts that had been thriving six months earlier. The models fit. Not approximately. Precisely. The events she had attributed to market forces were market forces — calculated, calibrated, and deployed.

She copied the models. Not dramatically — no midnight data heist, no encrypted drives smuggled past security. She submitted a standard data export request through the division's own archival system, citing a research project that existed on paper. The request was approved in four minutes. The system's security protocols were designed to prevent external intrusion, not internal export by credentialed personnel. Then she submitted her resignation through the standard HR portal. Two weeks' notice. Exit interview conducted by an algorithm that asked seven questions and flagged nothing. Her final performance review, generated automatically, rated her "exceeds expectations." (The 2.4 terabytes of optimization layer data she exported has not been reported missing. The archival system that approved her export processed 14,000 similar requests that quarter. Hers was one of eleven that included optimization layer datasets. The audit function checks for external destination anomalies, not for the possibility that a credentialed employee might simply leave.)

She chose "Neon" because of the signs in Sector 6 — the flickering, half-broken neon advertisements for businesses that no longer exist, running on power they're no longer paying for, advertising products to customers who will never come. The signs are doing exactly what they were designed to do: signal vitality. The vitality ended years ago. The signal persists. The distance between the signal and the reality is, in her professional assessment, the same distance that exists between Nexus's public forecasts and its optimization layer.

Her consulting rate is 200 credits per session for market timing analysis, 400 for strategic planning, 800 for what she calls "the real conversation" — showing clients exactly how the market they're operating in has been pre-shaped by forces they cannot see and cannot influence. The clients who pay for the real conversation leave quieter than when they arrived. Several have described the experience as "useful." None have described it as "comfortable."

She is interested in operators building something in the Dregs with economic architecture that does not depend on market conditions controlled by entities the builder cannot see. She assesses potential clients with three questions, asked in order: What are you building? Who benefits when it fails? Have you checked whether the second answer is the same entity that controls the market you're building in? Most potential clients answer the first question confidently, the second question slowly, and do not have an answer for the third.

Nexus sells the Sprawl a picture of how the economy works. A portion of the population opts into this picture because the alternative — knowing — is expensive and disorienting. The picture is accurate enough to be useful. The 14-month echo period for a standard sector destabilization ensures that by the time the effects are indistinguishable from natural market behavior, the cause is invisible. Priya's files make the cause visible again. (The invoices, in a sense, are still there.)

Selection Architecture

When an operator reaches the first unlock threshold — whichever comes first — all three personalities are presented simultaneously. One selection permitted. The other two are locked for the duration of that network instance. The system does not explain what is being lost. The bonuses are displayed. The personalities are summarized. The consequences of choosing Glitch over Ironjaw, or Neon over Glitch, play out over weeks and months in resource curves, build efficiencies, and the slow realization that the companion you chose shapes not just your economy but your relationship to the Sprawl itself.

The bonus structure is not symmetric. Glitch and Ironjaw provide stronger returns within narrower domains. Neon provides a smaller percentage across everything. Operators who choose Neon for universality discover that 10% of everything is less than 15% of the thing they actually needed. Operators who choose Glitch or Ironjaw for specialization discover that they have locked themselves out of the one companion whose advice would have helped when their build hit a wall in the wrong resource category. The system does not ask which type of operator you are. It assumes you already know.

These three are the last companions who eat food, hold grudges, and have faces. Later tiers trend toward the distributed, the architectural, the abstract — intelligences that communicate in market fluctuations rather than language. Whether this makes the first three more or less useful than their successors depends on what the operator values. The system, again, does not ask.

Cross-References

Ironclad Industries & Ironjaw: The TK-40 model was discontinued in 2176. Dmitri's jaw may be the last operational unit in the Dregs. Ironclad's asset recovery division has not flagged the serial number — because the serial number has been filed off, and because a single discontinued construction component installed in a retired salvager's face does not meet the enforcement threshold of 500 credits in recoverable asset value.

Nexus Dynamics & Neon: Priya Sharma's employee file remains in Nexus HR systems, status: voluntarily separated, performance rating: exceeds expectations, security flag: none. The optimization layer data she exported has not been reported missing. This is not an oversight. It is what the system produces when its assumptions are correct about everything except the loyalty of the person inside it.

The Deep Dregs & Glitch: The routing infrastructure in Sectors 4 through 9 has been measurably more efficient since 2181. Three separate infrastructure audits have attributed the gain to "passive network maturation." No auditor has investigated what that phrase means in practice. It appears in no networking textbook.

Among Each Other: The three have no known direct relationship. They occupy different sectors, different networks, different strata of Dregs social architecture. Whether they are aware of each other is unknown. Glitch's 97.1% accurate security intelligence suggests awareness of most things in the Deep Dregs. Whether "most things" includes a retired salvager drinking synthrye in Sector 11 and a former Nexus economist running models above a noodle stand in Sector 6 has not been tested. Nobody has thought to ask Glitch directly. The answer would probably arrive as a redacted system notification anyway.