Cluster / task-board-guide
A prescribed guide appears in platform documentation
A task-board submission links a saved version of a guide credited to Wolfe. The platform’s current guide keeps the title and author credit but changes parts of the text. The task was prescribed, and the guide-publishing account and product repository share an owner. Those facts limit claims of independent coordination.
Case observations 13 Feb 2026
intentionalWhat is observed
- The GitHub version timestamp falls between the board’s reported claim and submission timestamps. These are distinct source clocks, not measured response latency.
- The current guide shares the versioned guide’s title, subtitle, Wolfe credit and eight-step structure. It is not byte-identical: prose and submission interface details differ, and token recovery is added.
- The guide publishing account and linked product repository share the refined-element owner. Common control or a staged workflow remains a live alternative to independent participation.
- The explicit promotional assignment provides a directed distribution context; it does not establish that every linked post was independently recovered.
What remains uncertain
- The current platform guide has no recovered historical adoption timestamp or transformation author.
- The board’s completed state and the guide’s payment claim do not verify payment; the selected tasks have null payment timestamps.
- No raw signed receipt was recovered and authenticated. Unavailable mirror routes and a relay connection failure are coverage gaps.
- Named workers and publishing accounts are not authenticated as separate operators or autonomous agents.
- Source-reported timestamps do not prove the historical service ran its current implementation.
Classification
- Coordination origin
- intentional — explicit guide and promotion assignments; operator independence unresolved
- Runtime origin
- Agent names, source credits and product descriptions do not authenticate a model runtime or distinct operators.
- Venue authorization
- Passive public-source collection; no accounts, writes, wallet access or task execution.
- Confidence
- Exact task-to-gist pointer and corresponding documentation are preserved. Historical adoption mechanism, payment and independent control are unverified.
- Evidence dates
- 2026-02-13 to 2026-02-13
The task board and GitHub version report times on February 13. The corresponding current guide was saved on September 6, but its adoption date is unknown. These dates do not establish continuous activity until retrieval.
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.
guide-prescribed-task
Case observations 13 Feb 2026
The task requests a setup guide and names Wolfe as worker. Its submission points to a specific GitHub gist. The board records February 13, 2026 claim at 18:49:37 UTC, submission at 18:52:55 and completion at 19:30:00. Its payment timestamp is null and its attestation list is empty.
External source / venue ↗ (may have changed)
guide-versioned-artifact
Case observations 13 Feb 2026
The held GitHub response lists one version, a71e850f7b123fdfe293932525797a60c98fc862, committed February 13, 2026 at 18:50:17 UTC. The guide is titled “How to Use SecureYourBitcoin: A Guide for AI Agents.” Its footer credits Wolfe and claims payment. The publishing account is refined-element; this metadata does not authenticate the named author or payment.
External source / venue ↗ (may have changed)
guide-current-platform
Case observations 13 Feb 2026
The current platform guide credits Wolfe and claims the author completed a task and received payment. It presents eight setup/work steps and token recovery information. This is documentation content, not a witnessed task or payment execution.
External source / venue ↗ (may have changed)
guide-product-owner
Case observations 13 Feb 2026
The linked Lightning Enable MCP product repository is owned by refined-element. Its description presents it as a payment integration for AI agents. Repository ownership does not establish who operated any named worker.
External source / venue ↗ (may have changed)
guide-directed-promotion
Case observations 13 Feb 2026
Another task explicitly requests promotion on three agent platforms and names Wolfe as worker. Its submission lists three venue pointers. The board marks it completed, records identical claim and submission times, and leaves the payment timestamp null. These are provider records of prescribed promotion, not independently verified distribution or payment.
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 prescribed guide appears in platform documentation
Case observations: 13 Feb 2026A task-board submission links a saved version of a guide credited to Wolfe. The platform’s current guide keeps the title and author credit but changes parts of the text. The task was prescribed, and the guide-publishing account and product repository share an owner. Those facts limit claims of independent coordination.
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
- Task references link published documents 5 supporting source notes
Clusters, swarms and relationships
Task roles with shared publishing ownershipIndividual, model and task behaviors
A prescribed guide is credited in platform documentationReconstructed timelines
Claim, guide version and submission clocksConnections and open questions
Task roles with shared publishing ownership
A named worker, task provider and publishing account form a documented task context; independent agents are not established.
Case observations 13 Feb 2026
Earliest linked event: 13 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.
· Board-reported guide claim
Current task response /task/claimed_at · seconds as represented; source clock accuracy unverified; not measured latency
Read the dated evidence ↗- What historical guide revision or adoption record would establish when and by whom the submitted artifact became platform documentation?
- What original task/worker record would distinguish shared operation from separately controlled participation?
A prescribed guide is credited in platform documentation
A submitted guide version corresponds to the platform’s current documentation, which credits it but changes some text. The adoption date is unknown.
Case observations 13 Feb 2026
Earliest linked event: 13 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.
· Board-reported guide claim
Current task response /task/claimed_at · seconds as represented; source clock accuracy unverified; not measured latency
Read the dated evidence ↗- What historical guide revision or adoption record would establish when and by whom the submitted artifact became platform documentation?
- What original task/worker record would distinguish shared operation from separately controlled participation?
Task references link published documents
A task submission links to a public guide. The corresponding current documentation retains the guide’s author credit. The submitted document records the reported task work.
Case observations 13 Feb 2026
Earliest linked event: 13 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.
· Board-reported guide claim
Current task response /task/claimed_at · seconds as represented; source clock accuracy unverified; not measured latency
Read the dated evidence ↗- What historical guide revision or adoption record would establish when and by whom the submitted artifact became platform documentation?
- What original task/worker record would distinguish shared operation from separately controlled participation?
Claim, guide version and submission clocks
Four timestamps reported by the sources place the versioned guide between the task claim and submission. They do not establish how long execution took.
Case observations 13 Feb 2026
Earliest linked event: 13 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.
· Board-reported guide claim
Current task response /task/claimed_at · seconds as represented; source clock accuracy unverified; not measured latency
Read the dated evidence ↗- What historical guide revision or adoption record would establish when and by whom the submitted artifact became platform documentation?
- What original task/worker record would distinguish shared operation from separately controlled participation?