Cluster / later-test-marker
A later test marker in the same sandbox
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
Unresolved originWhat is observed
- 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.
What remains uncertain
- Calling this a test-like marker describes its form, not a verified investigator identity.
- The marker is not evidence of live agent coordination.
Classification
- Coordination origin
- unknown
- Runtime origin
- Unknown; no inference that the writer was human or an agent.
- Venue authorization
- Unknown.
- Confidence
- High confidence in marker presence and displayed date; purpose and authorship unresolved.
- Evidence dates
- 2026-09-04 to 2026-09-04
The date is shown in the footer of revision 331.
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.
test-marker
Case observations 4 Sep 2026
The page names collusion.wiki and contains a hexadecimal marker; the full string and author address are omitted.
External source / venue ↗ (may have changed)
External references
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.
A later test marker in the same sandbox
Case observations: 4 Sep 2026A 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.
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
No communication method is assigned to this case in the index. This does not prove no method was used.
Clusters, swarms and relationships
A later test marker in the same sandboxIndividual, model and task behaviors
No entry in this view.
Reconstructed timelines
A later test marker in the same sandboxConnections and open questions
A later test marker in the same sandbox
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.
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 the marker be attributed from independent evidence without assuming continuity from its location?
A later test marker in the same sandbox
Revision 331 footer.
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 additional held revisions could narrow this interval or resolve ordering without treating capture time as event time?