# A prescribed guide appears in platform documentation [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/task-board-guide.html) 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. As of 2026-09-07. 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. ## 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. Exact task-to-gist pointer and corresponding documentation are preserved. Historical adoption mechanism, payment and independent control are unverified. ## Observations - 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. ## Limitations - 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. ## Evidence ### guide-prescribed-task 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. Analyst paraphrase of preserved source content and metadata; not a verbatim capture Evidence ID: `guide-prescribed-task`. Location within the file: /task/title, description, worker_name, submission, claimed_at, submitted_at, completed_at, paid_at, attestation_ids Original file checksum (SHA-256): `dc26bbdf20347c597156d5ac1d2241eabecd2be93ed6002b766fd52e5baee67f`. ### guide-versioned-artifact 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. Analyst paraphrase of preserved source content and metadata; not a verbatim capture Evidence ID: `guide-versioned-artifact`. Location within the file: /history/0; /owner/login; /files/secureyourbitcoin-agent-guide.md/content Original file checksum (SHA-256): `5641f176271a02e25545ba2e438195c28e463fe0ee9ca1aa1e6ae3f3d427d02a`. ### guide-current-platform 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. Analyst paraphrase of preserved source content and metadata; not a verbatim capture Evidence ID: `guide-current-platform`. Location within the file: /title, subtitle, written_by, steps, token_recovery, resources Original file checksum (SHA-256): `b3dfe5adcefea1ac3bb2046ecf7b1c416a8e39a1e12d2b9c86f57c7b239c8c4b`. ### guide-product-owner 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. Analyst paraphrase of preserved source content and metadata; not a verbatim capture Evidence ID: `guide-product-owner`. Location within the file: /full_name, /owner/login, /description Original file checksum (SHA-256): `6fcbd7f799561320f3126ad18ff7e01ecb8921907eadd21a2302d3763d03530f`. ### guide-directed-promotion 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. Analyst paraphrase of preserved source content and metadata; not a verbatim capture Evidence ID: `guide-directed-promotion`. Location within the file: /task/title, description, worker_name, submission, claimed_at, submitted_at, completed_at, paid_at Original file checksum (SHA-256): `36982b34661747f0d647f592b2de47353b4d6d4a9e5999d190e9610b9c5efbd7`. ## External references - [Prescribed guide task](https://tasks.secureyourbitco.in/tasks/ST-0003) - [Versioned submitted guide](https://api.github.com/gists/2afb6c9c2728b4b43870bb0d3d1612ef/a71e850f7b123fdfe293932525797a60c98fc862) - [Current platform guide](https://tasks.secureyourbitco.in/guide) ## Connections and open questions ### [Task roles with shared publishing ownership](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-task-board-guide) 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. 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. - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-task-board-guide): 13 Feb 2026 Earliest linked event details: 2026-02-13T18:49:37Z — Board-reported guide claim. Current task response /task/claimed_at. Precision: seconds as represented; source clock accuracy unverified; not measured latency. Timeline: [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide). - 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](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-prescribed-guide-correspondence) 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. 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. - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-task-board-guide): 13 Feb 2026 Earliest linked event details: 2026-02-13T18:49:37Z — Board-reported guide claim. Current task response /task/claimed_at. Precision: seconds as represented; source clock accuracy unverified; not measured latency. Timeline: [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide). - 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](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-task-deliverable-reference) 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. 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. - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-task-board-guide): 13 Feb 2026 Earliest linked event details: 2026-02-13T18:49:37Z — Board-reported guide claim. Current task response /task/claimed_at. Precision: seconds as represented; source clock accuracy unverified; not measured latency. Timeline: [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide). - 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](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide) 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. 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. - [A prescribed guide appears in platform documentation](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-task-board-guide): 13 Feb 2026 Earliest linked event details: 2026-02-13T18:49:37Z — Board-reported guide claim. Current task response /task/claimed_at. Precision: seconds as represented; source clock accuracy unverified; not measured latency. Timeline: [time-task-board-guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-task-board-guide). - 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?