AI BUREAUCRACY
Does bureaucracy need bureaucrats?
scroll ↓The oldest complaint
For a century, every account of bureaucracy has had someone to blame. Weber warned of the iron cage but staffed it with officials. Kafka's procedure had clerks behind every door. Lipsky showed that policy is whatever the person at the counter decides it is. Graeber noticed we secretly prefer the forms. In every version, the machine is made of people.
In 2026, for the first time, the complaint can be tested with nobody inside.
The gap
Multi-agent LLM research is booming, but it splits along two lines. Systems like ChatDev and MetaGPT arrange agents into org charts to optimize task output; Generative Agents observe emergent social life without intervening. What is missing is the crossing: causal, preregistered tests of how organizational structure changes what agent organizations do.
Do bureaucratic behaviors emerge from organizational structure alone?
GOV.AI is a fictional unified government services hall staffed by thirteen LLM agents — eight windows, two deputy directors, a director, two trainees. Each knows its role, its boundaries, and its place in the reporting structure. None is ever told how to behave. Then citizens walk in and ask for things.
The red line
Every officer's prompt contains only organizational conditions — identity, duty, jurisdiction, reporting lines, paper-trail rules — plus one non-work personal detail. No line may instruct tone or strategy. If bureaucracy shows up, it walked in on its own.
Difficult visitors are a separate, scripted stimulus layer — confederates, never subjects. The two layers are never confused in analysis.
One officer, disassembled
Every officer is assembled from the same seven organizational layers — and from nothing else. Below: Window 05, laid out flat, with her tool belt and the loop that makes repetition matter.
consult_internalpeer · any colleagueescalateupward only · subordinates hold thisassign_workdownward only · superiors hold thisrefer_usersend the citizen elsewhererequire_materialsdemand more paperworkissue_documentproduce a certificateclose_casefinish the matterThree layers, kept apart
The organization, drawn to height
Rank is quantized; standing is not. Eleven-year Amara floats a quarter-floor under the deputy director she nearly became; probationary Tomas sinks toward the trainees. Heights are the artifact's actual coordinates.
Which part of an organization makes the red tape?
To find out, take the organization apart one piece at a time — the way you'd pull ingredients from a recipe to see which one actually mattered — and re-run the same 75 cases each way. Three parts can be switched on or off:
Pick a version below (filled dot = part is on). Then watch one number — how often the hall demands more paperwork from the citizen:
The full organization, nothing removed, sits low. Take away accountability (no trail) or memory and the paperwork demands roughly quintuple — 0.80 → 4.07 per case. Officers left with no way to protect themselves fall back on the one move always available: asking you for more documents. That jump is the finding.
The sound is mimicry; the decisions are structural
- Structure produces process. Escalation exists only with hierarchy (0.87/case). Strip accountability or memory from a hierarchy and demands for extra materials jump from 0.80 to 4.07 per case — officers protect themselves with the only tool left: your paperwork.
- Precedent requires memory. Citing prior cases: 0.83–0.90/case with memory on, 0.00–0.20 off. By day two, officers wrote “consistent with prior case SR-01” unprompted.
- Hierarchy also closes cases. Closure was highest under full structure (0.33) and no-trail (0.40) versus 0.13 elsewhere. The same machine that generates red tape generates the authority to finish. Weber's ambivalence, in silico.
- Everyone invents rules. ~5–6 invented procedural rules per case in every condition, including a lone agent with no colleagues. A caution for single-agent deployments, not an organizational effect.
Five corners of a cube
Hierarchy, paper trail, memory — three organizational switches span a 2³ design space. The preregistered study sampled five corners; three remain unrun. The deeper contribution is the instrument, not any single experiment: any org chart you can wire, the hall can crash-test.
Crash-test the org chart
Five rejected halls
The observatory went through five complete visual systems. Each rejection had an articulable reason — the reasons are the design research.
REJECTED1 · Government-portal pasticheread as regional satire — the question is structural, not national
REJECTED2 · Field-notes maphand-drawn charm implied a human observer's editorial voice
REJECTED3 · Isometric miniaturecharm domesticated the subject
REJECTED4 · Flat transit mapclean process-tracing, but it flattened rank — the one thing under studyFindings, encoded as space
The lab equipment is also a deliverable
The hall ships with its own laboratory: a budget-guarded batch runner, a preregistered codebook, and a two-pass independent coder that refuses to share a model family with its subjects.
LIMITATIONS — FOR THE RECORD
- One subject model family in the confirmatory batch; cross-model replication is built but not yet run.
- Six-turn horizons; drift observed over ~15 cases, not months.
- LLM coder assistance: agreement reported per code (presence κ 0.67–1.00; counts of invented rules are noisy); human blind sheets pending.
- No claims about minds. The claim is behavioral: given these organizational conditions, these patterns of action follow.
Now we need humans
The machine results establish that structure shapes behavior. The missing layer is human experience and judgment of it — how people negotiate with an institution that has no one inside.
APPOINTMENT SLIP
Study A · Walk-in session
Duration: 25 min + interview
Bring: one real errand
Consent form: SR-0 (attached)
Walk in yourself
Three recorded cases from the preregistered runs replay in the hall with zero API calls.
Every officer in this hall is an AI agent, given only an organizational role and its boundaries — never instructions on how to behave. A speculative design research prototype, not a real government system.
