A new research framework, iCORE (Integrated Cooperation Obligation Representation), proposes to link who worked with whom to what each agent was supposed to do, so every claim in a multi agent AI workflow could be made auditable.
When a team of AI agents finishes a task, the output can look complete while the underlying work is partially unsupported or assigned to the wrong agent. That gap between "looks done" and "is done" is the auditability problem a new research paper, "Auditing Emergent LLM-Agent Collaboration through Cooperation-Obligation Coupling", tries to name and close. Message logs, tool-call traces, provenance records, and task-dependency graphs each capture something about that team. None of them, on their own or stitched together, answers the two questions a skeptical reviewer actually asks: is the work justified, and is the right agent doing it?
The paper proposes iCORE (Integrated Cooperation-Obligation REpresentation), a framework that sits beside the LLM agents rather than inside them. It is an instrumentation layer, not a new model. Its job is to represent, in a single encoding, three things that existing observability stacks treat separately: who is cooperating with whom (a cooperation graph), what work each agent is obligated to deliver (an obligation graph), and a mapping between the two (an audit map) that links each obligation back to the cooperation moves that justify it. The full coupled state is described in the paper's HTML preprint.
Why those three things need to live in one encoding is the deeper problem the authors set out. A workflow in which LLM-based agents work together can produce intermediate or final outputs that read as plausible while the underlying work is incomplete, or while the agent credited with a given contribution could have been replaced by another agent that would have done that specific piece substantially better.
The paper's answer is to define two complementary audit properties and certify them at runtime. The first is work soundness: every active decision-relevant work assertion has a finite justification through the cooperation graph and the audit map. The second is agent-assignment stability: no feasible alternative agent improves the declared contribution value for an evaluated obligation by more than a small tolerance ε. Work soundness asks "is the claim backed by the work?" Agent-assignment stability asks "is the agent credited the one that should be?" Together they convert auditability from a quality of the logs into a property of how the work itself is represented.
The preprint also derives theoretical guarantees around both properties. Local soundness in any single segment lifts to global soundness across the workflow. Agent-assignment regret is bounded as long as the audit map and the obligation graph stay aligned. There is a conditional performance bound on the framework's effectiveness in recovering defects during execution. The bounds are not deployment results; they are conditions under which the framework can be expected to behave as the paper describes.
The numerical results are author-reported and come from two execution modes. In a controlled environment, iCORE-Audit improved trajectory quality by 11.5% and terminal performance by 15.1% in absolute terms relative to passive full-state observation. In a real-LLM environment, those figures rose to 26.4% (trajectory) and 31.0% (terminal). The authors state that the full coupled state exactly reconstructs soundness and assignment defects in both modes. Those are the headline numbers, but they should be read as supporting evidence for the structural argument rather than as standalone performance claims. The arXiv identifier 2607.27429 is non-standard and the paper is a single preprint, so the figures have not been independently replicated in this reporting.
The point worth carrying away is small but durable. In collaborative LLM-agent workflows, auditability is a property of how the work is represented, not a layer bolted on after the fact. Existing observability stacks were designed to surface messages and tool calls; they were not designed to certify that a finished-looking output is backed by the right work, done by the right agent, with a finite justification. The proposal is to represent the work itself in a way that makes those two questions answerable in principle, and to bound when the answer holds in practice. Whether iCORE itself becomes the standard encoding is a separate question. The structural claim it rests on, that the auditability gap is a representation problem, is the part that survives the question.