Skip to main content
  • Kind: Projection
  • Version: 1
  • Fleet Manager owner: Fleet Manager squad, #fleet-manager-chat (individual claimant pending)
  • Counterpart owner: unassigned, DevEx (owns the UI) with Deployment Engineering as the consumer (repository nscaledev/burn-in-testing, whose CODEOWNERS still names the Leverage team)
  • Last reviewed: 2026-09-09

​
What flows

A web dashboard over the Fleet Manager API for visualising and analysing burn-in results. Its client holds read scopes on organisations, sites, locations, racks, devices, workflows, jobs, cohorts and test executions, and also job:create, job:cancel, job-device-status:update, cohort:create, test-execution:create|update|mark_stale and stale-hold undo.

​
What breaks if this changes

Burn-in API or cohort shape changes break the dashboard. Because the client holds write scopes, it can also dispatch and cancel jobs; any dispatch from it competes with operators and CHAD for the same devices.

​
Enforcement

  • Principal: burn-in-testing.
  • Mechanism: FM OAuth client in the hub chart roster.
  • Hub roster client burn-in-testing in deployment/charts/hub/values.yaml.

​
Gaps

  • A read dashboard holding job-create and test-execution write scopes; whether those are still needed is unconfirmed.
  • Repository last pushed April 2026.

​
Change log

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