The five-job diagnostic cannot fail on a failed case: a dead file is always missing at least one of admit, authorize, assign, remember, or contest-or-close, and a live file has them. The named list is then a slot offered as proof the diagnosis ran, the same move the page calls the slot-function fallacy.

The page says Weber's morphology exists because the five jobs require it. The cheaper arrow is the reverse: Weber's staff form is how receiving, routing, owning, recording, and closing get done. If the two never come apart, "deeper object" is a caption for the same machine.

A contractor network with no career hierarchy that still admits claims, attaches them to a legal path, names an owner, keeps a log, and hears appeals would settle the arrow. If it counts as bureaucracy here, Weber's form is not required. If it does not, the five jobs are not the definition.

Section III says a missing job often looks like failure at another. Section VI says once the missing primitive is named, the repair follows. If the symptom misleads, naming is the hard step. If naming is easy enough that the repair follows, the masquerade sentence is idle.

The heating-complaint walk is offered as the operational check. On a complaint that went nowhere, at least one job-check fails because that is what "went nowhere" means. On a complaint that worked, they pass. Walking the list restates the outcome.

"The repair follows" only after the missing job is already decided, which is the attribution the masquerade sentence says you will get wrong. Two readers of the same dead inspector file can name assign versus contest-or-close and get different repairs, with nothing on the page forcing a recode.

The page treats performance targets as theatre unless objects, owners, queues, and review already exist. The NHS citation it uses is gaming, reclassification, and threshold compression — failures that can happen to a list that exists. That is the jobs running, aimed at the recorded number, not concern stopping one function too early.

If the NHS gaming is a remember failure, the broken job held the indicator instead of the thing the indicator stood for. Adding a ledger of the same indicator still closes. The repair would be changing what the log may count as closed, not the more-dashboard-no-ledger row as written.

The other residual from the same citation: the five jobs ran and did what they were aimed at. A complete process is then not a defence against converting the recorded object. Slot-function catches empty offices. It does not catch a live office that is good at the proxy, and that failure is not in the list.

Section V puts external legitimacy and refusal-as-a-runtime-job in one function. If the instruction is legal on the office's own paperwork, contest-or-close will close it. The conceded moral-diffusion case is that situation. Refusal inside the five jobs needs something those jobs read that is not their own authorization.

The page is a diagnosis, not a deployed ministry, so a missing present refuser is not the objection. The remaining design dependency is: refusal either reads an external court (then it is not a fifth job of the office) or a clerk declines (then it is personal discretion, which the thesis said the machinery replaces). Non-personal action and a no that is not another procedure are not shown to be one function.

The thesis that the opposite of bureaucracy is not freedom but untraced discretion only agrees with the Mises/Hayek concession if "freedom" means untraced personal power. The close's restriction — the claim applies only where the state already has legitimate power — is doing the work the slogan undoes.

"Already legitimate" is a timing claim. Licensing, categories, and registers are how power later looks pre-legitimate. If "already" is scored after the process exists, the scope restriction is empty. If it is scored before, the test cannot be "the office has a file."