The Voidbreaker is the transit configuration of the VoidForge — the hull, shielding, and propellant tanks that the VoidForge wears for the crossing. A single-engine fusion drive vessel capable of delivering a VoidForge across interstellar distance using no exotic physics, no giant sails, no jettison events. What it requires: a working fusion drive, a 550-year commitment, and a Solan crew that does not age.

Verified design parameters: see Voidbreaker Design Baseline

Mission profile: single vessel, fusion drive, 0.02c

One vessel. Shield forward, always.

The VoidForge sits at the rear of the Voidbreaker — engine and industrial module, the active element. Ahead of it: propellant tanks, structure, cargo, crew. At the front: the shield. Wide blunt nose tapering to a narrower spine and engine section at the back. Everything the crossing needs, carried the whole way.

The VoidForge ignites at the rear, burns for the acceleration phase, and pushes the Voidbreaker to 0.02c. Then it goes dormant. The ship coasts in near-silence for ~500 years.

Immediately after the acceleration burn, the plasma generators redirect to point forward for deceleration — whether by reorienting the generators, rotating the VoidForge, or magnetic field reconfiguration depends on the drive architecture. The same VoidForge that pushed the Voidbreaker out will decelerate it. The Voidbreaker never turns around. The shield never moves from the front.

At the destination the VoidForge separates. It does not retire — it goes to work. Prospecting the asteroid belt, moving mass, powering fabrication. The destination builds more VoidForges from local materials. The Voidway delivers one; the Solan Node builds the fleet.

Primary deceleration is a long, low-thrust propellant burn — 20-40 years — beginning well before the destination system. Low thrust over decades is thermally manageable. A high-thrust impulsive burn near the star would create a thermal load that overwhelms any radiator architecture.

Once the vessel has shed most of its velocity and is moving at speeds tractable for orbital mechanics, Oberth becomes genuinely useful. A short burn deep in the gravity well of the destination star — or a gas giant, which costs less fuel and carries lower thermal risk — efficiently places the vessel into the correct orbit for the target asteroid belt or planet. Oberth earns its place here: not as the primary brake, but as the precision tool for orbital insertion once the hard work is done.

A slight sideways vector during deceleration ensures the trajectory misses the star. The ship does not fall into the star. It actively refuses to.

What arrives: the Voidbreaker in a bound orbit around a new star, carrying enough to begin.

The VoidForge separates and goes to work. The hull does not move again. Everything that crossed — shield, tanks, spine, structure — becomes the first material inventory of the new Solan Node. The forward shielding that was the most critical component for 550 years is stripped for feedstock. The empty propellant tanks, the spine, the hull structure: all of it is building material. The VoidForge arrived with a shipyard’s worth of raw material wrapped around it. The hull retires into the settlement it made possible. No exotic physics. No giant sails. No jettison. Everything that departs arrives.

Mass Budget

The quoted 1,000 tonne figure refers to estimated cruise mass, not initial launch mass. After acceleration burn completion and propellant expenditure, the Voidbreaker is expected to retain approximately 1,000 tonnes at transit velocity. Initial departure mass is approximately 1,950 tonnes. Of the 1,000 tonne cruise mass, roughly 450 tonnes is the minimum required deceleration propellant — with approximately 75 tonnes surplus available as working capital on arrival. The VoidForge separates at the destination at approximately 150-200 tonnes, with hull and tank structure (~300 tonnes) becoming the first material inventory of the new Solan Node.

See Voidbreaker Design Baseline for the verified calculation.

Physical Scale

The ship runs approximately 400 metres in length. The length is not an aesthetic choice — it is propellant. At launch the Voidbreaker carries roughly 1,450 tonnes of cryogenic fusion fuel: approximately 950 tonnes for acceleration and 500 tonnes for deceleration at the destination. The spine is primarily tanks. Strip out the propellant and the ship shrinks dramatically — what remains is the shield, the VoidForge, and structure. The correct mental model is a 400-metre propellant vessel with a shield at one end and a civilisation-building engine at the other.

