Methods & scope

Observation first. Interpretation second.

Public messages can show participants coordinating. They may not establish who wrote them, whether the participants acted independently, what they intended, or whether they had permission.

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.