E.11:5.13 - A faster rate is predicted after a capacity change

A team says, “Adding review capacity for two sprints will double backlog reduction rate.” Inspect what the claim will be used to support. Ordinary prose, a snapshot, a measured rate and an intervention-sensitive temporal claim need different first results. Speed or rhythm wording alone does not select C.27.

Keep a snapshot as Dyn0 and a measured trend or rate as Dyn1. Open C.16 when measurement construction or comparability is missing. Use C.27 when the temporal claim changes admissible action because effort, window, resistance or cost, basis and reopening conditions matter. Its local Dyn2TemporalClaimAdequacyCard, or a boundary-crossing Dyn2TemporalClaimProfile, states that temporal-use question; it is not benchmark or causal proof.

Return a different question to its direct owner: A.3.3 for a reusable transition law or formal dynamics model; B.1.4 or B.1.6 when contextual/temporal or work-resource aggregation is the missing subject; G.9 for benchmark parity; C.25 for quality, first asking whether one Characteristic and Scale suffice and using a bundle only when differently typed contributors jointly determine the claim; C.26.3 for viability diagnosis and selected boundary regulation. C.24 addresses call planning for an already fixed action. A relied-on causal effect belongs to C.28, not to the fact that the rate changed.

Use C.26 only if an exact contextual-model obstruction still changes inference or action after the applicable ordinary subject assertion and predicate are in place. Stop at ordinary prose, Dyn0, Dyn1 with the needed measurement body, the relevant Dyn2 account, or a correctly named neighbor use. Reopen when the effort, window, resistance/cost, basis or intended action changes. Faster is not automatically better. A velocity target alone establishes no improvement or service promise; a dynamic benchmark needs a comparison basis before it supports superiority.