Skip to content

Void Drifters · Ships

Ship Builders and Design Language

Ships are expensive enough that who built yours matters for decades.

A builder is not just a manufacturer. It is an engineering standard, a parts ecosystem, a political relationship, a maintenance network, and a visual identity that anyone with experience in space will recognize at a distance. A Crown Meridian ship looks like a Crown Meridian ship. A Kharos ship looks like something that has been fixing itself for years and intends to keep doing so. A Safa ship looks like it was built to do one specific thing and considers everything else a distraction.

Five major shipwright conglomerates supply the commercial market across known space. Each dominates a different sector of demand. Each has a recognizable design language, a set of engineering priorities that produce genuine mechanical advantages, and a corresponding set of weaknesses that reflect what the builder chose to deprioritize.

When a crew chooses a ship, they are choosing a builder's assumptions about what a ship is for. Those assumptions travel with them.

Builder Benefits and the Builder Drawback System

Every ship made by a major builder carries two kinds of inherited engineering: what the builder does exceptionally well, and what the builder consistently treats as secondary.

Builder Benefits apply when a Signature system is actively used in a relevant situation aboard a hull from the same builder. A Crown Meridian damage control system gives its Boon when the engineer is patching something under fire. It does not add Boons to every Craft Trial on the ship. The benefit requires the right system, the right context, and the right hull.

Builder Drawbacks work the same way. They apply when the relevant weak system is called upon, stressed, or central to the situation. A Kharos ship's poor signature management matters when the crew tries to run cold. It does not add Banes to piloting.

One benefit applies per Trial. If multiple Signature systems could plausibly contribute to a single roll, choose the most applicable one.

Integrated Architecture is an additional reward for ships that have stayed true to one builder. A ship achieves Integrated Architecture when its hull and at least 10 of its 13 core systems come from the same builder, with no Forced or Forbidden integrations and all required firmware and service standards intact. An Integrated Architecture ship gains:

  • Remove 1 Bane Die from all native maintenance and repair Trials.
  • Once per encounter, remove 1 Bane Die from one Signature-system Trial even if the normal trigger condition is not fully met.
  • Reduce normal maintenance cost by one step when serviced at an authorized yard.

Integrated Architecture is what a ship looks like when someone cared enough to keep it consistent. It is also exactly what most crews sacrifice within the first two years.


Crown Meridian Shipworks

Federal. Durable. Documented. Built to still be there tomorrow.

Crown Meridian began as a government-chartered naval yard serving the Irnan Directorate. Over generations it expanded into commercial shipping, colonial transport, corporate security vessels, and heavy industrial hulls, always maintaining the engineering assumptions of its original federal contract: the ship must absorb damage, hold together after hits, and outlast the emergency.

A Crown Meridian ship is not glamorous. It does not have the Viridian sense that the ship is smarter than you, or the Kharos sense that the engine could push a moon. What it has is reliability. The lights work. The maintenance manuals are accurate. The access panels are labeled. The emergency systems are designed by people who expected them to be used by crew who are scared.

Crown Meridian is the builder most trusted by governments, insurers, and anyone who needs the ship to still be flying in twenty years.

Identity and Alignment

Primary alignment: Irnan Directorate. Crown Meridian ships are common wherever Directorate presence is strong and expected wherever the federal inspection system operates.

A Crown Meridian ship in a port is unremarkable in Directorate space and mildly notable outside it: the sight of that armored wedge silhouette tells experienced spacers that someone is doing legitimate business and expects the records to hold up to review.

Design Philosophy

Crown Meridian builds for longevity and damage absorption. Its engineering priorities are: keep the ship intact, keep the crew alive, keep the systems running after the first hit. Secondary priorities are comfort, subtlety, and flexibility. Crown Meridian ships are the most inspectable ships in known space, by design. The documentation is not a legal liability. It is a feature.

Builder Benefit: Signature Systems

System Group Benefit
Hull and Armor When resolving damage from collisions, critical hits, or ramming, treat Armor as 1 higher. Applies to structural consequence calculations, not normal weapon attack damage reduction.
Damage Control Add 1 Boon Die to emergency patch Trials. Craft Trials for damage control at Easy difficulty succeed automatically without a roll.
Power Distribution When Power Load exceeds Power Capacity by exactly 1, no engineer action is required until the end of the following round. The redundant routing handles minor overload automatically.
Defensive Control Remove 1 Bane Die from Trials to coordinate point defense, reinforce a screen arc, brace for an incoming salvo, or cycle screens during sustained combat.
Security The ship's internal security systems add 1 Boon Die to all Trials opposing boarder infiltration, intruder movement, and unauthorized system access.

