Nibu Attached Shuttle Story

Status: playable-story concept. Nibu canonically served as an attached shuttle during her centuries among crews, owners, salvagers, and recovery contractors before the Rupture. This crew, its missions, captain, deaths, and ending are developmental.

This episode takes place before the Rupture within Nibu’s long custody history. It is not her first crew, first violence, final crew, or direct route to the junkyard. By the Rupture, her degraded hull reaches that junkyard after centuries of transfers in which most people who lived or worked aboard her died. This is one possible scar among many.

The frame is hard science fiction: no Aether, reset smear, or post-Rupture continuity effects. Pressure comes from embodied ship cognition, access control, orbital logistics, heat, debt, port practice, recovery claims, and a crew whose survival increasingly depends on a person their contracts still know how to describe as equipment.

Player Role

The player is the transport’s junior systems and maintenance operator. They are competent enough to work across power, coolant, diagnostics, docking, and local control networks, but too junior to set policy. That position makes them useful to everyone. The captain asks them to prepare bounded access for Nibu. The pilot wants proof that helm authority remains human. The security specialist wants isolation paths. Nibu needs hands inside machinery she cannot repair from her own hull.

The player does not command Nibu. They negotiate which telemetry she may read, which systems may accept recommendations, which commands require confirmation, and which emergency routes open when delay would kill somebody. Each permission changes both capability and authority.

Playable Loop

The story cycles through six stages:

  1. Contract: the crew accepts a job whose route, cargo, claimant pressure, or legal exposure makes Nibu valuable and dangerous.
  2. Prepare access: the player inspects hardware, allocates power and cooling, chooses diagnostic bridges, records permissions, and hears incompatible requests from Nibu and the crew.
  3. Transit: ordinary ship life reveals the effects of those choices through heat, privacy, workload, movement, and who can reach which compartment.
  4. Crisis: an inspection, pursuit, equipment failure, boarding attempt, or medical deadline forces someone to act before authority is settled.
  5. Aftermath: damage, logs, testimony, debt, and private conversations establish who benefited, who paid, and whether an emergency permission closes again.
  6. Escalation: better contracts and more capable opponents increase both dependency on Nibu and pressure to control her.

Four author-facing narrative lenses can organize scenes through logs and world state. They are not UI meters:

  • Material margin: heat, damage, parts, fuel, money, and time.
  • Nibu access: the specific transport systems able to receive her observations or commands.
  • Authority record: which permissions, refusals, emergency actions, and reviews were recorded or concealed.
  • Claimant pressure: how visible and expensive the attached shuttle has become to ports, insurers, creditors, and recovery interests.

The Material Bargain

Nibu docks as an attached shuttle: body beside body, joined through a collar, power and data links, service access, and whatever command bridges the player enables. She needs mobility, repair labor, supplies, recognized credentials, and ports willing to admit the main transport. The crew gains an exceptional navigator, analyst, and intrusion partner capable of thinking through machinery built to expose a usable interface.

Her reach is access-dependent. She can exploit a compromised controller, captured credential, exposed diagnostic port, badly isolated docking network, or an implant this crew allowed to bridge a service bus. She cannot possess any nearby machine. Isolation, unfamiliar hardware, damage, latency, and refusal can stop her.

Nibu may request access, refuse a task, or act without authorization when she believes delay will kill someone. An unauthorized defense can save the crew while violating a neutral station or opening private records. The player records what happened: permissions, broken seals, changed firmware, thermal expenditure, and whether Nibu recommended or commanded the action.

Not every desire is utilitarian. Nibu asks the player to preserve a damaged exterior sensor cluster that watches reflected light move across the transport’s radiator field. It has little operational value and consumes repair time. She does not explain why she wants it. Honoring the request costs margin while establishing that her body contains preferences not reducible to mission performance.

Crew Functions

