Transport-Layer Agnosticism: One Protocol Stack Above Any Carrier

Mechanism

The memory-native protocol stack is structured as a strict separation between the semantic layer, which handles addressing, integrity, ordering, and policy evaluation, and the carriage layer, which handles only the movement of opaque byte sequences from one node to another. The semantic layer constructs each protocol unit as a self-contained record that includes its own addressing fields, its own cryptographic commitments, its own ordering metadata, and its own policy bindings. The carriage layer is presented with this record as an opaque byte sequence and is responsible only for delivering it, with no knowledge of its structure or contents.

A protocol unit at the semantic layer carries a content hash, a chain reference linking it to its predecessor in the relevant memory region, a signature from its originating node, an envelope reference linking it to the integrity policy under which it was produced, and the payload itself. The content hash is computed over all preceding fields and is signed before the unit leaves the originating node. Any modification of any field, by any actor, breaks the signature and causes the unit to be rejected at any subsequent node that evaluates it. The carriage layer cannot modify the unit without detection, and the integrity guarantee is therefore a property of the unit itself rather than a property of the channel over which it travels.

The carriage interface is defined by three primitive operations: send, which accepts an opaque byte sequence and a destination address and returns either acknowledgment or failure; receive, which delivers an opaque byte sequence to the semantic layer along with a hint regarding the carrier from which it arrived; and discover, which returns the current set of reachable destinations along with metadata describing the latency, bandwidth, and reliability characteristics of each. Any transport that can implement these three primitives, in any form, can carry the protocol. The protocol does not require ordered delivery, does not require reliable delivery, does not require low latency, and does not require duplex operation; absence of these properties affects throughput and latency but does not affect correctness.

Over IP-based transports, the carriage layer typically maps send and receive onto TCP connections, UDP datagrams, HTTP request-response cycles, WebSockets, or WebRTC data channels. Each mapping is a thin adapter, on the order of a few hundred lines of code, that accepts the opaque byte sequence from the semantic layer and delivers it to its peer.

Over mesh-radio transports, the carriage layer maps send and receive onto mesh-routed datagrams. The semantic layer is unaware of intermediate hops and unaware of the routing decisions made by the mesh; it sees only that a byte sequence was delivered to a named destination, and the destination sees only that a byte sequence arrived from a named source.

Over satellite transports, the carriage layer accommodates the long round-trip times and intermittent visibility windows characteristic of orbital relays. The protocol's tolerance for unordered, unreliable, and high-latency delivery makes satellite carriage operationally indistinguishable from terrestrial carriage at the semantic layer.

Over courier transport, the carriage layer maps send and receive onto the writing and reading of physical media. A protocol unit serialized to a removable storage device, transported physically from one site to another, and read back at the destination is, at the semantic layer, identical to a unit that traversed an IP network. The integrity commitments established at the originating node are verified at the receiving node by exactly the same logic, and the resulting memory state is exactly the same.

Operating Parameters

The operating envelope of transport-agnostic carriage is parameterized by the maximum unit size, the timeout for acknowledgment of delivery, the deduplication window for retransmitted units, and the discovery interval for refreshing the set of reachable destinations. Reasonable values observed during reduction to practice include maximum unit sizes between sixty-four kilobytes and one megabyte, acknowledgment timeouts that scale with the carrier's expected round-trip time, deduplication windows of several minutes, and discovery intervals of seconds for IP transports and minutes or hours for mesh, satellite, and courier transports.

The protocol does not impose latency requirements on the carriage layer. A unit may be delivered within milliseconds, within hours, or within days; the integrity and policy properties of the unit are unchanged by the delivery time. The receiving node evaluates the unit against the current state of its local memory at the moment of receipt, and the evaluation logic is robust to arrival of units that are temporally out of order or that reference predecessors not yet present at the receiving node. Out-of-order arrivals are queued until their predecessors arrive; missing predecessors are requested through the same carriage primitives.

Bandwidth requirements scale with the rate of unit production at the originating nodes and with the size of the units themselves. The protocol supports compression of payload contents at the semantic layer before signature, and it supports batching of multiple small units into a single carriage operation when the carrier favors larger transfers. Both compression and batching are transparent to the carriage layer.

Reliability requirements are explicit. The protocol distinguishes between best-effort and durable delivery at the semantic layer, with durable delivery requiring acknowledgment from the receiving node. Best-effort delivery is appropriate for ephemeral state updates that will be subsumed by subsequent units; durable delivery is appropriate for state changes that must be incorporated into the receiving memory region with certainty. The carriage layer is responsible only for the mechanics of acknowledgment, not for the policy decision regarding when acknowledgment is required.

