Search papers, labs, and topics across Lattice.
This paper introduces the Persona-Execution Separation (PES) architecture, which allows LLM agents in governed organizations to maintain an evolving persona while ensuring that execution remains traceable and auditable. By separating persona and execution into different trust domains and utilizing a governed contract bridge, PES addresses the challenges of persona drift and execution transparency without compromising on security or compliance. The findings from a pilot case demonstrate that PES effectively maintains execution integrity despite changes in persona, highlighting its potential for regulated environments where both adaptability and accountability are crucial.
LLM agents can now evolve their personas without sacrificing execution traceability, thanks to a novel architecture that separates these domains.
Large language model (LLM) agents in governed organizations must let the persona (instructions, tone, self-presentation) evolve freely, while keeping execution (stateful, audited work) traceable. A single trust domain does not satisfy both cheaply. We present Persona-Execution Separation (PES): persona and execution reside in different trust domains, connected by a governed contract bridge. The persona is singly-homed and may drift; execution is faceless and audited. Status summaries may return; data bodies remain in the restrictive domain except a graded data-loss-prevention (DLP) exception; identity stays continuous. An approval matrix, DLP, and audit enforce the crossing. PES follows from three goals---free drift, execution traceability, and decoupling. Under LLM representational indistinguishability, any single-domain mechanism that meets all three must re-introduce typed change objects, an external gate, and a stable audit anchor: PES rebuilt at higher coupling cost. A development/pilot case in a regulated digital-employee platform records five decisions over one month, each with a rejected alternative. A mechanism check on the shipped implementation found no execution-side re-validation under persona perturbation (five model configurations) and no persona fingerprint on hard-asserted fields. A probe of a recovered pre-separation build found the governed execution path decoupled from the persona by omission, not by construction; a later wiring change could reverse that isolation, which PES makes an audited architectural rule. The pattern applies when multi-user deployment, execution audit, and expected persona churn hold jointly.