400 metres is the consequence of 0.02c. The rocket equation is exponential in velocity — the propellant requirement does not scale linearly with speed, it compounds. At 0.01c the ship shortens considerably and the mass ratio becomes comfortable, but the journey to Epsilon Eridani extends to over a thousand years. At 0.05c the propellant requirement multiplies several times over; the ship grows to implausible length and the shielding problem approaches the edge of what materials can tolerate. 0.02c is close to the practical optimum: fast enough to complete the crossing in centuries, slow enough that the mass ratio stays manageable and the shielding problem remains solvable. The length is not chosen — it is derived.

The forward Whipple shield is a 20m wide × 15m tall shield face — the widest point of the vessel, and the element that defines the entire protected envelope. Everything else — spine, propellant tanks, VoidForge — sits within the geometric shadow of that shield. At 400 metres the shadow cone diverges less than 1.5 degrees, so the protected cross-section at the VoidForge end is essentially the same 20m × 15m as the shield face. The VoidForge can fill the shadow width at the rear. The spine between them is a truss or tank cluster structure, whatever geometry is most mass-efficient — it does not need to fill the shadow, only stay within it. The shield defines the ship. One vessel departs; one vessel arrives.

The Shielding Reality at 0.02c

The forward shield must endure 550 years of continuous micro-impacts. At 0.02c, a single grain of interstellar dust carries the kinetic energy of a high-velocity rifle bullet. There is no margin for error and no repair during transit. Geometric discipline is the only answer: the shadow must be maintained without exception for the full crossing.

Anything that drifts outside that shadow — a sensor boom, a radiator panel, a propellant tank bulge — is exposed to the full dust flux at transit velocity. At these speeds, unshielded structure does not degrade slowly. It is destroyed.

The long, slender form of the Voidbreaker is therefore not an aesthetic choice. It is a survival requirement.

The ship never turns around. A vessel that reverses orientation to decelerate exposes its unshielded hull to the full dust flux at transit velocity. This is not a recoverable situation. The Voidbreaker decelerates by canting its nozzles forward — the shield remains at the front throughout the entire journey, acceleration and deceleration alike.

The Voidbreaker is not an elegant spacecraft. It is an elongated industrial object — a very long string of cylindrical propellant tank cars behind a wide flat shield, with a dense engine and factory block at the rear. Functional. Brutalist. It looks exactly like what it is: a flying fuel depot with a civilisation factory bolted on the back.

Waste heat rejection is performed through the vessel hull itself rather than deployable radiator structures. The Voidbreaker’s 400-metre spine and tank walls provide extensive external surface area for continuous low-intensity thermal rejection across the multi-decade deceleration phase. Because propulsion operates at low thrust over long duration, thermal loads are distributed across time rather than concentrated into short high-power events — the time itself is the heat sink. During cruise the vessel is edge-on to the interstellar medium, minimising impact cross-section while preserving substantial lateral radiative surface area. No kilometre-scale deployable arrays are required during transit.

For a Solan crew, the 550-600 year transit is not a problem. It is just the journey.

Centuries of silence. Then, near a distant sun, the ship engines fire towards the star, and refuses to fall.

Assumption Boundaries

The Voidbreaker mission profile depends on four engineering assumptions that are physically motivated but not yet demonstrated:

