Two Kinds of No Link
This application is built on the Memory-Native Protocol, disclosed in United States Patent Application 19/366,760, in which the unit of transmission is a memory-bearing agent that carries its own identity, policy, lineage, and routing constraints. 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 agent carries. Because there is no authority to defer to at the moment of action, identity, policy, lineage, and routing must travel inside the agent itself. As disclosed, each agent comprises a unique identifier, a semantic payload, a transport header that encodes propagation constraints such as time-to-live and trust scope, an append-only memory field holding signed lineage, access logs, and policy references, and a cryptographic signature computed over those fields by the originating node. The signature proves the originator and detects tampering by local validation against the sender's public key, without a reachable certificate authority or session server. The memory field's access log and appended traces record the staged path the agent took across hops, and the embedded policy references let an executing node decide locally what the agent may do. The specification states expressly that this embedded-policy design enables secure operation in disconnected or intermittently connected networks, such as IoT or interplanetary systems, and that the substrate may be deployed atop delay-tolerant mesh architectures from edge devices to interplanetary networks.
Routing keyed to trust state rather than to reachable addresses is the natural fit for a network with no stable end-to-end paths. Under the disclosed dynamic routing protocol, a node parses the agent's transport header and memory field, builds a local trust graph from access history and any network-health signals it holds, scores candidate next hops against policy-defined trust thresholds and time-to-live cost, and forwards, caches, or quarantines accordingly. A node thus 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. Agents that exceed time-to-live or fall below a trust threshold are dropped or flagged, and a node configured in stateless mode relies solely on the agent's embedded data, which suits resource-limited or transient relays in the field. 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 disconnected regime admits several deployment shapes, all grounded in the disclosed stack. A minimal edge node, a sensor or a small rover relay, may run only the routing layer and a simplified memory layer in stateless mode, forwarding agents on routing and time-to-live alone. A core or relay-orbiter node may run the full stack, including the dynamic indexing protocol for entropy-driven local reorganization, the adaptive consensus protocol for trust-weighted quorum over mutation proposals, and a network health monitoring module that emits and consumes health agents to reroute around degraded links. Federated zones let separate operators, a science team and a navigation team, or two agencies, define their own policy and trust models while the substrate enforces compliance through agent-carried rules across administrative boundaries with no shared ledger. Because agents carry all context needed for execution, they propagate and validate even after long store-and-forward delays.
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 United States Patent Application 19/366,760, including the memory-bearing agent structure, the store-and-forward transport-agnostic stack, and the trust-weighted dynamic routing, adaptive consensus, dynamic indexing, and network health monitoring primitives. The specification expressly contemplates deployment over delay-tolerant mesh architectures and interplanetary networks. 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. It draws on sibling portfolio inventions in the Adaptive Query family for the surrounding network framework. References to public delay-tolerant networking and rover autonomy work are used for context only, and no specific commercial product is referenced.
