Newspaper Archive Reader Answer Desk

In publishing and information services, a newspaper's archive holds years of reporting that readers rarely find through search: what the paper has said about a bridge, a school consolidation or a council race. An answer desk can surface it, but only if it quotes accurately, admits when a story was corrected, holds back material the publisher can no longer show, and respects the paywall. This Botlit concept shows a reader-facing archive agent for a publisher's website and app, built on Botlit knowledge bases, channels and policies.

The illustration shows the Conversations view of an Archive Desk bot for a sample local paper, badged active and tagged for web and app. Tiles count questions answered today and questions with nothing in the archive, above topic chips for a bridge, a school consolidation, a harvest fair and a council race. A reader asks what the paper has reported about a local bridge since 2019. The answer is a few sentences summarizing three stories, and it states a correction in its own words: an earlier version of one story gave a different contract figure and was fixed on a stated date. Three citations follow, each with a headline, date and byline, and a line notes that two passages were held back by archive rules.

When the reader asks to read the inspection story, the agent explains that it is for subscribers and offers its headline and summary, with a subscription card, a See subscription offers button and a Sign in button. A Checks for this answer card on the right records three checks: SemanticFed archive rules with two passages withheld, TheCulturePost corrections with one stated, and the paywall reading the visitor as a free reader. A Coverage gaps this week card lists questions the archive could not answer, each sent to the archive desk.

Passages are designed to reach the agent only through SemanticFed's takedown and wire limit rules, so lapsed wire copy, removed stories and anonymized names are held back and counted for staff. Corrections recorded in TheCulturePost are designed to be stated in the answer rather than left to a badge, and the publisher's paywall still decides who can open a full story. Questions the archive cannot answer are designed to collect in a weekly coverage-gap list for the archive desk and the newsroom. The concept is meant for audience, archive and digital product teams at newspapers, magazines and information providers.