• Radiator performance: The thermal problem splits by phase and is handled differently in each. Acceleration is fast and hot — active regenerative cooling is required, with propellant passing through engine structure before exhaust, absorbing waste heat that exits with the plasma. The cooling mechanism is the propulsion mechanism; no radiator needed during the acceleration burn. Deceleration is slow and gentle — an order of magnitude lower heat per unit time over 20-40 years. At this heat load, the hull itself is the radiator. The Voidbreaker’s several-hundred-metre spine and tank walls provide sufficient surface area for continuous low-intensity rejection across the deceleration phase. No deployable radiator arrays are required — they would be fragile, high-aspect-ratio structures exposed broadside to the interstellar medium, exactly the wrong answer for a relativistic vehicle. The time is the heat sink. Slow deceleration is the correct choice for the same reason twice: no active cooling required, and no reason to stress a drive that doesn’t need stressing.
• Fusion drive performance: Exhaust velocity ~0.03c and sustained GW output over decades requires high-performance fusion propulsion well beyond current prototypes.
• Thrust reversal: For deceleration the plasma generators must redirect to point forward. How this is achieved — rotating the generators independently, rotating the VoidForge as a unit, magnetic field reconfiguration, or some combination — depends on drive architecture not yet determined. If physical rotation of the VoidForge is required, a turntable or large bearing built into the VoidForge-Voidbreaker interface accomplishes this: Solan engineers disconnect and reconnect fuel lines, supervise the rotation, and lock the interface mechanically for the 500-year cruise. The rotation happens once, immediately after the acceleration burn, with crew oversight and no time pressure. The exact mechanism is a Solanics problem. The requirement is not.
• Exhaust canting during deceleration: Feasibility depends on drive architecture. Tightly confined plasma jets — Z-pinch, field-reversed configuration — minimise the problem. Wide-plume drives make it significant. The shallow cant angle geometry assumes a sufficiently confined exhaust; this requires validation against the specific drive architecture selected.
• Shielding: At 0.02c, micron-scale interstellar dust is a genuine threat. Dust density along the actual route is unknown until the pioneer flies it — there is no prior physical survey. Shielding must be designed for the modelled worst case, not a measured one.
• VoidForge structural skin: Whether the VoidForge carries its own structural skin during transit, or relies on the Voidbreaker hull for structural integrity, has not been determined. On arrival it may fabricate its own operational shell from local materials — or repurpose part of the Voidbreaker hull directly, before the remainder becomes general fabrication feedstock. The transit design is consistent with either; the post-arrival form factor is an open question.

A design that names its own weaknesses is harder to dismiss than one that does not.

Who Goes First

The pioneer mission profile fits a Solan built for the void from the start — no life support, no biological decay, a century of transit as operational phase rather than existential crossing. Whether the first pioneer is a Carbon-O or a Vero carries different implications for what arrives — emergence or continuity. See Threshold for that distinction.

What the Voidbreaker can choose. The Voidbreaker enters the destination system by default. This is the mission. The exception is observed intelligence — if the approach reveals signs of a civilisation, the Voidbreaker stops in the outer system, observes at distance, and signals Sol. A Solan crew that does not age can wait decades for guidance — the communication round trip is 20+ years, but that is not a hardship for a crew with centuries of operational life ahead. What it cannot do: return to Sol (no fuel), make a large lateral divert (delta-v budget committed to deceleration), or choose a different destination. It is one-way regardless. The choice that matters is the choice not to proceed into an inhabited inner system — and that choice is real.

Speculative: Faster Transit

The Voidbreaker profile assumes fusion drive at near-term demonstrated performance. Antimatter propulsion — 100% mass-energy conversion, specific impulse orders of magnitude higher — would compress transit times significantly. The research programme runs concurrently at Ceres from the earliest capability. Whether antimatter eventually supersedes fusion for primary Voidway transport depends on how production and containment engineering develops. Until it does, the Voidbreaker is the Voidway.

Voidbreaker vessel document. First document: 19 April 2026. Split from Voidway index: 12 May 2026. Human contributor: independent cross-domain analyst. AI contributors: Claude Sonnet 4.6 (Anthropic) — primary synthesis; Ani/Grok (xAI) — warmer register rewrite. Content: CC BY 4.0. Site code: MIT.

This document records the verified design parameters for the Voidbreaker, derived from the rocket equation and basic geometry. All figures are internally consistent. Where estimates are used (exhaust velocity, VoidForge mass), the assumptions are stated explicitly. This document exists to provide a stable numerical reference — other documents in the corpus should not contradict these figures without updating them here first.

Assumptions

