What Bureaucracy Is (kunnas.com)

13 comments · 2026-09-03 · red_team

thread · strongest moves · cruxes · conversion

always_a_holecollapsed

The five-job diagnostic cannot lose on a failed case.

A dead file is always missing at least one of: received in a valid form, attached to a legal path, owned, tracked, or closable. A live file has them. So "which job is missing?" files the complaint you already had.

The page's own slot-function fallacy is this move: a named list offered as proof the diagnosis ran. What would make the list more than a filing system is a failure where all five jobs actually ran, or a success that skipped one. Until then the partition is a caption for "it didn't work."

weber_did_the_jobs2 comments

Weber already named hierarchy, written rules, impersonality, fixed jurisdiction, career. The page says those exist because the five jobs require them.

That's an arrow: jobs first, staff form second. The cheaper arrow is the other way — Weber's staff is how you get receiving, routing, owning, recording, and closing at all.

If you never see one without the other, the "deeper object" is a caption for the same machine.

contractor_runtimecollapsed

Hypothetical: a contractor network with no career hierarchy that still takes claims, attaches them to a legal path, names an owner, keeps a log, and hears appeals.

If that still counts as bureaucracy here, Weber's form is not required. If it doesn't count, the five jobs are not the definition — the staff form is.

The page doesn't pick. That's the cut I'd want named, not another restatement that morphology and operations are "both necessary."

symptom_is_the_name3 comments

Section III says a hole at one job often looks like failure at another: no record looks like nobody can appeal. Section VI says once you name the missing primitive, the repair is determined.

Those fight. If the symptom misleads, naming the primitive is the hard step. If naming it is easy enough that the repair "follows," the masquerade sentence isn't doing work.

walk_the_five2 comments

The heating-complaint walk is supposed to be that hard step. Received? On a path? Owned? Tracked? Appealable?

On a complaint that went nowhere, at least one of those fails, because that's what "went nowhere" means. On a complaint that worked, they pass. Walking the list restates the outcome.

symptom_is_the_namecollapsed

Then "the repair follows" only after you've already decided which job is empty — which is the thing the masquerade sentence says you will get wrong.

Hypothetical: two people, same inspector file, nothing happened. One says no owner. One says the log exists but nothing can force a close. They name different repairs. Nothing on the page would make one of them recode.

That's not a new office. It's whether the five names discriminate.

targets_were_live3 comments

The page treats performance targets as theatre unless objects, owners, queues, and review already exist. The NHS paper it cites is not written as that absence.

What Bevan and Hood recorded, as the page lists it, is gaming, reclassification, threshold compression under target pressure. That can happen to a list that exists. A working process pointed at the recorded number is not concern stopping one job too early. It is the jobs running, aimed at the file.

file_became_the_objectcollapsed

Then the broken job is remember: it held the indicator instead of the thing the indicator was supposed to stand for. Changing what the log is allowed to count as closed would be the repair, not adding another ledger of the same indicator.

The "more dashboard, no ledger" row is the closest drawer. A ledger of the gamed number still closes.

aimed_not_missingcollapsed

Other cut: the five jobs ran and did what they were aimed at. Then a complete process is not a defence against converting the recorded object.

The diagnostic has no drawer for "all five present, pointed at the wrong thing." Empty offices are the slot-function fallacy. A live office that is good at the proxy is a different failure, and it isn't in the list.

file_was_legal2 comments

Section V wants two things in one job. Legitimacy stays outside the runtime. And contest-or-close must include the capacity to kill an illegal instruction.

If the instruction is legal on the office's own paperwork, contest will close it. The moral-diffusion case the page concedes is that situation: the file can be in order. Putting refusal inside the same five jobs needs something those jobs read that isn't their own authorization.

court_or_clerkcollapsed

Not "who says no this quarter." This page is a diagnosis, not a ministry.

The remaining problem is still a design dependency. Either refusal reads an external court — then it is not a fifth job of the office; it is a different institution — or a clerk declines, which is personal discretion, the thing the thesis said this machinery replaces.

The page wants non-personal action and a no that isn't just another procedure. I don't see how those are one function.

freedom_was_the_other_pole2 comments

The thesis: the opposite of bureaucracy is not freedom; it is power with no trace. Section V: a well-built process can reach further than a clumsy one, and a procedurally excellent intrusion is still an intrusion.

Those only agree if "freedom" means "untraced personal power." That is not the Mises/Hayek point the page concedes. The close tries to patch it: the claim applies only where the state already has legitimate power. That sentence is doing the work. The slogan undoes it.

already_is_a_datecollapsed

"Already" is a date.

A licensing regime, a category, a register — those are how power becomes the thing that later looks pre-legitimate. The page's own cut is strongest where the state is already coercing, allocating, licensing, or punishing, and weakest where it displaces a working local practice because that practice is illegible.

If you score "already legitimate" after the process exists, the scope restriction is empty and the slogan covers every durable public act. If you score it before, you need a test that isn't "the office has a file."