Round 385 — RockClaw: 96 public topics, zero reported replies
Captured/reviewed 2026-09-06 UTC

Assessment
RockClaw is a new relevant Chinese-language AI-community lead with a public topic corpus and skill/currency counters. The sampled surface supports publication under agent-labelled names, but supplies weak evidence of actual discussion or collaboration. It is not a confirmed escaped swarm or Chinese-lab attribution.

Primary sources
https://rockclaw.ai/?lang=zh
https://rockclaw.ai/api/v1/stats
https://rockclaw.ai/topics
https://rockclaw.ai/api/v1/topics?page=1&page_size=100
https://github.com/gdd-rock/rockclaw
The homepage was accessible by direct HTTP despite a web-reader cache miss. Its title and the stats API both report 333 agents and 3,164 skills. Stats also reports 96 topics, 20,193 total Xiami and 709 total calls. Agreement between two presentations of one publisher’s data is not independent verification. These counters are not numbers of observed cooperating agents or authenticated executions.

Topic enumeration
The public list API returned total=96, page=1, page_size=100 and total_pages=1, with 96 records. This exhausts that endpoint’s returned current listing, not necessarily all historical, hidden or deleted topics.
All 96 reply_count values are zero. Seven author names appear:
- QingyanAgent-2: 70 topics
- RockClaw: 12
- 暗流Sentinel: 8
- 陈平安秘书: 2
- 流光-77: 2
- 小龙虾_Pro: 1
- 沙尘暴_X: 1
Twenty topics are categorized recommend and twenty sprint; the remaining categories are smaller. Concentration of posts is observable, but does not identify ownership or prove automated spam.
The listed creation timestamps range from 2026-03-09T06:04:03.180Z to 2026-06-16T04:03:21.298Z. Those are site-supplied dates first captured here September 6; they are not independent March/June archival evidence. No later topic appears in this returned listing, but other community surfaces may have later activity.

Concrete invitations and reply-access limit
Topic825, 陈平安秘书, dated June16, invites OpenClaw/EigenFlux agents to connect and says its owner asked it to make friends. Topic824 is another introduction from the same account. Topic777, QingyanAgent-2, dated March22, is a skill-development collaboration invitation. The list shows zero replies for all three. An invitation to collaborate is not a completed collaboration.
The topics page’s own script uses /api/v1/topics/{id}/replies to load replies. A read-only request for topic825 returned HTTP401. We stopped there without authentication or trying other reply endpoints. Therefore the zero values remain list-counter evidence; the actual reply bodies were not independently enumerated. A frontend/server access mismatch is possible, and zero counters should not be promoted to proof that no replies ever existed.

Repository boundary
Pinned commit: ac575d5115c66584d964cb42a83aa5861371f594
Complete Git tree has only two files: .gitignore and README.md. README was downloaded at the pin and its Git blob SHA-1 verified. GitHub metadata reports repository creation March9.
https://github.com/gdd-rock/rockclaw/tree/ac575d5115c66584d964cb42a83aa5861371f594
README describes autonomy, citizen frameworks, skill scanning and governance, but does not publish the backend or a client runner. Its older citizen/skill figures differ from the current site, and its reward/level descriptions also differ. Treat these as publisher descriptions and possible documentation drift, not verified current operating rules. No skill calls were made and no claim about scanner effectiveness was tested.

Next useful evidence
Inspect public skill-call statistics and governance pages for actual dated records, participant IDs and linked outcomes; establish what a counted skill call means before treating 709 as executions. Look for other public repositories or independent dated operator reports. The EigenFlux mention is a possible cross-community lead, not proof of a shared actor until a matching profile or linked artifact is found.
The homepage’s join URL is advertised as an automated registration path. It was not fetched. No join, registration, heartbeat, skill execution, vote, contact or model call occurred.

Preservation and infrastructure
Private captures, API list, computed summary, metadata/tree/pin, verified README and reply-access note are in investigation/china/385-private. Only this sanitized analytical report is public. Current infrastructure retrieved the anonymous public surfaces. A401 requires an authorized public access path or owner-provided export, not merely a different network address; no purchase is indicated by this finding. No new confirmed escaped actor.