What This Application Specifies

United States Patent Application 19/326,036 discloses an adaptive network framework built around an adaptive index: a set of entries organized in a parent-child hierarchy, where each entry is a semantic container identified by a structured, human-readable alias and governed by a local group of anchors. Anchors are the authoritative governance units for their assigned entry. They resolve aliases, cache content pointers, and vote on structural changes to the containers they govern, all within a defined scope rather than across the whole network.

Three disclosed behaviors matter most for delay-tolerant environments. First, alias resolution is stepwise and anchor-local: each segment of an alias is interpreted relative to its parent scope, so a name is resolved by delegating downward through the anchors that own each level, with no global directory lookup. Second, mutation governance runs on scoped quorums: only the anchors governing an affected container participate in validating a proposed change, and the applicable policy object defines the quorum threshold. Third, and central here, the disclosure specifies asynchronous consensus and localized consensus during disconnection. Anchors may accept mutation proposals asynchronously; anchor groups can form isolated quorums under partition, validate mutations, and keep resolution responsive without full network connectivity; and upon reconnection, signed vote records and mutation lineage are reconciled against the canonical ledger for that scope using policy-defined arbitration.

The disclosure names interplanetary links explicitly as a target environment. It describes localized consensus as particularly valuable in fragmented or high-latency environments such as remote deployments or interplanetary links, and it lists asynchronous consensus, trust-weighted anchor resolution, predictive health monitoring, and location-agnostic identity abstraction as the properties that let the framework span variable-latency, intermittently-connected domains from terrestrial 5G and LPWAN to orbital and interplanetary networks.

Why It Matters

A link between Earth and Mars carries a one-way light-time delay that ranges from roughly a few minutes near opposition to more than twenty minutes near conjunction, and the link can be occulted entirely when a body sits between the endpoints. Deep-space and near-space operations live with this by treating the network as a series of store-and-forward custody transfers rather than an end-to-end circuit, an approach standardized in the Bundle Protocol work carried out through bodies such as the Consultative Committee for Space Data Systems and the IETF DTN working group. Bundle Protocol solves reliable custody of data across delay and disruption. It does not, on its own, solve two problems that sit above the transport layer.

The first is naming. In a delay-tolerant network there is no realistic way to consult a centrally synchronized registry to turn a stable, human-meaningful name into a current endpoint, because the registry is minutes or hours away and may be unreachable. Endpoints move, get reassigned, and get replaced, and references to them must survive those changes.

The second is coordination. Nodes on a disconnected segment, an orbiter over the far side, a surface asset during a communication blackout, a relay whose window to Earth has closed, still need to make and record authoritative decisions about local state. Waiting for a globally consistent answer is not an option. The disclosed framework addresses both problems directly: it decouples names from locations through aliases bound to stable identifiers, and it lets a local anchor quorum decide and record changes now, reconciling later.

How It Composes With the Domain

Consider a deployment spanning an Earth ground segment, a set of relay orbiters, and surface assets on a remote body, connected by scheduled, occultation-limited contact windows. The adaptive index composes onto this topology as an overlay above whatever DTN transport carries the bundles.

Naming maps directly onto the disclosed alias structure. An asset such as a science instrument or a cached data product is referenced by a structured alias of the disclosed form, for example an alias scoped as a surface site under a mission domain, resolving through the anchors that own each segment. Each alias resolves to a stable unique identifier that, per the disclosure, remains fixed even as the alias is renamed, delegated, or restructured, and even as the underlying container is split, merged, or relocated. This is the property a DTN needs: a reference to a data product or a device survives handoff between relays and reassignment of hosting nodes, because resolution follows anchor-stored lineage rather than a hardcoded location. When an alias cannot be resolved within the local scope, the disclosure describes escalation to trusted peers or delegation upward through the nesting structure, which fits store-and-forward propagation: the query travels with the data as contact windows open.

Anchor placement follows the physical partition structure. Each disconnection-prone segment, a surface site, an orbiter, the ground segment, hosts its own anchor group governing the containers relevant to that segment. Because the disclosure specifies that anchors coordinate mutation decisions only within their jurisdictional boundaries, a surface asset can register data products, update device state, and re-alias containers using only the anchors reachable on its own segment. The disclosed asynchronous acceptance of mutation proposals means proposals generated during a blackout are cached and validated when quorum is available, exactly the store-carry-forward discipline DTN transport already imposes on payloads.

