Why the fleet speaks Neuromancer
Every repository in the hosaka fleet carries a name lifted from one novel. sensenet, wintermute, freeside, finn, maelcum, and hosaka itself are all William Gibson's, taken from Neuromancer and the Sprawl books that followed it through the 1980s. The choice was deliberate, and the reasoning has little to do with a fondness for science fiction. A coherent invented world turns out to be a place where human intuition and a language model's training already agree, which makes it useful infrastructure for a fleet built by both.

One novel, borrowed whole
The borrowing is exact, not atmospheric. In the book, Hosaka is a maker of computers, the brand stamped on the deck a character works from. Wintermute is one of the two artificial intelligences the plot turns on. Freeside is the orbital resort spun up for people with money to burn. The Finn is a fence who deals stolen hardware out of a booth in New York. Maelcum is the Zionite who crews the tug that pulls the story to its close. Sense/Net, which the fleet spells sensenet, is the media empire that owns the entertainment feeds. Each name arrives with a role attached, and the fleet kept those roles close to Gibson's: the resort, the fence, the media house, the machine intelligence.
The habit reaches past the repositories into how work gets done. A fast, human-in-the-loop build cycle is called simstim, after the technology in the book that lets one person ride another's senses in real time. An adversarial review that tries to kill a bad design is called a flatline, after the dead hacker in the book who lives on as a read-only recording, brilliant and slightly haunted. The names are chosen so that reading them tells you something about the thing.
Subscribe free
What Gibson was borrowing from
Gibson did not draw the future from engineering. He has said he built his picture of cyberspace, a word he first used in a 1982 short story and made famous two years later, from watching teenagers hunch over arcade cabinets wanting to climb inside the screen, and that he wrote the book on a manual typewriter knowing next to nothing about computers. The vision came from culture first and hardware a distant second.
Then he went deeper into culture. In the books after Neuromancer, his cyberspace fills with the loa: the spirits served in Haitian Vodou, a religion that took shape in Haiti among enslaved West Africans, carrying Fon and Yoruba traditions across the Atlantic. Gibson gave his fractured machine intelligences those faces, so his matrix comes to be inhabited by Papa Legba at the crossroads and the rest of the pantheon. This is why the framework the whole fleet runs on is named Loa, and why the repository that manages crossings between the others takes the name of the crossroads spirit.
The care runs down to smaller things. In the book, the orbital Rastafarians of Zion play dub, the studio craft shaped in the mixing rooms of Kingston, Jamaica in the early 1970s. Gibson's future is stitched from real places and real people, each named with precision. He was himself a borrower, feeding a live culture into an invented one, and that is worth holding onto, because it is the first clue about why the naming holds up under weight.
The book wrote two readers
Here is the mechanism the fleet leans on. Neuromancer and the vocabulary around it, cyberspace and the matrix and jacking in and the walls of ICE, did two separate things over four decades.
First, the words entered the working language of the people who went on to build the industry. A generation of engineers read these books young and reached for their images when they had something new to name. Software has always thought this way out loud: we run daemons, we store things in the cloud, we open ports, we catch a virus. The linguists George Lakoff and Mark Johnson made the general case in Metaphors We Live By, that we reason about abstract things by importing concrete ones. Gibson handed the industry a set of concrete pictures for the most abstract thing it was about to build, and the industry took them.
Second, that same stretch of writing, the code and the manuals and the mailing-list arguments and the fiction itself, became the record a language model learns to write from. The book shaped the mental models of the humans, and it shaped the priors of the machine, out of one source. That shared origin is the quiet fact underneath everything here.
So a name from that world lands twice. When the fleet calls a repository after the crossroads spirit, a human reader meets a reference they half remember, and a model meets a pattern that runs dense through its training. Neither has to be walked through the shape of the thing from the ground up. Both are being met where they already stand.
A shared world is an interface
A coherent world does a plain, practical job: one name carries a web of relationships for free. If you know that Freeside is the glittering resort and that Zion is the working settlement keeping its own rules, you already know which one courts paying visitors and which one does the labor, before a document ever spells it out. The relationships ride along with the names.
Give a person that kind of world and they extend it in keeping with itself. Give an agent the same world, and the same thing happens: it adds to the system in a way that fits what is already there rather than fighting it, because the next move is legible from the names it can see. This matters more, not less, when the workers are stateless and many. An agent that begins each session with no memory of the last one still inherits the world through its vocabulary, and a world that hangs together lets delegated work hang together too. Coherence at the level of names buys coherence at the level of what gets built. That is the whole argument for spending care here. Naming is infrastructure, not decoration.
Kept honest, or it curdles
A borrowed world only earns any of this if it stays honest, and the way it fails is exoticism: treating the loa as spooky set dressing, or a genre of music as a passing mood, cutting a reference loose from the people who made it. So the discipline the fleet holds to is plain attribution. Dub is Kingston. The loa are Haiti's. The novel is 1984. Where a reference is uncertain, the rule is to name less and cite more. A name is load-bearing, so it earns the same care as the code beneath it: grounded, checkable, never invented to sound good. Gibson kept faith with the cultures he drew from by getting them right; a fleet that lives inside his names owes the same debt back down the chain.
There is a name in the fleet's first roster that belongs to no character Gibson wrote and no spirit anyone can place, and every roster since has copied it forward, spelled the same, chosen by no one.
Send-off
The one-sentence version: give people and agents a world that hangs together, keep every reference true to the people and places it came from, and the names will carry the thinking for you. If you want the machinery this sits on top of, One human, twenty repos walks through how the fleet is put together.
Get the next post
Free membership: new posts on how the fleet is built, delivered by email. Subscribe free
Read next
- How a Feature Ships When Your Engineers Are Agents
- The Company Where Every Employee Is a Repo
- The harness that ships: why completion is the moat
Post history
- 2026-07-21: crosslinker + enrich phase + OQ-1 spike + caption-uniqueness law
- 2026-07-21: BLOG SURFACE ENRICHMENT: four corners + engine images + backfill (sprint-25)
№ 8993