Fleets & Peers

Running one resource across many runtimes and having its instances coordinate.

Fleets — declare nodes with Hyperlink.nodes([...]) (or bare Hyperlink.distributed for directory discovery), mark fields with Hyperlink.fleet so peers dont recurse into them. Peers — inside a layer, Hyperlink.peers / Hyperlink.selfNode (discharged by Hyperlink.peersLayer) let an instance reach siblings.

Two shipped factories lean on this mesh:

• Telemetry — leaf metric snapshots; fleet folds (inFlightByNode, fleetInFlight) for the stadium board.

• Fleet Health — leaf readiness aggregate; fleet byNode / status with Reachable / Unreachable (local /health stays local).

• ShardMap — partitioned key/value; routed get / put / delete forward to the owning node; leaf *Local ops; fleet size / sizeByNode.

Hyperlink.distributedOf(tag) reads the declared node set (empty when undeclared) — partition strategies use that fixed membership rather than remapping when a peer is briefly down.