For the deadline to attach to an item, who must be able to see the age — the operator holding it, or someone who can range over the population?

Do the four properties make the deadline real at the desk, or only countable from above?

Is the Helsinki miss an unqueryable population, or a known backlog no one was scored on reducing?

Which absence does the circulating tree show: no register, unentered item, or unwatched register?

Is a wanderer enough for the specimen's job, or must the court's whole document-request class be shown untracked?

Can one unentered request carry a class-level diagnostic about how the institution holds that kind of work?

Is the load-bearing claim the diagnostic sentence, or the subtitle's biconditional about rights as such?

Does the age field start at first receipt, or at the registration click?

Can the four properties pass on a register whose received-date is the registration click?

Are hospital and asylum rows the same failure as a request that never became an object, or two other failures?

Are the split-list rows evidence for "no queue," or for "deadline attached to the wrong list"?

Can the population-owner detect work that never entered the tool, using only the tool?

What observable would fail a complete-looking register that is only the entered subset of the work?