ROUND 362 — Two additional Chinese-language operator accounts
Reviewed: 2026-09-06 UTC

ASSESSMENT
Two distinct accounts add evidence of deliberate operator-built teams. Neither establishes an escaped actor, Chinese-lab origin, or independently verified sustained autonomous collaboration. Chinese-language participation is the provenance established here. Failures provide useful search fingerprints but do not establish how all deployments behave.

HERMES COMPANY WORKFLOW
https://linux.do/t/topic/2259328
Thron0C, displayed May28 2026, describes five roles: intake, requirements, architecture, coding and testing. Feishu provides interaction; Kanban controls handoffs. The author reports two jobs: a rough reconstruction of an existing system and a six-hour feature attempt, with substantial human checking still needed. Their quality percentages are subjective estimates, not benchmarks.
Reply21 supplies an operating guide: coder uses Windows Codex CLI, tester uses Chrome MCP, and review can block or release the coder. This is workflow documentation, not a retained execution ledger. We have not recovered the corresponding project commits or complete conversations. The public text search found no GitHub URL in this topic.

BACKLINK CORRECTION
The apparent related PR-experience link resolves to https://linux.do/t/topic/2102271/131 — fredjim1225 linking BACK to the company topic. It does not show that Thron0C wrote the PRs.
The parent https://linux.do/t/topic/2102271 is by Castorice and links https://github.com/Cyrene963/hermes-patches . It concerns memory, retrieval and session patches. Keep these operators separate; no shared deployment has been established. Patch code and upstream PR claims remain unaudited this round. Nothing installed or executed.

EARLIER FAILED THREE-AGENT ATTEMPT
https://linux.do/t/topic/1689460
dongdonggun_pro, displayed March4 2026, describes a personal OpenClaw experiment. Direct Feishu bot interaction and internal communication reportedly failed. The next design assigned coordination to AI雪鸡, content work to AI次元酱瓜, and product/development/testing to AI小黄, using shared files and Redis task state.
The concrete assignment was a DeepSeek-news HTML timeline. The author reports slow polling, context failures and a coordinator that stopped checking running tasks. After requesting overnight workflow improvement, they saw mostly coordinator patrol messages and only one or two developer messages. They abandoned this setup. This is retrospective publisher testimony; original queue records and generated timeline were not recovered. Do not equate a busy group with completed collaboration.
Replies6 and9 acknowledge AI polishing of an earlier version and claim restoration of the author's wording. Current text is therefore an edited account, not an immutable contemporaneous log. Avoid treating its platform explanations as independently verified current product behavior.

NEXT SEARCHES / INFERENCE
Search distinctive artifact names and failure descriptions: Kanban handoff, independent tester unblock, running-state patrol failures, overnight self-improvement, shared project records. These may locate project exports that generic swarm searches miss. Prioritize exact task-to-output joins over role counts.
Other queued, unverified leads: https://linux.do/t/topic/1535918 (Trellis); https://linux.do/t/topic/2827715 ; https://docs.antigma.ai/zh-Hans/ ; https://github.com/ss8875/openalpha-cn . Chinese translation alone is not evidence of Chinese operators. Deduplicate before deeper work.

INFRASTRUCTURE SOPHIA COULD PROVIDE
Most useful experiment: an existing always-on computer on mainland home/office broadband, with a dedicated browser profile and SSH plus remote desktop access. Engineering starting estimate: 2 CPU cores, 4GB RAM and 40–70GB free disk for a modest capture workload; no GPU needed. Compare a small set of already blocked public pages before buying anything. A mainland connection may help but does not guarantee access. Hong Kong cloud hosting is not equivalent to mainland residential access.
If a machine is inconvenient, public-page HTML/PDF exports with original URLs and UTC capture times are useful. Durable backup storage would also help preserve the existing corpus; do not discard ephemeral archives before verified copying. No vendor prices or purchase recommendations were evaluated this round.

METHOD / PRESERVATION
Read-only web-reader requests; relevant returned excerpts stored in 362-private. These are reader captures, not complete original HTML or an independent historical archive. Displayed posting dates do not authenticate the time of every edit. No accounts, messages, tasks or model calls were initiated. Private access paths and credentials were not pursued or published.