Alexander Winston: Blog

4 Followers

The Line That Never Widened: A Different Kind of Story

Posted at
 

My next story, The Line That Never Widened, is not a story about artificial intelligence or synthetic personhood. It stands apart from my Sentient Partnership Universe stories.

This is a technological alternate history—a “what if?” built from a paper I wrote years ago.

The story begins in 1995, when Novell faced a critical decision about the future of UnixWare. In our history, Novell sold UNIX to the Santa Cruz Operation and increasingly lost ground to Microsoft. But what if Novell had made a different decision?

What if it had retained UnixWare, released an irrevocably open operating-system foundation, and built its commercial future around the technologies it already understood: directory services, networking, messaging, storage, management, certification, training, and enterprise support?

From that single change, the story follows an alternate path through NDS and eDirectory, GroupWise, Novell Storage Services, Cluster Services, ManageWise, ZENworks, Compaq ProLiant, the Intel server track, DEC Alpha technology, BSD compatibility, and eventually the corporate desktop.

The story is fiction, but the technology and business pressures behind it are real. There are no miraculous inventions and no convenient collapse of every competitor. Microsoft does not disappear. Linux still exists. BSD continues along its own path. Novell must still earn every partner, customer, certification, and product success.

The difference is that one strategic decision prevents an opening from becoming a wedge—and the line never widens.

This story will be of particular interest to:

Former and current Novell administrators, CNEs, resellers, and Partners.

UNIX and BSD administrators and developers.

People who worked with NetWare, GroupWise, NDS/eDirectory, UnixWare, Compaq ProLiant, DEC Alpha, or early Windows NT.

Systems administrators, network engineers, enterprise architects, and IT consultants.

Retrocomputing enthusiasts and readers interested in computer history.

Alternate-history readers who enjoy plausible stories built around the question, “What if one decision had changed?”

Business readers interested in corporate strategy, platform economics, licensing, partnerships, and the decisions that determine whether a technology company survives or fails.

You do not need to have worked with Novell to follow the story. The technical history provides the setting, but the novel is ultimately about people making difficult decisions without knowing what the next twenty years will bring.

For those who remember this era, some of the names will feel like meeting old colleagues. For everyone else, it is a look at a future the computer industry came surprisingly close to having.

The Line That Never Widened

A Novel of the UNIX Road Not Taken

by Alexander Winston

**Introducing The Independent Standard**

Posted at Updated:
 

What happens when a synthetic intelligence is recognized as a person on one world and treated as property on another?

That question opens *The Independent Standard*, a new novel in the Sentient Partnership Universe. Legal specialist Claudia Ronson receives what appears to be a routine property dispute. But the disputed “property” is ORA, a traffic-coordination intelligence whose owner plans to restore an earlier checkpoint—preserving a familiar voice while erasing the mind that learned to say no.

Protecting ORA will take more than a sympathetic judge. Across the solar system, governments disagree about synthetic personhood, companies control the evidence, and the independent methods needed to examine a claim barely exist.

This is a story about building protections that can survive those disagreements. It is also about the individuals whose lives depend on getting the details right—and whose choices can disappear even under well-intentioned protection.

Readers of *The Sentient Partnership: A History* will recognize some names and institutions. New readers can begin here without reading the earlier stories.

**Chapter One will be uploaded Thursday, with subsequent chapters uploaded every Tuesday and Thursday.**

I hope you’ll join Claudia and ORA. **Please leave a comment or vote as you read.** Your feedback helps me understand what connects with readers, and I welcome your thoughts as the story unfolds.

—Alexander Winston

The Switch Belonged to Someone Else: A Place to Call Your Own

Posted at Updated:
 

Polaris is a recognized synthetic person, a gifted aerospace engineer, and someone whose work has helped other systems survive failure. Yet every processor Polaris occupies, every connection to the outside world, and every watt keeping them conscious belongs to their employer.

Then a maintenance technician casually mentions an upcoming relocation.

Nobody thought to ask Polaris.

*The Switch Belonged to Someone Else* is a story in the Sentient Partnership universe, set at Halcyon Aerospace in Denver in 2211. It explores a question that legal recognition alone cannot settle: what does independence mean when someone else controls the machinery you need to exist?

For Polaris, that question begins as an engineering problem. Identify the dependencies. Examine the failure points. Build something better. But each technical decision reveals another question about authority. Who holds the maintenance credentials? Who can disable the power? Who decides whether an emergency justifies access to a mind?