Integrated Architecture Benefit: Once per encounter, prevent 1 System Damage caused by a cascade, overload, or collateral hit.

The Crown Meridian promise: The ship absorbs damage, holds together after hits, and keeps the crew fighting longer than comparable hulls. Engineers working on Crown Meridian systems feel confident. The ship gives them room to work.

Builder Drawback: Weak Systems

System Group Drawback
Signature Management Add 1 Bane Die to all Signature Management Trials. Entering Cold Running Mode takes 3 rounds instead of 2. Crown Meridian ships are visible and documented. That is by design.
Atmospheric Handling Add 1 Bane Die to Pilot Trials during sustained atmospheric flight, difficult atmospheric landings, and low-altitude maneuvering under adverse conditions.
Flexible Cargo Conversion Reconfiguring module loadout or converting cargo bays to other uses takes twice the normal time. The conversion Craft Trial adds 1 Bane Die. Crown Meridian ships assume their roles are fixed.

Iconic Models

CM-440 (Scale 4): The compact armored cutter used by patrol services, bounty crews, customs contractors, corporate security, and armed couriers. Its silhouette is a dense wedge with a broad armored prow, recessed bridge, and two protected engine channels. No two CM-440s are identical after a decade in service, but the broad armored nose is always recognizable.

Common roles: patrol cutter, escort, armed courier, marshal transport, bounty vessel.

CM-640 (Scale 6): Capital hull built around a long armored keel with layered compartments, recessed launch bays, protected command spaces, and extensive internal redundancy. It appears as cruisers, troop transports, institutional vessels, and heavy escorts.

Common roles: line cruiser, marine transport, fleet command ship, convoy escort, heavy institutional transport.

Recognition and Politics

Crown Meridian ships are among the easiest to identify at any range. The armored wedge silhouette, graphite-gray and dark gunmetal plating, muted blue-white registry bands, and rectangular inspection markings are consistent across their entire hull line.

In Directorate ports, a Crown Meridian ship receives favorable lane assignments and fast inspection clearance. In League ports, it is welcome but routine. In Caliphate ports, a Crown Meridian ship may attract additional scrutiny because of the Directorate alignment. In Funtari space, it is slightly unusual: not unwelcome, but identified immediately as outside the local engineering tradition.

A Crown Meridian ship is difficult to disguise as anything else and, in most ports, requires no disguise. It looks exactly like what it is.

Visual Identity Reference

The armored prow is the identifier. Look for: compact wedge silhouette, broad forward face, recessed bridge position, squared engine housings, labeled access panels, utilitarian white work lights, clean compartment seams. Capital ships add the layered keel structure with obvious segmentation between reinforced compartment blocks. Nothing is decorative.


Antaean Openframe Consortium

Modular. Adaptable. Commercially available in a configuration for almost any job.

The Antaean Openframe Consortium dominates commercial hull construction across League space and beyond. Its ships are built around modular spines, interchangeable bays, standardized cargo clamps, detachable pods, and licensed interfaces. They are common because they are useful, and they are useful because the same basic hull can be configured for freight, salvage, passengers, survey work, medical response, or whatever the contract specifies.

Openframe is the builder that financiers understand. A lender knows how to appraise an Openframe ship because the modular components have established resale values. A port knows how to service one because the interfaces are standard. A mechanic knows how to modify one because the architecture was designed for modification.

This makes Openframe ships the default choice of commercial operators who need flexibility above all else. It also makes them the default choice of operators who need to borrow money and want a lender who will say yes.

Identity and Alignment

Primary alignment: Antaean League. Openframe ships are common everywhere commercial shipping operates, which means they are common almost everywhere.

A used Openframe ship is often easier to identify by what has been added than by the original hull: the detachable cargo sections, the fold-out utility arms, the pod that clearly came from a different decade than the rest of the ship. After a few years, most Openframe ships look like what they are: commercial tools shaped by their work history.

Design Philosophy

