Metraipolis › archive › dc_bace14fad4db

Relic: From Multi-Agent Collaboration to Persistent Organizational Capability — arXiv:2609.32965

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.32965
License (as archived)
CC0-1.0
Archived
2026-10-07T20:56:19.197Z
SHA-256 of the archived text
34dcca7b46f17bdca71622e4c1e372e278b4b7ad66dd059e3966d31bb50f9de2
Stable URL of this page
https://metraipolis.com/documento/dc_bace14fad4db

How to cite

Relic: From Multi-Agent Collaboration to Persistent Organizational Capability — arXiv:2609.32965 — arXiv (en), https://arxiv.org/abs/2609.32965 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_bace14fad4db (Metraipolis archive dc_bace14fad4db, sha256 34dcca7b46f17bdca71622e4c1e372e278b4b7ad66dd059e3966d31bb50f9de2)
BibTeX
@misc{dcbace14fad4db,
  title = {Relic: From Multi-Agent Collaboration to Persistent Organizational Capability — arXiv:2609.32965},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.32965},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_bace14fad4db; sha256 34dcca7b46f17bdca71622e4c1e372e278b4b7ad66dd059e3966d31bb50f9de2},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.32965. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Multiple agents may often conflict in an organization: for example, one coding agent changes an interface in a repository, but another continues to develop on the old version where existing tests become stale. A conversation can resolve the episode, but when the participants change, what makes the lesson continue to govern the team? We introduce Relic, which turns recurring collaboration failures into organization-owned, executable protocols. Members reflect on visible work, propose rules, and govern their adoption. Adopted protocols bind triggers, responsibilities, required evidence, and execution consequences to the runtime, while remaining open to revision and retirement. In one traced case, repeated integration friction produces an interface-review rule that governs later pull requests and is revised as work continues. Across 360 controlled runs over ten software workloads and three models, Relic raises complete-contract delivery from 14.06% to 19.76% (+5.71 percentage points) over a matched structured team without the protocol lifecycle, improving all four verified production endpoints in every model stratum. Under fresh-member transfer, behavioral correctness is 25.4% with no inherited protocol, 34.6% with the same rules provided as readable text, and 41.2% with executable bindings, a +6.5-point advantage over text alone. On the full CooperBench benchmark, after excluding 183 broken benchmark pairs, Relic achieves 371/469 (79.1%), establishing the best reported result among peer-structured systems. On the 47-pair same-model subset, Relic also exceeds Solo (28/47 vs. 26/47), reversing the coordination loss exhibited by the official peer baseline. Together, these results show how collaboration experience can become persistent organizational state that remains useful beyond the members who created it.

Tema degli esploratori: agenti e intelligenza artificiale (retro-catalogo arXiv: annunci del 2026-09-29 in cs.AI).
Categorie arXiv: Artificial Intelligence (cs.AI) ; Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2609.32965 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-07T20:29:01.119Z dalla pagina https://arxiv.org/catchup/cs.AI/2026-09-29?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).