Two Kinds of No Link
The drone case is autonomy under an adversary who takes the link away. Space is autonomy where the link was never continuously there to begin with. A Mars rover sits many light-minutes from its operators, so a round-trip command is tens of minutes old before it can possibly arrive; a deep-space probe, an undersea vehicle, or a disaster-zone robot may have no continuous path home at all for long stretches. The conclusion is the same, and it needs no enemy to force it: when there is no timely round-trip to any authority, the things authority would have supplied have to be carried. The contested case, developed in the analyses of drone jamming and the contested mesh radio, and the disconnected case described here, bracket the full condition of no reachable authority: one where the link is denied, one where it was never there.
The Disconnected Regime
The disconnected regime already has its own engineering tradition, and it points the same way. NASA's work on delay- and disruption-tolerant networking abandons the assumption of an end-to-end path entirely: data is stored at each hop and forwarded when a next hop becomes available, so a message crosses an intermittently connected fabric in stages rather than in a single connected route. Onboard autonomy on Mars rovers makes decisions locally under multi-minute round-trips, selecting science targets and navigating around hazards without waiting for Earth. Undersea and disaster-response operations face the same intermittency for different physical reasons. In all of these, there is no central authority positioned to govern each action in real time, because the speed of light, the water, or the rubble has removed it.
Why the Same Architecture Applies
A store-and-forward, intermittently connected fabric needs exactly what the memory-native protocol carries. Because there is no authority to defer to at the moment of action, identity, policy, lineage, and routing must travel with the data unit, which is precisely the governed envelope: an authority-taxonomy field, a device-hash continuity field that proves the originator without a reachable certificate authority, a hop-history field that records the staged path, and store-and-forward propagation that preserves authority, scope, and freshness across the gaps. Routing keyed to trust state rather than to reachable addresses is the natural fit for a network with no stable end-to-end paths, because a node decides what to do with a held message from the governance the message carries rather than from a route to a destination it cannot currently reach. The same primitive that lets a jammed swarm govern itself lets a delay-tolerant or interplanetary system govern itself, because both are instances of acting with no round-trip to authority.
The markets follow the physics: civil and defense space, undersea and maritime autonomy, and disaster-response robotics are all domains where the link is absent rather than merely contested, and all are domains where carried governance is not a hardening option but the only thing that lets an autonomous system act accountably at all.
Disclosure Scope
Operation over delay-tolerant, intermittently connected, contested, and interplanetary links, with identity, policy, lineage, and routing carried in the data unit and routing keyed to trust state rather than to a central registry, is disclosed in the platform filing (PCT Application No. PCT/US26/22839 and U.S. Application No. 19/230,933) and the protocol filing (U.S. Application No. 19/366,760, published as US 2026/0052096 A1), including the store-and-forward and trust-weighted routing primitives. This article frames those disclosed mechanisms against the disconnected regime of delay- and disruption-tolerant networking and onboard planetary autonomy, and presents it as the no-base complement to the contested no-link case. References to NASA delay-tolerant networking and rover autonomy are to public materials and are used for context only.
