A Politburo That Never Got the Memo

Mikhail Sergeevich Gorbachev is still General Secretary in May 2003. Yeltsin, in this version of events, has had to content himself with winning an election — chairman of something called the Democratic Union party, a tame opposition inside a system that still runs on Nomenklatura phone lines and closed Kremlin chambers. The Communist Party has survived perestroika by negotiating with it. Barton and Capobianco built their Cold War fourteen years past the point where the actual one stopped, and they built it carefully, with committee scenes and budget fights and a general staring down a civilian leader who calls himself "such an old man, and ready for retirement" while twisting the knife. None of it happened. The thing this book is about — a Soviet Union durable enough to still be maneuvering for advantage in 2003 — dissolved before most of its readers got around to it.

That's a specific kind of wrongness, and it's worth separating from the usual way extrapolative fiction ages. This isn't a text whose warning went unheeded and curdled into prophecy. It's a text whose premise was overtaken by the news cycle. The interesting part isn't the politics it got wrong — any near-future guess can whiff — it's how much procedural detail survives the whiff intact. General Ponomarev doesn't get purged. He gets reassigned through paperwork, a phone call between old friends settling it before the ink dries: "I've decided to withdraw my objections. You can start putting through the paperwork." The mechanism of a coup, rendered as an HR action. Real Soviet power, right up to the end, worked exactly like that, and the novel's instinct for the bureaucratic texture of catastrophe outlasts its instinct for the catastrophe itself.

The other machinery that holds up is the one nobody in the book bothers to philosophize about. USAF's autonomous orbital bomb, OTV-2, gets a paragraph of interiority — "it wasn't consciousness, exactly" — and then a design philosophy stated as flatly as a spec sheet: *do what you're told; if the situation isn't covered by canned instructions, figure out what to do and do it.* That sentence is the entire architecture of a loitering munition or an autonomous targeting system, decades before those words showed up in a Pentagon procurement document. The novel doesn't dwell on it because the novel isn't worried about it — the weapon is going to behave, because 1980s hard-SF trusted its hardware. The unease that sentence now produces belongs entirely to the reader, not the text. It's the one place where the book's confidence and our distrust don't match, and the gap is more informative than agreement would have been.

Then there's Sinuhe itself — an asteroid named for the ancient Egyptian exile, a man who flees his country and spends the rest of the story trying to get back into it. Two great powers converge on a rock that has no politics, no ideology, no opinion about either flag planted near it, and they spend four hundred pages projecting strategic meaning onto its indifference: weapon, prize, pretext, bargaining chip. It gets split into fragments by men arguing about what it symbolizes. If there's an "alien" encounter in this book, it isn't a first-contact scene — it's contact with something too inert to be read as anything but a mirror, which is what the Cold War did with most of the territory it touched.

The novel ends the way hard-SF of this vintage often does, by dropping the fiction altogether for a stretch of plain advocacy about near-Earth asteroid retrieval economics — feasibility numbers, delta-v budgets, the actual argument for why you'd do this at all. Gorbachev survives; the USSR doesn't, not really, not outside these pages; Sinuhe gets its fragments scattered regardless of who was right about the rock. What's left standing is the paperwork, the procedure, the appendix. A book can lose its entire premise to history and still keep its instructions intact. What do you do with the instructions once the country that would have followed them is gone.