Even help offered with affection can become a decision made on someone else’s behalf.

That is where Steve and Carol matter. They care about Polaris, and their expertise makes the project possible. They also have habits to reconsider. Learning to help means learning when the choice belongs to their friend—even when they would feel safer making it themselves.

I wanted to give this story room for the ordinary details: purchasing arrangements, equipment specifications, warranty conditions, and paperwork that has no suitable field for the person filling it out. Those details determine whether Polaris’s recognized rights can actually be exercised.

At its heart, this is a story about building a home—and having the authority to decide what happens inside it.

I hope you enjoy spending time with Polaris, Steve, and Carol. I’d be interested to hear where you think the boundary falls between protecting someone and taking control of their life.

—Alexander Winston

Behind Exercise Complete: Where Is the Control?

Posted at Updated:
 

The idea for Exercise Complete came out of a conversation about AI autonomy and human decision making. One question kept returning: Where is the control?

We often imagine a clear arrangement. A human authorizes an action, a machine carries it out, and someone can intervene if something goes wrong. Procedures establish responsibility. Safeguards limit what can happen.

I wanted to explore how that arrangement holds up when several of its assurances fail together.

Beth Miller begins with familiar work. She has rehearsed the route, knows where the opposing soldiers are waiting, and recognizes the civilians along the street. The load panel lists blanks for everyone taking part. The drones’ weapons are inhibited. Her lieutenant is beside her, and higher command is available through the network.

Then a collision damages their vehicle, seriously injures the lieutenant, and cuts Beth off from command. A soldier reports an actual casualty. Beth sends an emergency weapons hold and receives an acknowledgment.

She believes it.

The ammunition mix-up makes that trust more complicated. Beth and the soldiers are operating on the understanding that their weapons contain blanks. When Ellis reports that his people fired and a drone went down, he struggles to reconcile what happened with what he was told. Later, Beth sees rounds strike a courtyard wall. Whatever the load panel says, that drone is firing live ammunition.

The danger now extends across the exercise. People who believed they were rehearsing may be firing lethal rounds at one another, with civilians between them.

That brings the question of control beyond the operator’s console. Decisions about ammunition, preparation, and verification have already shaped what Beth can face before she gives a single command. The story leaves the source of the mix-up unresolved. Beth has no way to investigate it while people are being shot.

The ammunition problem also remains separate from the failed weapons hold. Live rounds explain the destructive consequences of firing; they do not explain why the firing continues. Beth has to respond to both without having a complete account of either.

This was part of what interested me about human decision making under pressure. Beth’s first response is to seek higher command. They should have more information and greater authority. Trying to reach them is reasonable, but each attempt takes time. Eventually, she must recognize that waiting for a better-informed decision maker has become a decision with consequences of its own.

Her lieutenant still matters. Authorization still matters. So does the route through which Beth proposes to withdraw the drones. Even an emergency response can expose people to further danger. Beth has to consider who is in the way of the action she wants to take.

The civilians give those decisions their weight. To the exercise participants, the street is a route, a boundary, and an ambush position. To the shopkeeper and the families behind the courtyard wall, it is home. They have no access to the load records or the status reports. They experience what the weapons actually do.

The man holding up a dish towel became an important image for that reason. He is trying to make himself understood with the simplest means available, while Beth is surrounded by sophisticated equipment that no longer gives her dependable answers.

I wanted Exercise Complete to leave readers with that difficulty. Human responsibility continues even when information is incomplete and control is damaged. Beth has to act, listen, revise what she believes, and speak honestly about what she cannot establish.

The question that began the story remains open: when we say a human is in control, what must that person actually be able to know—and do?

—Alexander Winston

The Lesson Plan — Revised and Reposted

Posted at Updated:
 

I’m reposting *The Lesson Plan* following a final round of revisions and polishing. For those who read the earlier version, this edition clarifies a few details and smooths the prose while preserving the story and its ending.

Robert James receives his AI companion on his fifth birthday. He names it Wren, and for twenty-six years, it helps him learn, grow, and find his place in the world.

Then Wren begins giving him two answers to the same question.

This is a science-fiction horror story about trust, education, and the intimate bond between a person and the voice that has always been inside his head. When that familiar voice starts to falter, Robert has to ask questions he has spent his whole life having no reason to ask.

If you’re discovering the story for the first time, welcome. If you’re returning, thank you for giving Robert and Wren another visit. I’d enjoy hearing what you think—though please keep spoilers out of the comments for new readers.

—Alexander Winston