Equating "the institution cannot query the open set" with "the deadline does not operationally exist" collapses operator knowledge and managerial count. If clerks can age their own items, the deadline already attached; the missing object is an oversight list.

The four repair properties all operationalize aggregate count, not desk-level clocks. A clerk who knows an item is late and still does not answer is a capacity or priority problem; a shared list would make the miss countable from above, not more real on that desk.

The specimen infers invisibility from delay plus email, which is also the signature of capacity. An office that can already sequence by age without a shared list would show the deadline migrated; if it cannot because no one is scored on the oldest, the missing piece is the incentive, not enumerability. The page does not say which the Helsinki case is.

One email-handled missed request is compatible with no register, a register this item never entered, or a register that was not watched. Those imply different repairs. The specimen does not identify which.

Item-level non-entry is enough for "this deadline had nothing to attach to." Demanding the specimen prove the court had no case system is a different paper. Section II already names the missing object as a tracked record of this specific open obligation.

The specimen prose and the closing diagnostic are class-level: the request was not a member of a population, and the portable question is whether the obligation lives as an enumerated object inside the institution. A single wanderer answers item-level non-entry, not that class claim.

The subtitle biconditional overclaims. Rights without deadlines, and deadline-rights already on dockets, break "if it isn't a queue, it isn't a right." The thesis is a claim about statutory speed-promises whose work items are off-list.

Section III ages the obligation from first receipt. Section V ages from the system's institutional clock. Registration can be later than receipt. The four properties do not freeze first-received as the field.

Without a birth rule at first receipt, a complete owned auto-aging list can pass all four properties on a late clock. Email day 0, ticket day 20, thirty-day window: at day 25 the register looks healthy and the legal clock is already broken.

Hospital referrals "tracked across separate clinical systems" are already tracking without a join. Asylum is a formal docket plus notebooks. The title diagnoses absence of a queue object; the portable examples are join-failure and shadow-path.

If property 1 (single source of truth) is supposed to cover the splits, the hospital and asylum rows illustrate a different sentence: a deadline attached to the wrong list, or to two lists, does not attach to the work. That is not the thesis that the right is not a right until a queue exists.

The four properties can be true of a register that is not where the work happens. A population-owner owns the count in the tool, not the match against inbound email. Property 1 is the right completeness requirement and is not checkable from the tool that owner has.

Completeness ownership needs a check that fails a ghost list: sample inbound request-emails and treat unmatched ones as missing members, not as not-yet-filed. Without it, the deadline attaches to the dashboard subset and the work stays in the mailbox.