The network follows relationships.

Spaces don't live on servers

Alice and Bob share a space. To carry an event between them, the network borrows a route — right now, a relay in Europe.

The relay changes. Nobody moved. Nothing was migrated, exported or re-invited.

The path changed.

Same room? The event walks across the local network and never touches the internet.

The path changed.

No internet at all? A radio hop will do. Slower — but the space is the same space.

The space did not.

Relays are routes, not homes

The question is never “which server are we on?”

It is “what is the best way to reach you right now?”

REACHABILITY

Topology emerges

Alice reaches Bob through one relay and Carol through another. The relays never talk to each other.

No relay federation required. The topology is assembled at the edges.

Reachability, not location

Everyone carries a small signed list of ways to reach them — and hears about ephemeral ones nearby.

Reachability
subject: Bob
epoch: 42

relay ru-1
relay eu-1

Paths can overlap

A route change does not have to interrupt a conversation.

A new path becomes reachable before the old one is retired. Make before break.

Failure becomes routing

A route that dies is not an emergency. It is a closed road — traffic takes another one.

One identity, many devices

Your Mac, your phone and a radio brick are each reachable in their own way — and they are all still you.

Transport is a capability

A text event fits through anything. A large video will not squeeze into a radio link — and nobody has to “switch to mesh”. The application chooses among compatible paths.

Local when possible. Relayed when useful. Radio when necessary.

The invariant

Watch the infrastructure change under a conversation that never notices.