Skip to main content
  • Kind: Projection
  • Version: 1
  • Fleet Manager owner: Fleet Manager squad, #fleet-manager-chat (individual claimant pending)
  • Counterpart owner: unassigned, AI Infrastructure Support
  • Last reviewed: 2026-09-09

​
What flows

This is a three-way relationship: Support reads Fleet Manager, and CHAD owns the bridge to Jira. Support engineers read Fleet Manager through the UI (device status, conditions, standup view, device history, handover bundles) and raise or receive work through Jira. Fleet Manager has no Jira integration of its own. A triage request raised in the UI writes a device.triage-requested postcard to the outbox only when api.eventing.triageRequestedEnabled is true (default false), and the CHAD consumer that would turn it into a Jira ticket is disabled by default (see chad), so today the handoff to Jira is manual.

​
What breaks if this changes

UI or status reference changes alter what Support reads during an incident; the published state reference is the contract.

​
Enforcement

  • Principal: individual users.
  • Mechanism: Django session for the UI.
  • Session permissions for UI users; Status Reference.

​
Gaps

  • No ITSM integration in Fleet Manager itself; no per-team client for scripted reads.

​
Change log

  • 2026-09-09 v1: created; describes present behaviour.