Who Owns the Machine? Autonomous vs All Systems Red on Ownership and Contracts

Autonomous: ownership meets biotechnology

Annalee Newitz’s Autonomous follows anti-patent drug pirate Jack and robot Paladin on Earth in 2144, where people can be owned.[1] For a reader interested in corporate AI ethics novels, this is a useful opening because the machine does not exhaust the ethical problem. My reading lens is the market around it: ask what can be sold, who benefits from access, and whose capacity to refuse becomes difficult to recognize. Those questions guide the comparison below, rather than summarize the ending.

The work addiction in Autonomous is a drug effect, not an AI optimization algorithm.[1] That distinction changes how I would discuss the book. A visible increase in output need not tell us whether the worker welcomes the activity. Treat the gap between productive behavior and meaningful choice as a question to carry into the novel, not as proof that all desire is manufactured. Equally, do not collapse the scientist’s motives, the effects of a substance, and the interests of a market into one villain. Separating those layers makes the biotechnology premise more unsettling, and gives a reading group something more precise to debate than whether technology is good or bad.

For the robot-ownership side of Autonomous, I would begin with a deliberately narrow question: does recognizing intelligence settle the issue of ownership? This comparison does not supply a complete legal code. It does, however, invite a reading that keeps economic classification separate from personal experience. Ask how a story presents a being before deciding that a sales category adequately describes it. With Paladin, keep that question open rather than announce a particular emancipation process or promise a liberating outcome. This is an interpretive approach, not a claim about Newitz’s intentions: it lets readers notice the difference between finding a character legible and discovering what institutions permit that character to do.

All Systems Red: whose safety does the contract serve?

Martha Wells’s All Systems Red opens with corporate security for scientists, where lowest-bid contracting sidelines safety.[2] Instead of making the drug market the route into the ethical problem, this opening puts a protective service in view. My suggested reading question is therefore not simply whether the protector is dangerous. Ask what the word protection promises when the arrangement is chosen on price. A useful discussion can hold two concerns together: the people depending on the service, and the being expected to provide it. Neither concern needs to erase the other for the premise to matter.

Its self-aware SecUnit has hacked its governor module and calls itself Murderbot.[2] I read this as an invitation to distinguish technical control from institutional standing, not as evidence of an invented legal reform. Being able to act differently is one question; being recognized as entitled to do so is another. Keep that distinction beside the security-contract premise while reading. A protective function describes an assignment, but need not explain everything that matters about the assigned being. For discussion, ask whether you are judging a decision by its consequences, by obedience, or by the character’s own perspective. Each test might bring a different part of the story into focus.

For All Systems Red, staying with the first installment is a strength, not a handicap. It keeps the reading exercise anchored to one opening situation rather than borrowing an answer from later adventures. I would separate three questions on a notebook page: what a client thinks has been purchased, what a security role demands, and what room the individual has to make a choice. This is a reader’s framework, not a list of contract clauses supplied by Wells. Readers who want a broader discussion of boundaries and individuality can follow our Murderbot reading essay; the present comparison remains about the first book’s security arrangement.

Two forms of control, two reasons to read

The strongest comparison is not that the two stories describe the same control mechanism. In my reading, Autonomous makes ownership a question to examine across bodies and markets, while All Systems Red gives us a security arrangement to examine from both sides of the service. Their shared usefulness lies in asking who sets the terms, not in declaring chemistry equivalent to software. Nor should the title’s ownership question turn every constraint into literal ownership: dependence, an assignment, and an owned status are distinctions worth preserving. For additional directions beyond the simple AI-villain framing, our AI science-fiction reading guide offers a broader map without replacing this specific pair.

Choose Autonomous first if your curiosity centers on biotechnology, patents, and the boundary between a person and a product. Choose All Systems Red first if you want to begin with a single security mission and ask how a service’s terms affect the being performing it. These are reading recommendations derived from their opening premises, not a ranking of their moral seriousness. After either book, try writing one sentence about who makes a decision and another about who bears its cost; the exercise helps avoid mistaking a shared concern for a shared setting. For a separate machine-civilization direction, M.K.’s Neo Babylon is an optional related read.