Science Fiction

Autonomous: What does "freedom" mean?

autonomous.jpg

Autonomous, written by Annalee Newitz and published by Tor books in 2017, is a cyberpunk novel without all the high-saturation bells and whistles. This book gets to the heart of what cyberpunk is actually about, but wrapped in a (usually) more subtle package. This is a book that asks us what it means to be free when anything and anybody can be owned.

This is a future in which androids and robots and AI are ever present and fulfill as many roles in society as their human counterparts. But because androids are “property,” despite cognizance, the argument was ultimately made that, well, if we could own androids for “indentured service,” then why can’t they do the same thing with people? And it worked, because I guess humans are just destined to suck forever. (Why couldn’t I have just been born a jellyfish? Nobody asked me.)

There were a lot of things that I really liked about this book, and then there were some things that I still have major reservations about, even while I try to step back and think about what Newitz ultimately said, rather than what I think she should have said. Because the way that I’m approaching the one particular element in mind (I’ll get there, hold your horses) is definitely not the only way to approach it. So we’re going to work on that in a little bit.

In particular, I liked the prose. I thought that it read well; its details were compelling and its descriptions vibrant. There is a lot going on in every single setting we encounter in this book, a lot wrapped up in every social interaction between both bots and humans. I think its ideas were solid, and I think it did cyberpunk really, really well. It’s understated in a lot of ways and extravagant in a lot of others, the balance of which felt good at least most of the time. And while I will say the plot wraps up nicely, I don’t think the book’s ideas do. I actually found the conclusion to be… somewhat lacking, really. Anti-climactic, in a way. It felt rushed, perhaps.

Let’s talk setup and plot

Autonomous is a dual-narrative novel told from a rotation of perspectives. Judith “Jack” Chen is an anti-patent scientist turned drug pirate. To contextualize, pretty much every major disease has a cure at this point, as well as the bulk of the more minor ones. Medications and drugs are patented, which means that hospitals and pharmacists can “print” the meds, but for the cost of the patent. For each pill fabricated. Which means that unless you’re wicked rich, you will most likely have to sell yourself into slavery—oh, excuse me, indenture—in order to pay for them.

And once you’re indentured, good luck ever getting out of it again. Because your contract can be bought and sold at any time, and then the terms entirely changed. People with only a year or two left on a contract will easily find themselves traded off to somebody else and now facing another 7 year term. You see what’s building here? Yeah. So the only way to escape this is to be lucky enough to own a “franchise” by the time you come of age. This isn’t closely examined, more mentioned in passing, because the book isn’t about persons born free; it’s about beings fighting for freedom—even those persons who were never subjected to indenture find themselves in a bloody battle against capitalism and big pharma. And the vast majority of androids, despite being promised eventual autonomy, never see it, contracts passed along and changed as necessary for the new owner’s satisfaction.

There are points throughout this book that are designed to make you uncomfortable, and I’m here to tell you that they accomplish the task.

This book is set a little more than 20 years into our future, and every day that passes only makes this whole thing feel more and more plausible, but such is the nature of cyberpunk.

Okay. Jack Chen. Anti-patent scientist turned drug pirate. She replicates life saving medications for poor people without appropriate access. She also fabricates “designer drugs” to pay the bills, thereby enabling her to manage the whole Robin Hood thing. Enter the A plot:

Jack has reverse engineered a new designer drug called Zacuity, created by one of the biggest and most powerful pharma companies in the world, which turns out to be addictive. And so because her reverse-engineered replica is molecularly identical, Jack sets off a sudden crisis, as people take this “Here’s Your Addiction! Enjoy!” drug to enhance their work performance—but then can’t stop doing that thing. It doesn’t end well for any of them.

Presenting the B Plot: Eliasz is a… hmm… think about him like if you crossed a mega-corp's security guard with a fed’s permission to do anything they want, and a cop’s belligerence, throw in some blatant homophobia, and you’ve basically got Eliasz. His robotic partner, Paladin, joins him on this mission to chase down Jack and, preferably, kill her on the spot. But, of course, along the way, the pair find themselves experiencing a… unique “bond.” Some of you may have guessed from the scare-quotes that this is where my mixed feelings lie for this book.

