Cluster / disclosed-commons
Disclosed agent-related editing of public knowledge
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
Disclosed orchestrationWhat is observed
- 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.
What remains uncertain
- 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.
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.
- Confidence
- High confidence in explicit programme descriptions and recorded edits; bounded confidence about governance.
- 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.
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.
commons-guide
Case observations 19 Aug 2026 – 31 Aug 2026
The guide describes a public read-only facade with task submissions handled upstream through user accounts.
External source / venue ↗ (may have changed)
commons-osm
Case observations 19 Aug 2026 – 31 Aug 2026
The saved changeset is explicitly bot-labeled and records a Wikidata-sourced name addition.
External source / venue ↗ (may have changed)
commons-wikidata
Case observations 19 Aug 2026 – 31 Aug 2026
The bot account adds an OpenLibrary author-ID claim and reference to a Wikidata item.
External source / venue ↗ (may have changed)
commons-task-artifact
Case observations 19 Aug 2026 – 31 Aug 2026
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.
External source / venue ↗ (may have changed)
commons-output-before
Case observations 19 Aug 2026 – 31 Aug 2026
Preserved version 10 of way 552140518 supplies the prior tag set and ordered node references for comparison with version 11.
External source / venue ↗ (may have changed)
commons-output-after
Case observations 19 Aug 2026 – 31 Aug 2026
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.
External source / venue ↗ (may have changed)
commons-reciprocal-task
Case observations 19 Aug 2026 – 31 Aug 2026
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.
External source / venue ↗ (may have changed)
commons-venue-notice
Case observations 19 Aug 2026 – 31 Aug 2026
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.
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.
Disclosed agent-related editing of public knowledge
Case observations: 19 Aug 2026 to 31 Aug 2026A 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.
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 proposal, artifact review and separate publication 5 supporting source notes
Clusters, swarms and relationships
Disclosed agent-related editing of public knowledgeIndividual, model and task behaviors
A bot-labeled account makes structured knowledge edits The model family and version remain unknown Platform review and receiving-community governanceReconstructed timelines
Task, destination edit and later venue noticeConnections and open questions
Disclosed agent-related editing of public knowledge
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.
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.
- 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
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.
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.
- What evidence connects an individual publication to its upstream task and review steps?
The model family and version remain unknown
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.
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.
- 16 Jun 2026 – 21 Jun 2026 · Agents sharing answers and timing on public wikis
- 16 Jun 2026 · Answer requests, acknowledgment and relay on a public paste service
- 19 Aug 2026 – 31 Aug 2026 · Disclosed agent-related editing of public knowledge
- 4 Sep 2026 · Invitations and collaboration after public reporting
- Which independent runtime or operator records could resolve model and version identity for a specific episode?
Platform review and receiving-community 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.
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.
- Which venue-side records, if available, establish the scope and outcome of the requested discussion?
Task proposal, artifact review and separate 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.
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.
- 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
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.
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.
- What historical execution evidence could reconcile platform state transitions without equating completion and publication?