Pillar — Fleet

Distributed workers. Capability matching. Scoped dispatch. Cross-tenant isolation enforced at the dispatch boundary.

The Fleet pillar is Sagewai's horizontal-scale story. Workers register with capability labels (model support, pool, project_id); the dispatcher matches tasks to workers by label intersection; the Sealed spine ensures cross-tenant credentials never leak. The result: a multi-tenant agent platform where a healthcare worker physically cannot see finance tasks.

What the pillar does

  • InMemoryFleetRegistry — worker registration, approval, heartbeat, enrollment keys for bulk onboarding.
  • FleetDispatcher, InMemoryTaskStore — task claim/report with capability matching.
  • WorkerCapabilitiesmodels_supported, pool, labels (including project_id).
  • Cross-project isolation — labels intersect at dispatch time; mismatched labels mean unreachable.
  • Enrollment keys — bulk onboarding with pool/model restrictions baked in.
  • Heartbeat + revocation — workers go offline cleanly; tasks reroute.

The Fleet pillar lives at sagewai/fleet/* in the SDK.

What proves it works

Primary lighthouse

Production multitenancy — Example 33 ships the full multi-tenant fleet integration: two tenants, four workers, mixed-tenant tasks, dispatcher refuses cross-tenant claims. Output prints the cross-tenant attempt being rejected at the dispatch boundary.

Sibling lighthouse

Observability and cost — Example 40 runs 20+ workers under mixed load with the Iron Man HUD streaming live state. The fleet pillar's stress-test surface.

Pattern examples

Where to go to ship it