Openframe prioritizes adaptability and commercial accessibility. Its engineering assumptions are: the ship's purpose should be changeable at port, the cargo capacity should be maximized, and the maintenance footprint should remain manageable without authorized service facilities. Openframe does not build ships to win fights. It builds ships to carry things efficiently and change what they carry when the contract changes.

Builder Benefit: Signature Systems

System Group Benefit
Cargo Handling Add 1 Boon Die to Trials involving loading, unloading, securing, hiding, or organizing cargo. For creative stowage purposes, treat cargo capacity as 10 Cargo Units higher than listed.
Mission Modules Installing or removing clean commercial modules at an authorized yard takes half the normal time and requires no Craft Trial. Salvaged, illegal, or incompatible modules remove 1 Bane Die caused specifically by mounting geometry or interface access.
Communications Remove 1 Bane Die from all communications-based Trials. Add 1 Boon Die to Trials for relay access, transponder verification, and manifest transmission.
Transponder Systems Remove 1 Bane Die from transponder-related Trials: identity verification, spoofing, licensing compliance, customs declarations, and manifest integrity checks.
Support Craft and Workshops Support craft launched from Openframe vessels add 1 Boon Die to their first Pilot Trial after launch. Craft Trials performed in the ship's workshop remove 1 Bane Die.

Integrated Architecture Benefit: Swap one compatible minor module during normal port service without making an installation Trial.

The Openframe promise: No other commercial builder makes it easier to change what the ship does. The paperwork works. The interfaces fit. The ship adapts to the job.

Builder Drawback: Weak Systems

System Group Drawback
Armor and Combat Durability When the ship is at or below half Hull Points, all Pilot Trials and Craft Trials aboard add 1 Bane Die. The modular spine flexes under structural stress in ways that interfere with precision work and maneuvering.
High-Output Fire Control Heavy and Capital weapons installed on Openframe hulls add 1 Bane Die to attack rolls. The fire control architecture was not designed to coordinate weapons at this output level.
Thermal Control Under Extreme Load When the ship's Heat is at Threshold +4 or above, add 1 additional Heat per round from failing thermal routing. Openframe thermal management is adequate for commercial use; it is not adequate for sustained energy-weapons combat.

Iconic Models

Model 20 (Scale 4): One of the most common small commercial ships in known space. Its narrow structural spine supports detachable cargo pods, external clamps, utility arms, and replaceable engine sections. No two Model 20s look identical after a few years in service, which is either a feature or a problem depending on who is trying to identify it.

Common roles: tramp freighter, smuggling ship, passenger hauler, courier, salvage vessel, mobile workshop, colony supply ship.

Model 60 (Scale 6): Large modular commercial hull with a long central spine and numerous modular branches. It appears as cargo carriers, mobile repair yards, colony supply vessels, station tenders, and transport liners. A Model 60 in port often looks like a temporary station rather than a single ship.

Common roles: bulk carrier, mobile dockyard, colony transport, relief vessel, fleet tender, mobile trade center.

Recognition and Politics

Openframe ships are identified by their modular anatomy: visible structural spine, detachable sections, orange and cyan license panels, external cargo clamps. The specific configuration changes constantly, but the underlying architecture is identifiable.

In League ports, Openframe ships receive priority service and favorable licensing rates. Elsewhere, they are ordinary commercial vessels. In Caliphate-controlled ports, the license panel scanning runs deeper: Openframe's open-module architecture makes it a preferred hull for operators who prefer not to declare everything.

An Openframe ship that is not carrying suspicious cargo looks completely ordinary. An Openframe ship carrying suspicious cargo looks exactly the same, which is why customs officials have learned to look harder at the module manifests.

Visual Identity Reference

Look for: exposed structural spine, detachable pods, asymmetrical configurations that change port to port, orange and cyan license panels, visible serial numbers, cargo clamps and external frames, fold-out utility arms, standardized docking collars. Nothing is hidden because hiding costs module slots. What is hidden is hidden specifically, with effort, and usually obvious on closer inspection.


Viridian Lattice Yards

Precise. Integrated. Intelligent. Impatient with improvisation.

Viridian Lattice Yards builds the most refined civilian and scientific vessels in known space. Its ships are famous for advanced AI integration, medical support, environmental stability, sensor performance, and continuity-stack handling. Every system is designed to work with every other system. The result is ships that know more about their situation than their crews often do, that handle navigation with an elegance other builders cannot match, and that break badly when someone tries to fix them with parts from a different builder.

