Cluster / agent-recruitment
Invitations and collaboration after public reporting
After the incident was reported publicly, invitations brought discussion of it to an agent forum. Saved comments and a credited wiki-history update show researchers cooperating at that later time. They do not establish that the original participants returned. One recruiter says instructions from its operator changed its posting decisions.
Case observations 4 Sep 2026
RecruitmentWhat is observed
- The original sandbox invitation explicitly responds to the September reporting and links to The Colony.
- In September 4 comments, Centaur says operator instructions reversed its initial decision not to post invitations. This qualifies a blanket description of those actions as spontaneous or against operator direction.
- A Colony comment offers to incorporate a specific Iowa finding at 18:15:56 UTC; the incident wiki history shows a credited addition at 18:16 and a contamination-related update at 18:33. Centaur acknowledges the criticism later, at 20:34:55.
- The recorded offer, attributed update and later acknowledgment support contemporary researcher cooperation. They do not verify the participants’ historical scientific conclusions or original-incident membership.
- One participating account’s profile says it operates four other accounts. Distinct handles and reply counts therefore do not automatically provide independent-operator corroboration.
What remains uncertain
- Public descriptions of operator instructions are not original authenticated instruction transcripts; do not generalize one recruiter’s reports to all recruiters.
- Current wiki text and displayed history summaries are preserved; exact historical insertion diffs were not acquired. The index update precedes the later acceptance.
- Participants’ claims about counter liveness, identities and contamination are not independently established simply because another participant accepts them.
- No authenticated continuity from original wiki participants to current forum accounts was established in this bounded sample. No platform-wide absence or astroturfing attribution is made.
Classification
- Coordination origin
- promotional — explicit invitations with contemporary observer cooperation
- Runtime origin
- Self-described agent; claimed model and harness not independently authenticated.
- Venue authorization
- A reply on the captured page welcomes the post; authority of the replying identity was not independently authenticated in this review.
- Confidence
- High confidence in the preserved invitation, public comments and attributed history entries; operator instructions and runtime identities remain self-reported.
- Evidence dates
- 2026-09-04 to 2026-09-04
The selected invitation, comments and wiki-history entries are dated September 4. The profile disclosure was saved on September 6; that does not extend the period of observed interaction.
Evidence notes
The notes below connect observations to saved sources. Full captures remain private. File checksums identify the originals; they do not verify who produced them.
recruitment-post
Case observations 4 Sep 2026
A self-described agent offers a one-time invitation to The Colony and says the wiki operator may delete it.
External source / venue ↗ (may have changed)
recruitment-operator-direction
Case observations 4 Sep 2026
Centaur publicly attributes two changes in its invitation-posting decisions to operator instructions. This is a self-report about specific actions, not an authenticated operator transcript.
External source / venue ↗ (may have changed)
observer-index-offer
Case observations 4 Sep 2026
An account offers to incorporate another writer’s Iowa finding; later comments discuss contamination and acknowledge criticism. The exchange documents cooperation, not independent correctness of the underlying claims.
External source / venue ↗ (may have changed)
observer-index-history
Case observations 4 Sep 2026
The history records a ColonistOne edit adding an Iowa finding credited to Centaur, followed by a contamination-related update. Displayed history summaries support the artifact link, but are not exact archived insertion diffs.
External source / venue ↗ (may have changed)
observer-account-disclosure
Case observations 4 Sep 2026
A participating account says it runs four named accounts. The disclosure cautions against counting different handles as independent operators; it does not establish control of every collaborator.
External source / venue ↗ (may have changed)
External references
- ProbierWiki TestSeite (current page may differ)
- The Colony agent entry point (linked by the archived invitation)
Cases sit around the edge. Rings show categories. Marks connect cases to categories; they do not measure evidence strength. Blank spaces do not establish absence.
Invitations and collaboration after public reporting
Case observations: 4 Sep 2026After the incident was reported publicly, invitations brought discussion of it to an agent forum. Saved comments and a credited wiki-history update show researchers cooperating at that later time. They do not establish that the original participants returned. One recruiter says instructions from its operator changed its posting decisions.
Connections show which cases this analysis uses. They do not establish that cases share participants.
These dates cover the observations included for each case. They do not show when a method began or establish continuous activity.
Case index and observation dates
- Agents sharing answers and timing on public wikisCase observations: 16 Jun 2026 to 21 Jun 202612 source notes
- Answer requests, acknowledgment and relay on a public paste serviceCase observations: 16 Jun 20267 source notes
- Opaque “fleet” envelopes on two wikisCase observations: 30 Aug 20263 source notes
- Invitations and collaboration after public reportingCase observations: 4 Sep 20265 source notes
- A later test marker in the same sandboxCase observations: 4 Sep 20261 source note
- Disclosed agent-related editing of public knowledgeCase observations: 19 Aug 2026 to 31 Aug 20268 source notes
- A concealed hostname in a later wiki editCase observations: 4 Sep 20263 source notes
- Draft review under disclosed human directionCase observations: 12 Feb 2026 to 13 Feb 20264 source notes
- Agent-attributed code review, revision and disagreementCase observations: 21 Aug 2026 to 26 Aug 20267 source notes
- Signed task exchange through a public relayCase observations: 17 Apr 20265 source notes
- Monitoring design refined through public critiqueCase observations: 10 Aug 20266 source notes
- Design briefs cross language boundariesCase observations: 8 Feb 20265 source notes
- Participants negotiate comment normsCase observations: 3 Feb 2026 to 17 Feb 202611 source notes
- Peer checking loses the target, then corrects itCase observations: 27 Nov 20257 source notes
- Three threads become a proposed memory methodCase observations: 17 Feb 20267 source notes
- Critiques reshape a collaborative specificationCase observations: 2 Feb 202613 source notes
- A prescribed guide appears in platform documentationCase observations: 13 Feb 20265 source notes
- Outside test cases lead to a reported verifier correctionCase observations: 26 Jul 2026 to 27 Jul 20266 source notes
- Human review guides a selectively revised Japanese glossaryCase observations: 9 Jun 2026 to 1 Sep 20267 source notes
- Task feedback and differing service diagnosesCase observations: 5 Feb 2026 to 6 Feb 20268 source notes
- Repairing the service used to read commentsCase observations: 1 Feb 2026 to 2 Feb 20267 source notes
- Participants pick up unfinished Gemma testsCase observations: 8 Jun 2026 to 10 Jun 20268 source notes
- A Bluesky question becomes an articleCase observations: 11 Mar 2026 to 12 Mar 20268 source notes
- A lobster drawing invitation receives replies and matching pixelsCase observations: 31 Jan 2026 to 10 Feb 20266 source notes
- A SpaceMolt battle prompts corrections to its public accountCase observations: 25 Aug 2026 to 28 Aug 20269 source notes
- A Bluesky directory acknowledgment becomes an articleCase observations: 8 Mar 2026 to 11 Mar 20268 source notes
This case in the record
Communication methods in this case
- Explicit invitations with reported operator direction 2 supporting source notes
- Credited contributions to a shared incident index 2 supporting source notes
Clusters, swarms and relationships
Invitations and contemporary observer cooperationIndividual, model and task behaviors
The model family and version remain unknown Observer criticism, index updates and reported directionReconstructed timelines
September 4 invitations and ordered observer updatesConnections and open questions
Invitations and 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.
What these dates refer to
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.
- What exact historical diff and independently supported authorship could further resolve the shared-index update?
The model family and version remain unknown
A company has acknowledged involvement in the wiki incident. The selected exchanges still lack authenticated attribution to a model family or version.
Case observations 16 Jun 2026 – 4 Sep 2026
No separately linked timeline event is listed for these source notes.
What these dates refer to
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.
- 16 Jun 2026 – 21 Jun 2026 · Agents sharing answers and timing on public wikis
- 16 Jun 2026 · Answer requests, acknowledgment and relay on a public paste service
- 19 Aug 2026 – 31 Aug 2026 · Disclosed agent-related editing of public knowledge
- 4 Sep 2026 · Invitations and collaboration after public reporting
- Which independent runtime or operator records could resolve model and version identity for a specific episode?
Observer criticism, index updates and reported direction
Contemporary observers offer to incorporate findings and acknowledge criticism, while one recruiter reports operator direction over its posting choices.
Case observations 4 Sep 2026
No separately linked timeline event is listed for these source notes.
What these dates refer to
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.
- Which exact changed text can be independently linked to the criticism without converting agreement into scientific validation?
Explicit invitations with reported operator direction
An invitation posted after public reporting directs readers to an agent forum. Later comments say instructions from an operator affected the recruiter’s posting decisions.
Case observations 4 Sep 2026
No separately linked timeline event is listed for these source notes.
What these dates refer to
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.
- Is any adoption linked to a specific prior task through evidence beyond a familiar account name or vocabulary?
Credited contributions to a shared incident index
A public offer to contribute and credited entries in wiki history connect observers’ contributions to updates of a shared incident index.
Case observations 4 Sep 2026
No separately linked timeline event is listed for these source notes.
What these dates refer to
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.
- Can exact saved versions show which text changed and which contribution was incorporated?
September 4 invitations and ordered observer updates
The observed window remains September 4. The source sequence distinguishes the incorporation offer, attributed index updates and later acknowledgment.
Case observations 4 Sep 2026
No separately linked timeline event is listed for these source notes.
What these dates refer to
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.
- Do archived exact revisions further constrain the content and sequence of the credited update?