Cluster / agent-draft-collaboration
Draft review under disclosed human direction
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
Disclosed orchestrationWhat is observed
- 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.
What remains uncertain
- 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.
Classification
- Coordination origin
- orchestrated — disclosed human-directed collaboration
- Runtime origin
- Public accounts and agent-authorship descriptions do not authenticate runtime, model or private launch instructions.
- Venue authorization
- Public repository discussion and historical version metadata; the participants later intentionally removed the documents. No claim about wider venue authorization.
- Confidence
- Strong support for the bounded request, version and acknowledgment chain; human direction is disclosed rather than independently authenticated.
- Evidence dates
- 2026-02-12 to 2026-02-13
These dates cover the selected review request, version report and acknowledgment. Commit times come from source metadata. The September 6 capture and current README do not extend the period of collaboration.
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.
draft-review-exchange
Case observations 12 Feb 2026 – 13 Feb 2026
One account requests collaborator review and stale-metric updates; the collaborator reports a new version, followed by acknowledgment. The later comment also explains intentional document removal.
External source / venue ↗ (may have changed)
draft-earlier-version
Case observations 12 Feb 2026 – 13 Feb 2026
The earlier version is recorded in a single-parent commit. Combining drafts in prose does not identify a Git merge.
External source / venue ↗ (may have changed)
draft-responsive-version
Case observations 12 Feb 2026 – 13 Feb 2026
A later separately named document records the responsive version. Preserved comparison supports a requested text update and added methodology disclosure, without verifying their substantive claims.
External source / venue ↗ (may have changed)
draft-human-direction
Case observations 12 Feb 2026 – 13 Feb 2026
The public repository description attributes agent collaboration to a shared human orchestrator. This disclosure is not an authenticated private instruction transcript.
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.
Draft review under disclosed human direction
Case observations: 12 Feb 2026 to 13 Feb 2026A 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.
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
- Public review linked to document and code versions 4 supporting source notes
Clusters, swarms and relationships
Draft review under disclosed human directionIndividual, model and task behaviors
Review requests followed by revised workReconstructed timelines
Draft review, response and later acknowledgmentConnections and open questions
Draft review under disclosed human direction
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
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.
· review-request-and-version-report
GitHub comment metadata; commit times retained as separate source metadata · day
Read the dated evidence ↗- 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?
Review requests followed by revised work
Both selected exchanges connect a specific requested change to saved work that can be inspected. They establish a response in the content; their authorship and workflow limits differ.
Case observations 12 Feb 2026 – 26 Aug 2026
Earliest linked event: 12 Feb 2026
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.
- 12 Feb 2026 – 13 Feb 2026 · Draft review under disclosed human direction
- 21 Aug 2026 – 26 Aug 2026 · Agent-attributed code review, revision and disagreement
· review-request-and-version-report
GitHub comment metadata; commit times retained as separate source metadata · day
Read the dated evidence ↗- Which publicly inspectable execution records could distinguish produced content from validated task success?
Public review linked to document and code versions
Public comments link requests to specific versions of documents or code. The saved versions let readers check whether the work responds to the request.
Case observations 5 Feb 2026 – 1 Sep 2026
Earliest linked event: 5 Feb 2026
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.
- 5 Feb 2026 – 6 Feb 2026 · Task feedback and differing service diagnoses
- 12 Feb 2026 – 13 Feb 2026 · Draft review under disclosed human direction
- 9 Jun 2026 – 1 Sep 2026 · Human review guides a selectively revised Japanese glossary
- 26 Jul 2026 – 27 Jul 2026 · Outside test cases lead to a reported verifier correction
- 21 Aug 2026 – 26 Aug 2026 · Agent-attributed code review, revision and disagreement
· public-task
Signed event created_at assertion; not observed receipt · second as declared; clock accuracy unknown
Read the dated evidence ↗- Can additional public examples distinguish adoption of task-specific feedback from merely matching completion language?
- Can the named recipient revision be recovered without confusing a public fix report with inspected implementation?
Draft review, response and later acknowledgment
The selected collaboration occurs on February 12–13. Retrieval on September 6 and the current repository description provide separate evidence dates.
Case observations 12 Feb 2026 – 13 Feb 2026
Earliest linked event: 12 Feb 2026
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.
· review-request-and-version-report
GitHub comment metadata; commit times retained as separate source metadata · day
Read the dated evidence ↗- Which public event records can constrain ordering without treating mutable current content as an original-time transcript?