Skip to content
ParamergeParamerge
Stephen Lieberman
Through Paramerge
Contact

PAN Lab example

Guided walkthrough: agentic low-oversight office

A walkthrough-only version of the agentic low-oversight office: an AI assistant that also acts as an autonomous agent, a stretched staff supervising many automated actions at once, and — added for the tour — the Outside System pathway every workplace has, so the guided walk can show what the Privacy gauge watches. Sideways pathways run through it too: coworker-to-coworker contagion and agent-to-agent hand-offs, with the peer checks that would catch them switched off by default. In the sociotechnical simulation — a modeled office, not a real one — errors stick here about 75% of the time, versus 20% and 16% next door.

Stylized model of a documented deploymentCaseworker documentation & copilots

Open this example in PAN Lab v0.1 to apply pressures and levers and watch what the system does.

What this models

This example runs on the Agentic low-oversight office (walkthrough) network: 5 components and 11 pathways between them. Every context in the Lab is a stylized model, never a reconstruction of any actual deployment, and each assumption behind it carries a provenance label.

Evidence base: 4 assumed · 1 published baseline. In the Lab, the shaded evidence band behind each headline readout draws its width from the least-established class below.

  • baseline

    How often errors stick in this office (≈75%) comes from the sociotechnical simulation, not from measuring a real office.

  • assumed

    The model's raw error output is held identical across all three office cultures; only oversight differs.

  • assumed

    Verification behavior is treated as homogeneous within the office.

  • assumed

    Peer pathways are authored on both signs, matching the agentic office: agent-to-agent chaining and coworker contagion run at baseline, while the inhibiting peer checks (second opinions, cross-model verification) start closed — this culture's defining absence. The agent coupling is left privacy-neutral here (unlike the base office) so the tour's one privacy demonstration stays the egress paste.

  • assumed

    This context is a walkthrough-only variant of the agentic low-oversight office: it adds the Outside System and its data-leaving pathway so the guided tour can demonstrate the Privacy gauge. That pathway carries nothing until an unsanctioned-tool pressure opens it.

Sources and evidence

What this example rests on, claim by claim. Every entry resolves to the same ledger the Evidence Registry publishes.

  • In the sociotechnical simulation, the same AI in three modeled office cultures - stylized, not real workplaces - let errors stick at very different rates: roughly 75% under low-oversight autonomy, 20% under human supervision, and 16% under high-governance professional controls.

    scenarioillustrative PAN-run result

    No published source is attached to this claim yet.

Where this connects

Institutional pressures in this domain

  • Workload surge — Demand outruns staffing; per-case attention shrinks and review becomes triage.
  • Deadline pressure — Statutory or managerial timeliness rules reward fast approval of machine output over slow disagreement.
  • Reviewer bottleneck — One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
  • Staff turnover — Experienced skepticism leaves; new staff calibrate their trust on the tool itself.
  • Vendor opacity — The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Compliance over substance — Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

All of them in context on the Caseworker documentation & copilots domain page.

Levers available here and the patterns behind them

Documented case histories