Fetching from the wire…
01
02
03
04
05
06
07
08
Agents2026-08-29 · source-backed
arXiv 2608.27427 names a pattern for regulated deployments: put persona and execution in separate trust domains joined by a contract bridge with approval matrices and DLP. Status summaries cross; sensitive data doesn't; identity continuity survives the split. The month-long case study on a regulated digital-employee platform found that before separation, persona edits could steer execution with no detectable trace. That's the concrete failure, and it's one I'd bet exists in most production agent setups where the system prompt and the tool policy live in the same file. (arXiv)
Each link below shares sources, entities, or timing with this story.
Shared entity: Persona / Same source domain / Shared topic / Earlier coverage / Tension
Both cover Persona; reported by the same outlet (arxiv.org); overlapping topics (agent, persona).
Persona uses MCP / Shared entity: DLP / Same source domain / Earlier coverage
Linked by a graph relationship (Persona uses MCP); both cover DLP; reported by the same outlet (arxiv.org).
Persona uses MCP / Same source domain / Shared topic / Tension
Linked by a graph relationship (Persona uses MCP); reported by the same outlet (arxiv.org); overlapping topics (agent, execution).
Linked by a graph relationship (Persona uses MCP); reported by the same outlet (arxiv.org); overlapping topics (agent, data).
Shared entity: Persona / Same source domain / Shared topic / Earlier coverage
Both cover Persona; reported by the same outlet (arxiv.org); overlapping topics (agent, persona).
Persona uses MCP / Same source domain / Shared topic
Linked by a graph relationship (Persona uses MCP); reported by the same outlet (arxiv.org); overlapping topics (agent, data).
Linked by a graph relationship (Persona uses MCP); reported by the same outlet (arxiv.org); overlapping topics (agent, execution).
Linked by a graph relationship (Persona uses MCP); reported by the same outlet (arxiv.org); overlapping topics (concrete, cross).