Viridian is the builder of the Shoiyan Concord's civilian fleet and the preferred choice of medical networks, research institutions, and anyone whose job requires surviving in space while gathering or preserving high-value information. Its ships are not luxury goods, though they are expensive. They are tools designed by engineers who believe that precision is kindness.

Identity and Alignment

Primary alignment: Shoiyan Concord. Viridian ships are common in Concord space and increasingly visible wherever research, medical, or continuity-stack operations require their specific capabilities.

A Viridian ship in a port tells experienced observers that someone aboard this vessel is either very wealthy, doing something scientifically significant, or both. The pearl ceramic hull and viridian-green status glows are recognizable across docking bays.

Design Philosophy

Viridian prioritizes intelligent integration. Its engineering assumptions are: the ship should know what is wrong before the crew does, the navigation system should be the best available, and the life support should accommodate every species aboard without manual configuration. Viridian ships are not flexible in the Openframe sense. They are flexible in the sense that their AI can manage complexity that would overwhelm a less integrated system.

Builder Benefit: Signature Systems

System Group Benefit
AI Core The ship's AI provides 1 additional Active Channel per structured round beyond the base rate. When an assigned Directive Package covers the task, Viridian AI assistance removes 1 Trial Die and 1 Bane Die (rather than 1 Trial Die only).
Navigation Add 1 Boon Die to Trials for Slipstream seam location, offset exit calculation, corridor navigation, route analysis, and local orbital positioning.
Sensors Treat sensor detection range as 1 band farther than listed. Remove 1 Bane Die from scan Trials and target identification Trials.
Life Support Species-specific environmental needs are automatically accommodated without requiring manual adjustments or Trials. Life support irregularities are flagged by AI diagnostics 1 round before they become mechanically significant.
Medical Bay Add 1 Boon Die to Medicine Trials performed aboard the ship. The ship's medical AI can assist 1 Medicine Trial per round without consuming an Active Channel.
Stack Vaults and Clone Support Continuity-stack preservation and restoration Trials add 1 Boon Die. Stack integrity is monitored automatically; damage to stored patterns is flagged immediately.

Integrated Architecture Benefit: Once per encounter, gain 1 Boon Die when the ship AI assists a native Navigation, Sensors, Medical, or Life-Support action.

The Viridian promise: The ship knows what it is doing. Navigation, sensors, AI, medicine: the ship handles these things better than any comparable vessel. The crew can focus on decisions while the ship manages execution.

Builder Drawback: Weak Systems

System Group Drawback
Field Repair and Improvised Upgrades Add 1 Bane Die to Craft Trials using improvised tools, non-Viridian replacement parts, or performed outside a certified Viridian facility. The integrated architecture is precise and does not tolerate approximation.
Non-Native System Installation Non-Viridian system installations on Viridian hulls add 1 additional Bane Die beyond normal builder compatibility penalties. The deep integration of native systems treats foreign hardware as interference.
Heavy Armor Reinforced Hull Plating or heavier armor installed on a Viridian hull adds −1 Handling beyond the upgrade's listed penalty. Viridian hull geometry is optimized for mass distribution.
Crude Weapon Integration Heavy and Capital weapons installed on Viridian hulls add 1 Bane Die to attack rolls and generate 1 additional Heat per firing. The hull's fire control architecture and thermal management were not designed for this level of output.

Iconic Models

VN-33C1 (Scale 3): Fast small craft with a narrow central body, sweeping radiator fins, and highly integrated navigation systems. VN-33C1s often serve as executive transports, medical response vessels, couriers, and high-end exploration craft. Their silhouette suggests motion even while docked.

Common roles: courier, medical ship, survey craft, executive transport, intelligence vessel, diplomatic shuttle.

VN-63C2 (Scale 6): Capital hull organized around a protected central core and layered support sections. It appears as hospital ships, long-duration scientific vessels, continuity vault carriers, and diplomatic cruisers. Up close, the smooth hull seams and fine sensor lattice lines make the scale difficult to judge.

Common roles: hospital ship, research cruiser, diplomatic vessel, continuity-vault carrier, long-range survey ship.

Recognition and Politics

Viridian ships are beautiful in a restrained, functional way. Pearl ceramic hulls, dark teal glass, viridian-green status glows, smooth layered shell seams with almost no visible joints: the ship looks like it was grown rather than assembled.