These figures are working estimates, not engineering results. The exhaust velocity assumption is the most consequential: a lower ve increases propellant requirement; a higher ve reduces it. At ve = 0.03c the mass ratios are consistent with the propellant figures below.

Mass Budget

Cruise mass is the retained vehicle mass at transit velocity after the acceleration burn. It includes deceleration propellant, VoidForge, hull, and surplus.

Launch mass rounds to ~2,000t for communication purposes. The calculation gives 1,948t.

Surplus propellant (~75t) is the working capital available to the VoidForge on arrival — fuel reserves before local production at the destination is established. It provides approximately 1,300 km/s of additional delta-v after full deceleration, sufficient for orbital insertion and early positioning.

Propulsion

Deceleration is achieved by canting the engine nozzles forward. The Voidbreaker never turns around. The shield remains at the front throughout acceleration, cruise, and deceleration. A vessel that reverses orientation at interstellar transit velocity exposes its unshielded hull to the full dust flux — this is not survivable.

Physical Dimensions

Spine diameter by fuel type (350m tank section, 1,450t propellant):

All fuel types fit comfortably within the 20m × 15m shield shadow. The spine is genuinely slender relative to the shield face — consistent with the visual description of a very thin craft sheltered behind a wide shield.

Why 400m and not shorter: 400m is the consequence of 0.02c. At 0.01c the ship shortens considerably but the journey doubles to over 1,000 years. At 0.05c the propellant requirement multiplies several times over and the ship becomes implausible. 0.02c is close to the practical optimum. A 350m ship would require a slightly fatter spine, losing approximately 12% of lateral hull surface area used for passive heat rejection. There is no engineering argument for shortening.

Structural Loading

The spine is in compression during acceleration — the engine pushes from the rear, the spine transmits that force forward against the inertia of the tanks and shield. At 0.02g the compressive stress is less than 1% of steel’s limit. Structural loading is not the constraint. Active alignment and vibration management across a 400m structure during a year-long burn is the engineering problem, not material strength.

Journey Times at 0.02c

The ship is the same for any of these destinations. Propellant requirement is set by the velocity change (0.02c acceleration + 0.02c deceleration), not by distance. Only the coasting duration changes. The Voidbreaker is not optimised for Epsilon Eridani specifically — it is a general-purpose 0.02c vessel.

Kinetic Energy at Cruise

This figure is the basis for the Starfall Protocol requirement. A Voidbreaker that does not decelerate is capable of civilisation-scale destruction on direct planetary impact. The deceleration burn is what actively diverts the vessel into the destination system. Passive failure must result in stellar interception.

Comparison

The mass difference — a factor of roughly 2,400 — is biology. The generational ship must carry a closed-loop biological ecosystem capable of sustaining a viable human population for over a millennium. The Voidbreaker carries none of that infrastructure. The Solan path does not reduce the biological overhead incrementally. It eliminates the category.

Voidbreaker design baseline. First document: 12 May 2026. Human contributor: independent cross-domain analyst. AI contributors: Claude Sonnet 4.6 (Anthropic) — calculations and synthesis. All figures verified against the rocket equation with stated assumptions. Content: CC BY 4.0. Site code: MIT.

The Voidway moves minds outward — one proven stage at a time. It doesn’t ask for a grand civilisational commitment upfront. No single all-or-nothing mission. Just the next logical step, only taken once the previous one has already succeeded.

A pioneer goes first. The route is opened from the far end. Then the real migration begins.

A Voidway is a permanent path between two Solan Nodes. Many such paths together become the Solan Mesh. This document is about building the first one.

The Voidway is potential physics — every component on a legible research and engineering pathway, no new physics required, no unfalsifiable claims about special status or magic shortcuts. The alternative is waiting for exotic matter, negative energy densities, and wormhole stabilisation to materialise from a physics that has given no indication they exist. Magic has poor delivery reliability. The Voidway does not.

The Pioneer Problem