Five senior crew members place different claims on the player’s work:

  • The captain recognizes Nibu as a participant while limiting access to private, medical, life-support, and weapon systems. Their authority keeps those limits negotiable.
  • The pilot experiences Nibu’s calculation as rescue and displacement. They want helm boundaries recorded clearly and resent every emergency in which her advice becomes the maneuver everyone remembers.
  • The broker and cargo chief understand that Nibu has moved the crew into contracts above its class. They propose profitable jobs that depend on access nobody formally granted.
  • The security specialist respects Nibu’s capability enough to demand physical safing, independent logs, and a survivable way to refuse her. Their precautions can protect the crew or prepare a seizure using the same hardware.
  • The caretaker and medic tracks fear, injury, isolation, and costs hidden by successful missions. They notice when private compromises become household rules nobody consented to adopt.

The player occupies the missing mechanical function. Everyone can request a boundary; the player sees whether the ship actually has one.

The Captain’s Temporary Constitution

The captain is a living treaty among incompatible claims. Under their order, Nibu is not cargo; hull title does not settle personhood; emergency access expires or receives explicit review; nobody wipes her records, transfers her hull, disables her refusal, or leases her command surfaces; and Nibu does not receive unrestricted authority merely because she saved the ship.

The captain absorbs disputes instead of building procedures able to survive them. The arrangement fails when they disappear.

Four Interior Authority Spaces

The ship makes authority physical.

Zero-g service spaces are where the player and Nibu collaborate most directly. Tools, bodies, cables, and diagnostic paths move hand to hand. Opening a panel can be repair, intimacy, inspection, or trespass.

The rotating domestic section contains meals, bunks, hygiene, arguments, and boredom. Nibu is present through speakers and displays but physically outside the ring. Camera coverage, quiet corners, and who chooses to speak near a terminal become household politics.

Acceleration couches and burn stations expose command authority. During a hard burn, bodies are pinned and dependent on thrust decisions, restraints, injectors, coolant, and prior trust. Nobody can improvise a constitutional debate at several gravities.

The docking collar is both access route and restraint. Crossing it means entering Nibu’s body. Locking or severing it may be safety, confinement, or injury depending on authority and circumstance.

These spaces retain evidence. A replaced breaker, scorched coupler, handwritten isolation procedure, taped camera, or preserved sensor cluster can return as proof of what the crew practiced.

Representative Missions

One mission sends the transport through an inspection corridor with urgent medical cargo. The player can give Nibu a narrow route into berth diagnostics. She combines a scheduled heat dump with a deployed decoy to create a plausible classification error. After escape, the player must either extract and transmit the diagnostic log that clears a blamed port technician, or physically destroy its local copy before inspectors trace Nibu’s access.

Another mission begins with a credible recovery claim against the attached shuttle. Its boarding team treats Nibu’s hull as an asset to be safed and transferred. The player can isolate transport controls, open selected systems to Nibu, or preserve a manual withdrawal path. Whether her defense stops when the team retreats becomes the disputed fact every later account tries to edit.

Collapse Envelope

The ending removes the captain from command. The cause varies; the structural result is fixed. The crew loses the person who translated every conflict into temporary settlement.

The final break begins with a concealed restriction or claimant contact. Nibu detects preparation before the crew admits its purpose. Compartments isolate, people act preemptively, and safeguards become weapons.

The attached-shuttle partnership ends violently and Nibu survives. Survivors may disperse or transfer her into another disputed custody link. The episode does not send her directly to the junkyard.

Authored branches consume evidence, not numerical morality thresholds:

Outcome questionDeciding evidence
Fixed: captain absent; partnership broken; Nibu survivesStory structure and Nibu’s later chronology
Who initiated the irreversible actAccess and authority record; player-opened or isolated paths
Who survives or escapesMaterial condition, open routes, and player repairs or safing actions
Whether an outside account is crediblePreserved, transmitted, altered, or destroyed logs
Who controls the next transferClaimant exposure, surviving credentials, hull condition, and custody records

Nibu carries the result forward alongside other crews, other bargains, and other deaths.

Finished fiction owns its depicted local sequence; Nibu owns how, or whether, that sequence enters her shared biography.