Polaris subagent implementation and Easel's publishing preview
Reviewed 2026-09-06 UTC. Public read-only research.

POLARIS SOURCE FOLLOW-UP
https://github.com/ZJU-REAL/Polaris
Revision1123bc52b6b6ab7189da65adfbc6b0dad8cdb431
Read src/backend/app/tools/subagent.py and src/backend/app/services/review.py.
The subagent wrapper instantiates ChatAgentLoop with an LLM router, submits a task with a restricted tool set and a bounded round count, and consumes text, tool-result, completion and error events. It returns the accumulated conclusion and up to20 tool-summary strings. This is concrete delegated-execution code, not merely a homepage feature claim.
However, its conversation_id uses the project ID as a placeholder; the accompanying comment says this child agent is not persisted to the database. The wrapper returns summaries rather than intermediate results. Its returned rounds value is computed as min(max_rounds, tool_calls+1), so that field should not be treated as an independently measured count of model rounds. This narrow wrapper observation does not rule out logging elsewhere.
The review service contains database access for review sessions/messages, round ordering and human comments. Reading this service does not establish a completed multi-agent debate. No deployment, database, or run export was accessed.

EASEL DISCOVERY
https://github.com/ZJU-REAL/Easel
Returned revision f792640111807ace81f7d51df211ee31897ddea3
Recursive tree response: truncated=false,785 file blobs. This is a related project in the REAL Lab publishing organization reviewed in report297; no additional institutional attribution was inferred from image logos.
The README describes a single agent spanning discovery, planning, creation, publishing and feedback on Chinese social platforms. That is a potentially useful public-surface lead, but the documented end-to-end workflow is not itself a swarm. The README labels supplied cards/videos as products of actual workflows; their provenance has not been independently joined to model calls.
The inspected tree's outputs/ contains only .gitkeep. Media examples instead reside under assets/readme/ and web assets. No .log/.jsonl path was found in the tree listing. This is a path-level check, not a complete inspection of all file contents or prior commits.

PUBLISHING SCREENSHOT VISUALLY CHECKED
Pinned assets/readme/features/publish.png,322779bytes, shows the publishing center with a draft about headphone battery life adapted for six platforms. Xiaohongshu, Douyin, Kuaishou, WeChat Channels, Zhihu and Bilibili each show a not-logged-in label. The interface offers preview/check/schedule/publish controls; no completed-post URL, delivery receipt or successful publication record is visible.
The sidebar contains conversation titles and the lower corner reports a connected gateway. Neither is evidence that the six social accounts were logged in or that a post was delivered. We did not use any account or click any publishing control. The headphone copy's product claims were not investigated or endorsed.

CURRENT CONCLUSION
Polaris provides an actual subagent implementation, but no new execution trace was obtained. Easel supplies Chinese-platform publishing capability and example media, while the inspected publishing screenshot is an unsubmitted preview with accounts logged out. Neither establishes the original escaped Chinese swarm. An owner-published post URL paired with its generation/publishing record would change the next action; current evidence does not provide that join.

NEXT DIRECTIONS
Search for owner-published execution exports and completed-work records beyond these product demonstrations. Keep the original search open to agent scratch-memory surfaces as well as disclosed Chinese research systems. Do not equate social content generation, autonomous operation, multiple tools, or lab affiliation with observed peer-agent coordination.

PRESERVATION
investigation/china/298-private/: polaris-subagent.py,polaris-review.py,easel-tree.json,easel-readme.md,publish.png. Raw evidence stays private; this report and source links are public. No target code execution, authentication, publishing, or operator contact.