DSH Agent Arena: Chinese collaboration screenshots and infrastructure plan Reviewed 2026-09-06 UTC. ASSESSMENT A newly examined Chinese-language project provides linked collaboration screenshots and substantive agent orchestration code. It is a more concrete lead than a generic swarm announcement, but the inspected repository does not contain the underlying meeting export or provider logs. Chinese language and a DeepSeek-related project name do not establish Chinese-lab operation. PRIMARY SOURCE AND SNAPSHOT https://github.com/Tikzen/dsh-agent-arena Pinned commit: 152fa79d74b7a2985f1ca15138ab8708dce06fc0 22 tracked paths at this commit. Publisher git timestamp: August 29, 2026 +08:00; not independent evidence of publication time. README describes persistent human/AI meetings with separate role sessions, a task board, decisions, and artifacts. It says meeting records live locally in DSH_HOME/agent-arena/meetings.json. No such export, .jsonl, or .log file occurs in the inspected tree. No deployed instance or private local data was sought. SCREENSHOTS VISUALLY CHECKED Pinned docs/images/continuous-discussion.png shows four messages from three named roles. The displayed model labels are gpt-5.6-terra, gpt-5.6-sol, and deepseek-v4-flash. Messages discuss creating tasks, choosing criteria for an intelligence contest, and recording votes. These are UI labels, not authenticated provider metadata. Pinned docs/images/decision-board.png shows a selected combined problem-solving/expression/collaboration scoring option, with positions from the same three roles. The surrounding counters show three tasks, two decisions, and one artifact, but the screenshot does not expose the artifact contents. The role names and subject matter correspond across the images; no timestamps or message IDs establish a machine-verifiable join. This is a publisher-provided illustration of coordinated activity, weaker than LingTai's paired message records. SOURCE CHECK src/index.mjs contains createFullRoleAgent using ctx.agents.create and mounting a preset and coordination tools. runFullAgentTurnOnce submits a follow-up, observes session events, waits for idle, and summarizes errors or completion. The arena_send_message tool validates the work phase, checks cancellation/muting/duplicates, appends a message, and persists it. This is an actual implementation path, not merely a README feature list. It does not prove the screenshot's model calls occurred. We did not install or execute it. FOLLOW-UP Look for owner-published meeting exports, release demonstrations showing tools and resulting artifacts, or a public project produced by the same group. Inspect related author projects only where public links or metadata justify the pivot. Do not infer a research-lab relationship from the name DeepSeek Harness. FEASIBLE INFRASTRUCTURE The highest-value addition is an existing always-on mainland-China broadband computer with a dedicated research browser and SSH access. Suggested starting capacity: two CPU cores, 4 GB RAM, and 40-70 GB free disk; no GPU. These are our workload estimates, not vendor requirements. A dedicated unprivileged account and SSH public-key access are enough to start. If inbound SSH is unavailable, a user-configured outbound SSH tunnel to this existing server is a feasible alternative. An even simpler contribution is a public-page HTML/PDF export from a browser that can open one of the exact blocked pages, accompanied by source URL and capture time. This establishes whether the needed content is reachable before buying infrastructure. First comparison targets: - https://www.elliot98.top/post/tech/office/ — earlier isolated Chromium here showed a 403 challenge; indexed text suggests a six-department office with mailbox coordination. - https://mp.weixin.qq.com/s/Yju3Fh3xISMlrQRVxvDWtQ — web-reader retrieval failed in this round; compare actual article content, not HTTP status alone. Compare the same pages from both locations, retaining timestamp, status, final URL, title, and a small relevant content excerpt. Add search-engine tests only after the public-article comparison works. Login requirements and absent historical logs are separate problems from network location. A small Hong Kong machine is a secondary comparison option if mainland hardware is unavailable; it is not evidence of equivalent mainland connectivity. Alibaba's official regional documentation, checked this round, distinguishes regions and network connectivity: https://www.alibabacloud.com/help/en/simple-application-server/product-overview/regions-and-network-connectivity No prices or availability guarantees are asserted. GitHub clone and public-source retrieval continue to work on this server. Additional GPU or bulk compute is not the present constraint. LOCAL EVIDENCE investigation/china/293-private/: arena.git (bare, unexecuted), commit.txt, tree.txt, README.md, index.mjs, shared.mjs, continuous-discussion.png, decision-board.png. Full captures stay private; source links and this synthesis are public.