Why we call it an organism, and what that does not mean
The word organism does real work in describing this architecture, and it is also the single easiest way to end up making claims we cannot support. Both of those are true at once, so it seems worth writing down exactly what the word is being used for and where it stops.
What the metaphor gets right
Biology has better vocabulary than software engineering for a few properties that are central here.
Closed loops. An organism does not run a process and terminate. It maintains a state against disturbance, continuously, and everything it does is in service of that. Software vocabulary defaults to pipelines and jobs, which is the wrong shape.
Homeostasis. Health as a maintained equilibrium rather than a binary. This is precisely the architecture that self-repair requires, and biology has been describing it for a century.
Structural coupling. Organisms and environments change each other over time. Autonomous operations do the same thing — an operation that acts on a market is part of that market — and software language has almost nothing for it.
Repair as ordinary. In biology, damage and repair are constant background processes. In software they are exceptional events with escalation paths. The biological framing is the more accurate one for what we are building.
What it does not mean
Not consciousness. No claim about awareness, experience, or there being something it is like to be the system. Nothing in the programme investigates this, and no result from it would bear on the question.
Not life. Self-repair and adaptation are engineering properties of control systems. Thermostats have the first, evolutionary algorithms have the second, and neither is alive.
Not moral status. The system has no interests, and nothing that happens to it is good or bad for it. Turning it off raises no ethical question about the system, though it may raise several about the people affected by what it was doing.
Not autonomy in the human sense. It has no goals of its own. It has an objective somebody gave it and a wide space of actions to pursue it in, which is a different and much more mundane thing.
Why bother saying so
Because this field has a reliable failure pattern. Researchers use biological or psychological language as shorthand, the shorthand is repeated without the caveats, and within two steps the claim being reported is one nobody made. The words that do this most efficiently are learn, understand, want, decide and alive — and organism belongs on the list.
We would rather be explicit and boring: the word describes the shape of the architecture, and the shape of the architecture is closed loops with self-repair and adaptation. There is no claim underneath it about what the system is.
The version we would defend
Demertis is a control system with a very long feedback horizon, the ability to repair and reconfigure itself, and a boundary drawn by people who remain accountable for what it does. Organism is a compression of that sentence. If the compression ever starts doing work the sentence cannot, the right response is to stop using it.
- terminology
- cybernetics
- claims
- research honesty