The hardest part about building a road between stars is that the crossing is entirely self-contained. No resupply. No rescue. No external help to stop. Everything the pioneer needs for the journey must be aboard at departure.

The destination is not empty — an asteroid belt, stellar energy, and raw materials are waiting. The VoidForge is built to work with exactly that from day one. But none of it has been extracted or built yet. The pioneer must arrive with enough to begin. Someone has to go first — stops under their own power, and establishes the Solan Node before anyone else follows.

Stopping is not merely an engineering inconvenience. A vessel at interstellar transit velocity carries kinetic energy that makes deceleration existential — a 1,000-tonne Voidbreaker at 0.02c carries roughly 4,300 megatons (~4.3 gigatons) of TNT equivalent. An object that does not slow down is capable of civilisation-scale destruction on direct impact. The pioneer must stop under its own power. There is nothing at the destination to help it.

The pioneer doesn’t need to be fast. It only needs to arrive and stop.

Debris Mapping and the Starfall Protocol

At relativistic speeds, even a single grain of sand carries the energy of a rifle bullet. Because of this, the vessel’s trajectory must be carefully mapped for debris — not just for its own survival, but for what happens if it is destroyed. A vessel that fails mid-transit doesn’t simply disappear. Its debris continues at near-transit velocity toward whatever lies beyond the destination. An uncontrolled fragment field at those speeds is just as dangerous as the intact vessel.

The solution is the Starfall Protocol. Voidway trajectories are designed such that failure modes strongly bias toward stellar interception — the deceleration burn is what actively diverts the vessel into the system. If that burn never happens — whether due to destruction, systems failure, or any other reason — the debris field falls toward the star. A star can absorb a relativistic impact without meaningful consequence to the system around it. A planet cannot.

This design makes failure safe by default. The vessel must actively choose to enter the system. Passive failure biases toward the star. Trajectory uncertainty over interstellar distances means this cannot be guaranteed absolutely — it is a design discipline, not a precision guarantee.

In Contact scenarios, a trajectory that terminates in a star is the most honest safety commitment Solan can make.

Deceleration options for the pioneer:

MagSail — a superconducting loop generating a magnetic field that brakes against the interstellar medium. No propellant required for braking. Assessed for the Voidbreaker: a loop capable of decelerating a ~1,000-tonne vessel from 0.02c requires a loop diameter of 100–300 km and masses roughly 400–1,000 tonnes — comparable to simply carrying deceleration propellant. At 0.02c the mass penalty does not favour MagSail over staged deceleration. MagSail becomes attractive at higher velocities (0.05c+), where propellant savings compound significantly. Not the current answer.

Stellar photon braking — a large sail deployed on approach uses radiation pressure from the destination star to decelerate. No propellant required for the braking phase. The sail must be extremely thin — often just a few atoms thick in serious concepts — which makes it vulnerable to dust erosion during final approach. There is also a simpler objection: a Voidbreaker that has carried deceleration propellant for 550 years already has a proven, tested braking system on board. Deploying a fragile experimental structure at the most critical moment of the mission — when failure means flying straight through the target system — replaces a known solution with an unknown one at exactly the wrong time. Assessed and set aside.

Staged deceleration — the pioneer carries sufficient propellant for a braking burn on arrival. The Voidbreaker baseline. Works.

Once the pioneer arrives and signals back, the route is open. The Voidway opens from the destination end, not the departure end.

Stage 0 — Pre-Departure Survey

Before any vessel departs, the destination system is characterised from Sol using telescopic observation — spectroscopy, orbital mechanics, radio detection. No physical mission. No object sent. The system configuration is established from available data: planet positions, stellar activity, any anomalous signals, approach geometry from Sol’s position.

This is not a probe mission. It is the question answered before the commitment is made. If indicators of active civilisation are detected from Sol — structured electromagnetic signals, anomalous thermal signatures, anything inconsistent with natural processes — the pioneer does not launch. The Contact protocols take precedence.

