The name
EXTREMIS to VECTOR. Why a name is a constraint on the thinking rather than a label on the result, and how to notice when yours has become the wrong one.
Naming is usually treated as the last and least consequential decision in a project. It is neither. A name determines the vocabulary available for describing the thing, and vocabulary determines which designs occur to you — silently, without ever producing an error that could be noticed.
This document records a rename, and the general lesson is more useful than the specific history.
EXTREMIS
The project was called EXTREMIS from its conception in October 2025 until the middle of 2026. The name came, roughly, from Marvel, and was chosen when the project was an adaptive traffic system and nothing more.
It was a good name for that. It was evocative, it suggested response under duress, and it fit a system whose job was to react to conditions at the edge.
What changed underneath it
The system stopped being an adaptive traffic controller. It became a fault-tolerant protocol stack, then a real-time system with an intelligence layer inside it, then a bounded and governed structure whose central concern was the authority of the thing rather than the quality of its decisions.
The name did not move. It described the first version accurately and every subsequent version less so, and because a name does not throw errors, nothing announced the growing mismatch.
How the mismatch made itself known
Not as dissatisfaction with the name. As a pattern in explanations.
Every attempt to describe a general component began at traffic and reached outward apologetically. Explaining the termination protocol would start with intersections, even though termination has nothing to do with intersections, because traffic was the vocabulary the name had established and general statements had to be translated out of it.
That is a communication symptom of an architectural problem. Components were being designed against traffic-shaped assumptions, because those were the assumptions the available vocabulary made easy to hold. Generalising a component afterwards costs considerably more than never having specialised it.
There was also a trivial reason, which is that the name belongs thoroughly to Iron Man. On its own it would have been an annoyance rather than a migration.
VECTOR
Variable Environment Control Through Observation Response.
It is an acronym and also a description. A vector carries a magnitude and a direction, and the interesting property of an autonomous decision is never how much it did but which way it pointed and why.
What it does structurally is name no domain. A component designed under this name has to state its assumptions rather than inherit them, because the name supplies none. That is the entire benefit, and it is worth the cost of a full migration.
The general rule
A name is a constraint on the thinking, not a label on the result.
The signal that a name has become wrong is not boredom with it. It is noticing that explanations of general things keep starting from a specific case. When that pattern appears, the vocabulary has narrowed the design space, and the cost of continuing is paid in components that have to be rewritten later.
Rename early. The migration is mechanical; the accumulated specialisation is not.