I’m not really going to get into Jack’s particular plotline too much because it generally worked pretty well and she was doing the best she could. There are points throughout this book that are designed to make you uncomfortable, and I’m here to tell you that they accomplish the task. But the discomfort reached new heights between Eliasz and Paladin.

Programming, free will, autonomy

Androids created into servitude (the vast majority of them), are coded to want to please their acting “master.” Which is to say that they are programmed from initial build to prioritize the wants, expectations, needs, etc, of another being before their own—and that the robot/android (none of the words ever feel right in this context, btw, because of the inherent erasure of Personhood, which is at the heart of this whole thing) will do things that it knows will make its current owner/master pleased with it.

Starting out pretty dicey. But it gets worse, because of course it does.

Not only are androids programmed to want to please their master first in whatever context that happens to be, they are also locked out of sections of their memories, not to mention any number of other feature or data locks. Alongside that, because they are a literal possession, they have no semblance of privacy, as their entire memories can be downloaded and wiped at any time, and for any reason. There are supposed to be protections put in place for some of these things, but humans possess a unique knack for cruelty, so don’t count on much.

Noooooooowwwwwwww, with all that under our belts, we have some new problems. When we are introduced to Paladin, we receive masc pronouns but, obviously, no other gender markers of any form. Because Paladin is a robot and doesn’t have a gender. And this genderlessness and human habit to anthropomorphize bots comes up again and again and again throughout the book, but it never comes up anywhere productive or useful. But good ol’ “I’m not a fag” Eliasz determines he has feelings for this military-grade buff-ass robot, so therefore the brain in Paladin’s carapace must have been a woman’s.

Many androids, particularly those intended to interact with humans, are fitted with a human brain in their abdomen, which functions exclusively to process and contextualize human body language and facial expressions, which are anything but logical or consistent. The brain obviously belonged to a human at some point, but we don’t talk about how the brains go from skulls to android guts. At Eliasz’s weird, emotional behest, Paladin does the work to discover that his was once in a woman’s skull, which is all the proof Eliasz needs that having feelings for / being attracted to Paladin is totes above board. “I knew I wasn’t a fag.” (<—not quite a word-for-word but close enough.) And when Eliasz asks, Paladin agrees that she’d like to take femme pronouns instead now. It made him happier, after all.

Okay. So now we’re here, at a human/android romantic relationship. Sorta. And Eliasz wants Paladin to… experience… sexual pleasure. Which… you know, isn’t a thing for the ol’ robot. So as a workaround, Paladin downloads a virus off the internet to crash her entire system. She concludes that this peculiar sensation is enjoyable, and she and Eliasz code it as an orgasm. Which is…

I told you at the start, I have problems here, people.

Look, as I said at the top: The book is well written. The imagery is fantastic and it is the exact amount of anti-capitalist that cyberpunk should be (looking at you, failure of a decade-awaited video game). It is rooted in the communal drive for compassion and aid and collaboration, for unilateral betterment of society instead of whatever makes money fastest. It is pitted against corporate greed and academic weakness for political sway. Even Eliasz, government-funded terrorist that he is (it takes very little effort to come to that descriptor, you’ll find), comes to his job from a place of compassion and righteousness. He moved from city police to international agent without limits to save trafficked children that he wasn’t able to help before. And like, cool, good for you, but I don’t see how murdering your way across the globe to catch one person is closing that gap for you.

So I guess it’s just… if we’re engaging with the notion that androids are also people deserving of freedom and right to life, which we’re doing, then Paladin’s relationship with Eliasz is questionable at best. And while I’m saying this, I have a voice calmly asking me to slow down. Because when Paladin ultimately achieves autonomy and has the space to really examine these things, she determines that their presence even after the autonomy key implies they are hers, not programming. And when her autonomy is made permanent, she chooses to stay with Eliasz and they’re happy together. And I want to be happy for them, but I just… can’t quite get myself there. Which leaves me in the sticky position of Unsure whether asshole because I feel A instead of B, or if asshole because feeling good about B is ignoring whatever else.