Heterogeneous deployments are supported uniformly. A single deployment may use IP carriage between data-center nodes, mesh-radio carriage between field devices, satellite carriage between continents, and courier carriage for high-assurance archival, all simultaneously, with units crossing between carrier types at gateway nodes that translate only the carriage envelope and never the semantic content. A unit produced at a field device may traverse a mesh hop, a satellite uplink, an IP backbone, and a courier transfer to reach its final destination, and the integrity properties verified at each hop are identical to those that would be verified if the unit had traveled over a single direct link.

Alternative Embodiments

A streaming embodiment maps the carriage layer onto persistent connections that carry a continuous flow of units, with framing performed by the carriage adapter. This embodiment is appropriate for high-throughput deployments in which the cost of establishing a connection is amortized over many units.

A request-response embodiment maps the carriage layer onto discrete request-response pairs, suitable for HTTP or other transactional carriers. Each unit is delivered as the body of a request, with acknowledgment delivered as the body of the response.

A store-and-forward embodiment maps the carriage layer onto delay-tolerant networking primitives, with units held in intermediate storage when no onward path is available and forwarded when connectivity is restored. This embodiment is essential for satellite and mesh deployments with intermittent connectivity, and it operates correctly even when the originating node and the receiving node are never simultaneously online.

A physical-media embodiment maps the carriage layer onto the writing, transport, and reading of removable storage devices. Units are serialized to the medium at the originating site, the medium is transported by any physical means, and units are deserialized at the receiving site. The integrity commitments hold across the physical transport because they are properties of the serialized units themselves.

A hybrid embodiment combines two or more of the above and uses gateway nodes to translate between carriage forms without altering the semantic content of any unit. Each embodiment preserves the property that integrity is a function of the unit and not of the carrier.

Composition

Transport-layer agnosticism composes with every other primitive of the memory-native protocol stack. Federation across zones operates over any transport because the federation messages are themselves protocol units subject to the same carriage-layer indifference. Policy mutations propagate over any transport because they are protocol units. Audit events propagate over any transport because they are protocol units. The entire governance, policy, and lineage machinery of the framework is therefore deployable in any environment in which any of the supported carriers is available.

Composition with the protocol's integrity envelope is the foundational property. The envelope is established at the originating node, before the unit is presented to the carriage layer, and it is verified at the receiving node, after the unit has been retrieved from the carriage layer. The carriage layer is therefore outside the integrity boundary, and no compromise of any carrier can affect the integrity of any unit. This property holds even when the carrier is operated by an adversary, even when the carrier corrupts or reorders units, and even when the carrier suppresses delivery entirely; the worst case is loss of availability, never loss of integrity.

Composition with the protocol's policy machinery permits policies to specify, in their export and admission clauses, which carriers are acceptable for which classes of unit. A high-assurance deployment may require that units of a particular class travel only over courier carriage, while a low-latency deployment may require that units of another class travel only over IP carriage. The policy machinery is unaware of the mechanics of any particular carrier; it specifies only the abstract requirement, and the carriage layer enforces it.

Prior-Art Distinctions

Conventional networking stacks tightly couple their semantic and carriage layers. TCP/IP integrates addressing, ordering, and reliability into the transport itself; replacing the transport requires re-engineering the addressing and ordering logic of every application above it. Application-layer protocols such as HTTP and gRPC similarly assume specific transport properties and degrade or fail when those properties are absent. Delay-tolerant networking research has produced protocols that accommodate intermittent connectivity, but those protocols do not generally provide the cryptographically anchored integrity envelope of the memory-native stack and do not generally support seamless transition across heterogeneous carriers in a single deployment.

Overlay protocols such as Tor and various mix networks decouple application semantics from carriage to a degree, but they still assume a packet-switched IP substrate and do not extend to mesh, satellite, or courier carriage without substantial modification.

The transport-agnostic mechanism disclosed here is distinguished from these prior approaches by the combination of three properties: integrity is a property of the protocol unit and not of any carrier, the carriage interface is defined by primitives that admit any transport including non-electronic carriage, and the semantic, governance, and audit properties of the protocol are uniform across all carriers within a single deployment.

Disclosure Scope

This article describes a structural mechanism disclosed in connection with Provisional Application 64/050,895, "Memory-Native Protocol for Cognition-Compatible Networking." The mechanism is presented at a level of detail sufficient to enable a person of ordinary skill in the art to implement it without undue experimentation, and the embodiments described are illustrative rather than exhaustive. The scope of protection sought is defined by the claims of any non-provisional application claiming priority to the provisional and as subsequently amended during prosecution, and no statement in this article should be construed as limiting that scope or as a disclaimer of subject matter.

Licensing inquiries and technical questions regarding integration with existing transport infrastructures may be directed to the author through the contact channels published at qu3ry.net.