ConcurProof checks whether a multi-agent system is actually concurrent. The same checkout-outage task runs sequential, naive-parallel, and reactive. Four agents work the incident while an observer scores overlap and whether they really reacted to each other.
What it does
ConcurProof solves the problem of multi-agent systems claiming to be concurrent when their agents may only be running at the same time without meaningful collaboration. It executes the same controlled task using sequential, naive-parallel, and reactive-concurrent agents, then records their timing, interactions, reactions, and answer quality. ConcurProof uses interaction graphs and ablation tests to determine whether agent-to-agent reactions genuinely improved the result, producing an auditable concurrency certificate.
How the agents run concurrently
The Evidence, Hypothesis, Critic, and Verifier agents run as separate asynchronous Mozaik v4 loops. In reactive-concurrent mode, they overlap in time and exchange events through a shared interaction stream, allowing one agent’s output to trigger another agent while the others are still active. ConcurProof records timestamps and causal links for every reaction, then compares this behavior against sequential and isolated-parallel baselines.
Newsletter
For developers who want to learn how to build self-organizing agents.
3alet Hackathon · 30–31 October, Novi Sad + online. Registration is open. 60 seats on site.
Register