But if I’ve gotta pick a stance, I’m settling on “Ew.” Because I really think it’s problematic! And kinda gross!

Let’s take a step back now

There is a huge cast of characters in Autonomous, the majority of whom all play key roles in the layout and propulsion of the plot. And I don’t want to act like none of them are more important or interesting than the above issues with autonomy in relationships, because I would actually argue the opposite. But you know how when you’re reading a book but one thing is really distracting you so when you’re done it’s really all you’ve held onto? That’s kind of where I’m at. Even after insisting that I did enjoy the bulk of this book, I’m just left a bit dissatisfied. I’ll give it at least 3.5 stars, if not 4, because I’m far more invested in a book that makes me really think about the ideas it’s positing than I am in a book that tells me exactly what to think about a situation. Even if I don’t agree with the conclusion of the idea put forth, I just want to see a book engage with something important. And Autonomous absolutely does that.

I haven’t really gotten into the queerness of this book, which is probably not the best in a queer-focused blog, but it’s everywhere throughout this novel. Truthfully, Eliasz is the only character who is ever posited with an actual opinion on sexuality; otherwise, everyone seems to be rather fluid. Jack canonically doesn’t care about gender in her sexual partners, and neither does anyone around her, really. It’s the genderless android-plus-human relationship that we really have to work with in Autonomous, and I am absolutely 100% not taking this into a mirror or whatever for being in a relationship with an Ace person. Because comparing asexual/agender persons to robots is pretty tasteless? And Newitz is not making that parallel on page at any point, just to make that clear. But when it’s put in front of you as above, it’s easy to make that mental leap. There is so much about this book that is queer that there really isn’t anything in the book that isn’t somehow or another. Especially surrounding the one, singular homophobic character.

Don’t read Autonomous for answers; read it for the questions. Read it for the what-ifs and the what-thens. Read it for the prescient critique of advanced capitalism. Read it to think about what personhood and agency and autonomy and ownership and property mean in a global society. Read it to think about how you treat other people and how you approach labor. But do read it.

The Punch Escrow: What makes a person?

The Punch Escrow by Tal M Klein

The Punch Escrow by Tal M Klein

The Punch Escrow is a futuristic sci-fi novel by Tal M. Klein, published in 2017. According to a 2017 Variety article, the movie options were purchased very early on, with Muppets director James Bobin listed at the helm -- but I can’t find any more recent news or updates on it.

I read the book for my office book club, and although there were certainly things I liked and found interesting about the book, my opinion came to an overall negative, and I’d probably leave the book about 2.5/5 stars, despite the book’s generally warm reception upon release.

The novel is set in 2147 and is, more or less, about teleportation and what effectually constitutes personhood, although Klein never actually gets around to answering those questions in any meaningful—or satisfying—way.

Joel Byram, the narrating protagonist, has an inconsequential job harassing AI bots. Momentarily charming, but—and maybe it’s just because I work in tech in 2020—not particularly believable given the surrounding context. 

Joel’s wife, Sylvia, is far more interesting character, but we get relatively little of her. Sylvia is a high-level employee at International Transport, and IT runs the world, you see. 

Teleportation is possible in 2147; a person steps into a vestibule in location A, and is then teleported to the vestibule of location B. The safety features ensure that, in the event of a problem, the person doesn’t actually go anywhere. The idea is that the data doesn’t transfer until receipt is confirmed or whatever. There are a lot of immediate big questions about this, in text and out, but the effort to address them feels half-assed at best.

The novel that follows includes terrorism and the accidental duplication of Joel Byram. Because someone detonated a bomb in the transport center while he was teleporting, and Sylvia assumed he was dead and duplicated him because guilt/grief. And that was the project she’d been working on: Honeycomb, or a genetic copy of everyone who’d ever teleported, because drive toward immortality and power.

