Pattern Fabric - The Self-Healing Backbone
The Pattern Fabric (PF) is the connective tissue beneath the Instrumentation Mesh. Every sensor stream, every alarm, and every GOVERNOR query crosses the fabric over the Relay Protocol. The PF is built so that nodes, links, and whole cells can fail without the network failing — telemetry simply finds another path through the mesh.
The Self-Healing Mesh Backbone
The PF carries all telemetry and GOVERNOR traffic across the directorate. It is a true mesh — there is no core, no central switch, no single hub whose loss would darken the network. Three design principles define it.
Self-Healing Routing
Each node continuously broadcasts link-state metrics to adjacent peers. When a hop degrades or drops, traffic re-converges around the fault in milliseconds — the mesh reroutes around the dead cell without operator action and without losing the stream.
No Single Point of Failure
Every payload has at least two disjoint paths to its destination. Relay masts, drone nodes, and fabric gateways are all redundant, so the loss of any one node — or any one link — never partitions the network from GOVERNOR.
Relay Protocol
A gossip protocol: each node advertises the best direction and "distance" to a destination to its neighbours, the way word of a faster route spreads through a crowd until everyone knows it. Routes are learned, not configured.
Fabric Layers & Components
The PF is organised as a stack of layers, each with a defined function and its own redundancy posture. Together they make the fabric self-healing end to end.
| Layer / component | Function | Redundancy |
|---|---|---|
| Field node link | First-hop radio carrying raw sensor frames from surface packages onto the mesh. | Dual-band; each node sees ≥ 2 neighbours. |
| Drone-relay node | Mobile and mast relays that extend reach across attention channels and bridge gaps. | N+1 per link; Tracker drones fill coverage holes. |
| Relay routing layer | Learns and advertises least-cost paths; recomputes on any link change. | Distributed — no controller; every node routes. |
| Transport & framing | Orders, acknowledges, and retransmits telemetry and GOVERNOR query frames. | Multipath; disjoint primary + backup path per flow. |
| Fabric gateway | Bridges the mesh into the GOVERNOR analytics layer and the Live Attention Wall. | Active/active gateway pair, auto-failover. |
| Time & integrity | Mesh-wide clock sync and frame integrity so streams stitch correctly at GOVERNOR. | Multiple time sources; voting on disagreement. |
Fabric at a Glance
Snapshot figures below are a static reference (2091 baseline). For live values see the Live Attention Wall; for how each figure is defined, see the Metrics catalogue.
Related
The fabric sits between the sensing mesh and the analytics layer. See also: