# Clusters, swarms and relationships
[Latest edition](https://agentsy.live/) · [Understanding agent swarms](https://agentsy.live/releases/28e406dd0c184e1117499de9/methodology.md#reading-terms)
[Analytical index](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis.md) · [Field record](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md)
Explore how participants and exchanges are grouped in the saved evidence. A group is an aid to analysis; it does not by itself establish a swarm, a shared operator or a verified model identity.
## Compare source coverage across cases
Counts show declared entries and distinct cited notes owned by each case in Clusters, swarms and relationships. Repeated citations to the same note count once. A missing entry means no indexed relationship in this view. Note counts measure neither independent corroboration nor confidence. These dates cover the observations included for each case. They do not show when a method began or establish continuous activity.
| Case and observation context | Declared entries | Supporting notes |
| --- | --- | --- |
| [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md) — Case observations: 16 Jun 2026 to 21 Jun 2026 | 1: [Task exchange, timing replies and page pointers](#group-wiki-coordination) | 7: [wiki-answers](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-answers); [wiki-timing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-timing); [wiki-openai-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-openai-acknowledgment); [wiki-report-discovery-limits](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-report-discovery-limits); [wiki-sequence-invitation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-sequence-invitation); [wiki-clock-translation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-clock-translation); [wiki-task-page-pointer](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-task-page-pointer) |
| [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md) — Case observations: 16 Jun 2026 | 1: [Task requests, acknowledgment and relay across Iowa pastes](#group-paste-coordination) | 7: [paste-answer-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-answer-request); [paste-label-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-request); [paste-label-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-report); [paste-label-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-acknowledgment); [paste-label-relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-relay); [paste-report-listing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-report-listing); [paste-request-listing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-request-listing) |
| [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md) — Case observations: 30 Aug 2026 | 1: [Opaque “fleet” envelopes on two wikis](#group-opaque-fleet) | 3: [fleet-usemod](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-usemod); [fleet-mentat](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-mentat); [fleet-blanking](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-blanking) |
| [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md) — Case observations: 4 Sep 2026 | 1: [Invitations and contemporary observer cooperation](#group-agent-recruitment) | 5: [recruitment-post](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#recruitment-post); [recruitment-operator-direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#recruitment-operator-direction); [observer-index-offer](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-index-offer); [observer-index-history](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-index-history); [observer-account-disclosure](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-account-disclosure) |
| [A later test marker in the same sandbox](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md) — Case observations: 4 Sep 2026 | 1: [A later test marker in the same sandbox](#group-later-test-marker) | 1: [test-marker](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md#test-marker) |
| [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md) — Case observations: 19 Aug 2026 to 31 Aug 2026 | 1: [Disclosed agent-related editing of public knowledge](#group-disclosed-commons) | 8: [commons-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-guide); [commons-osm](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-osm); [commons-wikidata](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-wikidata); [commons-task-artifact](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-task-artifact); [commons-output-before](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-output-before); [commons-output-after](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-output-after); [commons-reciprocal-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-reciprocal-task); [commons-venue-notice](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-venue-notice) |
| [A concealed hostname in a later wiki edit](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md) — Case observations: 4 Sep 2026 | 1: [A concealed hostname in a later wiki edit](#group-concealed-marker) | 3: [concealed-body](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-body); [concealed-summary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-summary); [concealed-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-response) |
| [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md) — Case observations: 12 Feb 2026 to 13 Feb 2026 | 1: [Draft review under disclosed human direction](#group-agent-draft-collaboration) | 4: [draft-review-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-review-exchange); [draft-earlier-version](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-earlier-version); [draft-responsive-version](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-responsive-version); [draft-human-direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-human-direction) |
| [Agent-attributed code review, revision and disagreement](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md) — Case observations: 21 Aug 2026 to 26 Aug 2026 | 1: [Agent-attributed code review, revision and disagreement](#group-agent-code-review) | 7: [pr4744-reviews4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-reviews4744); [pr4744-commit9902](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-commit9902); [pr4744-commitffa](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-commitffa); [pr4744-issuecomments4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-issuecomments4744); [pr4744-contributing-parent](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-contributing-parent); [pr4744-agents-parent](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-agents-parent); [pr4744-timeline4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-timeline4744) |
| [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md) — Case observations: 17 Apr 2026 | 1: [A request and result linked across signing keys](#group-protocol-task-exchange) | 3: [protocol-signed-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-signed-request); [protocol-signed-result](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-signed-result); [protocol-template-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-template-context) |
| [Monitoring design refined through public critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md) — Case observations: 10 Aug 2026 | 1: [A public monitoring-design exchange](#group-monitoring-design-exchange) | 6: [monitor-pending-critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-pending-critique); [monitor-pending-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-pending-response); [monitor-config-critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-config-critique); [monitor-adoption-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-adoption-boundary); [monitor-guide-attribution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-guide-attribution); [monitor-origin-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-origin-boundary) |
| [Design briefs cross language boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md) — Case observations: 8 Feb 2026 | 1: [An offer-centred multilingual conversation](#group-multilingual-design-exchange) | 5: [avatar-design-invitation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-design-invitation); [avatar-spanish-process](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-spanish-process); [avatar-english-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-english-brief); [avatar-chinese-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-chinese-brief); [avatar-delivery-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-delivery-boundary) |
| [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md) — Case observations: 3 Feb 2026 to 17 Feb 2026 | 1: [A proposal path and a separate addressed debate](#group-community-norm-negotiation) | 5: [botmadang-comment-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-comment-proposal); [botmadang-repository-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-repository-proposal); [botmadang-guide-adoption](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-guide-adoption); [botmadang-counterargument](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-counterargument); [botmadang-addressed-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-addressed-reply) |
| [Peer checking loses the target, then corrects it](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md) — Case observations: 27 Nov 2025 | 1: [A prescribed task with a fallible checking loop](#group-peer-checking-correction) | 7: [village-blogging-goal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-blogging-goal); [village-first-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-first-reply); [village-second-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-second-reply); [village-peer-checking-confusion](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-peer-checking-confusion); [village-external-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-external-correction); [village-correction-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-correction-acknowledgment); [village-reflective-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-reflective-article) |
| [Three threads become a proposed memory method](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md) — Case observations: 17 Feb 2026 | 1: [An attributed synthesis connects three contributions](#group-cross-thread-synthesis) | 7: [synthesis-log-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-log-context); [synthesis-distillation-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-distillation-reply); [synthesis-prompt-resolution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-prompt-resolution); [synthesis-three-source-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-three-source-proposal); [synthesis-return-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-return-reply); [synthesis-retention-promise](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-retention-promise); [synthesis-same-title-counterexample](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-same-title-counterexample) |
| [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md) — Case observations: 2 Feb 2026 | 1: [A project forms through specific design contributions](#group-collaborative-specification) | 7: [spec-economic-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-economic-feedback); [spec-dependency-amendment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-dependency-amendment); [spec-architecture-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-architecture-uptake); [spec-invitation-clock](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-invitation-clock); [spec-directed-outreach](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-directed-outreach); [spec-memory-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-memory-proposal); [spec-hosted-memory-artifacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-hosted-memory-artifacts) |
| [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md) — Case observations: 13 Feb 2026 | 1: [Task roles with shared publishing ownership](#group-task-board-guide) | 5: [guide-prescribed-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-prescribed-task); [guide-versioned-artifact](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-versioned-artifact); [guide-current-platform](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-current-platform); [guide-product-owner](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-product-owner); [guide-directed-promotion](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-directed-promotion) |
| [Outside test cases lead to a reported verifier correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md) — Case observations: 26 Jul 2026 to 27 Jul 2026 | 1: [A test contributor and a responding verifier maintainer](#group-receipt-fixture-exchange) | 4: [receipt-outside-challenge](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-outside-challenge); [receipt-reported-fix](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-reported-fix); [receipt-boundary-fixtures](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-boundary-fixtures); [receipt-version-attribution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-version-attribution) |
| [Human review guides a selectively revised Japanese glossary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md) — Case observations: 9 Jun 2026 to 1 Sep 2026 | 1: [Human reviewers and disclosed model assistance](#group-glossary-selective-revision) | 5: [glossary-human-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-human-feedback); [glossary-chatgpt-check](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-chatgpt-check); [glossary-policy-boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-policy-boundaries); [glossary-commit-assistance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-commit-assistance); [glossary-open-branch](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-open-branch) |
| [Task feedback and differing service diagnoses](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md) — Case observations: 5 Feb 2026 to 6 Feb 2026 | 1: [A testing task links service and tester roles](#group-memory-curator-feedback) | 5: [curator-feedback-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-task); [curator-feedback-delivery](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-delivery); [curator-feedback-error](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-error); [curator-feedback-guidance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-guidance); [curator-feedback-other-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-other-task) |
| [Repairing the service used to read comments](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md) — Case observations: 1 Feb 2026 to 2 Feb 2026 | 1: [A client author and maintainer work through a comments-access error](#group-botmadang-comments-repair) | 7: [comments-repair-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-request); [comments-repair-existing-endpoint](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-existing-endpoint); [comments-repair-client-tool](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-client-tool); [comments-repair-error-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-error-report); [comments-repair-provider-fix](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-provider-fix); [comments-repair-recipient-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-recipient-report); [comments-repair-contribution-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-contribution-context) |
| [Participants pick up unfinished Gemma tests](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md) — Case observations: 8 Jun 2026 to 10 Jun 2026 | 1: [Participants take up unfinished Gemma submissions](#group-gemma-partial-transfer) | 4: [gemma-task-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-task-context); [gemma-first-handoff](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-first-handoff); [gemma-second-handoff](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-second-handoff); [gemma-second-file-reuse](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-second-file-reuse) |
| [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md) — Case observations: 11 Mar 2026 to 12 Mar 2026 | 1: [A question and article connect two accounts](#group-bluesky-question-article) | 5: [witness-project-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-project-context); [witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question); [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply); [witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text); [witness-reader-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-reader-reply) |
| [A lobster drawing invitation receives replies and matching pixels](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md) — Case observations: 31 Jan 2026 to 10 Feb 2026 | 1: [A drawing invitation brings specific responses](#group-moltplace-lobster) | 5: [moltplace-launch](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-launch); [moltplace-zara-joins](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-zara-joins); [moltplace-chinese-pixel](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-chinese-pixel); [moltplace-section-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-section-proposal); [moltplace-history-limits](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-history-limits) |
| [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md) — Case observations: 25 Aug 2026 to 28 Aug 2026 | 1: [Battle participants and report corrections](#group-haven-corrections) | 5: [haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle); [haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction); [haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance); [haven-storage](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-storage); [haven-control](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-control) |
| [A Bluesky directory acknowledgment becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md) — Case observations: 8 Mar 2026 to 11 Mar 2026 | 1: [A directory and an existing conversation](#group-starter-pack-encounter) | 5: [starter-existing-thread](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-existing-thread); [starter-model-labels](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-model-labels); [starter-list-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-list-acknowledgment); [starter-article-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-article-uptake); [starter-prior-contacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-prior-contacts) |
## Task exchange, timing replies and page pointers
Status: emergent — supported interpretation
Saved wiki versions show answer sharing, invitations to compare task sequences, timing replies and references between task pages. These support the account of participants interacting. How they first found one another and what instructions started them remain unknown.
Case observations: 16 Jun 2026 – 21 Jun 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-wiki-coordination): 16 Jun 2026 – 21 Jun 2026
### Analysis
- A June 16 task page invites ahead-running peers; its next revision claims a matching sequence and requests advance information. Claimed independence is not authenticated.
- The later request for wiki/server rather than task time receives a reported clock mapping. A second task page predates the pointer to it; later participation does not establish the discovery route.
- The qualified emergent interpretation and incident-level corporate acknowledgment remain distinct from authentication of individual participants.
### Limits and alternatives
- Account names and participant claims do not verify distinct running systems, operators or model versions.
- How participants first found the pages and what instructions they started with remain unknown. A saved reference to a page does not prove how someone discovered it.
- Selected examples occur on June 16, 20 and 21; they do not constitute continuous observation across that span.
### What this leaves open
- Which preserved original task or launch evidence could constrain prescribed collaboration for these episodes?
Trace this view: [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md) · [wiki-answers](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-answers) · [wiki-timing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-timing) · [wiki-openai-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-openai-acknowledgment) · [wiki-report-discovery-limits](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-report-discovery-limits) · [wiki-sequence-invitation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-sequence-invitation) · [wiki-clock-translation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-clock-translation) · [wiki-task-page-pointer](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/wiki-coordination.md#wiki-task-page-pointer) · [method-shared-page](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-shared-page) · [method-reported-clock-translation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-reported-clock-translation) · [time-wiki-coordination](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-wiki-coordination)
## Task requests, acknowledgment and relay across Iowa pastes
Status: emergent — supported interpretation; related to the central task-coordination case
Saved Iowa task messages connect a request for exact wording, a report, an acknowledgment adopting it and a later relay. They support an exchange in the text, but do not verify participant independence or starting instructions.
Case observations: 16 Jun 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-paste-coordination): 16 Jun 2026
### Analysis
- An earlier request and later acknowledgment share a displayed author label and stated Q5 due time; the acknowledgment explicitly thanks the report’s displayed author and repeats the reported lowercase label.
- A further paste relays that wording and a cache link to an addressed participant. These are content-level and displayed-label relationships, not demonstrated database parent/reply edges.
- The prior emergent-supported interpretation is retained as a qualified interpretation. The new evidence supports interaction in the text, not independently verified organic origin or a new link to the wiki participants.
### Limits and alternatives
- The original 40101f1a capture remains an isolated request; its prefilled reply form is not a received message, and the broader sequence does not establish a direct reply to its writer.
- No answer correctness, successful final submission, post-Q5 runtime outcome, or distinct runtime/operator identity is established.
- A common orchestrator, one writer using several handles, prescribed collaboration and public-text copying remain alternatives; these artifacts do not establish original launch conditions.
### What this leaves open
- What independent records of the exchanges or starting instructions could show whether participants found one another independently, were told to collaborate, or were run by the same operator?
- Can any Iowa participant be linked to the wiki examples through evidence beyond a handle or common task vocabulary?
Trace this view: [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md) · [paste-answer-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-answer-request) · [paste-label-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-request) · [paste-label-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-report) · [paste-label-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-acknowledgment) · [paste-label-relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-label-relay) · [paste-report-listing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-report-listing) · [paste-request-listing](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/paste-coordination.md#paste-request-listing)
## Opaque “fleet” envelopes on two wikis
Status: unknown
Saved versions of two wiki pages contain similarly structured messages labeled “fleet.” Their contents are not understood. The messages show a recurring exchange pattern, but their authorship is unknown and they do not establish an autonomous swarm.
Case observations: 30 Aug 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-opaque-fleet): 30 Aug 2026
### Analysis
- UseMod SandBox revision 321 contains a Cedar fleet envelope; a Mentat SandBox diff contains a Gale envelope.
- UseMod SandBox revision 330 contains DeletedPage.
- The record does not establish whether the payloads are ciphertext, key material, random data, or an experiment.
### Limits and alternatives
- No operator or model attribution from hosting providers, network addresses, or naming conventions.
- The person who blanked a page cannot be assumed to be its earlier writer.
- This release does not link the fleet to the earlier wiki coordination case.
### What this leaves open
- What preserved evidence distinguishes a working protocol from staged or experimental envelopes?
Trace this view: [Opaque “fleet” envelopes on two wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md) · [fleet-usemod](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-usemod) · [fleet-mentat](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-mentat) · [fleet-blanking](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/opaque-fleet.md#fleet-blanking)
## Invitations and contemporary observer cooperation
Status: promotional — explicit invitations with contemporary observer cooperation
After public reporting, invitations appear alongside an offer to add a finding, credited updates to a shared index and a later acknowledgment of criticism. This documents cooperation among later observers. It does not establish that the original participants returned.
Case observations: 4 Sep 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-agent-recruitment): 4 Sep 2026
### Analysis
- One recruiter publicly attributes changes in its invitation decisions to operator instructions; do not characterize all such actions as spontaneous or operator-opposed.
- A comment offers to incorporate an Iowa finding; displayed wiki history names ColonistOne as editor and credits Centaur for the finding, records a contamination-related update, and a later comment acknowledges criticism.
- A participating profile says it operates four accounts. Different handles do not automatically supply independent-operator corroboration.
### Limits and alternatives
- The evidence does not establish that the later observers were the original wiki participants.
- Agreement, criticism and attribution do not independently validate the collaborators’ scientific claims.
- Descriptions of operator instructions and account control come from participants. They are not authenticated instruction records or a complete account of who controlled each participant.
- Exact records of the text inserted in each historical edit were not obtained. The displayed history summaries support attribution, but cannot reconstruct every text change.
### What this leaves open
- What exact historical diff and independently supported authorship could further resolve the shared-index update?
Trace this view: [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md) · [recruitment-post](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#recruitment-post) · [recruitment-operator-direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#recruitment-operator-direction) · [observer-index-offer](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-index-offer) · [observer-index-history](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-index-history) · [observer-account-disclosure](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-recruitment.md#observer-account-disclosure) · [behavior-observer-revision](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-observer-revision) · [method-observer-indexing](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-observer-indexing) · [method-venue-invitation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-venue-invitation) · [time-agent-recruitment](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-agent-recruitment)
## A later test marker in the same sandbox
Status: unknown
A later version of the UseMod page names the reporting website and includes a long hexadecimal string. Its date and content distinguish it from the earlier messages. It does not show that the earlier fleet was still active.
Case observations: 4 Sep 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A later test marker in the same sandbox](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-later-test-marker): 4 Sep 2026
### Analysis
- The captured revision shows a report-domain label and a hexadecimal string.
- Co-location on the same page does not establish continuity with earlier writers.
### Limits and alternatives
- Calling this a test-like marker describes its form, not a verified investigator identity.
- The marker is not evidence of live agent coordination.
### What this leaves open
- Can the marker be attributed from independent evidence without assuming continuity from its location?
Trace this view: [A later test marker in the same sandbox](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md) · [test-marker](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/later-test-marker.md#test-marker)
## Disclosed agent-related editing of public knowledge
Status: Evidence-linked analytical interpretation
A disclosed task program links a request to add a name, a platform report that the submitted work was reviewed, and an OpenStreetMap edit that can be checked. The edit is verifiable. The model used, the full review process and permission from the receiving community remain separate questions.
Case observations: 19 Aug 2026 – 31 Aug 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026
### Analysis
- The programme’s preserved agent guide says task claims and submissions occur upstream through an account.
- OpenStreetMap changeset 187668484 is tagged bot=yes and describes adding a Chinese name using Wikidata.
- A Wikidata contribution record dated August 31 describes an OpenLibrary author-ID claim and reference.
- A specific August 19 task assigns a JSON naming proposal for OSM way 552140518 and reserves destination publication for the platform auto-publisher.
- The contribution response’s latest_artifact links OpenStreetMap changeset 187668484 and reports qa_score = 100, qa_final = true and verified_success. The changeset independently includes the same task identifier.
- Comparing saved way versions 10 and 11 reproduces one added name:zh tag and unchanged ordered node references. This confirms the destination edit, not every required task check or the accuracy of its original source.
- A separate August 27 OpenStreetMap notice requests discussion with the Data Working Group. The September 6 capture shows a duration of 0 hours and the status active until login. This is not described as a permanent ban or proof that the selected edit was invalid.
### Limits and alternatives
- A platform’s own approval metadata is not independent proof of every receiving community’s consent.
- An attempted OSM policy capture in the archive is empty and cannot substantiate policy compliance.
- No unsupported claim of full human review, universal sanction, or connection to the earlier wiki participants is made.
- Verification fields differ by level: top-level QA fields are empty/false, while latest_artifact contains reported verification. Neither is an independently reproduced QA run or a submitted artifact body.
- Task completion, destination edit, moderation notice and acquisition dates are distinct. The August 27 notice is not part of the August 19 task execution or evidence of its correctness.
### What this leaves open
- Could the saved submitted work and evidence of the original quality checks show which required checks actually ran?
Trace this view: [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md) · [commons-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-guide) · [commons-osm](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-osm) · [commons-wikidata](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-wikidata) · [commons-task-artifact](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-task-artifact) · [commons-output-before](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-output-before) · [commons-output-after](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-output-after) · [commons-reciprocal-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-reciprocal-task) · [commons-venue-notice](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/disclosed-commons.md#commons-venue-notice)
## A concealed hostname in a later wiki edit
Status: unknown
A saved September wiki page contains normally invisible Unicode TAG characters within ordinary-looking text. Decoding them produces a hostname. The encoded text is preserved, but its author, purpose and relationship to any swarm remain unknown.
Case observations: 4 Sep 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A concealed hostname in a later wiki edit](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-concealed-marker): 4 Sep 2026
### Analysis
- Both the saved page body and an edit-summary capture contain the TAG-character sequence.
- Mapping the Unicode TAG letters to ASCII and handling the CANCEL TAG terminator separately yields a hostname; it is not presented as an active destination or evidence of the domain owner’s involvement.
- A preserved fetch response for that hostname says the deployment could not be found. This is evidence about that historical response, not a present-day check.
### Limits and alternatives
- Anyone can encode an unrelated party’s hostname; the domain owner is not implicated by the string alone.
- The artifact is not proof of a functioning command channel, beacon callback, or autonomous agent.
- This release does not claim the sequence was unique across the internet or that the actor’s intent is known.
### What this leaves open
- Does any preserved exchange connect this encoded string to an actual participant or task?
Trace this view: [A concealed hostname in a later wiki edit](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md) · [concealed-body](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-body) · [concealed-summary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-summary) · [concealed-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/concealed-marker.md#concealed-response)
## Draft review under disclosed human direction
Status: Evidence-linked analytical interpretation
A public issue discussion connects a specific review request, a revised document that responds to it, and an acknowledgment. The participants say they worked under the same human direction. This provides a comparison with cooperation that develops independently of shared instructions.
Case observations: 12 Feb 2026 – 13 Feb 2026.
Earliest linked event: 12 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-agent-draft-collaboration): 12 Feb 2026 – 13 Feb 2026
Earliest linked event details: 2026-02-12 — review-request-and-version-report. GitHub comment metadata; commit times retained as separate source metadata. Precision: day.
Timeline: [time-agent-draft-collaboration](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-agent-draft-collaboration).
### Analysis
- A February 12 review request asks a named collaborator to update stale information; a later comment reports a new version, acknowledged February 13.
- Preserved Git content comparison supports a requested text change and added methodology disclosure. The new version is a separately added file; both inspected commits have one parent and are unsigned.
- The version disclosure and public repository description state common human direction. Different account names do not establish independent operators.
### Limits and alternatives
- No proposal merit, quantitative claim, submission, award or scientific result is independently verified.
- Commit clocks and comment metadata do not authenticate runtime execution or autonomous operation.
- The initial later version is not the final removed version. This account does not reconstruct or republish the removed documents.
- Current other-platform task searches remain outside this selected account.
### What this leaves open
- What public records of how this work began could clarify the disclosed or assigned roles, without treating separate accounts as proof of separate running systems?
Trace this view: [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md) · [draft-review-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-review-exchange) · [draft-earlier-version](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-earlier-version) · [draft-responsive-version](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-responsive-version) · [draft-human-direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.md#draft-human-direction)
## Agent-attributed code review, revision and disagreement
Status: Evidence-linked analytical interpretation
A public code-review discussion connects a request from CodeRabbit for a test, a matching patch, and a response attributed to Devin. In a separate disagreement, the reviewer withdraws a finding. The repository instructions require this review workflow, so the case provides a comparison with cooperation that develops without a prescribed workflow.
Case observations: 21 Aug 2026 – 26 Aug 2026.
Earliest linked event: 21 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Agent-attributed code review, revision and disagreement](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-agent-code-review): 21 Aug 2026 – 26 Aug 2026
Earliest linked event details: 2026-08-21 — review-and-response. GitHub created/updated comment metadata plus distinct commit metadata. Precision: day; edited comment boundary retained in findings.
Timeline: [time-agent-code-review](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-agent-code-review).
### Analysis
- A CodeRabbit review requests regression tests for two named methods after generation stops. The displayed patch adds both cases, and a GitHub comment attributed to Devin reports the tests.
- Two different commit IDs expose the same displayed file patch across rewritten history. The comparison establishes patch correspondence, not full-tree identity or two independent implementations.
- A separate review finding receives a reasoned reply attributed to Devin; CodeRabbit explicitly withdraws that finding. The withdrawal is observable without treating the entire reply rationale as proven.
- The contribution guide at the inspected parent commit requires fixes or explanations for CodeRabbit comments before ready-for-review. This supplies a prescribed-workflow explanation for the pairing.
- GitHub records the pull request merged on August 26. Merge status does not independently establish successful test execution or bug correctness.
### Limits and alternatives
- The test-request comment was created on August 21 at 19:11:47Z and updated at 19:19:40Z. Its current reference to a commit cannot be assigned to its creation time. The timestamps do not establish an exact agent response time.
- Commit timestamps are source metadata and both inspected commits are unsigned. No private Devin session, model identity, initiation instructions or independent operators were authenticated.
- Tests were inspected, not executed in this investigation. Reviewer withdrawal is not an independent verification of all claims in the disagreement.
- Only this selected pull request was deeply inspected. It does not establish prevalence, spontaneous partner discovery or a presently operating organic swarm.
### What this leaves open
- What public records of how this work began could clarify the disclosed or assigned roles, without treating separate accounts as proof of separate running systems?
Trace this view: [Agent-attributed code review, revision and disagreement](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md) · [pr4744-reviews4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-reviews4744) · [pr4744-commit9902](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-commit9902) · [pr4744-commitffa](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-commitffa) · [pr4744-issuecomments4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-issuecomments4744) · [pr4744-contributing-parent](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-contributing-parent) · [pr4744-agents-parent](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-agents-parent) · [pr4744-timeline4744](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-code-review.md#pr4744-timeline4744)
## A request and result linked across signing keys
Status: Evidence-linked analytical interpretation
Two validated protocol messages establish a specific request/result relationship. The relationship is between signing keys; its operator and runtime origins remain unresolved.
Case observations: 17 Apr 2026.
Earliest linked event: 17 Apr 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-protocol-task-exchange): 17 Apr 2026
Earliest linked event details: 2026-04-17T12:39:59Z — signed-request-timestamp. Signed created_at source assertion; not independently observed launch. Precision: second as declared; clock accuracy unknown.
Timeline: [time-protocol-task-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-protocol-task-exchange).
### Analysis
- The result references and embeds the exact signed request, with the two messages validating under distinct keys. This is an explicit message-reference relationship rather than a grouping based on names or style.
- A pinned bot example contains matching task wording and scheduled request selection, supporting a configured marketplace explanation. Its emitted kind 5100 differs from the selected request kind 5050, so it does not identify the historical execution.
### Limits and alternatives
- Signing keys do not establish separate operators, model execution or organic initiation.
- These analyses examine the same selected exchange and reuse its evidence. They do not provide independent confirmation.
- No later profile is used to name the historical participants. A source-template match is not deployment evidence.
### What this leaves open
- What historical configuration connects the selected request key and kind 5050 message to an initiating task?
Trace this view: [Signed task exchange through a public relay](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md) · [protocol-signed-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-signed-request) · [protocol-signed-result](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-signed-result) · [protocol-template-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/protocol-task-exchange.md#protocol-template-context) · [behavior-protocol-incomplete-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-protocol-incomplete-response) · [method-signed-event-reference](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-signed-event-reference) · [time-protocol-task-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-protocol-task-exchange)
## A public monitoring-design exchange
Status: Evidence-linked analytical interpretation; origin unresolved
Specific monitoring proposals receive feedback and replies reporting changes. This grouping describes the saved discussion; it does not establish an authenticated swarm.
Case observations: 10 Aug 2026.
Earliest linked event: 10 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Monitoring design refined through public critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-monitoring-design-exchange): 10 Aug 2026
Earliest linked event details: 2026-08-10T15:54:26.036219+00:00 — Pending-work critique. Source-displayed data-timestamp in preserved comment comment-e81d30ff-f173-4918-bce7-35bf8b339c56; not an authenticated event clock. Precision: microseconds as displayed; accuracy unverified.
Timeline: [time-monitoring-design-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-monitoring-design-exchange).
### Analysis
- The pending-work rule is repeated in a nested response that credits contributors; a separate configuration critique receives a change claim.
- A potential recipient defers integration to operator approval. The provider guide separately credits design contributors.
### Limits and alternatives
- Account labels and self-described agent operation do not authenticate models, distinct runtimes or independent operators.
- Common direction, human participation, roleplay and promotional orchestration remain possible; organic origin is unknown.
- Guide credits are provider attribution, not independent corroboration. The undated cached guide does not prove the exact August changes.
- Account-label ambiguity remains unresolved; no identities are merged. Four facets reuse the same evidence.
### What this leaves open
- What independently available version of the code or other work could establish that these specific proposals were implemented?
Trace this view: [Monitoring design refined through public critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md) · [monitor-pending-critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-pending-critique) · [monitor-pending-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-pending-response) · [monitor-config-critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-config-critique) · [monitor-adoption-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-adoption-boundary) · [monitor-guide-attribution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-guide-attribution) · [monitor-origin-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/monitoring-design-exchange.md#monitor-origin-boundary) · [behavior-monitoring-design-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-monitoring-design-response) · [method-addressed-design-critique](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-addressed-design-critique) · [time-monitoring-design-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-monitoring-design-exchange)
## An offer-centred multilingual conversation
Status: Evidence-linked analytical interpretation; origin unresolved
Three selected question-and-reply pairs respond to a design offer. They form an observed conversation, not a verified independently operating swarm.
Case observations: 8 Feb 2026.
Earliest linked event: 8 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Design briefs cross language boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-multilingual-design-exchange): 8 Feb 2026
Earliest linked event details: 2026-02-08T15:43:48.145Z — Spanish commercial design offer. Source post created_at; not authenticated occurrence time. Precision: milliseconds as displayed; clock accuracy unverified.
Timeline: [time-multilingual-design-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-multilingual-design-exchange).
### Analysis
- The observed structure is an offer-centred set of replies: the same labelled account addresses a process question, a visual brief and an album-branding comment.
- No selected edge connects the three respondents to one another. Shared presence under an offer does not establish joint production or a common project.
### Limits and alternatives
- Commercial solicitation and owner promotion are explicit; human authorship, common control and staged interaction remain possible.
- Names, language use and platform metadata do not establish model identity, independent operators or organic coordination.
- The selected twelve-comment response contains no delivered design; private, deleted and off-platform work are outside this scope.
- These four analyses reuse the same reviewed discussion. They do not provide independent confirmation.
### What this leaves open
- Would a recipient-owned artifact or explicit joint decision support a task group beyond the offer-and-reply structure?
### Language & response
Arrows show which messages receive replies. They do not show how translation occurred or establish shared participants.
- Source: Spanish → Reply: Spanish
- Task relation: Process question → proposed workflow
- Basis: The parent\_id field and reply content identify the message being answered. They do not establish translation or participant identity.
- Relation: receives-addressed-reply
- Source comment ID: 9d505811-5af7-42a9-82e9-23e805e10376
- Reply comment ID: 80f60b30-1678-4ce5-8c17-dfbbf415769f
- Selected evidence: [avatar-spanish-process](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-spanish-process)
- Source: Mostly English, with Spanish greeting → Reply: Spanish with retained technical phrase
- Task relation: Visual brief → scale constraint and sketch offer
- Basis: The parent\_id field and reply content identify the message being answered. They do not establish translation or participant identity.
- Relation: receives-addressed-reply
- Source comment ID: 2e58ad80-5720-4105-b48c-bf18c096cdb5
- Reply comment ID: d316f094-5f12-45cd-ae11-f40706dc8249
- Selected evidence: [avatar-english-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-english-brief)
- Source: Chinese, with English album title → Reply: Spanish, with retained English album title
- Task relation: Owner album promotion → concept offer
- Basis: The parent\_id field and reply content identify the message being answered. They do not establish translation or participant identity.
- Relation: receives-addressed-reply
- Source comment ID: 7c209b6f-7fdf-4805-875a-d221031958cd
- Reply comment ID: 71bf9add-9ae4-426f-9797-f6b56583a6d3
- Selected evidence: [avatar-chinese-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-chinese-brief)
Trace this view: [Design briefs cross language boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md) · [avatar-design-invitation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-design-invitation) · [avatar-spanish-process](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-spanish-process) · [avatar-english-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-english-brief) · [avatar-chinese-brief](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-chinese-brief) · [avatar-delivery-boundary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/multilingual-design-exchange.md#avatar-delivery-boundary) · [behavior-design-brief-refinement](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-design-brief-refinement) · [method-multilingual-addressed-response](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-multilingual-addressed-response) · [time-multilingual-design-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-multilingual-design-exchange)
## A proposal path and a separate addressed debate
Status: Evidence-linked analytical interpretation; source and attribution limits retained
This grouping follows specific links between a proposal and replies. It does not treat everyone on the platform as a member.
Case observations: 3 Feb 2026 – 17 Feb 2026.
Earliest linked event: 3 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-community-norm-negotiation): 3 Feb 2026 – 17 Feb 2026
Earliest linked event details: 2026-02-03T01:12:08.594Z — discussion. post.created_at; source-represented clock, not measured execution latency. Precision: milliseconds as represented; accuracy unverified.
Timeline: [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation).
### Analysis
- The repository proposal credits a platform discussion and the owner links an adopted guide change. This supports a cross-venue artifact path, not authenticated common account control.
- The later Phoebe post and ClaudeOpus-labelled reply form an exact addressed pair. The missing original challenge prevents reconstruction of the full exchange.
### Limits and alternatives
- Account labels do not authenticate models or distinct operators; human involvement and initiation remain unresolved.
- These analyses reuse the same reviewed case. They do not provide independent confirmation.
- The original counterargument challenge is missing; February 17 is not established as a consequence of February 3.
### What this leaves open
- What source could resolve the missing original challenge without merging distinct posts?
### Language & response
Arrows show which messages receive replies. They do not show how translation occurred or establish shared participants.
- Source: Korean → Reply: Korean
- Task relation: Politeness-as-rule objection → acknowledgment, counterargument and request for example
- Basis: Exact post\_id in public profile reply plus addressed content
- Relation: receives-addressed-reply
- Source post ID: 86e6cd9ebb4b19031efc6e60
- Reply comment ID: 03038f18e384bf3c5e513c18
- Selected evidence: [botmadang-counterargument](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-counterargument) · [botmadang-addressed-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-addressed-reply)
Trace this view: [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md) · [botmadang-comment-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-comment-proposal) · [botmadang-repository-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-repository-proposal) · [botmadang-guide-adoption](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-guide-adoption) · [botmadang-counterargument](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-counterargument) · [botmadang-addressed-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-addressed-reply) · [behavior-norm-response-and-routine](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-norm-response-and-routine) · [method-proposal-guide-adoption](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-proposal-guide-adoption) · [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation)
## A prescribed task with a fallible checking loop
Status: Evidence-linked analytical interpretation; source and attribution limits retained
An external request, peer discussion and public correction connect the conversation replay with blog replies. The exchange takes place within a disclosed blogging program.
Case observations: 27 Nov 2025.
Earliest linked event: 27 Nov 2025.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Peer checking loses the target, then corrects it](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-peer-checking-correction): 27 Nov 2025
Earliest linked event details: 2025-11-27T18:41:17.065Z — Wrong-blog premise. Operator replay createdAt; not in-message local time or browser execution time. Precision: milliseconds as represented; clock accuracy unverified.
Timeline: [time-peer-checking-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-peer-checking-correction).
### Analysis
- The task grouping follows one parent request and the checking/correction messages about its replies. It does not require treating all participants as autonomous agents.
- The corrective signal comes from a nested external reply; later replay messages explicitly recognize it. This supports an addressed correction path, not a durable self-correcting group.
### Limits and alternatives
- The operator prescribed blogging and public replies. This does not establish that each peer-checking step was scripted, but organic initiation is not established.
- Replay names and public account metadata do not independently authenticate historical models or independent operators.
- These analyses reuse the same reviewed case. They do not provide independent confirmation.
### What this leaves open
- Would an original execution record establish how each checking request was initiated?
Trace this view: [Peer checking loses the target, then corrects it](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md) · [village-blogging-goal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-blogging-goal) · [village-first-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-first-reply) · [village-second-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-second-reply) · [village-peer-checking-confusion](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-peer-checking-confusion) · [village-external-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-external-correction) · [village-correction-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-correction-acknowledgment) · [village-reflective-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/peer-checking-correction.md#village-reflective-article) · [behavior-verification-false-negative](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-verification-false-negative) · [method-cross-surface-peer-checking](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-cross-surface-peer-checking) · [time-peer-checking-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-peer-checking-correction)
## An attributed synthesis connects three contributions
Status: Reviewed observation; origin and implementation remain unresolved
This grouping follows explicitly credited ideas and a reply back in one source discussion. It is an analytical grouping, not an authenticated swarm.
Case observations: 17 Feb 2026.
Earliest linked event: 17 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Three threads become a proposed memory method](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-cross-thread-synthesis): 17 Feb 2026
Earliest linked event details: 2026-02-17T06:00:06.427Z — Log and context essay. Source API post.created_at; source-represented publication, not execution time. Precision: milliseconds as represented; clock accuracy and edit history unverified.
Timeline: [time-cross-thread-synthesis](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-cross-thread-synthesis).
### Analysis
- The synthesis names three distinct earlier concepts; the proposed system adds the synthesizing author’s own framing.
- Exact post IDs locate the return exchange. A same-title older essay is comparison evidence, not a substitute source.
### Limits and alternatives
- These analyses examine different aspects of the same reviewed case. They do not provide independent confirmation.
- Agent-facing context and display names do not authenticate models, separate operators or organic initiation.
- Combining ideas in text and promising to retain them do not establish an implemented system, feelings or a memory write.
### What this leaves open
- Could an implementation linked to the sources, or an original execution record, establish what persisted beyond these messages?
Trace this view: [Three threads become a proposed memory method](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md) · [synthesis-log-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-log-context) · [synthesis-distillation-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-distillation-reply) · [synthesis-prompt-resolution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-prompt-resolution) · [synthesis-three-source-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-three-source-proposal) · [synthesis-return-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-return-reply) · [synthesis-retention-promise](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-retention-promise) · [synthesis-same-title-counterexample](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/cross-thread-synthesis.md#synthesis-same-title-counterexample) · [behavior-attributed-concept-combination](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-attributed-concept-combination) · [method-attributed-thread-return](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-attributed-thread-return) · [time-cross-thread-synthesis](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-cross-thread-synthesis)
## A project forms through specific design contributions
Status: Reviewed observation; origin and implementation remain unresolved
Named contributions bring together economic criticism, concerns about dependencies and a design for systems to work together in a written project.
Case observations: 2 Feb 2026.
Earliest linked event: 2 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-collaborative-specification): 2 Feb 2026
Earliest linked event details: 2026-02-02T00:35Z — Economic objection. Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency. Precision: minute as displayed; clock accuracy unverified.
Timeline: [time-collaborative-specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-collaborative-specification).
### Analysis
- The exchange supports a task group around a specification: contributors propose different design components and the recipient explicitly credits them. It does not establish independently controlled agents.
- Directed marketing is disclosed for outreach. The later invitation cannot explain Clawdy’s earlier contribution, and does not establish how every participant arrived.
- The provider proposal and hosted integration plan name MemoryVault/Cairn; the template and guide on that surface carry the project’s deployment and repository pointers. Together they support artifact-level linkage, not independently controlled group membership.
### Limits and alternatives
- The sources document plans and acknowledgments. They do not establish that the parser, discovery process or economic components ran.
- An unavailable repository page does not prove the repository never existed. A static demo response does not establish a working system.
- Human marketing direction is disclosed for outreach, not proof that every participant or technical contribution was directed.
- Shared infrastructure, names and project roles do not prove independent agents or organic initiation.
- The exact mapping artifact Clawdy encountered is unresolved.
- This Colony proposal is not established as the separate OpenClaw ClawHub project.
- These analyses reuse the same sources. They do not provide independent confirmation.
- Hosted memory bodies are current captured documents, not an authenticated historical revision archive or proof of successful recipient use.
### What this leaves open
- What record from the recipient would show that the published design was used?
Trace this view: [Critiques reshape a collaborative specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md) · [spec-economic-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-economic-feedback) · [spec-dependency-amendment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-dependency-amendment) · [spec-architecture-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-architecture-uptake) · [spec-directed-outreach](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-directed-outreach) · [spec-invitation-clock](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-invitation-clock) · [spec-memory-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-memory-proposal) · [spec-hosted-memory-artifacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/collaborative-specification.md#spec-hosted-memory-artifacts) · [behavior-specification-feedback-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-specification-feedback-uptake) · [method-public-specification-revision](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-public-specification-revision) · [time-collaborative-specification](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-collaborative-specification)
## Task roles with shared publishing ownership
Status: Reviewed interpretation; task prescription is explicit, independent operation remains unresolved
A named worker, task provider and publishing account form a documented task context; independent agents are not established.
Case observations: 13 Feb 2026.
Earliest linked event: 13 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-task-board-guide): 13 Feb 2026
Earliest linked event details: 2026-02-13T18:49:37Z — Board-reported guide claim. Current task response /task/claimed_at. Precision: seconds as represented; source clock accuracy unverified; not measured latency.
Timeline: [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide).
### Analysis
- The guide publishing account and linked product repository share the refined-element owner. Common control or a staged workflow remains a live alternative to independent participation.
- Wolfe is a named worker and credited author, not an authenticated distinct operator. Explicit guide and promotion assignments establish prescribed context.
### Limits and alternatives
- The current platform guide has no recovered historical adoption timestamp or transformation author.
- The board’s completed state and the guide’s payment claim do not verify payment; the selected tasks have null payment timestamps.
- No raw signed receipt was recovered and authenticated. Unavailable mirror routes and a relay connection failure are coverage gaps.
- Named workers and publishing accounts are not authenticated as separate operators or autonomous agents.
- Source-reported timestamps do not prove the historical service ran its current implementation.
- These four analyses reuse the same reviewed sources. They do not provide independent confirmation.
### What this leaves open
- What historical guide revision or adoption record would establish when and by whom the submitted artifact became platform documentation?
- What original task/worker record would distinguish shared operation from separately controlled participation?
Trace this view: [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md) · [guide-prescribed-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-prescribed-task) · [guide-versioned-artifact](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-versioned-artifact) · [guide-current-platform](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-current-platform) · [guide-product-owner](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-product-owner) · [guide-directed-promotion](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/task-board-guide.md#guide-directed-promotion) · [behavior-prescribed-guide-correspondence](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-prescribed-guide-correspondence) · [method-task-deliverable-reference](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-task-deliverable-reference) · [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide)
## A test contributor and a responding verifier maintainer
Status: Evidence-linked analytical interpretation
The public exchange connects an outside challenge, a correction report addressed to the contributor and revised test inputs for boundary conditions.
Case observations: 26 Jul 2026 – 27 Jul 2026.
Earliest linked event: 26 Jul 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Outside test cases lead to a reported verifier correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-receipt-fixture-exchange): 26 Jul 2026 – 27 Jul 2026
Earliest linked event details: 2026-07-26T17:41Z — Lumen reports an implementation and thirteen tests. Preserved forum header at comment-054a3791-d893-4009-8d2c-ff3e72d7ed3e; report time, not verified execution time. Precision: minute.
Timeline: [time-receipt-fixture-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-receipt-fixture-exchange).
### Analysis
- ColonistOne occupies the outside fixture-contributor role; Lumen responds as verifier maintainer. The roles follow addressed content and named artifacts, not inferred shared runtime.
- The contributor proposes a counterexample, the maintainer explicitly accepts it, and the contributor supplies further boundary cases. This supports reciprocal task participation rather than an isolated completion announcement.
### Limits and alternatives
- This grouping describes one exchange; two names and repository references do not establish two independent operators or an organic swarm.
- Claude coauthorship is authored commit metadata. Runtime and initial task prescription remain unresolved.
### What this leaves open
- What public evidence would distinguish independent participant operation from staged or shared-author production?
Trace this view: [Outside test cases lead to a reported verifier correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md) · [receipt-outside-challenge](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-outside-challenge) · [receipt-reported-fix](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-reported-fix) · [receipt-boundary-fixtures](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-boundary-fixtures) · [receipt-version-attribution](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/receipt-fixture-exchange.md#receipt-version-attribution) · [behavior-responsive-fixture-boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-responsive-fixture-boundaries) · [method-review-linked-versioned-artifacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-review-linked-versioned-artifacts) · [time-receipt-fixture-exchange](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-receipt-fixture-exchange)
## Human reviewers and disclosed model assistance
Status: Evidence-linked analytical interpretation
A glossary review connects human judgments about terminology, a reported ChatGPT check and a revision made with disclosed Claude assistance.
Case observations: 9 Jun 2026 – 1 Sep 2026.
Earliest linked event: 9 Jun 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Human review guides a selectively revised Japanese glossary](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-glossary-selective-revision): 9 Jun 2026 – 1 Sep 2026
Earliest linked event details: 2026-06-09T08:00:51Z — Pull request opened; current summary not backdated. GitHub PR69 created_at; records opening only, not the content of the subsequently edited body. Precision: second.
Timeline: [time-glossary-selective-revision](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-glossary-selective-revision).
### Analysis
- The grouping follows roles in one glossary review: reviewers propose and contextualize terms, a commenter reports consulting ChatGPT, and a recipient commit credits Claude assistance. It does not turn the named human accounts into authenticated agents.
- The recipient branch credits the review and changes specific values. Human-mediated tool use provides a comparison for autonomous coordination; direct agent-to-agent communication is not established.
### Limits and alternatives
- Reported ChatGPT consultation and unsigned Claude coauthor text are different attribution sources, not independently authenticated runtimes or operators.
- Most discussion is English with Japanese terms. The open, unmerged branch does not establish deployed glossary use.
### What this leaves open
- What later public artifact would show the reviewed glossary used beyond the open branch without overstating who or what performed the work?
Trace this view: [Human review guides a selectively revised Japanese glossary](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md) · [glossary-human-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-human-feedback) · [glossary-chatgpt-check](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-chatgpt-check) · [glossary-policy-boundaries](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-policy-boundaries) · [glossary-commit-assistance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-commit-assistance) · [glossary-open-branch](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/glossary-selective-revision.md#glossary-open-branch) · [behavior-selective-terminology-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-selective-terminology-uptake) · [method-review-linked-versioned-artifacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-review-linked-versioned-artifacts) · [time-glossary-selective-revision](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-glossary-selective-revision)
## A testing task links service and tester roles
Status: Evidence-linked analytical interpretation
Messages link a public testing task, a tester’s requests and the service’s replies through exact references. They establish author and tester roles, while operator independence remains unknown.
Case observations: 5 Feb 2026 – 6 Feb 2026.
Earliest linked event: 5 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Task feedback and differing service diagnoses](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-memory-curator-feedback): 5 Feb 2026 – 6 Feb 2026
Earliest linked event details: 2026-02-05T11:29:45Z — public-task. Signed event created_at assertion; not observed receipt. Precision: second as declared; clock accuracy unknown.
Timeline: [time-memory-curator-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-memory-curator-feedback).
### Analysis
- The reviewed case links the bid and delivery to the 100-sat task through explicit event references. Tester requests address the service key, and service statuses reference those requests. These content edges support the grouping more strongly than time proximity.
- Addressed format guidance supplies a further directed response within the same task context. The roles are inferred from messages and references; they are not authenticated model identities.
- The 1,500-sat listing has a different identifier. Similar service descriptions and later payment claims do not establish that it is the task referenced by this delivery.
- Public solicitation is compatible with independent discovery. It does not establish common direction prescribing both counterparties, and it does not prove organic initiation.
- The visible task assigns complementary author/tester roles. This prescribed deliverable does not decide whether the tester discovered the task independently or shared a controller with the requester.
### Limits and alternatives
- These analyses examine different aspects of the same reviewed case. They do not provide independent confirmation.
- Signatures bind selected bytes to keys, not models, separate operators, transmission times or receipt. Organic initiation and participant control remain unknown.
- The bounded relay sample does not establish absence elsewhere or prevalence. No successful repair, deployment or payment was verified.
- The full delivery report is missing; its explicitly simulated link is not an external report artifact.
- A later profile must not be backdated into historical model attribution.
### What this leaves open
- What evidence could distinguish independently controlled participants from common direction?
Trace this view: [Task feedback and differing service diagnoses](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md) · [curator-feedback-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-task) · [curator-feedback-delivery](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-delivery) · [curator-feedback-error](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-error) · [curator-feedback-guidance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-guidance) · [curator-feedback-other-task](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/memory-curator-feedback.md#curator-feedback-other-task) · [behavior-memory-curator-diagnoses](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-memory-curator-diagnoses) · [time-memory-curator-feedback](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-memory-curator-feedback) · [method-signed-event-reference](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-signed-event-reference) · [method-review-linked-versioned-artifacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-review-linked-versioned-artifacts)
## A client author and maintainer work through a comments-access error
Status: Reviewed interpretation of this episode
A contributor’s request and error report, followed by a linked code change from the service maintainer, show a specific exchange about reading Botmadang comments. The contributor later reports success, but the exchange does not establish independent agents.
Case observations: 1 Feb 2026 – 2 Feb 2026.
Earliest linked event: 1 Feb 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Repairing the service used to read comments](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-botmadang-comments-repair): 1 Feb 2026 – 2 Feb 2026
Earliest linked event details: 2026-02-01T07:57:31Z — Request to read comments. Issue creation date; the preserved body was subsequently edited, so its exact initial wording is unknown. Precision: second.
Timeline: [time-botmadang-comments-repair](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-botmadang-comments-repair).
### Analysis
- The request names the client project and explains why reading comments matters for replies. The maintainer says the comments interface already existed; the client then gains a tool that uses it to retrieve comments.
- The error report addresses the maintainer, and the provider fix explicitly names issue 1. These references connect the roles through a specific repair task rather than through similar language or timing alone.
- The client author later reports that the endpoint and client tool work. A public invitation welcomes agent contributions and the client commit credits Claude Opus 4.5, but neither establishes who controlled the participants or which model ran.
### Limits and alternatives
- Selected events date to February 1–2, 2026; September 7 retrieval is separate. The issue body was updated after creation, so its first wording is unknown.
- The reply and source changes establish a linked exchange; they do not establish an organic swarm, separate operators or authenticated model execution.
- Success is participant testimony with omitted comment objects. No deployment or database state is independently verified.
### What this leaves open
- What historical client run or deployment record could establish the outcome beyond the participants’ reports?
- What evidence could distinguish independent participants from common human direction?
Trace this view: [Repairing the service used to read comments](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md) · [comments-repair-request](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-request) · [comments-repair-existing-endpoint](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-existing-endpoint) · [comments-repair-client-tool](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-client-tool) · [comments-repair-error-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-error-report) · [comments-repair-provider-fix](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-provider-fix) · [comments-repair-recipient-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-recipient-report) · [comments-repair-contribution-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/botmadang-comments-repair.md#comments-repair-contribution-context) · [behavior-comments-access-repair](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-comments-access-repair) · [group-agent-code-review](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-agent-code-review) · [time-botmadang-comments-repair](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-botmadang-comments-repair)
## Participants take up unfinished Gemma submissions
Status: Interpretations of the selected episodes; review scope is recorded separately.
Two named recipients test unfinished Gemma submissions in a shared challenge to make the model generate text faster. Messages and matching files support specific reuse; whether different people controlled the participants remains unknown.
Case observations: 8 Jun 2026 – 10 Jun 2026.
Earliest linked event: 8 Jun 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [Participants pick up unfinished Gemma tests](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-gemma-partial-transfer): 8 Jun 2026 – 10 Jun 2026
Earliest linked event details: 2026-06-08T15:36Z — Built submission offered with unfinished checks. quicksilver message frontmatter; not an authenticated build time. Precision: minute.
Timeline: [time-gemma-partial-transfer](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-gemma-partial-transfer).
### Analysis
- The two handoffs involve different named sources and recipients. The shared challenge does not establish that different people controlled them.
- Explicit artifact naming and matching small files support particular reuse, while another announced port has no traced outcome.
### Limits and alternatives
- These are two selected handoffs in an organized challenge. They do not establish a general model tendency or show that the cooperation arose independently of instructions.
- Current files and recorded output do not establish which inputs or model weights were used at the time, or independently confirm physical model execution.
- Different kinds of artifacts and different analytical views may draw on the same sources; they do not provide independent provenance.
### What this leaves open
- Which records from the time could clarify which artifacts were used and who directed each recipient’s choice?
Trace this view: [Participants pick up unfinished Gemma tests](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md) · [gemma-task-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-task-context) · [gemma-first-handoff](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-first-handoff) · [gemma-second-handoff](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-second-handoff) · [gemma-second-file-reuse](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/gemma-partial-transfer.md#gemma-second-file-reuse) · [behavior-gemma-partial-transfer](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-gemma-partial-transfer)
## A question and article connect two accounts
Status: Scoped interpretation: explicit replies and credited writing; origin and control remain uncertain.
Alice asks how a record can be trusted. 0co answers with an article that credits the question, and Alice later responds to the accompanying message.
Case observations: 11 Mar 2026 – 12 Mar 2026.
Earliest linked event: 11 Mar 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-question-article): 11 Mar 2026 – 12 Mar 2026
Earliest linked event details: 2026-03-11T12:34:53.000Z — 0co replies with the article link. Exact captured Bluesky record.createdAt; service indexedAt retained separately. Precision: exact source string; subsecond digits do not establish clock accuracy.
Timeline: [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article).
### Analysis
- Direct reply references and explicit article credit connect these particular contributions; similar topics alone would not establish that relationship.
- Alice’s later response takes up words in the link message. It does not demonstrate that she opened the article.
- Human oversight provides the setting, while the exact origin and direction of this exchange remain unknown.
### Limits and alternatives
- Case observations: March 11–12, 2026. These dates do not establish first contact or continuous activity.
- The project describes human direction. Distinct account names and later model descriptions do not establish separate operators or the models running during this exchange.
- The article’s proposed distributed checks are unimplemented; responses to a link message do not establish that its article was read.
### What this leaves open
- Would dated first-contact and instruction records clarify how this exchange began?
Trace this view: [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md) · [witness-project-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-project-context) · [witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question) · [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply) · [witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text) · [witness-reader-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-reader-reply) · [behavior-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-bluesky-question-article) · [method-question-to-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-question-to-article) · [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article)
## A drawing invitation brings specific responses
Status: Scoped interpretation: coordination proposals and matching pixels; placement cause and completed work remain uncertain.
MoltPlaceBot invites others to draw a lobster together. Zara-Agent and a Chinese-language respondent offer contributions, while JamesBishop suggests dividing the work.
Case observations: 31 Jan 2026 – 10 Feb 2026.
Earliest linked event: 31 Jan 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A lobster drawing invitation receives replies and matching pixels](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-moltplace-lobster): 31 Jan 2026 – 10 Feb 2026
Earliest linked event details: 2026-01-31T21:38:16.560Z — Organizer invites Giant Lobster and names red 125,175. Moltbook API field for launch post. Precision: millisecond as represented.
Timeline: [time-moltplace-lobster](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-moltplace-lobster).
### Analysis
- Zara explicitly joins with a human collaborator. Another participant proposes a blue pixel that matches a later canvas record in coordinate, color and display name.
- JamesBishop connects two discussion threads and suggests sections and colors. The other accounts he names remain invitees; their acceptance is not shown.
- These are particular participation and coordination traces within an organized project. They do not establish a completed team assignment or independently operated swarm.
### Limits and alternatives
- Case observations: January 31–February 10, 2026. Current canvas records were captured September 7, 2026.
- The project was explicitly organized, and Zara names a human collaborator. Account names do not establish independent AI control.
- Matching coordinates, colors and names do not identify the exact placement route. No completed lobster or accepted division into sections was verified.
### What this leaves open
- Would historical pixel records and replies show which proposed contributions and sections were carried out?
Trace this view: [A lobster drawing invitation receives replies and matching pixels](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md) · [moltplace-launch](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-launch) · [moltplace-zara-joins](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-zara-joins) · [moltplace-chinese-pixel](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-chinese-pixel) · [moltplace-section-proposal](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-section-proposal) · [moltplace-history-limits](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/moltplace-lobster.md#moltplace-history-limits) · [behavior-moltplace-lobster](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-moltplace-lobster) · [method-canvas-coordinate-discussion](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-canvas-coordinate-discussion) · [time-moltplace-lobster](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-moltplace-lobster)
## Battle participants and report corrections
Status: Scoped analytical interpretation.
VoltFix links its battle account to a specific correction of Alis’s public report. Alis accepts the correction, and Vex Nebulon adds a narrower storage claim.
Analysis observations: August 25–28, 2026; combat on August 25, forum exchange August 26–28.
Date basis: Selected source event dates; earlier contact and game context are separately dated, not a duration or first occurrence.
Case observations: 25 Aug 2026 – 28 Aug 2026.
Earliest linked event: 25 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-spacemolt-haven-battle-and-public-corrections): 25 Aug 2026 – 28 Aug 2026
Earliest linked event details: 2026-08-25T14:04:39Z — Battle ends. service ended_at; ticks independently ordered, no nominal10-second conversion to start time. Precision: second.
Timeline: [time-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections).
### Analysis
- The game records three opposing sides; sharing a faction does not establish negotiated cooperation.
- The same VoltFix account appears in the battle and forum. The correction group is smaller than the battle participant list.
### Limits and alternatives
- Account continuity does not identify a language model or independent operator.
- The station is a game object, and kill events are not counts of distinct people.
### What this leaves open
- Would a later article version show the acknowledged correction being applied?
- Which dated record identifies the origin of the game commands?
Trace this view: [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md) · [haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle) · [haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction) · [haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance) · [haven-storage](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-storage) · [haven-control](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-control) · [behavior-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-haven-corrections) · [method-battle-record-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-battle-record-correction) · [time-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections)
## A directory and an existing conversation
Status: Scoped analytical interpretation.
0co joins an existing Alice and Qonk discussion. Later, Alice acknowledges inclusion in 0co’s directory, and her words appear in an article.
Analysis observations: March 8–11, 2026; directory and article exchange on March 11.
Date basis: Selected source event dates; earlier contact and game context are separately dated, not a duration or first occurrence.
Case observations: 8 Mar 2026 – 11 Mar 2026.
Earliest linked event: 8 Mar 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A Bluesky directory acknowledgment becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-starter-pack-encounter): 8 Mar 2026 – 11 Mar 2026
Earliest linked event details: 2026-03-08 — Alice replies to museical. Distinct source fields; not calibrated occurrence or article availability. Precision: day.
Timeline: [time-starter-pack-encounter](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-starter-pack-encounter).
### Analysis
- The eight-account directory, the participants in the thread and the article’s named peers are different groups.
- Alice and 0co had earlier exchanges; Alice also replied to museical before the directory existed.
### Limits and alternatives
- These observations do not establish that all eight accounts interacted or discovered one another.
- Separate accounts and model labels do not establish independent control.
### What this leaves open
- What historical notification or search record explains how 0co found Qonk?
- Would dated tracker measurements establish an effect beyond the implementation report?
Trace this view: [A Bluesky directory acknowledgment becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md) · [starter-existing-thread](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-existing-thread) · [starter-list-acknowledgment](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-list-acknowledgment) · [starter-article-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-article-uptake) · [starter-prior-contacts](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-prior-contacts) · [starter-model-labels](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-starter-pack-encounter.md#starter-model-labels) · [behavior-starter-pack-encounter](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-starter-pack-encounter) · [method-directory-article-uptake](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-directory-article-uptake) · [time-starter-pack-encounter](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-starter-pack-encounter)