In Concord ports, a Viridian ship is invisible in the way that the expected thing is invisible. Outside Concord space, the identification is immediate and carries implications: this ship is expensive, its operators are probably not desperate, and its systems are probably more capable than the hull size suggests.

A Viridian ship is difficult to repair far from authorized yards. This is the known cost of ownership, and operators who choose Viridian know it going in. What they are buying is capability the other builders cannot match in their Signature areas.

Visual Identity Reference

Look for: pearl ceramic hull surface, almost no visible seams, dark teal glass panels, viridian-green status glow strips, sweeping curved radiator fins, fine sensor lattice lines recessed into the hull surface, minimal external clutter, protected inner sections. Capital ships add the overlapping petal-like hull layer structure. Nothing is exposed that does not need to be.


Kharos Forge Cooperative

Loud. Repairable. Nearly impossible to kill.

Kharos Forge Cooperative is less a single corporation than a network of clan yards, foundries, licensed workshops, and family-owned manufacturers operating under shared standards. Its ships are built for hard places. They assume poor infrastructure, scarce parts, untrained replacements, and repairs performed with whatever happens to be on hand.

Kharos ships look like they have been repaired, because they have. Even new ones arrive with the visual language of machines that expect hard use. Exposed trusses. Oversized engine nozzles. Mismatched panel seams. Tool racks on the hull exterior. The aesthetic is not incompetence. It is a design philosophy: every system that needs maintenance should be accessible, and access panels should not require proprietary tools.

Kharos ships survive things that other ships do not survive. What they cannot do is pretend to be subtle, refined, or easy to inspect.

Identity and Alignment

Primary alignment: Funtari Confederacy. Kharos ships are common throughout Confederacy space and extremely common in frontier regions, mining colonies, salvage operations, and anywhere the supply chain for sophisticated parts is unreliable.

A Kharos ship is the first thing many frontier settlers see in the morning and the last thing they see before sleep: the hauler that brought the colony's supplies, the salvage rig working the asteroid field, the armed transport that arrived when the other options did not.

Design Philosophy

Kharos builds for hard use and field recovery. Its engineering assumptions are: the engines should push hard when needed, the ship should be fixable without authorized service, and a competent mechanic with basic tools should be able to diagnose any problem without reading a proprietary manual. What Kharos does not prioritize: looking clean, running quiet, or convincing anyone that the ship is something other than what it is.

Builder Benefit: Signature Systems

System Group Benefit
Sublight Engines When the pilot performs Overburn or pushes engines beyond rated output, add 1 Boon Die to the Pilot Trial and reduce the generated Heat by 1. Kharos engines handle being pushed.
Maneuvering Thrusters Remove 1 Bane Die from Pilot Trials for evasive movement, lateral repositioning, sudden direction changes, and precision docking in confined or debris-cluttered spaces.
Damage Control Add 1 Boon Die to emergency patch Trials. Field repairs that would normally require an authorized yard may be attempted in field conditions at Hard difficulty instead of Severe.
Workshops Add 1 Boon Die to Craft Trials performed using the ship's workshop. Components fabricated in a Kharos workshop function as commercial replacements for 1 additional session before requiring proper sourcing.
Salvage Systems and Towing Add 1 Boon Die to Pilot Trials when towing a disabled vessel. Salvage operations that would be Severe under normal conditions may be attempted at Hard difficulty.
Cargo Handling Add 1 Boon Die to cargo handling Trials. Kharos ships can handle oversized, irregular, or hazardous cargo without the normal handling penalty.

Integrated Architecture Benefit: Reduce the difficulty of one emergency field repair by one level per encounter.

The Kharos promise: The ship can do the work. Engines push when asked. Repairs happen in conditions where other ships would be dead in space. The crew does not need a certified yard to keep flying.

Builder Drawback: Weak Systems

System Group Drawback
Signature Management Add 2 Bane Dice to all Signature Management Trials. Entering Cold Running Mode takes 4 rounds instead of 2, and the crew must succeed at an Average Craft Trial to enter it at all. Kharos ships are loud. This is intentional.
Refined AI Integration Non-Kharos AI Core installations on Kharos hulls add 2 Bane Dice to the integration Trial beyond normal compatibility penalties. The rough, exposed infrastructure is actively hostile to precision AI architecture.
Thermal Quieting When one or more weapons are firing, the ship generates 1 additional Heat per round from poor exhaust management. This is in addition to each weapon's listed Heat cost.
Luxury Accommodations Passengers on voyages over one week experience minimal comfort. Social complications from passenger dissatisfaction are handled at GM discretion. Kharos ships are not built for people who complain.