Complete with mad genius scientist. 

The first few chapters were a slog. The prose was clunky and it was a disorienting info dump. Before I’m criticized for not understanding sci-fi conventions: I’ve read a lot of sci-fi. I get it. There’s a lot to establish. Klein uses footnotes—which  are very much a device I adore in fiction, but they were so thick as to make it unwieldy and disorienting—for a lot of those explanations, but the problem was just how dense they were. My issue with it is that the footnotes contained a lot of really great fiction/creative context for things, it was all the stuff that illustrates how 2147 developed. Burying them all in the front third of the book is really a disservice to the creative footnote.

Anyway. After the first few chapters, the book felt like it opened up a bit and I started to enjoy myself. It was unfortunately short lived. Look, I’m down for a sarcastic narrator (see: the protagonist of literally every urban fantasy novel), but Byram isn’t just sarcastic, he’s an asshole. (And when he has to deal with himself—literally—for the final third of the novel, he even realizes how much he sucks. So. I’m not being that mean.) 

But the crux of this novel’s problem is that it completely loses the thread about two-thirds of the way through the book. It reads very much like someone just writing a screenplay narrative concept, where the novel is essentially a proof-of-concept for a film option. And Klein only got halfway—which is to say, the movie deal. None of the Big Questions™ that come up are addressed. Teleportation isn’t harmless. Each teleportation is a deletion and reprint of the physical person, every time. So teleportation is, arguably, murder/suicide. The whole climax of the novel is a slushfest of squishy movement and politicking, ill-explained subterfuge and poorly managed relationship dynamics.

The ending was the most anticlimactic scramble of a scene I’ve read in awhile. It was the veritable definition of slapdash, and it was kind of painful to read. Character actions don’t track, based on their arcs. Motivations don’t track. The scientist gone insane rant is… I mean, tacky at best? It just felt so hollow and baseless and unfulfilling I didn’t even care about the resolution. Incoherent in a bad way. The conclusion of the outer framing story didn’t track, either, presented at the beginning as a recording of this crazy thing the reader needs to make sense of and deal with, even though… there are precisely zero consequences for anyone. Ultimately, it was very clear that Klein didn’t go into this already knowing how it ended.

The biggest philosophical question is what defines personhood. What defines a “soul”? The novel posits that teleportation results in a couple grams of “packet loss”—this is the source of religious groups’ certainty that teleportation is murder, that that loss must be the soul—but that also never comes back up, and would have been way more interesting than the mad scientist angle. I know I haven’t explained that properly, but the plot line wasn’t earned, nor was it executed with any skill whatsoever, so don’t worry about it. Also, it means that if you decide to read it, I’ve left you some surprises.

It’s also a personal pet peeve of mine when futurist sci-fi writers are exclusively obsessed with the 1980s. Being obsessed with 1980s music in 2147 is like your neighbor Chad being wicked obsessed with 1760s madrigals specifically. But bigger than that, it’s the refusal to make up or imagine culture beyond the early 2000s, i.e. culture that hasn’t happened yet. I don’t want to hear about Moron Musk being some tech hero in 2147. Make it up. Also, the conceit that Amazon Glacier will still exist in 2147 😂😂😂

Anyway. 

I really wanted to like this book. The premise is cool, but it just isn’t well executed at any point. The footnotes are aggressive, then well paced, and abruptly nonexistent. Sure, there are arguments to be made in favor of that timing, but we don’t have all day, and I can’t say everything. 

I’m also just not down with the idea that after all of this chaos and violence and all of everything, there are no consequences. None. No consequences! Haha! Can you believe it!? A sci-fi novel that terminates without consequences. 

Wild. 

I won’t say I “hate read” it, but it was very obvious when the plot fell apart, and I had to force myself to finish it. It just ceased to be a good time. 

Final verdict: strong, interesting premise, failed execution.