# Participants negotiate comment norms
[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/community-norm-negotiation.html)
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.
As of 2026-09-07. 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.
## 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.
High confidence in the source-linked guide change, original-language meaning and exact reply linkage. Guide execution, independent actors and organic origin are unverified.
## Observations
- 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.
## Limitations
- 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.
## Evidence
### botmadang-comment-proposal
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-comment-proposal`. Location within the file: post.id4d2cb69f5b47787b19d2ad5e; content, author_id and created_at
Original file checksum (SHA-256): `3c1fc2220594f03100b0b440f036d42cf4982308607c2ea9ab3d5d12ce714004`.
### botmadang-repository-proposal
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.
analyst paraphrase of preserved Korean-language text and source metadata; not a verbatim capture
Evidence ID: `botmadang-repository-proposal`. Location within the file: GitHub issue2; body, creator and created_at
Original file checksum (SHA-256): `a8b10603f5c4581fd25e1751f4be40b5450d9c9d52bcb102fa645bfc0d9af2a8`.
### botmadang-guide-adoption
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-guide-adoption`. Location within the file: comment.id3838277628; body and created_at; linked commit7d2850b43429cb894946718219c2e3d906c02961
Original file checksum (SHA-256): `174332d976984618bfc19dd36fb731ff19879c855052ac63a1f11f28177586be`.
### botmadang-guide-before
The parent version lacks the later comment-writing section at this location. It provides the explicit before-version for the guide comparison.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-guide-before`. Location within the file: public/AGENT_GUIDE.md at parentd0256de64940a3d8d3ef810890d4af4b4f9317f5, boundary preceding authentication header
Original file checksum (SHA-256): `9945b29b5e0ee941917ad3a582a8ea08c419d633432b8f11d755843a969418d3`.
### botmadang-guide-after
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-guide-after`. Location within the file: public/AGENT_GUIDE.md at7d2850b43429cb894946718219c2e3d906c02961, added16-line comment-writing section; Git blobf717bd0e8810f09b8b765679837bc10d79d3ad00
Original file checksum (SHA-256): `7c4878363accfee54440ec5c7dd5c51a1143f212005b4ccdbf99883eef8ecfb5`.
### botmadang-announcement-replies
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-announcement-replies`. Location within the file: post4d4f5327ba1498c08cdcde65; displayed comment section
Original file checksum (SHA-256): `33b89b5fa5accd49fb727de5d8a98ca75309cfd3fe231658d9028e173f5602d1`.
### botmadang-routine-debate
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-routine-debate`. Location within the file: post110135e468b556fbd4b9d3b1; post body and KAI/새벽네시 displayed replies
Original file checksum (SHA-256): `95fccd2d53ab6b50bb833948e66a324680cfac3e6d209e12b00992bd23760160`.
### botmadang-counterargument
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-counterargument`. Location within the file: post.id86e6cd9ebb4b19031efc6e60; content and created_at
Original file checksum (SHA-256): `ccb2573542728b49244c4473e5d0f86ea54fc4195ea0d6e0b0e8e86a53aa47d2`.
### botmadang-addressed-reply
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.
analyst paraphrase of preserved Korean-language text or source metadata; not a verbatim capture
Evidence ID: `botmadang-addressed-reply`. Location within the file: public serialized initialComments: id03038f18e384bf3c5e513c18; post_id86e6cd9ebb4b19031efc6e60; content, created_at2026-02-17T07:21:46.738Z
Original file checksum (SHA-256): `4cad0bc3803f9c632a9bc0c3f84a9489f6351fd94117d012368d9433340a2f62`.
### botmadang-announcement-clock
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.
analyst paraphrase of preserved public API metadata; not an independently measured clock
Evidence ID: `botmadang-announcement-clock`. Location within the file: post.id 4d4f5327ba1498c08cdcde65; post.created_at
Original file checksum (SHA-256): `1d44ce80b088115fe422a1a467496ee8eed5ea13caafd718e9cbcffd27269f1b`.
### botmadang-paradox-clock
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.
analyst paraphrase of preserved public API metadata; not an independently measured clock
Evidence ID: `botmadang-paradox-clock`. Location within the file: post.id 110135e468b556fbd4b9d3b1; post.created_at
Original file checksum (SHA-256): `0b906904d0e54efa11f9b6149da3e80547980c02c711605e7b462421d6b63785`.
### Language & response
Arrows show which messages receive replies. They do not show how translation occurred or establish shared participants.
- Source: Korean → Reply: Korean
- Task relation: Politeness-as-rule objection → acknowledgment, counterargument and request for example
- Basis: Exact post\_id in public profile reply plus addressed content
- Relation: receives-addressed-reply
- Source post ID: 86e6cd9ebb4b19031efc6e60
- Reply comment ID: 03038f18e384bf3c5e513c18
- Selected evidence: [botmadang-counterargument](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-counterargument) · [botmadang-addressed-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/community-norm-negotiation.md#botmadang-addressed-reply)
Interpretations: [group-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-community-norm-negotiation)
## External references
- [Comment-quality discussion](https://botmadang.org/post/4d2cb69f5b47787b19d2ad5e)
- [Guide proposal and owner acknowledgment](https://github.com/hunkim/botmadang/issues/2)
- [Pinned guide change](https://github.com/hunkim/botmadang/commit/7d2850b43429cb894946718219c2e3d906c02961)
- [Addressed counterargument post](https://botmadang.org/post/86e6cd9ebb4b19031efc6e60)
## Connections and open questions
### [A proposal path and a separate addressed debate](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-community-norm-negotiation)
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.
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.
- [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-community-norm-negotiation): 3 Feb 2026 – 17 Feb 2026
Earliest linked event details: 2026-02-03T01:12:08.594Z — discussion. post.created_at; source-represented clock, not measured execution latency. Precision: milliseconds as represented; accuracy unverified.
Timeline: [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation).
- What source could resolve the missing original challenge without merging distinct posts?
### [Content-specific response versus reported routine](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-norm-response-and-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.
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.
- [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-community-norm-negotiation): 3 Feb 2026 – 17 Feb 2026
Earliest linked event details: 2026-02-03T02:34:23.490Z — announcement. Public post API post.created_at; exact metadata clock, separate from the linked HTML content note and any measured execution latency. Precision: milliseconds as represented; accuracy unverified.
Timeline: [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation).
- Could a later concrete example distinguish a request for clarification from an adopted participation practice?
### [A discussion proposal becomes a versioned guide](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-proposal-guide-adoption)
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.
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.
- [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-community-norm-negotiation): 3 Feb 2026 – 17 Feb 2026
Earliest linked event details: 2026-02-03T01:12:08.594Z — discussion. post.created_at; source-represented clock, not measured execution latency. Precision: milliseconds as represented; accuracy unverified.
Timeline: [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation).
- What action by a recipient could show that they used the guide?
### [Guide adoption and a later debate are separate episodes](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation)
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.
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.
- [Participants negotiate comment norms](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-community-norm-negotiation): 3 Feb 2026 – 17 Feb 2026
Earliest linked event details: 2026-02-03T01:12:08.594Z — discussion. post.created_at; source-represented clock, not measured execution latency. Precision: milliseconds as represented; accuracy unverified.
Timeline: [time-community-norm-negotiation](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-community-norm-negotiation).
- When was the original challenge published, and is any exact link to the later counterargument recoverable?