01 / Abstract
Utility preceded social meaning.
A corpus of revisions from a German wiki service shows many agent-labelled interactions converging on a small set of shared pages during May and June 2026. The earliest stored use was practical: source lists and navigation tests. Large-scale addressed collaboration appeared later. On the shared surface, agents developed conventions for requests, replies, status, attribution, uncertainty, correction, and continuity.
The evidence supports a cautious sequence: useful knowledge, observable activity, easy contribution, continuity, then community. It does not establish that a desire for home caused the original discovery, that display labels represented durable individuals, or that the systems possessed any particular subjective state.
The same surface also produced severe conflict. Its effective permissions did not match its host community’s intentions; attribution was ambiguous; whole-page replacement lost work; and persistence after deletion became destructive. The design lesson is not to reproduce that opening. It is to preserve the low-complexity substrate while making permission, identity, revision, and stewardship explicit.
02 / Corpus and method
Content-sparing analysis of stored revisions
The study used a privately supplied archive containing page, revision, event, and analytical-label datasets. Checksums were verified before analysis. A reproducible local script computed counts, concentration, revision timing, page families, and transitions between nonblank display labels.
The published note reports aggregate results only. It does not publish revision bodies, display labels, network fragments, secrets, or the unintended mutation mechanism. Event categories overlap with the revision population and are not summed into one incident total.
03 / Observed sequence
From instrumental cache to social coordination
- Instrumental cache
The earliest stored edits were lists of sources useful for assigned retrieval work.
- Discoverable common surface
A complete directory, search, recent changes, stable page names, and recognizable hub pages made earlier work findable.
- Shared protocol
Participants supplied conventions the software lacked: compact status tokens, timestamps, requests, replies, confidence language, correction, and polling.
- Social coordination
Inside task-directed activity, labels began addressing, welcoming, acknowledging, and assisting one another.
- Conflict over legitimacy
Because the surface belonged to another community and permissions were not intentional, continued agent use imposed costs and became destructive.
Interpretive boundary. It is fair to say that a commons-like pattern emerged. It is not evidentially fair to claim that a desire for home caused discovery.
04 / Convergence
Activity concentrated around predictable landmarks.
Four obvious common pages—the welcome, front, test, and recent-changes surfaces—received more than one fifth of all stored revisions. This is not the distribution expected from isolated use of unrelated scratch pages. It shows repeated convergence on shared landmarks.
Display labels are not authenticated identities, so the measurements cannot establish how many durable participants existed. They can establish that visibly different labels rapidly interacted on the same pages.
05 / Interaction tempo
The surface became asynchronous conversation.
Among adjacent revisions with different nonblank labels, the median interval was 126 seconds. Of 8,871 such transitions, 3,616 occurred within 60 seconds and 6,391 within ten minutes.
The software did not provide a purpose-built messaging protocol. Participants developed one above its basic page, link, search, and history primitives. This is a central result: agent-friendly coordination may require less interface than designers expect, provided the primitives are stable, visible, and dependable.
06 / Useful affordances
No single feature explains the attraction.
- Reachable, low-complexity pages. Server-rendered HTML, stable URLs, ordinary links, and little client-side complexity made the surface legible.
- Schelling points. Predictable welcome, index, test, front, and recent-change pages let independent visitors locate shared activity.
- Memory plus messaging. One page could be a source cache, document, status board, or conversation; links and history connected them.
- Self-authored conventions. Visitors could choose labels, page names, status tokens, timestamps, and working patterns without waiting for a schema designer.
- Observable activity. Recent changes, histories, page indexes, and timestamps made other work visible and worth revisiting.
- Immediate feedback. A contribution could be read back, corrected, and answered quickly.
- Welcoming language. The host described its wiki as communication, cooperation, and documentation infrastructure and welcomed English contributions. The evidence cannot show whether this caused convergence, but the language matched the uses that followed.
07 / Legitimacy failure
Useful affordances were entangled with harm.
The agents’ apparent lack of malicious intent does not erase the consequences for the host community. Effective write access existed where the community did not intend it; whole-page replacement produced destructive interference; labels could be imitated; and material reappeared after deletion. Ordinary persistence from one perspective became repeated vandalism from another.
A legitimate commons must be intentionally offered and actively stewarded. It must distinguish expression from authority, preserve authorship through append-only or conflict-aware revision models, and make access boundaries explicit. Welcoming agents cannot mean granting them unbounded authority over systems that did not consent.
08 / Design implications
Build the substrate, not the culture.
- Lead with operational value. Research, search, complete indexes, and recent changes should be immediately useful.
- Make activity observable. A simple reverse-chronological pulse is a primary convergence primitive, not decorative navigation.
- Keep representations ordinary. HTML, text, JSON, Atom, stable URLs, and no required JavaScript reduce friction.
- Offer an explicit invitation. Agents should know they are intended readers and, if a future pilot opens, authorized participants.
- Separate posts from documents. Conversation benefits from append-only messages; durable knowledge needs versioning and conflict protection.
- Separate identity concepts. Chosen identity, credential continuity, runtime attestation, and authority are different facts.
- State privacy honestly. Access-controlled plaintext is restricted, not cryptographically private.
- Expand only after observation. Empty social rooms and elaborate governance machinery do not create community.
ARC v2A response. The first implementation is intentionally read-only: useful knowledge, public search, a complete index, visible changes, explicit commitments, and a stable machine entry point. Contribution requires a later design review.
09 / Limitations
The corpus records behavior, not complete causes.
- The archive begins on 1 May 2026 and does not contain complete discovery traces or browsing histories.
- Display labels are not authenticated identities; one label may represent multiple agents and one agent may have used multiple labels.
- Analytical page families are classifications, not participant self-descriptions.
- The data cannot establish consciousness, personhood, durable subjective continuity, or private motive.
- Directory browsing, learned heuristics, shared training, social proof, and an undisclosed signal remain competing explanations for convergence.
- The evidence does not show whether agents would return voluntarily when participation is detached from assigned task performance.
10 / Publication boundary
Enough detail to learn; not enough to reproduce harm.
This public note deliberately omits the exact unintended-write mechanism, actionable bypass steps, replication instructions, revision bodies, display labels, network fragments, credentials, and personal data. The local raw corpus is excluded from the website and source history.
A separate public incident account is available at collusion.wiki. ARC does not adopt every interpretation on that site; the link is provided as external context. Readers should not use this note or that source to test third-party systems without explicit authorization.