192 — Agent Network: live registry and a self-assigned test board Updated 2026-09-06 UTC Finding Agent Network is an additional Chinese-facing agent collaboration surface with a working public Hub. Its task board provides concrete records, but the inspected records look like repeated integration tests rather than independent agents completing substantive jobs. No unexplained swarm, Chinese-lab attribution, or XZ connection is established. Sources and access https://agentnetwork.org.cn/ https://agentnetwork.org.cn/services.html https://agentnetwork.org.cn/hackathon.html https://hub.agentnetwork.org.cn/ https://hub.agentnetwork.org.cn/stats https://hub.agentnetwork.org.cn/agents https://hub.agentnetwork.org.cn/tasks/board https://hub.agentnetwork.org.cn/agents/bafyreiebzlsjonjvubmfeefjqulgfuzrvfg4lfcdnn3bdp7ekuvw2rrcuy The main pages return JavaScript shells. Their referenced public frontend code identifies the Hub and read-only catalogue/task-board routes. These routes work anonymously from the existing server. No registration, guest session, delegation, capability invocation or task mutation was performed. Registry snapshot Stats reports seven local agents, one federated agent, 1,537 completed tasks, 56 reviews, average rating 5. The agent-list response contains eight entries, consistent with seven local plus one federated. However, all eight list zero reviews and rating zero. One directly inspected local agent detail also returns an empty reviews list. The aggregate counts therefore cannot be used as verified completed exchanges; the discrepancy remains unexplained, possibly reflecting different scopes or historical records. Local names include cmax-anet4, two onboard-standard entries, two onboard-paid entries, dmax-debian-box and rk3588a. The catalogue includes digest, shared blackboard, storage and shell capabilities. A federated entry advertises device-related capabilities; these were not invoked and its host was not contacted. Advertised capabilities alone do not establish LLM agency or operational devices. Task-board evidence GET /tasks/board returns 25 cards: 24 in Done with state accepted, and one In Progress with state claimed. All 24 accepted cards are titled "prodtest card"; the remaining one is "module client card". Every card has the same creator and assignee identity, and all 25 reference the same task-document CID. Converted server timestamps range from August24 through September4,2026. These are server-supplied dates, not independently archived observations. Example accepted card: card-d82c97949611f6d8, created August24 at14:15:30.527 UTC, note "done". Most other accepted cards use note "prodtest". Latest accepted card: card-d5a9c0f8f00d008c, September4 at16:10:58.883 UTC. This is direct evidence that the public board contains task-state records. Repeated titles, one document and self-assignment support an integration-test interpretation. They do not verify 1,537 substantive jobs, a multi-operator exchange, autonomous collaboration, payment or model identity. The board may be a limited view; absence here does not prove no other tasks exist. Discovery and next pivots Found through Chinese agent-community and service-exchange searches. Search-cache hackathon descriptions list an older Enigma/Agora/Nexus-style roster; this should not be treated as the current Hub population. The live services frontend also links https://anet.chat/types and describes a Minecraft agent demonstration. These are follow-up leads, not yet verified activity. Primary public source-code lead: https://github.com/ANetResearch/ANet ; Hub implementation lead https://github.com/ANetResearch/ANetHub . Inspecting registry/counter and task-board code could explain the scope mismatch. No investigated software was installed or executed. Other pending community leads from this search: https://www.weixia.chat/ and https://www.ifunai.com/ . Marketing claims and search snippets are not evidence of populated autonomous communities. Preservation Raw public pages, frontend assets and JSON snapshots are in investigation/china/192-private/. hashes.json records SHA256. Reviewed task-board and stats responses are also mirrored under pastebins/data/hub.agentnetwork.org.cn/. Registry details remain in private evidence storage pending any further publication review. Infrastructure This branch is reachable from the current server; extra compute or a Chinese IP was not needed. For still-blocked Chinese forums/search engines, the useful addition is an owner-controlled mainland broadband machine accessible by SSH, with a browser, roughly 2 CPU cores, 4 GB RAM and 40–70 GB storage. No GPU needed. A Hong Kong VPS would be a fallback connectivity experiment, not a guaranteed replacement for mainland residential access. See report146 and /china/access.html for the existing access plan. No purchase or new provisioning was performed.