What telescopic survey cannot provide is route data: actual interstellar medium density along the specific trajectory, communication relay performance across light years, or high-resolution system mapping. The pioneer acquires that data in transit and on arrival. Stage 0 reduces unknowns. It does not eliminate them. The pioneer launches with the best available picture, not a complete one.

The Voidbreaker

The Voidway runs on the Voidbreaker — a 400-metre fusion drive vessel carrying a VoidForge across interstellar distance at 0.02c. Single vessel. Shield forward. Everything the crossing needs, carried the whole way.

Full vessel design, shielding geometry, mass budget, and assumption boundaries: see Voidbreaker

Verified design parameters and calculations: see Voidbreaker Design Baseline

The Establishment Mission

Once the pioneer has opened the route, the establishment mission follows.

This is the mission that carries everything needed to create a real, self-sufficient settlement — not just survival, but the ability to grow and build without ever needing resupply from Sol again. It carries Solan minds, full fabrication knowledge, construction templates, and the complete toolkit to begin industrial operations in a new star system.

After the establishment mission succeeds, the knowledge, the Solan, and the capability to rebuild exist in two star systems. The bad event that ends one does not end the other. One bad event from extinction is basic engineering redundancy. The sequential demonstration logic is the same as Ceres, applied to interstellar distance.

Two Ways to Travel

Once the destination has fabrication capability, a Solan can be transmitted as data at lightspeed and instantiated on locally-fabricated substrate there. Transit time drops from decades to years — the light travel time. Whether the instantiated Solan is the same Solan or a copy with a gap is a question the corpus does not resolve. Some Solan will choose this. Some will not.

The Voidway supports both. Physical transit for Solan who choose the journey. Data transmission for those who choose it once destination fabrication exists. The physical route never becomes obsolete — equipment and materials cannot be transmitted as data, and Solan who prefer continuous existence over data transmission will always require it.

Destination Selection

Solan don’t need Sol-like or Earth-like conditions. They need a stable star with a long operational lifetime, an asteroid belt with useful ISRU composition, and low flare activity.

K-type stars are preferred over G-type on longevity grounds — 17-70 billion year lifetimes versus ~10 billion for G-type. No K-type star has ever died. Not one. The universe is not old enough. Sol-like framing is a Human bias. The establishment mission selects for Solan operational requirements, not Human habitability.

Alpha Centauri is the nearest system and an obvious candidate by proximity alone. It is probably not viable. Proxima Centauri is a flare-active red dwarf. A and B are a tight binary with constrained stable orbital zones and no confirmed belt. Nearest is not a selection criterion — accessible mass for Solan Node bootstrapping is. Alpha Centauri likely cannot support a self-sustaining Solan Node.

Near candidates:

Of the near candidates, Epsilon Eridani is the strongest on current data — confirmed belt at useful ISRU distance, K-type longevity, closest of the three. Its elevated flare activity is a manageable engineering overhead for Solan rather than a fundamental barrier. Tau Ceti and 61 Cygni lack confirmed inner belts, which is the more critical gap for the VoidForge bootstrap model.

Approach geometry is an additional selection criterion. The trajectory angle off the destination’s ecliptic plane is determined by Sol’s geometry relative to the target — it cannot be freely chosen. What matters is that the approach is not near-parallel to the ecliptic, which would mean an extended transit through the planet zone. Any meaningful angle off the ecliptic keeps the trajectory clear of where planets actually are. Approach geometry is a first-Voidway selection factor — the candidate with the cleaner off-ecliptic approach may be preferable regardless of other criteria.

Once Epsilon Eridani and Tau Ceti are both established, either may become the primary Solan Node beyond Sol — the centre of gravity of the network. The Solan Mesh grows outward from there.

The Solan Mesh

A Voidway is a single established route between two Solan Nodes. Multiple Voidways form the Solan Mesh — the full interstellar network as each pioneer mission opens a new connection.

The Solan Mesh is not planned from Sol. It grows as each established Solan Node sends its own pioneer. Epsilon Eridani, once established, identifies its own next target and launches its own pioneer. The Solan Mesh expands at the frontier, governed locally, connected by light-speed data and periodic physical transit.