Consensus under partition is the load-bearing mechanism. The disclosure describes anchor groups forming isolated quorums during disconnection, validating mutations and maintaining index responsiveness without full connectivity, then reconciling mutation lineage on reconnection through policy-defined arbitration. In the deployment, a relay that has lost its Earth window continues to govern its scope with its local quorum. Each approved mutation records its lineage: the previous anchor map, the justification, and the exact quorum configuration at ratification, all cryptographically committed. When the contact window reopens, those signed vote records reconcile against the canonical ledger for the scope. The disclosure's adjustable consensus thresholds let policy demand a light quorum for routine local updates and a heavier, possibly unanimous, quorum for sensitive operations such as policy rekeys, which is the right knob for a mission that wants surface autonomy for telemetry but tight control over command-affecting changes.

Identity and routing compose the same way. The disclosed pseudonymous device authentication uses a dynamic hash derived from an intrinsic device identifier and a short-lived local salt, stored on a private anchor group rather than published globally, and the disclosure states this identity resolution is designed to function in delay-tolerant or high-latency environments such as interplanetary networks. Because only the location of a user's private anchor appears in the public index, a device on a remote segment can be addressed by a stable alias while its actual current handle is resolved locally by its custodial anchor. For routing, the disclosed proximity-based selection weights candidate nodes by proximity, latency, load, and a trust score, and reroutes to the next best node when one degrades; in a scheduled-contact topology this maps onto selecting among relays and rerouting around a node whose window has closed or whose link has degraded, using the anchor-maintained node index rather than a static route table.

What This Enables

Composed onto a DTN, the disclosed framework enables a mission or operator to give a data product or a device a stable, human-readable name that keeps resolving correctly after the product is relocated between relays, the hosting node is replaced, or the alias is restructured, with no coordinated global rebind. It enables a disconnected segment to keep making and recording authoritative, auditable decisions about its own state during a blackout, then merge those decisions cleanly when the link returns, because every decision carries signed lineage and a recorded quorum configuration. It enables mission-appropriate governance granularity, routine local mutations under a light local quorum and command-affecting mutations under an elevated or unanimous quorum, enforced by anchor-local policy without a controller in the loop. And because the disclosure presents the framework as a retrofittable structural overlay that adds anchors and aliases without altering core protocols or consensus layers, it enables an operator to layer this naming and governance fabric above an existing Bundle Protocol deployment rather than replacing the transport.

Boundary Conditions

The framework is an overlay for naming, governance, and resolution. It is not a transport protocol and does not change light-time delay, contact scheduling, or link budgets; the underlying store-and-forward layer, such as a Bundle Protocol implementation, still moves the bytes, and the framework's benefits are bounded by what that layer delivers. Local autonomy has a cost the disclosure is explicit about: isolated quorums produce state that must be reconciled on reconnection, and reconciliation is resolved by policy-defined arbitration, so a mission must define arbitration policy for genuinely conflicting mutations made on segments that could not see each other. The disclosure describes reconciliation preserving coherence through lineage records but does not eliminate the need for a well-specified conflict policy. Quorum during a long blackout is only as strong as the anchors reachable on that segment; a single-node segment cannot form a meaningful multi-anchor quorum, so the security properties of scoped consensus degrade toward those of a single trusted node under deep isolation. Finally, the trust-weighting, predictive health monitoring, and forecasting behaviors described in the disclosure depend on accumulated telemetry and history, which are sparse for a newly deployed remote segment and improve only as operational data accrues.

Disclosure Scope

The technology described here, the adaptive index, anchor-scoped local consensus, asynchronous mutation acceptance and reconnection reconciliation, alias-to-identifier binding with preserved lineage, pseudonymous dynamic-hash device resolution, and proximity-and-trust-weighted routing, is disclosed in United States Patent Application 19/326,036, which names interplanetary and delay-tolerant networks among its target environments. The delay-tolerant and interplanetary networking framing in this article, including references to store-and-forward custody transfer, Earth-to-Mars light-time ranges, occultation-limited contact windows, and Bundle Protocol standardization through bodies such as the Consultative Committee for Space Data Systems and the IETF, is external domain and regulatory context provided to illustrate a faithful enabling deployment. That context is not part of the disclosure and is not claimed here; it is offered only to show how the disclosed mechanisms apply to a real-world domain.