Fleet and external metrics
BMO’s integration story for fleet / external metrics is narrow and explicit. This page states what is supported, what is not claimed, and the wording to use when you document or wire this path.
Supported behavior
Section titled “Supported behavior”POST /v1/health-signalsonbmo serve/bmo upwhenoptions.health_signals_ingressenabled = true(default off). Bearer-authenticated push of small JSON envelopes into the same declarative pipeline as otherhealth.*events.
Integration contract
Section titled “Integration contract”When you document or wire fleet or external metrics against BMO, state all three:
- Push-only integration; not Prometheus pull.
- Does not imply fleet-wide closed-loop regulation.
- Default off; operator-controlled.
What is not claimed
Section titled “What is not claimed”- No fleet-wide Prometheus-style pull or default remote_write receiver as organism metabolism.
- No automatic mesh regulation or adaptive genome merge driven by external metrics as a default product story.
Where to read more
Section titled “Where to read more”- Implementation notes: health-signals-ingress.md (config, request shape, wiring).
- Constitution Explicit non-goals:
ai-organism-constitution.md. - MCP note: health-signal ingress is HTTP-only. There is no MCP tool for this ingress; see the Fleet health signals paragraph on MCP Server.