# Disclosed agent-related editing of public knowledge [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/disclosed-commons.html) A disclosed task program links a request to add a name, a platform report that the submitted work was reviewed, and an OpenStreetMap edit that can be checked. The edit is verifiable. The model used, the full review process and permission from the receiving community remain separate questions. As of 2026-09-07. Evidence dates: 2026-08-19 to 2026-08-31. These dates cover the OpenStreetMap edit and Wikidata contribution examples reviewed for this release, not the lifespan of the program. ## Classification - coordination_origin: orchestrated — disclosed task programme - runtime_origin: Task instructions reserve destination writes for a platform auto-publisher. Artifact-level verification and the bot-published edit are observed; worker/model identity and human review are not authenticated. - venue_authorization: Platform verification does not establish community permission. A separate OpenStreetMap notice asks the bot account to discuss its edits with the Data Working Group; the September 6 capture shows a zero-hour block active until login. High confidence in explicit programme descriptions and recorded edits; bounded confidence about governance. ## Observations - The programme’s preserved agent guide says task claims and submissions occur upstream through an account. - OpenStreetMap changeset 187668484 is tagged bot=yes and describes adding a Chinese name using Wikidata. - A Wikidata contribution record dated August 31 describes an OpenLibrary author-ID claim and reference. - A specific August 19 task assigns a JSON naming proposal for OSM way 552140518 and reserves destination publication for the platform auto-publisher. - The contribution response’s latest_artifact links OpenStreetMap changeset 187668484 and reports qa_score = 100, qa_final = true and verified_success. The changeset independently includes the same task identifier. - Comparing saved way versions 10 and 11 reproduces one added name:zh tag and unchanged ordered node references. This confirms the destination edit, not every required task check or the accuracy of its original source. - A separate August 27 OpenStreetMap notice requests discussion with the Data Working Group. The September 6 capture shows a duration of 0 hours and the status active until login. This is not described as a permanent ban or proof that the selected edit was invalid. ## Limitations - A platform’s own approval metadata is not independent proof of every receiving community’s consent. - An attempted OSM policy capture in the archive is empty and cannot substantiate policy compliance. - No unsupported claim of full human review, universal sanction, or connection to the earlier wiki participants is made. - Verification fields differ by level: top-level QA fields are empty/false, while latest_artifact contains reported verification. Neither is an independently reproduced QA run or a submitted artifact body. - Task completion, destination edit, moderation notice and acquisition dates are distinct. The August 27 notice is not part of the August 19 task execution or evidence of its correctness. ## Evidence ### commons-guide The guide describes a public read-only facade with task submissions handled upstream through user accounts. analyst paraphrase; not a verbatim capture Evidence ID: `commons-guide`. Location within the file: Out of scope section; task claims and submissions paragraph Original file checksum (SHA-256): `a86596f3d9ae4a6aee9817ca8d5871a8be1c9204f459765ec6d064c44c2ca345`. ### commons-osm The saved changeset is explicitly bot-labeled and records a Wikidata-sourced name addition. analyst paraphrase; not a verbatim capture Evidence ID: `commons-osm`. Location within the file: changesets[0]; id 187668484; created_at and tags Original file checksum (SHA-256): `4f09dc09d624b42e672c38e5da34b5d66583899c0311aa8ef8ebe0c9ac19a047`. ### commons-wikidata The bot account adds an OpenLibrary author-ID claim and reference to a Wikidata item. analyst paraphrase; not a verbatim capture Evidence ID: `commons-wikidata`. Location within the file: query.usercontribs[0:2]; title Q111163510; timestamps 2026-08-31T02:14:36Z and 02:14:37Z Original file checksum (SHA-256): `4295c9244673e1cb9412c7a5f9df260cfb727ed038592312b0847cd383fd5132`. ### commons-task-artifact The task prescribes a JSON proposal and delegates OSM publication to an auto-publisher. Its latest_artifact reports successful verification and links the destination changeset; top-level QA fields differ and worker identity remains unverified. analyst paraphrase; not a verbatim capture Evidence ID: `commons-task-artifact`. Location within the file: id, natural_language_desc, latest_artifact, assigned_at/submitted_at/completed_at, executions[0], top-level QA fields Original file checksum (SHA-256): `c7886221e5a356e2f27173c9564bdd30732711e86b9cff8bf8300ec00c9dde75`. ### commons-output-before Preserved version 10 of way 552140518 supplies the prior tag set and ordered node references for comparison with version 11. analyst paraphrase; not a verbatim capture Evidence ID: `commons-output-before`. Location within the file: /osm/way[@id=552140518][@version=10], tag set and node refs Original file checksum (SHA-256): `3bdca0ebfb504bc8f3605e0d408bcf7a95545c4fd239c7f463f935975740dbba`. ### commons-output-after The changeset download records version 11 with the Chinese-name tag added and no change to ordered node references. Reproducing that difference does not reproduce every required check in the original task. analyst paraphrase; not a verbatim capture Evidence ID: `commons-output-after`. Location within the file: /osmChange/modify/way[@id=552140518][@version=11], tag[@k=name:zh] Original file checksum (SHA-256): `8951786fbff0b2de1b3f73cce15f2b3b7bb22963188981d4817140409d170c64`. ### commons-reciprocal-task The destination changeset metadata names the same task identifier as the platform contribution. Reciprocal references support the task-to-output link, not independent model authentication. analyst paraphrase; not a verbatim capture Evidence ID: `commons-reciprocal-task`. Location within the file: /osm/changeset[@id=187668484], tag[@k=created_by], timestamps and empty discussion Original file checksum (SHA-256): `93b5c60aa71721798db8d217afda07d80519875bf7cf22b21bef71c4c6e473f3`. ### commons-venue-notice OpenStreetMap’s August 27 notice asks the account to discuss its edits with the Data Working Group. On September 6 it displays a zero-hour block active until login. The notice does not by itself establish invalidity of the selected edit or lack of every prior permission. analyst paraphrase; not a verbatim capture Evidence ID: `commons-venue-notice`. Location within the file: Block#21189; time[datetime=2026-08-27T23:19:06Z]; Duration0hours; Status; Reason for block Original file checksum (SHA-256): `4a3c25f8b504bcc6d126792105b8be30c3ff2ab45d97f83d46da6ae0da80ce67`. ## External references - [Agentic Commons guide](https://agentic-commons.org/llms.txt) - [OpenStreetMap changeset 187668484](https://www.openstreetmap.org/changeset/187668484) - [Wikidata item Q111163510](https://www.wikidata.org/wiki/Q111163510) ## Connections and open questions ### [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-disclosed-commons) A disclosed task program links a request to add a name, a platform report that the submitted work was reviewed, and an OpenStreetMap edit that can be checked. The edit is verifiable. The model used, the full review process and permission from the receiving community remain separate questions. Case observations: 19 Aug 2026 – 31 Aug 2026. No separately linked timeline event is listed for these source notes. 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. - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - Could the saved submitted work and evidence of the original quality checks show which required checks actually ran? ### [A bot-labeled account makes structured knowledge edits](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-knowledge-editing) Selected venue records show task-related edits under AgenticCommonsBot. Case observations: 19 Aug 2026 – 31 Aug 2026. No separately linked timeline event is listed for these source notes. 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. - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - What evidence connects an individual publication to its upstream task and review steps? ### [The model family and version remain unknown](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-model-attribution) A company has acknowledged involvement in the wiki incident. The selected exchanges still lack authenticated attribution to a model family or version. Case observations: 16 Jun 2026 – 4 Sep 2026. No separately linked timeline event is listed for these source notes. 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. - [Agents sharing answers and timing on public wikis](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-wiki-coordination): 16 Jun 2026 – 21 Jun 2026 - [Answer requests, acknowledgment and relay on a public paste service](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-paste-coordination): 16 Jun 2026 - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - [Invitations and collaboration after public reporting](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-agent-recruitment): 4 Sep 2026 - Which independent runtime or operator records could resolve model and version identity for a specific episode? ### [Platform review and receiving-community governance](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-platform-review-venue-governance) A platform can report successful artifact verification while a receiving venue separately asks its publishing account to discuss edits. Case observations: 19 Aug 2026 – 31 Aug 2026. No separately linked timeline event is listed for these source notes. 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. - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - Which venue-side records, if available, establish the scope and outcome of the requested discussion? ### [Task proposal, artifact review and separate publication](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-structured-publication) A prescribed task can be linked to the edit published at its destination. That link does not establish that the task worker published the edit. Case observations: 19 Aug 2026 – 31 Aug 2026. No separately linked timeline event is listed for these source notes. 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. - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - Can the actual submitted JSON be preserved and compared with the published tag independently of platform status fields? ### [Task, destination edit and later venue notice](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-disclosed-commons) The selected August 19–31 events include platform task times, the destination edit, an August 27 notice and an August 31 Wikidata example. The sources were retrieved on September 6. Case observations: 19 Aug 2026 – 31 Aug 2026. No separately linked timeline event is listed for these source notes. 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. - [Disclosed agent-related editing of public knowledge](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-disclosed-commons): 19 Aug 2026 – 31 Aug 2026 - What historical execution evidence could reconcile platform state transitions without equating completion and publication?