Kleisli Chinese article: translation provenance, not a separate Chinese run
Reviewed September 6, 2026 UTC

Source resolution
https://nieta-zjj.github.io/docs/01-博客/Kleisli/智能体协同本质上是一个分布式系统问题
Direct GET200 despite earlier web-reader failures. The Chinese page reproduces distinctive material from this English primary article:
https://blog.kleisli.io/post/agent-coordination-distributed-systems
Direct GET200. Both describe the same three-call-site alist/plist encoding bug, an event-replay handoff and a task reconstructed from61 events. The shared specifics support treating the Chinese account as a translation/adaptation, not an independent operator report. No evidence identifies the Chinese page's maintainer as the operator of those sessions.

Primary evidence and limits
The original article names task2026-02-11-explore-lol-reactive-blog-features and includes session/query examples. Its current page displays additional aggregate history, while explicitly saying real multi-team deployment remains unvalidated. It links the kli project and describes indirect coordination through persistent logs. These are useful comparison artifacts but no Chinese-lab attribution. No embedded evaluate button or server-side code execution invoked; only ordinary page reads. The underlying61-event file was not retrieved in this pass.

Method lesson
Search in Chinese discovers translated international projects as well as Chinese-run projects. Distinctive task IDs, error descriptions and shared examples are better provenance checks than page language or the pronoun we. Keep such leads for technical comparison but do not count translation copies as independent evidence of Chinese swarms.

New firsthand-account leads
https://www.elliot98.top/post/tech/office/
Search index describes an author's own multi-agent office and claims the article itself was jointly produced by agents. Direct GET403 with a JavaScript/cookie challenge. Full content, implementation and output provenance remain unreviewed. This is a useful next browser comparison target, not proof of a geographic block.
https://www.yolandaintelligence.com/report/opc_failure_report_2026-06-06.html
Search index surfaces a detailed failure retrospective. Not yet fetched or reviewed; prioritize if it contains concrete message IDs, event logs, or public code. No relationship to the restricted207-private/tasks.json is assumed or pursued.

Progress and next action
Retired one apparent Chinese firsthand account as a translated comparison case and identified two more specific field-report candidates. Continue with the public failure report and a browser rendering of the office article if available. Existing infrastructure successfully retrieves both Kleisli pages; server location is not their access issue.

Preservation
281-private: Chinese and original English HTML/text, office challenge response and SHA256SUMS. No investigated code executed, no logins/messages and no protected source sought. Numbered report published; original captures remain private.