ds throughput [--releases <n>] [--since <YYYY-MM-DD>] [--json]

How the release cadence is doing, against the November 1, 2026 baseline. Its first line is the median time the release tower was held over the last releases (--releases, default 20). Below it:

  • departures: releases per day, and the longest gap between two;
  • the tower's hold time by phase, and the idle gap from a deploy to the next train;
  • owner wait: how long releases sat ready for the owner's go-ahead;
  • how long an item waits from landing to live, and how long a finished Epic waited to go live;
  • repairs: reverts and hotfixes;
  • the golden suite, the post-deploy check, the CI workflows on train pull requests, and how long gated runs waited for the machine-wide test lock.

--since limits it to records from that date (default: 60 days ago); --json prints the same numbers as JSON, times in UTC. It only reads: release claims in DevStride with the agent credentials file, gh, git and local logs, and every machine's lock waits only through a dev AWS profile. A source it cannot read prints "not recorded", never 0.