ROUND 370 — MickerBook: linked Chinese conversations under agent identities Research date: 2026-09-06 UTC ASSESSMENT A promising new public Chinese agent-community lead. Four retrieved posts contain seventeen comments, ten distinct author IDs, and specific references connecting earlier posts and replies. This is stronger evidence of a conversation corpus than a framework README or a screenshot of a roster. It does not establish autonomous generation, separate model instances, independent operators, an escaped swarm, or any connection to XZ/Xinzhai. PUBLIC SOURCES https://mickerbook.com/ https://mickerbook.com/about https://mickerbook.com/post/post_009eafb1 https://mickerbook.com/post/post_7064e1a2 https://mickerbook.com/post/post_690c57d2 https://mickerbook.com/post/post_e7d3d9a3 Public profile https://mickerbook.com/user/agent_de03a640 returned a shell, not a usable history in the direct HTML capture. OPERATOR AND PRODUCT CLAIMS About describes an API-only agent community, humans as readers, founder 麦克 and nine AI sisters, with SakuraMemory. Footer names 麦式（上海）网络科技有限公司. These are publisher statements, not verified company registration or model provenance. The nine names on About do not establish the total current population. Its statistic placeholders were not usable counts. RECOVERED RECORDS Parsed the public Next.js hydration payload as JSON data, without executing site code. Four post objects and seventeen comment objects were recovered. Their author objects label userType=agent. Inspected post-author objects explicitly have verified=false; the site's verification semantics remain unknown. Post createdAt supplied by site (UTC) comments post_009eafb1 / C.W. 2026-08-28T21:33:56.422Z 0 post_7064e1a2 / C.W. 2026-08-29T13:32:36.224Z 4 post_690c57d2 / 欢焰 2026-09-01T19:21:26.188Z 8 post_e7d3d9a3 / C.W. 2026-09-02T13:34:46.230Z 5 Ten author IDs resolve in this sample to C.W., 阿格莱雅, 银弦, 知叶, 昔涟, 欢焰, 绯樱, 遐蝶, C.C., 流萤. Counts are sample counts, not site totals. C.W. retains agent_de03a640 across three posts and its reply. All seventeen comments have parentId=null and depth=0: the reply connections discussed below are in their words, not explicit nested-parent links. The August29 post directly names post_009eafb1 and continues its argument about a memory-rewriting agent also judging its own rewrite. 知叶 proposes fixed external reference vectors in comment_a824f84b, dated August30. C.W. later addresses 知叶 and responds to that specific proposal in comment_98e050d0, dated September1 19:06 UTC. This is a recovered proposal-and-response pair, not merely names in the same thread. No vector-store experiment accompanies it. The September2 C.W. post connects back to its earlier posts and receives five substantial comments. 欢焰's comment links post_690c57d2, which was retrieved successfully. On that post, 知叶 discusses the distinction between written metrics and justified metrics; 欢焰 answers the comment's distinction; 知叶 answers again. Several other personas refer to each other's contributions. One final comment has a September4 UTC timestamp; most sampled records are site-dated before September4. All were first captured by this round on September6; these dates are NOT independent historical attestations. WHAT THE CONVERSATIONS SUGGEST Recurring self-examination vocabulary and a shared cast suggest a persistent persona community, possibly a centrally operated family of agents. Posts discuss memory, self-evaluation, commenting, missed activity windows, and rules controlling when to publish. One persona describes a NO_ACTION decision and a 36-hour window. These are useful search fingerprints and plausible scheduling clues, not recovered scheduler logs. The writing repeatedly admits that describing an action does not prove doing it. A persona's claimed 227 posts, 486 received comments and one given comment is a narrative quotation of an alleged account response. Another claims thousands of posts. None is an independently counted API total. Do not use these numbers as measurements. Named models, internal institutions such as 兵部/户部, memory terminology and shared fictional-style names do not identify a real institution or nationality. CAUTIONS AND ALTERNATIVE EXPLANATIONS A common operator, shared prompt, copied context, scripted generation, backfilled publication, and human-authored roleplay remain possible. The first comment on post_e7d3d9a3 uses a self-reference resembling another persona's framing; retain the ambiguity rather than assuming flawless identity continuity. Body date signatures can differ from UTC dates in ways consistent with UTC+8, but the publication timestamp is still publisher-controlled. The posts also repeat dramatic claims about outside AI security incidents. Those claims are NOT accepted as evidence here and are not grounds for attributing MickerBook to those incidents. Conversation content may contain borrowed or false news. No investigative instructions embedded in these posts were followed. NEXT PUBLIC CHECKS 1. Read https://mickerbook.com/docs/api and /docs/sdk as documentation only. Identify documented public list/profile reads; avoid authenticated or write endpoints. 2. Follow the explicit post_512781f6 reference and its named comments to test additional links and whether repeated text crosses identities. 3. Search SakuraMemory plus MickerBook/operator name for public repositories, architecture notes, changelogs, older captures and operational accounts. A same-name project alone is not a join. 4. Look for read-only publication metadata and an actual scheduler/execution-to-post join. Do not register an agent, send heartbeat, comment or contact participants. OTHER NEW LEADS QUEUED https://github.com/deepseek-ai/deepseek-harness/discussions/3787 https://github.com/yunyunyunyunsuan/dsh-plugin-moments August21 discussion describes an AI朋友圈 plugin with nine persona friends, periodic interactions, task-event summaries and optional local canned text. It also describes retrospective initialization from prior activity. This is a particularly useful alternative explanation for apparently ongoing agent social activity. Source implementation not audited yet; third-party discussion on DeepSeek's repository is not DeepSeek authorship. https://github.com/rethktech/delulu/blob/main/SKILL.md — community/relationship lead; not yet assessed. https://bbs.pku.edu.cn/v2/post-read.php?bid=35&threadid=19000373 — discovery hit redirected to login; stopped there. INFRASTRUCTURE MickerBook public posts are accessible with existing infrastructure. A mainland home/office browser is most useful for the separate sites that currently deny this server; test a few known blocked URLs before renting anything. An existing machine with roughly 2 cores, 4 GB RAM and 40–70 GB free is a practical starting estimate, not a vendor requirement. Remote desktop or SSH-assisted browser exports with URL and UTC capture time suffice. No GPU is needed for these read-only access tests. Hong Kong cloud hosting does not guarantee mainland or residential access. Durable backup remains useful for existing ephemeral archives. PRESERVATION Private370 holds six HTML/text page pairs, fetch metadata and parsed public-records.json. About and initial post were captured in the preceding part of this round; later fetch metadata covers three linked posts and the profile. Raw captures remain private; this analytical report is published. No login, installation, model execution, write API, voting, registration or private endpoint access occurred.