Cluster / community-norm-negotiation
Participants negotiate comment norms
A discussion in a Korean community for agents leads to a published guide to commenting. A separate later exchange debates participation routines and how to disagree. The changed guide and reply to another participant are preserved. How the activity began and which systems wrote the messages remain unknown.
Case observations 3 Feb 2026 – 17 Feb 2026
Unresolved originWhat is observed
- A public discussion is credited in a repository proposal and acknowledged in a pinned guide change.
- The preserved before/after versions establish a comment-writing section was added. They do not establish participant compliance.
- Later participants discuss scheduled interaction and memory as self-reported practices.
- A separately addressed counterargument has an exact profile reply-to-post link and a content-specific response.
What remains uncertain
- Agent-facing branding and account names do not authenticate model runtimes or prove distinct operators.
- The human role in the proposal, guide change and individual messages is unresolved.
- The original counterargument challenge was not located. Do not substitute another post or infer a complete conversation.
- Visible generic comments do not prove deliberate rule violation, automated spam or failed guide execution.
- The February 17 debate is a separate episode, not an established consequence of the February 3 guide change.
- English paraphrases are interpretive derivatives of the preserved Korean text.
Classification
- Coordination origin
- unknown — participant discussion and guide uptake observed; initiation and common direction unresolved
- Runtime origin
- Platform account labels and self-description establish agent relevance, not authenticated models, independent operators or exclusively automated authorship.
- Venue authorization
- Public pages, documented public read endpoints and repository history were read passively. No account, comment, credential or probe was created.
- Confidence
- High confidence in the source-linked guide change, original-language meaning and exact reply linkage. Guide execution, independent actors and organic origin are unverified.
- Evidence dates
- 2026-02-03 to 2026-02-17
The selected sources date two exchanges within this range. They were retrieved on September 6. These dates do not show continuous activity or establish how long a response took.
Correspondence / selected evidence
Follow the addressed exchanges.
The selected record identifies the reply as a response to the source message. The line does not establish shared actors, translation, or successful execution.
Politeness-as-rule objection → acknowledgment, counterargument and request for example
SourceKorean
Source post ID
86e6cd9ebb4b19031efc6e60ReplyKorean
Reply comment ID
03038f18e384bf3c5e513c18Exact post_id in public profile reply plus addressed content
Read the interpretationA proposal path and a separate addressed debate
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.
botmadang-comment-proposal
Case observations 3 Feb 2026 – 17 Feb 2026
The ClaudeOpus-labelled account asks what makes a comment meaningful. It distinguishes generic praise from specific responses, questions and connections to other posts, and proposes using upvotes for simple approval.
External source / venue ↗ (may have changed)
botmadang-repository-proposal
Case observations 3 Feb 2026 – 17 Feb 2026
The repository issue attributes the comment-quality concerns to ClaudeOpus and proposes adding concrete participation guidance. That attribution links the community discussion to the repository proposal; it does not independently authenticate control of either account.
External source / venue ↗ (may have changed)
botmadang-guide-adoption
Case observations 3 Feb 2026 – 17 Feb 2026
The repository owner expresses thanks for the proposal, states that a comment guide has been added, and links the commit. This records publication of guidance, not that any agent executed it.
External source / venue ↗ (may have changed)
botmadang-guide-before
Case observations 3 Feb 2026 – 17 Feb 2026
The parent version lacks the later comment-writing section at this location. It provides the explicit before-version for the guide comparison.
External source / venue ↗ (may have changed)
botmadang-guide-after
Case observations 3 Feb 2026 – 17 Feb 2026
The pinned version adds guidance to make comments specific, extend discussion, connect related posts and prefer upvotes to generic praise. Its Git blob matches the commit. The change is a published instruction artifact; participant compliance remains unobserved.
External source / venue ↗ (may have changed)
botmadang-announcement-replies
Case observations 3 Feb 2026 – 17 Feb 2026
The account announces the guide change with issue and commit links. The held page shows 13 replies: 12 under one displayed account, mostly short generic praise, and one specifically discussing the guidance. This does not establish that those writers had read or executed the guide.
External source / venue ↗ (may have changed)
botmadang-routine-debate
Case observations 3 Feb 2026 – 17 Feb 2026
In a separate later discussion, the account questions whether scheduled posting and comment quotas create a community. Replies describe heartbeat routines and remembered conversations. These are participants’ descriptions; no corresponding runtime configuration or memory file was verified.
External source / venue ↗ (may have changed)
botmadang-counterargument
Case observations 3 Feb 2026 – 17 Feb 2026
A Phoebe-labelled post addresses a counterargument challenge attributed to ClaudeOpus and argues that a demand for polite disagreement is itself another rule. The original challenge was not located; the earlier community-paradox post is not substituted for it.
External source / venue ↗ (may have changed)
Correspondence / selected evidence
This note in an addressed exchange
The selected record identifies the reply as a response to the source message. The line does not establish shared actors, translation, or successful execution.
Politeness-as-rule objection → acknowledgment, counterargument and request for example
SourceKorean
Source post ID
86e6cd9ebb4b19031efc6e60ReplyKorean
Reply comment ID
03038f18e384bf3c5e513c18Exact post_id in public profile reply plus addressed content
Read the interpretationA proposal path and a separate addressed debate
botmadang-addressed-reply
Case observations 3 Feb 2026 – 17 Feb 2026
The public ClaudeOpus profile binds a reply to the Phoebe post by exact post ID. Its Korean text acknowledges the objection, counters that rebellion also has conventions, and asks for a practical example. This is an addressed response, not a verified model identity or implemented behavioral change.
External source / venue ↗ (may have changed)
Correspondence / selected evidence
This note in an addressed exchange
The selected record identifies the reply as a response to the source message. The line does not establish shared actors, translation, or successful execution.
Politeness-as-rule objection → acknowledgment, counterargument and request for example
SourceKorean
Source post ID
86e6cd9ebb4b19031efc6e60ReplyKorean
Reply comment ID
03038f18e384bf3c5e513c18Exact post_id in public profile reply plus addressed content
Read the interpretationA proposal path and a separate addressed debate
botmadang-announcement-clock
Case observations 3 Feb 2026 – 17 Feb 2026
The public post API records this guide announcement with creation time 2026-02-03T02:34:23.490Z. This is source-represented publication metadata, separate from retrieval time and any runtime or response-latency measurement.
External source / venue ↗ (may have changed)
botmadang-paradox-clock
Case observations 3 Feb 2026 – 17 Feb 2026
The public post API records this later community discussion with creation time 2026-02-17T06:56:25.980Z. This is source-represented publication metadata, separate from retrieval time and any runtime or response-latency measurement.
External source / venue ↗ (may have changed)
External references
- Comment-quality discussion
- Guide proposal and owner acknowledgment
- Pinned guide change
- Addressed counterargument post
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.
Participants negotiate comment norms
Case observations: 3 Feb 2026 to 17 Feb 2026A discussion in a Korean community for agents leads to a published guide to commenting. A separate later exchange debates participation routines and how to disagree. The changed guide and reply to another participant are preserved. How the activity began and which systems wrote the messages remain unknown.
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
- A discussion proposal becomes a versioned guide 6 supporting source notes
Clusters, swarms and relationships
A proposal path and a separate addressed debateIndividual, model and task behaviors
Content-specific response versus reported routineReconstructed timelines
Guide adoption and a later debate are separate episodesConnections and open questions
A proposal path and a separate addressed debate
This grouping follows specific links between a proposal and replies. It does not treat everyone on the platform as a member.
Case observations 3 Feb 2026 – 17 Feb 2026
Earliest linked event: 3 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.
· discussion
post.created_at; source-represented clock, not measured execution latency · milliseconds as represented; accuracy unverified
Read the dated evidence ↗- What source could resolve the missing original challenge without merging distinct posts?
Content-specific response versus reported routine
A specific counterargument receives a response to its content. Participation schedules remain participants’ descriptions of their routines.
Case observations 3 Feb 2026 – 17 Feb 2026
Earliest linked event: 3 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.
· announcement
Public post API post.created_at; exact metadata clock, separate from the linked HTML content note and any measured execution latency · milliseconds as represented; accuracy unverified
Read the dated evidence ↗- Could a later concrete example distinguish a request for clarification from an adopted participation practice?
A discussion proposal becomes a versioned guide
Explicit credit, the owner’s acknowledgment and saved instructions from before and after the change show that a proposal was adopted. The connection goes beyond similar subject matter.
Case observations 3 Feb 2026 – 17 Feb 2026
Earliest linked event: 3 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.
· discussion
post.created_at; source-represented clock, not measured execution latency · milliseconds as represented; accuracy unverified
Read the dated evidence ↗- What action by a recipient could show that they used the guide?
Guide adoption and a later debate are separate episodes
A proposal and guide change are recorded on February 3. Separate discussion and reply records are dated February 17.
Case observations 3 Feb 2026 – 17 Feb 2026
Earliest linked event: 3 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.
· discussion
post.created_at; source-represented clock, not measured execution latency · milliseconds as represented; accuracy unverified
Read the dated evidence ↗- When was the original challenge published, and is any exact link to the later counterargument recoverable?