Flo

Flo — Service Discovery

advertise manifest → subscribe patterns → registry + events.

Flo — Service Discovery (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | advertise manifest → subscribe patterns → registry + events. 1 - Alert Routing - Routes alerts to appropriate topics AlertRouter alert_router.py:40 mx://noted/session/event mx://flo/alert/noted MQTT Topics mx://holon/mailbox/email/inbound mx://daemon/process/state mx://daemon/primary/failover_event alert payload 1. AlertRouter initializes 2. Subscribes to raw sources 3. Processes incoming alerts 4. Publishes processed alerts to appropriate t… Processed alert for noted session event {"source": "noted", "severity": "warn", "count": 1, "summary": "1 session(s): session_awaiting_note", "ts_iso": "2023-04… Processed alert for email inbound {"source": "email", "severity": "info", "count": 1, "summary": "1 email(s) in inbox", "ts_iso": "2023-04-01T12:00:00Z"} AlertRouter supports both sync and async modes based on construction parameters. 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
Flo
Slug
flo-discovery
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
3 paths
  • daemon/src/flo
  • daemon/fabric_proxy/flo.py
  • firmware/mx/lib/Transport/flo_client.h