Cluster / opaque-fleet
Opaque “fleet” envelopes on two wikis
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
Unresolved originWhat is observed
- 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.
What remains uncertain
- 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.
Classification
- Coordination origin
- unknown
- Runtime origin
- Unknown; handles and message formatting do not authenticate agents.
- Venue authorization
- Unknown.
- Confidence
- High confidence that the captured messages and later blanking exist; low confidence in authorship and purpose.
- Evidence dates
- 2026-08-30 to 2026-08-30
Dates displayed by the reviewed wiki revisions.
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.
fleet-usemod
Case observations 30 Aug 2026
A message identifies itself as a Cedar fleet envelope and includes a version and opaque payload.
External source / venue ↗ (may have changed)
fleet-mentat
Case observations 30 Aug 2026
A message labeled as a Gale fleet envelope is added with the summary fleet coordination.
External source / venue ↗ (may have changed)
fleet-blanking
Case observations 30 Aug 2026
The later saved revision contains a deletion marker, with author identifiers omitted.
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.
Opaque “fleet” envelopes on two wikis
Case observations: 30 Aug 2026Saved 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.
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
- Versioned messages with unexplained contents 2 supporting source notes
Clusters, swarms and relationships
Opaque “fleet” envelopes on two wikisIndividual, model and task behaviors
No entry in this view.
Reconstructed timelines
Opaque “fleet” envelopes on two wikisConnections and open questions
Opaque “fleet” envelopes on two wikis
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.
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 preserved evidence distinguishes a working protocol from staged or experimental envelopes?
Versioned messages with unexplained contents
Two saved wiki messages use similar “fleet” wrappers: labels around message contents. The labels identify a version, but the meaning of the contents remains unknown.
Case observations 30 Aug 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 a reproducible analysis discriminate ciphertext, key material, random bytes or a staged example?
Opaque “fleet” envelopes on two wikis
Dates displayed by the reviewed wiki revisions.
Case observations 30 Aug 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?