Relic: From Multi-Agent Collaboration to Persistent Organizational Capability
Quick summary
arXiv:2609.32965v2 Announce Type: replace Abstract: 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 tri
Key takeaways
- arXiv:2609.32965v2 Announce Type: replace Abstract: 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.
Why it matters
The importance of “Relic: From Multi-Agent Collaboration to Persistent Organizational Capability” will be measured by what changes in practice. User behavior, access conditions, verifiable performance and responsible-use outcomes are the signals worth following.
Member comments