A route is not an agreement.

Some physical nodes may host both SPECTRE transport services and a separate ledger process. Sharing operators or machines does not make them one protocol. The research baseline leaves Hashgraph-style consensus gossip and its agreement rules intact. Separately, the MESH primitive routes application packets.

A route score must not change consensus membership, voting weight, event validity or finality. Any future use of adaptive routing for consensus gossip needs its own liveness and safety analysis.

DAV domains would retain their own relevant records under an explicit agreement and verification profile. Messages, knowledge and inference do not all need one global ordering. Cross-domain locking, release proofs, failure handling and recovery remain open design obligations.

The Hashgraph research describes gossip-about-gossip and virtual voting. The consensus algorithm is Hashgraph’s own. MESH routing over SPECTRE is a separate research question. See the architecture draft and the Layer-1 design status.

Nexus governs which context a participant may receive. An available route does not override that boundary. Likewise, connectivity or a consensus result does not authorise a payment or establish a commercial obligation.

Each integration needs to identify its actual rail, responsibilities and evidence. A route, delivery receipt or ledger event can record a bounded fact; it cannot create permission or authority by itself.

These chapters explain a research design. An animation, source specification or local website test does not establish a running network.