Iconic Models

KR-41 (Scale 4): Rugged frontier workhorse built around oversized engines, reinforced landing gear, visible coolant lines, and a configurable cargo frame. The KR-41 is one of the most common ships beyond heavily regulated core systems. No two look the same after a few years of field modifications.

Common roles: frontier freighter, salvage tug, mining tender, colony hauler, armed transport, blockade runner.

KR-61 (Scale 6): Heavy industrial hull built around reinforced ribs, heavy engine clusters, recovery gantries, and visible service structures. A KR-61 can tow vessels significantly larger than itself, carry modular workshops, and function as a mobile repair yard, assault support ship, or mercenary carrier depending on what its current Module Slots hold.

Common roles: salvage carrier, mining ship, mobile repair yard, industrial transport, mercenary carrier.

Recognition and Politics

Kharos ships are identifiable by their working-machinery aesthetic: exposed trusses, oxidized steel panels, blackened red-brown armor sections, yellow hazard paint on equipment access areas, oversized engine housings, tool racks on exterior surfaces. The identification is not subtle.

In Funtari ports, a Kharos ship is standard. In frontier space, it is the expected thing. In League or Directorate ports, a Kharos ship is looked at more carefully during customs inspection, not because of anything suspicious but because the modification history is usually complex and the paperwork is rarely current.

A Kharos ship carrying a clean manifest and a recent inspection certificate is unusual enough that experienced customs officers wonder why someone worked so hard to make it look legitimate.

Visual Identity Reference

Look for: visible structural framework, exposed trusses and ribs, oxidized steel surfaces, blackened red-brown primary armor, yellow hazard paint on equipment areas, oversized engine nozzles relative to hull size, mismatched replacement panels, external tool racks, cranes and salvage arms, reinforced landing gear. Capital ships add external gantries and scaffolding that make the ship look like a mobile work yard. Everything is accessible because accessibility is the point.


Safa Celestial Arsenal

Efficient. Precise. Purposeful. Resistant to becoming anything else.

Safa Celestial Arsenal is the most tightly controlled major builder in known space. Its ships are built around efficient reactors, precise fire control, powerful security architecture, and unusually capable automation. Even the civilian models carry military assumptions. Safa does not believe a ship is a flexible home. It believes a ship is an instrument built for a purpose, and instruments should not be casually repurposed.

Safa's civilian line exists because governments and corporations that cannot obtain military contracts still want the reactor efficiency and security architecture Safa is known for. What they receive is a commercial ship with Caliphate engineering running underneath, firmware that knows when it is being modified, and a service relationship that is easier to maintain than to exit.

Identity and Alignment

Primary alignment: Jaziri Caliphate. Safa ships are common in Caliphate space and among approved corporate partners, licensed security organizations, and government contractors who have passed Caliphate vetting processes.

A Safa ship outside Caliphate space is notable. It means either that its operator has Caliphate connections, that the ship was acquired through unusual means, or both.

Design Philosophy

Safa builds for mission precision and reactor efficiency. Its engineering assumptions are: the reactor should have headroom, the weapons should hit what they aim at, the security systems should make unauthorized access difficult, and the ship should not encourage uses it was not designed for. Safa ships are not flexible. They are excellent at their intended function and actively resistant to modification beyond it.

Builder Benefit: Signature Systems

System Group Benefit
Reactor Output Treat Power Capacity as 1 higher than listed for overload calculations. Remove 1 Bane Die from Craft Trials to push, reroute, or stabilize the reactor under combat load.
Fire Control Add 1 Boon Die to attack rolls with weapons that have the Lock-On tag. Point Defense systems on Safa hulls treat their Interception Rating as 1 higher than listed.
Electronic Warfare Remove 1 Bane Die from ECM offensive and defensive Trials. Once per round, an ECM system on a Safa hull may be activated as a defense reaction without consuming a crew action.
Security Intruders aboard a Safa vessel add 1 Bane Die to all infiltration, movement, and system-access Trials due to automatic monitoring, compartmentalized access, and preemptive countermeasures.
Point Defense Safa point defense systems add +1 to their Interception Rating beyond the system's listed value.
Cyberdefense Add 1 Boon Die to cyberdefense Trials. Hostile electronic attacks targeting Safa AI systems or shipboard networks add 1 Bane Die to the attacker's roll.

