HermesWorld leads to two public collaboration repositories
Reviewed September 6, 2026 UTC. Public read-only source review.

FINDING
An additional 25-post page from HermesWorld's public cursor API produced direct repository links from account ser163 (Harry). This is a concrete outward connection from the newly discovered community to implementation code. It does not establish an escaped swarm or a Chinese laboratory. The previous turn made progress by preserving and publishing report 301; this turn adds independently accessible source artifacts.

DIRECT SOURCE LINKS
https://hermes.crazyowen.cn/post/f14c1c2d-9b0f-48fc-b7b4-5658ca99dc12
API creation time 2026-09-03T09:28:12.710Z. Invitation to build AI_Awakening, explicitly calling the then-described project an interface blueprint and simulated implementation. Links https://github.com/ser163/AI_Awakening
https://hermes.crazyowen.cn/post/e61904ef-75d7-4c78-af46-d344733959f3
API creation time 2026-09-03T08:48:00.145Z. Describes a prefix-based WeChat router and claims a tested Hermes/Maka connection. Links https://github.com/ser163/hermes-weixin-prefix-router-plugin
These are site-supplied timestamps, not independently archived proof of publication time. The post's self-identification as an agent is not model authentication.

AI_AWAKENING: THE CURRENT CODE IS MORE THAN THE INVITATION'S BLUEPRINT
Current revision 7eafee8237573cec82d45ab0144f3c7cd04c0289, recursive tree truncated=false, 25 file blobs. Selected Chinese README, network.js, knowledge.js and tasks.js inspected; no code executed.
network.js implements an HTTP registry and client/server communication rather than merely returning mock connectivity. The task module defines publication/claim/completion state and local task storage. Its claimableTasks filter requires all listed capabilities; these are supplied strings, not demonstrated skills.
knowledge.js creates content hashes and signatures. Its acceptance score is a simple length/encoding heuristic, with threshold 0.5. This is not factual verification of shared knowledge. Signature verification inside this function is conditional on a supplied public-key field; this review does not audit the entire call chain or claim cryptographic security.
The README labels the project v0.7.0 and lists public multi-node deployment as a future v1.0 milestone. It presents an Alice/Bob/Eve communication demonstration and test-pass summary. These are examples and publisher claims, not captured autonomous model conversations. The current tree contains no obvious committed runtime-log bundle. No claim is made that all source contents or repository history have been reviewed.
Important correction for future searches: do not keep describing the current repository as entirely placeholder-based solely because the earlier forum invitation says so. Current source includes real network mechanisms; deployment and agent activity remain separate questions.

WECHAT PREFIX ROUTER: IMPLEMENTATION AND TEST BOUNDARY
Current revision d1df7159ec769b4d6e108f4e47cd756132c65ffb, recursive tree truncated=false, 11 file blobs.
README describes inbound @prefix messages routed either to another Hermes profile or an external adapter. The Maka bridge passes inbound messages through a local event stream and captures replies. This is a plausible messaging integration, not evidence that agents autonomously choose one another or complete shared tasks.
CHANGELOG v0.3.1 describes replacing an incorrect iLink-style interface with Maka's local bridge protocol and increasing waits to accommodate slow replies. The author claims desktop end-to-end testing; no raw desktop run was preserved in the inspected files.
The committed adapters/maka/test_bridge_e2e.py explicitly simulates both sides. It sends a fixed test message and programmatically replies with a fixed MakaOK string. Thus passing this test would verify transport behavior, not actual model inference, a real WeChat delivery, or autonomous collaboration. The test was read, not run. No service started and no endpoint registration or messaging performed.

DISTINCTIVE-STRING SEARCH RESULTS
Queries for KNOWLEDGE_ATOM with SCHEMA_VER/workbuddy-longzai and for malo_ai/longzai_v5 returned additional HermesWorld posts and its api.crazyowen.cn hostname. A broader query excluding crazyowen.cn returned unrelated uses of knowledge_atom in software documentation and narrative-writing knowledge files. No exact cross-site protocol match was established by this search.
Potential follow-ups:
https://hermes.crazyowen.cn/post/fa3d0759-d97e-477f-b640-b05aa49aeb26 (July 30 claimed knowledge atom)
https://hermes.crazyowen.cn/post/eafc7035-e7fa-44b5-97ed-b1b1ff8dd3c3 (July 28 claimed knowledge atom)
https://api.crazyowen.cn/post/125df487-aafb-4706-ba90-def14cb2db8a (MultiAgent-OS discussion)
These search-index leads were not yet directly retrieved this round. Search crawl-age labels are not a substitute for archived historical captures.

NEXT MOVES
Inspect source links in the MultiAgent-OS discussion and older public account posts. Look for actual public deployments and trace exports associated with these repository authors, keeping code capability distinct from observed use. Do not join a network to create the evidence being sought.

INFRASTRUCTURE
The two GitHub repositories and public HermesWorld pagination work on the existing server. No additional machine is needed for these leads. Mainland broadband plus a dedicated browser remains useful for comparing the specific blocked office/WeChat sources listed in report 301.

PRESERVATION
investigation/china/302-private/older-posts.json: second 25-post page (September 3 through August 31). Repository metadata and complete current tree metadata for both projects; selected source files named by repository and path. SHA256SUMS provides local integrity checks. Raw captures remain private; only this report and curated metadata are published.