THEFLUX CORP · WORKING DOCUMENT · REV A
theFlux: Layers and Components
The layer stack of the Flux Capacitor, and the reasoning behind the three-three-five component ladder.
theFlux Corp · Campbell River, BC · July 2026
This document reads in two passes. The first pass describes theFlux as a set of layers: what the mesh does for the community that hosts it, from free wireless at the surface down to governance at the root. The second pass describes theFlux as a set of components: the physical ladder that climbs from a single pole to a complete Flux Capacitor, and why each rung uses the number it uses. The layers are the promise; the components are the proof.
Part One — The Layers
Community Wireless
The first thing a community sees is the simplest: wireless that works. Free public connectivity is the outermost layer of theFlux and the one that earns the right to exist in a neighbourhood. It is deliberately unremarkable — phones connect, pages load, nobody registers anything.
Public layer — open, unauthenticated wireless carried on standard unlicensed spectrum. Anyone in range can use it. It carries no identity and asks for none.
Private layer — a second radio plane on asymmetric licensed frequencies, visible only to registered slates. This is where community services, health pointers, and mesh coordination live. The two layers share poles but never share trust.
Why wireless first — connectivity is the honest handshake. A community can evaluate it in a week, cancel it without ceremony, and no institutional permission is required to say yes. Every deeper layer inherits its legitimacy from this one working well.
Community Commons
Beneath the wireless sits the compute. Every fluxPole carries more processing than its radio duties require, and the surplus is not sold upward to a cloud — it is pooled sideways into a commons the community draws on.
Local inference — language models, translation, transcription, and search that run inside the mesh. Queries never leave the community to be answered, which means they never leave the community to be harvested.
Community storage — replicated, encrypted storage across nodes for local institutions — the school, the band office, the volunteer fire hall — priced at cost or contributed as membership.
Shared services — the boring civic software (booking, notices, mapping, archives) hosted where its users live, maintained by the co-op rather than rented from elsewhere.
Why a commons and not a product — surplus compute treated as a commodity flows to whoever bids highest, which is never the neighbourhood. Treated as a commons, it compounds locally: every service built on it becomes a reason the next household registers a slate.
Communication — Multiple Methods, and Why
theFlux does not bet on one radio. A mesh that survives weather, terrain, outage, and interference carries several communication methods at once, each chosen for what it alone does well. Redundancy here is not waste; it is the design.
Unlicensed Wi-Fi (2.4/5/6 GHz) — the public access layer. Ubiquitous client hardware, zero regulatory friction, short range. This is how people join.
Licensed asymmetric links — the private backbone between poles and slates. Licensed spectrum gives interference protection and legal standing; asymmetry (different up and down bands) frustrates casual interception and makes the private plane hard to impersonate.
Point-to-point backhaul (microwave/mmWave) — high-capacity directional links across the node triangles and between capacitor sites. Line-of-sight, weather-sensitive, enormous bandwidth — the arteries.
Sub-GHz long-range (LoRa-class) — low-rate telemetry that punches through forest canopy and terrain where nothing else will. Sensors, alarms, and heartbeat traffic ride here. When everything else is down, this layer is usually still up.
Wired where it exists — fibre or copper interconnect at city-serviced sites. Never assumed, always used when present.
Store-and-forward — the method beneath the methods. Messages that cannot cross a broken link wait, hop, and arrive late rather than never. A coastal mesh must treat disconnection as weather, not failure.
Why multiple methods — each method fails differently. Rain fade takes the mmWave links but not LoRa; interference takes unlicensed bands but not licensed ones; a cut cable takes fibre but nothing wireless. Diversity of failure modes is the only real uptime guarantee a distributed system can make.
Defence Sensors
The same antennas that carry the community's traffic are, passively, instruments. A mesh of receivers with known geometry and disciplined clocks is a sensor array whether or not anyone asks it to be — theFlux simply refuses to waste that fact.
Spectrum as training signal — every pole continuously observes its RF environment. The ambient spectrum — who transmits, where, when, on what — is the training corpus for models that learn what normal looks like, so that abnormal announces itself.
Passive coherent location — a fluxNode triangle forms a complete multistatic PCL cell: three synchronized receivers exploiting existing broadcast energy to detect and track vessels and aircraft without transmitting anything. A chain of nodes along the coast is a passive radar fence over the Strait of Georgia's small-vessel traffic.
RF fingerprinting — transmitters have physical-layer accents — oscillator drift, power ramp signatures — that identify devices independent of what they claim to be. The mesh learns its regulars.
Passive, not active — the legal and ethical line the architecture holds: sensing listens, it does not emit. This distinction is the pre-emptive answer to regulatory objection (DAOD 6002-4 notice requirements attach to transmission, not reception) and the ethical answer to surveillance concerns — the mesh watches the spectrum, not the citizens.
Dual-use boundary — where defence workloads run, they run behind a hard partition (the Option C classification boundary) on designated hardware. Community traffic and defence sensing share poles, never processes.
Governance
Infrastructure is a constitution written in hardware. theFlux makes the constitution explicit rather than accidental.
Slate registration — the mechanical form of flux citizenship. Registering a slate is joining the polity: it grants access to the private layer and standing in decisions, and it is the only identity act the mesh ever requires.
Two-sided privacy — each resident's secure side (biometrics, identity tokens, health pointers) is physically and cryptographically separated from the shared mesh side, which carries anonymous tokens only. Re-identification happens solely on the resident's own secure side — the mesh cannot do it even if compelled.
CAMA governance — decisions about the shared mesh follow the community-anchored model: local trust areas hold authority over their own nodes, with proportional voice in the whole.
OCAP alignment — data touching Nations partners follows ownership, control, access, and possession principles as a design constraint, not a compliance afterthought. Nation-hosted nodes are Nation-governed nodes.
Co-op form — the operating entity is structured so that the people the infrastructure serves are the people the infrastructure answers to. Editorial and architectural sovereignty are protected in the share structure itself.
theFlux Commons — Global versus Local
Commons is used twice in this architecture, deliberately, at two scales that must not be confused.
Local commons — the pooled compute, storage, and services of one community's mesh, governed by that community, priced by that community, benefiting that community. The local commons is sovereign: nothing obliges it to share upward.
Global commons (flux commons) — the voluntary federation layer — model weights, spectrum learnings, protocol improvements, and threat signatures that communities choose to contribute and draw from, managed proportionally so that contribution and benefit stay coupled. This is Team 3's mandate.
The direction of obligation — the local commons owes the global commons nothing; the global commons owes the local commons everything it has. Federation is a gift economy with receipts — proportional management means a small coastal mesh is never outvoted by aggregate scale.
Why both — purely local meshes re-solve every problem alone; purely global systems recreate the cloud with extra steps. The two-commons design lets learning travel while power stays home.
Part Two — The Components
The component ladder has three rungs — pole, node, capacitor — and each rung's number is an argument, not an accident. Three, then three, then five.
theFlux Pole — Why Three Mac Minis?
The fluxPole is the atomic unit: a mast carrying radios, solar, LiFePO4 storage, and a compute bay holding three Mac Mini M4 Pro machines. One machine would be cheaper. Two would be redundant. Three is the smallest number that is also an institution.
Quorum — three machines can vote. A 2-of-3 quorum lets a pole make trustworthy local decisions — which reading is real, which unit has failed — without appealing to the network. One machine asserts; two machines argue; three machines decide.
Role separation — the triad maps cleanly onto the trust architecture: one unit anchors secure-side services, one carries the shared mesh side, one floats as spare, training host, and maintenance target. Roles rotate; the separation does not.
N+1 that stays N+1 — with two machines, the first failure ends redundancy and begins emergency. With three, the first failure is a Tuesday: the pole degrades to a still-redundant pair while a replacement ships.
Thermal and power staggering — three small machines under partial load sip from the solar-battery budget and shed heat passively, where one large machine under full load would demand active cooling the enclosure cannot spare. Perf-per-watt is why the platform is Apple silicon at all.
The social echo — one pole serves roughly three housing units — the confirmed pilot ratio. Three machines, three households: the atomic unit of the mesh mirrors the atomic unit of the street. This symmetry is rhetorical, but it is also true.
theFlux Node — Why Three fluxPoles?
A fluxNode is three poles in a full-mesh triangle (fluxNode/3). The triangle is not a shape preference; it is the minimum geometry at which several essential properties switch on at once.
Minimal full mesh — three poles yield three links, and every pole reaches every other directly. Any single link can fail and the node remains connected — the smallest topology with no single link of failure.
Triangulation — two receivers give a bearing ambiguity; three give a fix. The triangle is the minimum array for locating a transmitter in the plane, which makes it the minimum unit of spectrum sensing that produces positions rather than hunches.
A complete PCL cell — the triangle geometry is precisely what a multistatic passive radar cell requires: spatially separated, time-synchronized receivers with known baselines. Each deployed node is a finished sensing instrument, not a fraction of one — the defence layer arrives whole with every node.
Structural honesty — the triangle is the rigid polygon. As with trusses, so with topologies: a three-pole node keeps its logical shape when stressed, degrading to a still-functional line before it degrades to an island.
Local consensus above pole consensus — three poles, each internally 2-of-3, give the node nine machines and two tiers of quorum. A node can detect and quarantine a lying pole the same way a pole quarantines a lying machine.
theFlux Capacitor — Why Five fluxNodes?
A Flux Capacitor is a minimum of five fluxNodes operating as one mesh. Five is where a network stops being a chain of dependencies and becomes a fabric.
Byzantine margin — tolerating one arbitrarily faulty participant requires four (3f+1); five tolerates one traitor and one absentee at the same time. In practice that means the mesh keeps consensus through the ordinary coastal condition: one node storm-isolated while another is down for maintenance.
Routing diversity — five nodes admit up to ten pairwise links and genuinely disjoint paths between any two points. Below five, most 'alternate routes' secretly share a hop; at five, path diversity becomes real rather than nominal.
Sensing baseline — five triangles distributed across geography give the PCL fence multiple long baselines and overlapping cells, turning point detections into tracks. The capacitor is to the node what the node is to the pole: the scale at which observation becomes coverage.
Load and burden sharing — with five nodes, no single site must host the heaviest services, the embassy function, and the spare capacity at once. Duties distribute; no node is load-bearing for the whole.
Governance floor — five nodes usually means five host communities or neighbourhoods at the table — enough for the governance layer to be a genuine plurality rather than a bilateral arrangement wearing a constitution.
The Embassy — The Boundary Layer
A Flux Capacitor is sovereign but not isolationist. It maintains exactly one kind of contact point with the wider internet, and the diplomatic metaphor is meant literally: an embassy, on the boundary, operating under the community's flag.
Single negotiated border — all traffic between the community mesh and the internet crosses at the embassy — a designated, hardened gateway function — rather than leaking from every pole. One border can be defended, audited, and reasoned about; a thousand borders cannot.
Representation outward — the embassy presents the community to the internet as one entity. Individual slates, poles, and residents are never directly visible from outside; the mesh's interior topology and its citizens' identities stop at the boundary.
Consular services inward — residents reach the outside world through the embassy's services — anonymizing egress, cached and verified content, filtered inbound connectivity — receiving the internet's benefits without accepting its default terms of surveillance.
Policy enforcement point — community decisions about what crosses the border (what is cached, what is blocked, what is metered) are enforced here, once, visibly — which makes the governance layer's choices real rather than aspirational.
Graceful severance — because the interior never depended on the border for its own operation, the embassy can close — by outage or by choice — and the community's wireless, commons, communication, and sensing continue untouched. Sovereignty is the ability to lose the internet and keep the lights on.
The Ladder, Read Once More
Three machines make a pole that can decide. Three poles make a node that can locate. Five nodes make a capacitor that can endure. And one embassy makes the whole thing a neighbour to the internet rather than a tenant of it. The layers describe what the community receives; the components describe why the promise holds when a link fails, a storm lands, or a machine lies. Coherence isn't accidental at any rung.