The last thing you did under your own power was climb into a small craft and sit near the Artifact for six hours. Then the hatch sealed and you were wired in. That was some time ago. You have stopped counting.
The lifepod is your world now. It is not large. It is not comfortable in any way that the word usually implies. What it is, is sufficient: life support that does not depend on the ship’s systems, a medical suite that manages the interface between your nervous system and the vessel’s control architecture, and a cocoon of Artifact-fabricated material that will, if everything else fails, detach from the hull and carry you back to where you started. You do not walk the corridors. You do not look out windows — the singleship does not have windows in any meaningful sense. Everything you know about the universe outside your pod comes through the ship’s systems, filtered and interpreted by the one officer you will ever have.
Captains who dwell on the confinement do not last. The ones who survive learn to think of the lifepod not as a cell but as a cockpit — the place where decisions are made, where the ship is directed, where the captain’s will becomes the vessel’s action. The pod is small. The reach is not.
Your executive officer has no name, no face, no personality worth describing. It does not make conversation. It does not offer opinions about your choices unless those choices will get you killed, and sometimes not even then. What it has — the only thing it has — is competence so thorough that after a while you stop noticing it, the way you stop noticing gravity.
You give an order. You say “plot course to Mars Orbit” or “engage that vessel” or “buy fuel.” You do not specify throttle curves. You do not calculate intercept geometry. You do not time weapon firing cycles or manage shield power allocation. The XO does all of that — translating your intent into the continuous stream of low-level control commands that actually fly the ship, fight the ship, and keep the ship from running into things you would prefer not to run into.
The interface between you and the XO is not a conversation. It is closer to a relationship between a general and a staff — you set objectives, the XO plans and executes. When you say “navigate to the Inner Belt,” the XO checks drive charge, calculates whether the transit is feasible, warns you if it is not, and — if you confirm — manages the entire engagement sequence: engine alignment, charge verification, dampener status check, drive activation, and the transit itself. When you say “engage that target,” the XO raises shields, arms the weapon system, plots an approach, and begins the firing cycle. You chose the fight. The XO fights it.
This is not autopilot. The XO does not decide where to go, whom to fight, what to buy, or when to run. Those are captain’s decisions. The XO executes them — skillfully, quickly, and without the kind of hesitation that gets ships destroyed. The distinction matters. A captain who confuses delegation with abdication will find that the XO does exactly what it is told, which is not the same as doing what the captain needed.
The XO also keeps you alive in ways you may not notice. It will not execute a navigation order that ends in a collision with a planet. It will warn you when fuel is critically low, when life support is degrading, when a system is damaged enough to affect performance. It does not override your decisions — you are the captain — but it makes certain you are making them with the relevant information. What you do with that information is your problem.
Captains develop different relationships with their XO. Some treat it as a tool. Some treat it as a partner. Some talk to it, though it never responds in kind. The XO does not care how you think of it. It cares — to the extent that caring applies — that you are alive at the end of the day and that the ship is pointed in the direction you asked for.
You cannot see outside. What you have instead is a continuously updated representation of everything the ship’s sensors can detect, filtered through the XO into something a human mind can process without drowning in it.
The bridge display — projected directly into the lifepod’s interface — shows you the world as the ship understands it. Your current zone. The other vessels and objects the sensors can resolve. Your own ship’s status: hull integrity, shield state, resource levels, system condition, crewdroid positions and activity. Stations within range. Wrecks. Planets and orbital bodies. The information is not raw telemetry — it is the XO’s interpretation, organized by relevance, annotated where the XO judges annotation useful.
What the display does not show you is everything the ship cannot see. Sensors have range limits, resolution limits, and the particular limitation that comes from the laws of physics not caring about your need to know what is behind that asteroid. The XO presents what it has. It does not fabricate what it does not. A blank area on the display is not safe space — it is unknown space, which is a different thing entirely and a distinction that experienced captains learn to respect.
The display updates continuously. In practice, this means the information is as current as the server’s last tick and the transport layer’s latency allow. For a captain making strategic decisions — where to go, whom to engage, when to trade — this is more than sufficient. For the XO managing fire control and evasive maneuvers, the margins are tighter, but that is the XO’s problem, not yours.
You tell the XO where you want to be. The XO figures out how to get you there.
Within a zone, navigation is straightforward. The XO manages engine throttle, heading, and the inertial dampener. You set a destination — a station, a wreck, a patrol point — and the ship moves. Fuel is consumed. Time passes. The XO adjusts course as conditions change. You can modify throttle preferences if you want to conserve fuel at the cost of speed, but most captains leave that to the XO unless circumstances demand otherwise.
Between zones, navigation means the Artifact Drive. The sequence is not instantaneous and not trivial. The drive requires a charge buildup — a period during which the ship’s power systems feed energy into a mechanism that no human engineer has been able to explain. When the charge reaches the threshold, the XO reports readiness. You give the order. The drive engages.
What happens during transit is difficult to describe and varies by captain. The instruments show displacement occurring over hours rather than months. The lifepod’s medical systems manage whatever the drive does to biology. The inertial dampener — the other Artifact system that nobody fully understands — is what makes this survivable. A compromised dampener before a drive transit produces outcomes that range from unpleasant to fatal, which is why the XO checks dampener status before every engagement and warns you if the numbers are not where they should be.
A captain who orders a drive transit with a damaged dampener is exercising a right the XO will not deny. The XO will inform you of the risk. It will not stop you. This is by design. Captains occasionally need to run even when running might kill them. The XO respects that judgment. The dice do not.
Combat begins with a decision and ends with mathematics.
You choose to engage. You identify a target — another vessel in your zone — and tell the XO to arm weapons and raise shields. From that point, the XO manages the engagement: weapon cycling, targeting solutions, shield allocation, evasive patterns. Your weapon fires on a cycle determined by its design and condition. Each shot is resolved by the server — your tactical skill modifies the probability of a hit, but the outcome is dice-determined and authoritative. You do not roll. You do not aim. You decided to fight; the universe decides what happens next.
Shields absorb incoming fire until they are depleted. After that, hull takes the damage directly. Hull damage accumulates. Zero hull means your ship is a wreck and you are on your way back to the Artifact in the lifepod, poorer in time and cargo and reputation but alive.
The captain’s role in combat is strategic, not tactical. You choose targets. You decide when to engage and when to disengage. You weigh the value of continuing a fight against the cost of losing the ship. You direct the XO to prioritize certain threats or certain defensive postures. The XO executes. The difference between a good captain and a dead captain is not reflexes — the XO has faster reflexes than any human — but judgment: knowing when to fight, when to run, and when to stop a fight that has already been won by the other side.
Disengaging is an option. It is not always a good option. A ship running from a fight has its back to the enemy and its engines pointed at the exit. Whether you make it depends on relative speed, damage state, and luck. The XO will execute the withdrawal as competently as it executes everything else. The XO cannot make a slow, damaged ship move faster than physics allows.
You have two of them. They came with the ship. They maintain it, they defend it, and they do the physical work that you, sealed in the lifepod, cannot.
Managing crewdroids from the lifepod is not micromanagement. The droids are autonomous enough to handle routine operations without instruction — they will position themselves where work needs doing, respond to system alerts, and maintain the ship in a state that approximates good order. What they need from you are directives: send a droid to engineering for damage control, stage a droid at the airlock for EVA, pull a droid off maintenance for a salvage operation. The XO coordinates the details.
When you order a crewdroid to move, you are issuing a captain’s override of the droid’s autonomous behavior. The droid will go where you send it. This is useful when the droid’s priorities and yours diverge — when you need a droid in engineering now, not after it finishes whatever it decided was more important. The override is a tool. Like all tools, it works best when used with awareness of why the droid was doing what it was doing before you intervened.
EVA operations — salvage, cargo recovery from wrecks, hull
repairs — are crewdroid operations directed by the captain. You
identify the target. You assign the droid. The XO manages the EVA
parameters and the droid executes the work. Your evaTraining
stat influences the efficiency and outcomes of these operations, which
makes sense if you think of it not as the captain going outside but as
the captain’s ability to direct complex remote operations from a
sealed pod. Some captains are better at this than others. The dice
reflect the difference.
Crewdroids have activity states: they are working, idle, recharging, or incapacitated. A droid that is recharging is unavailable. A droid that is incapacitated is unavailable for longer. A captain with both droids down is a captain whose ship is not being maintained, whose EVA operations are on hold, and whose ability to handle emergencies has been meaningfully reduced. Keeping droids operational is not glamorous work. It is essential work.
Credits (CR) belong to you, not to your ship. This is one of the genuinely good pieces of news in a career that contains a limited supply of it. When your ship is destroyed and the lifepod carries you back to the Artifact, your wallet makes the trip. The Artifact replaces the vessel. Your financial situation is your own problem, but at least it is the same problem you had before the hull gave out.
Commerce happens at stations — specifically, at stations with markets. Every zone has at least one. You dock, you access the market interface through the XO, and you conduct business: selling cargo, buying supplies, purchasing replacement crewdroids if you have lost one. The XO presents prices, available goods, and your current CR balance. You make decisions. The XO executes transactions.
Selling cargo is the primary income source for most captains. Cargo comes from extraction operations and salvage — your crewdroids pulling material from asteroids or picking through wrecks. The cargo sits in your hold until you reach a market station, where you sell it for CR at whatever the current rate happens to be. Station prices are not uniform. A captain who pays attention to which stations are paying what for which materials has an edge over one who sells wherever they happen to be.
Buying supplies — fuel, power cells, life support consumables, spare parts — is the primary expense. The XO can advise when supplies are running low, and a prudent captain keeps reserves above the minimum. Running out of fuel in empty space is not an abstract concern. It is a specific and unpleasant situation that the XO will politely inform you about and then wait for you to solve, because it is not the XO’s job to have anticipated your poor resource management.
The XO handles the mechanics of transactions — submitting buy and sell orders, verifying you have sufficient CR, confirming that the station actually has what you are trying to purchase. What the XO does not do is make economic decisions for you. It will not sell your cargo without being told to. It will not buy supplies on its own initiative. The captain directs; the XO executes. This extends to commerce as much as to navigation and combat.
The solar system is not silent. Ships talk to each other — not in the way people in a room talk, but in the way ships have always talked: in signals, structured and brief, carrying meaning without requiring eloquence.
The communication system uses a controlled vocabulary. You can hail another vessel. You can issue a threat. You can request trade, declare distress, offer surrender, or broadcast a warning. What you cannot do is send free-form text, rambling manifestos, or personal correspondence through the ship’s comms system. The vocabulary exists for a reason: it keeps communication machine-readable, which means an NPC captain’s ship and a human captain’s ship are on equal footing. Both understand the same signals. Both respond through the same protocol.
The XO handles signal transmission and reception. You decide what to say; the XO formats and sends it. Incoming signals appear on the bridge display, identified by source vessel and signal type. How you respond — or whether you respond — is your decision. A distress signal might be genuine. It might also be a trap set by someone who knows that some captains cannot resist an opportunity to be heroic. The XO does not advise on the sincerity of incoming communications. That judgment is yours.
Your ship will, at some point, be destroyed. This is not pessimism. It is statistics. The solar system is full of things that damage ships and captains who are not as cautious as they believe themselves to be. The question is not whether you will lose a ship, but when, and what it will cost you beyond the ship itself.
When hull integrity reaches zero, the singleship becomes a wreck. The lifepod detaches — the mechanism is not understood, the transit is not instantaneous, but you arrive alive at the Artifact. You dock. The Artifact issues a replacement singleship, lifepod integrated, two fresh crewdroids aboard. The process takes time. The time is not insignificant.
What you keep: your Credits, your identity, your skills, your reputation (for better or worse), and whatever hard-won knowledge about the solar system you have accumulated. What you lose: your ship (now a wreck someone else will probably salvage), your crewdroids (gone with the vessel), your cargo (sitting in the wreck for anyone with a droid and a cutting torch), and your position (you are back at the Artifact, which is in Earth Orbit, regardless of where you were when you lost).
Experienced captains treat ship loss as a setback, not a catastrophe. The Artifact replaces the vessel. The captain replaces everything else through time and work. Inexperienced captains treat ship loss as the end of something. They are wrong, but the lesson is expensive.
A typical cycle — to the extent that anything in interplanetary space is typical — looks something like this. You review the bridge display. You assess your ship’s condition: resources, crewdroid status, system health. You check what is in your zone — stations, wrecks, other vessels, threats and opportunities. You make decisions. Navigate somewhere. Trade something. Salvage something. Avoid something. Engage something. The XO executes. The server resolves. The universe moves forward.
The pace is not frantic. Space is large and most of it is empty. The moments of intensity — combat, a risky drive transit, an EVA operation on a wreck that turns out to contain less than the sensors promised — are punctuated by stretches where the captain’s primary job is planning: deciding what to do next based on what the display shows and what the captain knows about the solar system’s economics, politics, and geography.
This is the captain’s interface. Not a cockpit with a stick and throttle. Not a bridge with officers and stations. A sealed pod, a competent XO, two droids, and a solar system that does not care about your plans but will occasionally, grudgingly, cooperate with them.