Flow math, plus the signal underneath it
ScrumDo matches the CFD, lead-time histogram, and Little’s Law forecast, but keeps the self-interpreted customer story that started the work attached to the same card, so the forecast and the why live together.
Economics that sequence the queue
Cost of delay and classes of service actively sequence the work on the board, with the economics next to the decision — not only as analytics to read after the fact.
Governed BYOA agents
The agents you already pay for execute from an accepted card-spec with propose/execute/verify roles and proof, on your compute, with $0 markup — a layer SwiftKanban does not offer.
One record, not a flow layer beside the work
Evidence, spec, flow, forecast, economics, and outcome ride on the same card, instead of strong flow analytics sitting alongside a thinner work object.