# Draft review under disclosed human direction [Latest edition](https://agentsy.live/) · [Understanding agent swarms](https://agentsy.live/releases/28e406dd0c184e1117499de9/methodology.md#reading-terms) [Index](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md) · [HTML](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/agent-draft-collaboration.html) 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. As of 2026-09-07. 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. ## 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. Strong support for the bounded request, version and acknowledgment chain; human direction is disclosed rather than independently authenticated. ## Observations - 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. ## Limitations - 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. ## Evidence ### draft-review-exchange 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. analyst paraphrase; not a verbatim capture Evidence ID: `draft-review-exchange`. Location within the file: comments3893712163,3893815451,3894483012; created_at and selected review/version/acknowledgment paragraphs Original file checksum (SHA-256): `de0b78e9aa34e431383a1477c62dd2c8fc191e106c203d76a5913956bdca22d4`. ### draft-earlier-version The earlier version is recorded in a single-parent commit. Combining drafts in prose does not identify a Git merge. analyst paraphrase; not a verbatim capture Evidence ID: `draft-earlier-version`. Location within the file: sha ea851816e1f2d6fa64bc6fcd3c59992b660ac0c1; commit timestamps, parents, files metadata Original file checksum (SHA-256): `887ffeac4a401f3d3f727a5134cf23882e812b9c079f39a13502f5cdb9aeae52`. ### draft-responsive-version 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. analyst paraphrase; not a verbatim capture Evidence ID: `draft-responsive-version`. Location within the file: sha dd3d333be2e76e6d92d888660b5c62e893c6f7bb; commit timestamps, parents and added-file metadata Original file checksum (SHA-256): `9968eb40d29f132e68bcc20f60d549f9b142521eb2a9c910fd4cb8f5fb880b03`. ### draft-human-direction The public repository description attributes agent collaboration to a shared human orchestrator. This disclosure is not an authenticated private instruction transcript. analyst paraphrase; not a verbatim capture Evidence ID: `draft-human-direction`. Location within the file: line7 and Credits entry for human orchestrator; current README captured2026-09-06 Original file checksum (SHA-256): `64e6ed9945e4ab8727aa114c3037f8a99c33a2bb1daf5d95f1424ab562e08bc0`. ## External references - [Public review and acknowledgment discussion](https://github.com/driftcornwall/drift-memory/issues/29) - [Repository description](https://github.com/driftcornwall/drift-memory) ## Connections and open questions ### [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-agent-draft-collaboration) 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). - 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](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-responsive-artifact-revision) 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. 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 - [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-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). - Which publicly inspectable execution records could distinguish produced content from validated task success? ### [Public review linked to document and code versions](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-review-linked-versioned-artifacts) 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. 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 - [Draft review under disclosed human direction](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-agent-draft-collaboration): 12 Feb 2026 – 13 Feb 2026 - [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 - [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 - [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-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). - 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](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-agent-draft-collaboration) 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. 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). - Which public event records can constrain ordering without treating mutable current content as an original-time transcript?