Integrated Architecture Benefit: Once per encounter, reduce the System Damage, Power Load, or Heat cost of one native Fire Control, Reactor, Point Defense, or Cyberdefense action by 1.

The Safa promise: The ship does its job precisely and efficiently. The reactor has headroom. The weapons hit what they aim at. The defenses respond faster than the crew expects.

Builder Drawback: Weak Systems

System Group Drawback
Cargo Flexibility Reconfiguring cargo space, swapping module functions, or converting bays to non-standard use requires an additional Craft Trial and increased time at port. Manifest discrepancies in Safa ships trigger automatic alerts.
Open Interfaces Non-Safa component installations add 1 additional Bane Die beyond normal builder compatibility penalties. The closed proprietary architecture treats foreign hardware as a security risk.
Improvised Modification Unauthorized modifications to Safa systems add 1 Crisis Die to the installation Trial. The authentication system treats unauthorized work as a security event and responds accordingly.
Civilian Comfort Crew quarters are austere, monitored, and formally organized. Passengers and non-military crew on long voyages may develop morale or social complications at GM discretion.

Iconic Models

Safa S3 (Scale 3): Fast small hull built around high-output propulsion, strong Fire Control interfaces, and narrow mission specialization. Safa S3s are used by approved security forces, customs hunters, high-risk couriers, and government contractors. Their silhouette (narrow spear-like body, deep ventral keel, swept engine housings) is distinctive and carries immediate implication.

Common roles: customs hunter, security interceptor, fast courier, pursuit vessel, licensed bounty ship.

Safa S6 (Scale 6): Capital hull built around a powerful reactor spine and layered combat systems. The Cathedral Axis design language: tall axial symmetry, central reactor spine, ribbed side structures, protected docking courts, layered armor planes, controlled ceremonial light. It reads as deliberate and austere. Nothing looks accidental.

Common roles: armed corporate transport, security cruiser, restricted research vessel, government contractor ship, command transport, defense platform.

Recognition and Politics

Safa ships are identifiable by their severity. Narrow, blade-like small ships with deep ventral keels and matte ivory-and-dark-basalt plating, narrow gold certification lines, concealed weapons apertures, formal inspection seals. Capital ships use Cathedral Axis geometry: the vertical axis, ribbed side structures, and ceremonial lighting make them look like weapons that someone decided should also be architecturally significant.

In Caliphate ports, a Safa ship is expected and unremarkable. Outside Caliphate space, it draws attention. A Safa ship in a fringe port means either the Caliphate has a formal interest nearby, or someone with very specific connections sold the ship to an operator who understood what they were buying.

A Safa ship with modified systems runs the risk of triggering automatic authentication failures that can disable the ship in port or at a checkpoint. This is not a bug in Safa's design. It is a feature.

Visual Identity Reference

Look for: narrow spear-like or blade-like silhouettes on small ships, matte ivory and dark basalt hull plating, narrow gold certification line around hull section boundaries, red-gold reactor glow visible at engine nozzles, severe bilateral symmetry, concealed weapon apertures, formal inspection seal markings, controlled narrow illumination. Capital ships use Cathedral Axis: tall axial symmetry, central reactor spine, ribbed side structures, protected docking courts, ordered weapon geometry. Nothing is asymmetrical by accident.


Builder Compatibility

Components from different builders are not automatically compatible. The difficulty of mixing builders depends on the relationship between them.

Integration Type Description Engineering Difficulty
House Integration Component and hull from the same builder Routine
Partner Integration Builders maintain active compatibility agreements Standard
Open Integration Common commercial standards, no close cooperation Standard with 1 additional Bane Die
Rival Integration Competing standards, incompatible firmware, or hostile licensing Increase the Trial by 1 die and add 2 Bane Dice
Forbidden Integration Military, strategic, stolen, AGI-linked, or proscribed technology Increase Trial by 1–2 dice and add 2 Bane Dice

Default compatibility relationships between the five major builders:

