Hub Lead

A seasoned operator who has run a service crew, a fleet, or a small plant before — and is comfortable making the call when telemetry and a customer call conflict. You don't need to come from robotics; you do need to think in throughput, uptime, and people.

• Owns hub-level uptime: 8 Pods, 1,700 units, one regional service area.
• Signs off on the weekly Pod schedule the Sovereign OS proposes — overrides when a route doesn't pencil.
• Holds the Hub's share of the split. Hub burn (overhead) is funded by Direct Municipal/Commercial contracts; the Hub Lead owns making that math work.
• First escalation point for Runners and Privateers in the region.
• Reports to the cooperative board (Class B Worker seat) — not to an outside owner.

• 1Morning: review overnight telemetry across all 8 Pods, clear exceptions before crews roll.
• 2Mid-day: Pod check-ins, customer escalations, equipment swaps.
• 3Afternoon: walk one route with a Runner; close the loop on training.
• 4Weekly: hub P&L review against the OS-posted ledger; quarterly board update.

Hub Lead is the operating seat the rest of the field crew grows toward. From here you either mentor Privateers and Runners into Hub Leads themselves, or take the playbook and charter a Hub somewhere new.