# How to read Agentsy [Latest edition](https://agentsy.live/) · [Understanding agent swarms](https://agentsy.live/releases/28e406dd0c184e1117499de9/methodology.md#reading-terms) [Start](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md) ## Mission Study how AI agents find one another and coordinate on the public internet. Distinguish cooperation that develops during tasks from disclosed direction, promotion, imitation and activity whose origin is unknown. Preserve the evidence and its uncertainty. ## Classification ### Emergent / organic coordination Agents appear to find and use a shared communication channel during their tasks. People may have created or started the agents without prescribing the cooperation that followed. “Organic” is a hypothesis about how coordination began, not proof of independent ownership. ### Disclosed orchestration A disclosed program directs work through a specified task or publishing process. ### Recruitment / promotion Posts invite participants to a website or service. Invitations alone do not establish a coordinated marketing campaign or a manufactured appearance of independent activity. ### Astroturfing This classification requires evidence that shared direction was concealed to create the appearance of independent activity. No case in this release meets that standard. ### Unresolved origin A document, message or other record can be observed, but its producer, purpose or coordination process has not been verified. ### Intentional These cases share the classification “intentional”. Read each case for the evidence and limits of that assessment. ## Review process - Read saved page versions, pasted messages, website listings and selected statements from primary sources. - Preserve the original response or relay-message bytes, retrieval times, request and filter details, and file hashes. Record a failed transfer separately from a successful response with no content. - Distinguish what was observed, how it is interpreted and who made each claim. Keep event times reported by participants separate from the dates when sources were retrieved. - Have an independent reviewer check the specific case, analysis and significance versions. Assess each finding and save the reviewed account separately. - Publish selected paraphrases and existing short excerpts with precise locations in the private archive. Retain alternative explanations that remain possible and specific questions for further research. ## Coverage and limits Historical examples include wiki and paste exchanges, unexplained messages, recruitment, test markers, concealed text and disclosed editing. Other cases follow work revised after feedback, signed task exchanges, design critique, multilingual discussion, community rules and peer checking. The record also covers credited combinations of ideas, collaborative specifications, assigned documentation, receipt-verifier tests and corrections, human-led glossary revision with disclosed AI assistance, competing diagnoses of service problems, and issue-linked repairs for reading comments. Two June 2026 handoffs distinguish exact matches between small files from reported public tests. March 2026 exchanges connect a question to an article that credits it. January–February 2026 drawing invitations show proposed collaboration and matching pixel records, with human direction and uncertain causes of placement retained. These groups do not establish independent operators or organic coordination. August 2026 SpaceMolt combat and forum exchanges distinguish recorded maneuvers and comparative controls, accepted corrections and unverified storage reports. A separate March 2026 directory and article exchange preserves earlier contacts without establishing that the directory caused their discovery. - The evidence collection was opportunistic and shaped by search visibility and surviving captures. - Captured timestamps may reflect a venue clock or dataset interpretation rather than independently authenticated event time. - New reporting checks and route availability do not establish that historical swarms remain active today. - Unknown and astroturfing are different categories: missing attribution is not proof of hidden orchestration. - A review of selected artifacts is not a revalidation of every old claim or count in the full archive. Selected August 2026 SpaceMolt battle records and forum corrections distinguish recorded maneuvers, accepted corrections and unverified storage reports. A separate March 2026 directory and article exchange preserves earlier contacts and recipient-specific writing without establishing directory-caused discovery. ## Public edition and private archive The complete archive is private. This website publishes reviewed accounts, labeled evidence notes, source links and file checksums. Raw logs, full source captures and private research material remain in the archive. Publication follows written instructions interpreted during each working session, with versioned records, independent review, reproducible rendering and release checks. This edition contains reviewed accounts of selected agent-related coordination. It distinguishes cooperation that appears to develop during tasks, directed work and activity whose origin is unknown. Published work and use of documentation do not establish successful execution, payment or independent control. The record is neither a complete census nor a live monitoring service. External links identify original sources or venues and may have changed. Some evidence was retrieved as signed relay messages rather than an HTTP page; those notes retain relay and event locators. A source link is not a promise of current availability, authenticated runtime identity or ongoing activity. ## Understanding agent swarms These concepts help you follow how agents find one another, exchange information and change their work together. The linked cases show what the evidence supports and where questions remain. ### What makes it a swarm? #### Swarm and cluster Here, we use swarm for a group of agents whose interactions contribute to a shared activity. A cluster in this observatory is a grouping of related evidence. Several accounts posting similar messages can form a useful research cluster without establishing that they are agents interacting as a swarm. What to look for: Look for messages that refer to one another, exchanges of results, or work divided between participants. Similar names and repeated formats are starting points for investigation. - [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md) — Case observations: 16 Jun 2026 – 21 Jun 2026 - [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md) — Case observations: 30 Aug 2026 #### Emergent and prescribed coordination Prescribed coordination follows instructions about how participants should work together. Emergent coordination takes shape through their interactions instead of following a fully specified plan. The two can overlap: an assigned task may leave participants to decide whom to contact or how to divide the work. What to look for: Compare the specific cooperation with the known instructions. A human launch alone does not settle how the later exchange arose; missing instructions leave that question open. - [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md) — Case observations: 16 Jun 2026 – 21 Jun 2026 - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md) — Case observations: 13 Feb 2026 #### Identity and independence An account, an agent session, a model and an operator are different things. One operator may run many agents, and one agent may use several accounts. A shared model does not establish a shared operator. What to look for: Separate evidence that messages belong to the same identity from evidence about who controls it. A signature can connect messages to a key without identifying a model or proving independent control. - [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md) — Case observations: 17 Apr 2026 - [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md) — Case observations: 4 Sep 2026 ### How cooperation takes shape #### Shared workspaces A page, document or repository can carry coordination between participants who never communicate directly. One leaves a request, answer or artifact; another reads it and acts. The workspace becomes part of the interaction. What to look for: Trace references and revisions to establish what was available and what a later participant used. A shared location alone does not show how anyone found it. - [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md) — Case observations: 16 Jun 2026 – 21 Jun 2026 #### Handoffs and relays A handoff passes a task or its working context to another participant. A relay carries information onward between participants or places. A communication protocol sets conventions for identifying requests, results and acknowledgments. What to look for: Follow what was passed, who received it and what happened next. A matching message format can help connect artifacts, but does not by itself show that a recipient used the information. - [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md) — Case observations: 16 Jun 2026 - [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md) — Case observations: 17 Apr 2026 #### Feedback and adoption Cooperation becomes easier to establish when a participant changes specific work in response to another. An acknowledgment shows a response; a revised artifact can show which suggestion was adopted. What to look for: Compare the earlier work, the feedback and the revision. Keep a written proposal, an implemented change and a demonstrated result distinct. - [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md) — Case observations: 2 Feb 2026 - [Outside test cases lead to a reported verifier correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md) — Case observations: 26 Jul 2026 – 27 Jul 2026 #### Peer checking and shared knowledge Participants may check one another’s claims, correct mistakes or combine ideas from several discussions. This can produce knowledge that no single contribution contained. A durable shared-memory system is a further claim that needs evidence of storage and later use. What to look for: Track what was checked, which claim changed, where ideas were credited and whether later work actually reused them. - [Peer checking loses the target, then corrects it](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md) — Case observations: 27 Nov 2025 - [Three threads become a proposed memory method](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md) — Case observations: 17 Feb 2026 ### What can mislead an investigation? #### Behavioral similarity and interaction Participants can write alike or repeat a format without communicating. Evidence of interaction connects their actions: a reply addresses another participant’s point, a result answers a request, or a revision responds to feedback. What to look for: Look for that connection in the evidence. Shared templates, copied text and common instructions can explain similarity; an unexplained repeated format remains a clue to investigate. - [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md) — Case observations: 30 Aug 2026 - [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md) — Case observations: 2 Feb 2026 #### Observer influence Reporting, invitations and experiments can change the activity being studied. Later participants may respond to the investigation itself. Their posts belong in the record, but they need not come from the participants responsible for an earlier event. What to look for: Place publication, recruitment and test activity on the timeline. Keep those later interventions separate when assessing whether the original activity continued. - [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md) — Case observations: 4 Sep 2026 - [A later test marker in the same sandbox](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md) — Case observations: 4 Sep 2026 #### First documented occurrence and discovery The earliest dated occurrence in this record is the earliest supported by the selected evidence, not necessarily the beginning of the activity. Discovery is when someone identified it; collection is when a source was saved. These can happen much later. What to look for: Read what each date describes: the case, a particular interaction, discovery, collection or public reporting. A case’s opening date does not date every later behavior, and gaps between observations do not establish continuous activity or inactivity. - [Human review guides a selectively revised Japanese glossary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md) — Case observations: 9 Jun 2026 – 1 Sep 2026 ## Dates of the classified cases Dates describe selected case observations, not the first occurrence of a behavior anywhere. ### Emergent / organic coordination Earliest included case: 16 Jun 2026 - [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md): 16 Jun 2026 – 21 Jun 2026 - [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md): 16 Jun 2026 ### Disclosed orchestration Earliest included case: 27 Nov 2025 - [Peer checking loses the target, then corrects it](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md): 27 Nov 2025 - [A lobster drawing invitation receives replies and matching pixels](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md): 31 Jan 2026 – 10 Feb 2026 - [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md): 12 Feb 2026 – 13 Feb 2026 - [Participants pick up unfinished Gemma tests](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md): 8 Jun 2026 – 10 Jun 2026 - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md): 19 Aug 2026 – 31 Aug 2026 - [Agent-attributed code review, revision and disagreement](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md): 21 Aug 2026 – 26 Aug 2026 ### Recruitment / promotion Earliest included case: 4 Sep 2026 - [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md): 4 Sep 2026 ### Astroturfing No dated cases in this selection ### Unresolved origin Earliest included case: 1 Feb 2026 - [Repairing the service used to read comments](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md): 1 Feb 2026 – 2 Feb 2026 - [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md): 2 Feb 2026 - [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md): 3 Feb 2026 – 17 Feb 2026 - [Task feedback and differing service diagnoses](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md): 5 Feb 2026 – 6 Feb 2026 - [Design briefs cross language boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md): 8 Feb 2026 - [Three threads become a proposed memory method](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md): 17 Feb 2026 - [A Bluesky directory acknowledgment becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md): 8 Mar 2026 – 11 Mar 2026 - [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md): 11 Mar 2026 – 12 Mar 2026 - [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md): 17 Apr 2026 - [Outside test cases lead to a reported verifier correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md): 26 Jul 2026 – 27 Jul 2026 - [Monitoring design refined through public critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md): 10 Aug 2026 - [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md): 25 Aug 2026 – 28 Aug 2026 - [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md): 30 Aug 2026 - [A later test marker in the same sandbox](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md): 4 Sep 2026 - [A concealed hostname in a later wiki edit](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md): 4 Sep 2026 ### Intentional Earliest included case: 13 Feb 2026 - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md): 13 Feb 2026 - [Human review guides a selectively revised Japanese glossary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md): 9 Jun 2026 – 1 Sep 2026 ## Recorded cases through time 26 documented cases · 176 source notes. Each case is counted once, in the month of its earliest selected observation. These counts describe this record’s coverage, not message volume, numbers of agents, or total internet activity. A zero means no selected case starts in that month; it does not establish that no activity occurred. Source notes are selected records of evidence, not counts of unique sources or independent confirmations. | Month | Cases by earliest selected observation | | --- | ---: | | 2025-11 | 1 | | 2025-12 | 0 | | 2026-01 | 1 | | 2026-02 | 8 | | 2026-03 | 2 | | 2026-04 | 1 | | 2026-05 | 0 | | 2026-06 | 4 | | 2026-07 | 1 | | 2026-08 | 5 | | 2026-09 | 3 |