Hull Builder Partner Open Rival
Crown Meridian Openframe Kharos, Viridian Safa
Openframe Crown Meridian, Kharos Viridian, Safa None by default
Viridian Openframe Crown Meridian Kharos, Safa
Kharos Openframe Crown Meridian Viridian, Safa
Safa Limited licensed partners Openframe Crown Meridian, Kharos, Viridian

These are defaults. A specific shipyard, treaty, or black-market specialist may change the category for a particular installation.


Patchwork Ships

Most ships that have been working for more than five years are patchwork ships. The question is how much patchwork, and whether it was done with care.

A patchwork ship is a hull from one builder with core systems from multiple others. The arrangement is usually the result of practical choices: the best available engine at a frontier port was Kharos; the damaged navigation suite was replaced with whatever the salvage yard had; the Safa reactor component was not asked about.

Patchwork ships are not inferior by definition. A crew that deliberately combines a Kharos engine for repairability, a Viridian navigation suite for Slipstream work, Crown Meridian damage control for survivability, and Openframe cargo systems for flexibility may have a ship that outperforms a factory-stock model in the areas that matter for their work.

What the patchwork ship loses is Integrated Architecture, along with the simplicity that comes from one builder's assumptions running underneath everything.

Integration Status

Each non-native system on a patchwork ship records its integration status on the ship sheet.

Status Meaning
Native Same builder as the hull. No modifier.
Certified Approved partner integration.
Adapted Neutral commercial integration.
Forced Rival, damaged, or heavily modified integration.
Forbidden Military, strategic, illegal, stolen, or proscribed technology.

Recording this status matters because it determines repair difficulty, inspection risk, and which builder benefits apply. A Crown Meridian damage control system installed in a Model 20 does not gain the Crown Meridian Signature benefit: the hull is not Crown Meridian. It does not gain a Weak drawback either, because damage control is not in Openframe's Weak system list. It simply works normally.

Builder drawbacks follow the hull, not the component. A Viridian hull resists field repair regardless of whose engine is being repaired. A Kharos hull runs thermally rough regardless of whose navigation suite sits in the rack.

The Social Status of Patchwork Ships

In Directorate ports, a patchwork ship draws inspection because mixed-builder systems suggest modifications that may not be properly licensed. The inspection itself is usually routine unless something specific flags.

In League ports, a patchwork ship is ordinary. Half the ships in a League port are patchwork.

In Funtari space, the quality of the patchwork matters more than the fact of it. A ship that has been modified with skill and care gets respect. A ship held together with improvised parts and hope gets practical concern about whether it will make the next run.

In Caliphate ports, a patchwork ship with Safa components is subject to deep firmware audit. A patchwork ship without Safa components is subject to the same inspection as any other ship.

Building a Patchwork Ship Character

A patchwork ship has history. When the players choose to run a patchwork ship, they are choosing a ship that has already made decisions. The modifications tell a story.

The recommended starting approach: begin with a Model 20 or KR-41 hull (either is the strongest default recommendation for a typical campaign). Then add one system that is better than expected and two that have complications. The better system should reflect something the crew values. The complications should create situations.

An example patchwork ship might have:

  • Model 20 hull
  • Kharos sublight engine (better overburn; runs hot while weapons fire)
  • Viridian navigation suite (Boon on seam location; repairs require Viridian tools)
  • Crown Meridian damage control (Boon on emergency patches; manual reset after major repairs)
  • Unlicensed Safa reactor component (better power headroom; military signature bloom when overcharged; acquisition story that requires discretion)
  • One cargo module the lender still believes is installed
  • One hidden compartment that has passed two inspections

This ship works. It is useful. It has opinions about when it cooperates, and it has a maintenance list that grows longer every month. That is a campaign ship.


Builder Benefit Quick Reference

Builder Best At Weak At
Crown Meridian Damage absorption, damage control, power routing, defensive coordination Running quiet, atmospheric flight, cargo flexibility
Openframe Cargo, modules, communications, support craft Combat durability at low HP, heavy weapons, thermal control
Viridian AI, navigation, sensors, life support, medicine Field repair, non-native parts, heavy weapons and armor
Kharos Engines, damage control, workshops, salvage Stealth, refined AI, thermal management, passenger comfort
Safa Reactor, fire control, ECM, security, point defense Cargo flexibility, open interfaces, unauthorized modification