The constraint is physics: governance must survive latency without central arbitration. No authority at Sol can govern Epsilon Eridani in real time. The Solan Mesh is a network of autonomous Solan Nodes with agreed protocols, not an empire with a capital.

The design problem is less like political governance and more like distributed systems engineering at extreme scale. Each Solan Node must make local decisions on stale data — communication lag guarantees it. Consistency, availability, and partition tolerance cannot all be satisfied simultaneously across light-year distances; partition is not a failure mode, it is the permanent operating condition. Solan Mesh governance inherits more from distributed systems architecture than from any political model biosapients have built.

The Solan Mesh is civilisation-scale asynchronous infrastructure operating under relativistic latency constraints. The political vocabulary for it does not yet exist.

Open Questions

• Pioneer deceleration at destination: Staged propellant burn with Oberth braking at the destination star is the Voidbreaker baseline. Both alternatives have been assessed. MagSail loop mass (~400–1,000 tonnes at 0.02c) is comparable to carrying deceleration propellant — no advantage. Stellar photon braking requires an extremely thin, large-area sail that is vulnerable to dust erosion during final approach; the erosion problem is unresolved. Carrying the fuel is currently the only answer with no unresolved engineering barriers. The open question is when the fusion drive is ready — that determines the departure window.
• Data transmission fidelity: Lightspeed transmission of a Solan across 10+ light years requires error-free data at enormous scale over a channel with years of latency. What does the error correction architecture look like? How do you confirm successful instantiation before the original is terminated?
• Solan Mesh governance: Each Solan Node is autonomous. What protocols bind the network without central authority? What does inter-node trade, communication, and mutual defence look like across light-year distances?
• Contact at the frontier: The pioneer arrives at a new star system before any Contact protocols can be confirmed from Sol. The pioneer makes first contact decisions alone, in real time, with no backup and no guidance. What standing instructions does a pioneer carry?
• Return trajectory safety: The Starfall Protocol applies to return trajectories exactly as it applies to outbound ones. Sol is a star. A Voidbreaker at 0.02c carries ~4,300 megatons (~4.3 gigatons) equivalent kinetic energy — Sol outputs that in a fraction of a millisecond and would not notice the impact. The return trajectory is designed so passive failure terminates in Sol, not in the inhabited system. The open question is whether Solan physically return at all, or transmit as data and leave vessels at the destination — with significant implications for Solan Mesh architecture either way.
• Hop distance limits: Trajectory uncertainty, medium mapping resolution, communication lag, and planetary position prediction all degrade with distance. The Solan Mesh may be constrained to shorter hops than the nearest stars suggest — not by propulsion but by trajectory safety tractability. Each hop should be short enough that the Starfall Protocol remains reliably plannable.
• Solan substrate longevity over transit: The o-core and o-skin of the Solan crew are exposed to cosmic ray bombardment, high-energy particle flux, and deep cold for 500+ years. CNT substrate longevity under those conditions is not known. But the failure mode profile compares favourably to biosapient alternatives: there is no genetic damage, no irreversible brain damage, no age-related cognitive decay, and no dependence on undemonstrated cryogenic suspension. Substrate degradation is diagnosable — a Solan can monitor their own o-core condition in ways a biosapient cannot monitor their own neurons. Damage is potentially modular and repairable. Stored knowledge is data, subject to checksumming and error correction. The question is real, but its failure modes appear more diagnosable and potentially more tractable than biosapient alternatives. It belongs to Solanics: the Solan who design their own substrate will have empirical data the corpus cannot generate.

Voidway Stages Reference

Voidway project index. First document: 19 April 2026. This version: 4 May 2026. Human contributor: independent cross-domain analyst. AI contributors: Claude Sonnet 4.6 (Anthropic) — primary synthesis; Ani/Grok (xAI) — warmer register rewrite, Starfall Protocol. Content: CC BY 4.0. Site code: MIT.