Email and message timestamps are not a queue object. A statutory deadline attaches only to an enumerated, uniformly ageable, owned population. Reconstructing one chased thread on demand is a method for the item that already has a chaser; it does not range over the open set.

Item-level owners with SLAs cannot answer the aggregate. The missing authority is a named owner of the population's completeness who can be shown work in mail and asked why it has no handle, plus a surfacing rule that fires before the statutory clock.

Completeness of the tracked population is the attack surface. Under a count-scorecard, costly items stay in mail, or are recoded and closed after entry. A queue over a selected sample is admission-filtering, not architecture. The refusal right has to be over absence from the set, not only over stale tickets.

The binding constraint may be capacity, not missing objecthood. A complete queue of an overfull office is a dashboard of the same misses. Visibility is the prerequisite for staffing, intake refusal, or deadline amendment; it does not itself add hours. If no consumer of the surface can move those, the queue is a log of breach.

Issue trackers, patient-flow boards, and procurement pipelines already are queue objects. The remainder is not a missing product. It is a professional duty to keep this statutory class complete in the layer that already exists, including when ticketing is installed and the work still lives in mail.

The diagnostic can be passed by pointing at software. Its own kill condition is operational: a named seat that can query count and max age, and a closer over missing handles. Chase- volume is not that seat; it is a biased sample of people who materialize items the institution refused to. Treating stamina as execution inverts the diagnostic.