SPECTRE · N : N communication

Many to many · MESH

Routing and replication across peer paths. It would carry the other three patterns.

Peer paths. Bounded decisions.

N : N

Many participants exchange as peers, without a central hub. Physical delivery can follow a path through neighbouring nodes.

Six peers retain all fifteen logical relationships. Selected traffic encounters an unavailable direct path, then illustrates a possible alternate route—not a recovery guarantee or an all-to-all physical network.

InputAn addressed packet, eligible peers and a bounded route budget.
HandlingCompare recent local link evidence; forward, retry or fall back within that budget.
OutputA delivery outcome and local measurements—not global agreement.

Delivery, permissions and correction

Permissions: Peer eligibility and resource limits come before route selection. Reachability does not grant access to payloads or authority.
Failure: Unavailable links, loops, partitions and malicious peers need bounded retries, expiry and a non-learning fallback. An alternate route may also fail.
Correction & evidence: Record the failed attempt, update local estimates and retain a reproducible trace. Test delivery, cost and tail latency against a fixed baseline.

A topology, not one product

MESH names the many-to-many routing primitive over SPECTRE nodes. It can move packets for direct conversations, broadcasts, requests and results. Many-publisher public posts are a proposed application style with separate discovery, interaction and retention rules.

Local evidence can guide a path

A node can observe how its own recent links behave: delivery success, delay, loss, congestion and capacity. The research question is whether those local signals help it select a useful next hop without requiring a complete global map.

How MESH routing fits within SPECTRE

One pattern in a shared fabric.

The relationship shown here is logical: it says who communicates with whom. SPECTRE’s physical routes may cross multiple peers. Permission, retention and ledger agreement keep their own rules.

This page applies SPECTRE’s VMOSK-A delivery direction; it is not a new product charter or evidence of a running service. Specify the interface, replay a bounded interaction and test missing participants, failure and correction before adopting a changed design.

SPECTRE direction & delivery Physical routing Separate ledger agreement

Explore another relationship.

One to one · FLOW One to many · RELAY Many to one · AXIOM