Mona

Fleet Control (Groups + Devices)

Group routing, command fanout.

Fleet Control (Groups + Devices) (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | Group routing, command fanout. 1 - Fleet Control Router - Handles library and execution requests _index_holons() daemon/src/fleet_control_router.py:204 _load_holon_content() daemon/src/fleet_control_router.py:238 _execute_holon() daemon/src/fleet_control_router.py:265 holon index holon content 2 - Fleet Groups Router - Manages device groups and commands _dispatch_command() daemon/src/fleet_groups_router.py:40 DeviceRegistry daemon/src/device_registry.py command dispat… 3 - Capability Deployment - Handles capability distribution _validate_capability_artifact() _create_deployment_plan() _monitor_deployment() capability val… deployment plan 1. Marco queries /api/fleet-control/library 2. Daemon indexes holons and returns library i… 3. User selects a holon, Marco posts to /api/f… 4. Daemon loads holon content and executes it… Holon Index Response { "categories": { ... }, "total_count": 10, "last_indexed": "2023-10-01T12:00:00Z" } Deployment Plan Request { "capability_id": "skill-sync-v2.1", "target_scope": { ... }, "deployment_strategy": "staged" "batch_config": { ... } } The capability deployment steps are not fully implemented in the source code. Device registry and command dispatch rely on external components not shown. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Mona
Slug
fleet-control
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
3 paths
  • daemon/src/fleet_control_router.py
  • daemon/src/fleet_groups_router.py
  • fleet-control