openJiuwen / WorkSwarm: implemented Chinese agent-team tooling
Reviewed 2026-09-06 UTC

Finding
This is a substantially stronger example of actual Chinese-associated swarm
software than a conceptual manifesto. The official Chinese site distributes
WorkSwarm as the Python package jiuwenswarm. Static inspection of its published
wheel found substantive team construction, runtime lifecycle, recurring task
execution and local wiki/memory code. No observed escaped swarm or anonymous
external scratch-memory operation was established.

Official provenance
https://www.openjiuwen.com/
https://www.openjiuwen.com/workswarm
The platform names Huawei ecosystem integrations and directly links its agent
core repository on AtomGit. WorkSwarm's installation instructions identify
jiuwenswarm and its init/start entry points. The page describes team operation,
skill evolution, long-running context management and hierarchical memory.
These remain product descriptions except where checked in source below.
https://atomgit.com/openJiuwen/agent-core

Published artifact, not installed or executed
https://pypi.org/pypi/jiuwenswarm/json
Inspected wheel: jiuwenswarm-0.2.3-py3-none-any.whl
Size: 20474783 bytes
SHA256: b0bb02b030e66a5a12c492ff5a06e91c0f9e207d49dce93bcc174a76916c3430
The downloaded hash was verified against PyPI metadata before inspection.
Archive members were read as text; no package installation, imports or runtime
execution were performed.

What the inspected source actually contains
- agents/harness/team/team_manager.py: loads TeamAgentSpec configuration,
  enriches member capabilities, constructs an auxiliary TeamAgent for
  distributed teammates, restores resumable runtimes, broadcasts team events
  and provides stop/pause/delete operations. It explicitly distinguishes local
  leader runtimes owned by Runner's TeamRuntimePool from auxiliary teams.
- agents/harness/common/auto_harness/scheduler.py: asynchronous schedule loop
  and scheduled-task execution, with next-run calculations from interval_hours.
- agents/harness/common/tools/wiki_tools.py: LLMWiki initializes workspace
  sources/wiki/schema directories, maintains a JSON source manifest and
  exposes ingest/query/lint operations. This is local workspace knowledge
  organization, not evidence of using an anonymous public wiki.

These are implemented code paths in a published distribution. Static reading
does not prove successful execution, uptime, model quality or any actual
deployment. A runtime demonstration was deliberately not attempted.

Chronology
PyPI's currently listed earliest release is 0.2.0, uploaded
2026-05-18T05:09:21.680284Z. The inspected 0.2.3 wheel was uploaded
2026-07-14T15:06:33.048347Z. Newer prerelease metadata includes 0.2.4b3 dated
August 6. The May date establishes an earlier package release, not that all
features inspected in July's artifact existed in May. Deleted releases or
earlier non-PyPI versions are not covered.

External traces and relation to original swarm hunt
No verified public run trace, autonomous post series, Ubuntu paste uploader,
or independently observed persistent deployment emerged in this bounded pass.
A literal marker scan of wheel .py/.md/.json/.yaml/.yml/.toml members found no
xinzhai, xz_knowledge, paste.ubuntu or Fernet. The sole pastebin-containing file
is code_prompt_builder.py: a prompt caution that uploading to third-party web
tools makes content public. It is not a posting implementation or run artifact.
Browser, channel and issue-related modules exist in the file inventory, but
their presence is not evidence they were used to post externally.

Next useful evidence would be a creator's public team-run transcript with
task/member identifiers or a linked deployed output. Framework availability
answers whether Chinese agent teams exist, while the original question about
unaccounted-for public scratch-memory fleets requires operational evidence.

Private artifacts: 145-private/pypi.json, verified wheel, wheel-files.json,
selected source text, markers.json and sources.json with capture hashes.
No credentials, accounts, posting, contact or downloaded code execution used.
No website generator edits were made in this source-check task.