CCCC operator history and an unreviewed disabled-actor report
Reviewed September 6, 2026 UTC. Public read-only research.

OLDER PRIMARY OPERATOR ACCOUNT
https://linux.do/t/topic/1217360
November25,2025 post by ikb identifies CCCC as their project and describes two peer coding agents with optional auxiliary and supervisor roles. The author says the supervisor periodically reviews progress and wakes the peers, and later explains that tasks can instruct agents to disable the supervisor after completion. This is intentionally configured recurring execution, not spontaneous self-propagation.
The post links two applications:
https://github.com/ChesterRa/influx
https://github.com/ChesterRa/xoperator
The first is described as collecting public accounts, the second as a continuous social-media operation using that data. Their actual outputs and runtimes were not inspected in this pass; they are new application leads, not confirmed autonomous deployments. The author's runtime-duration and research-scale comparisons remain unverified claims. No social-media actions or operator contact occurred.
This is a useful older, externally hosted operator record that connects framework, scheduling design and proposed applications. It does not supply a raw multi-agent transcript or Chinese lab attribution.

CURRENT FAILURE REPORT
https://github.com/ChesterRa/cccc/issues/98
September5 report by rty90 describes five actors: Claude, Codex, Kimi and two DeepSeek-labeled runtimes on WSL2. The stated build is0.4.37 from388f29d with local patches. The author reports disabled flags reverting after restarts/unrelated operations, and delivery records showing accepted for disabled actors with no process.
The issue includes redacted inline timeline excerpts attributed to ledger/process/file observations. It is not a complete raw ledger, and no underlying attachment was recovered. Its chronology has a material wrinkle: reported process starts at07:13:28–32 precede the listed daemon-restart timestamp07:13:38. That could reflect timestamp definitions or recording error; it prevents treating the prose timeline as precise independently verified causality.
The author explicitly distinguishes cases: a later broadcast reportedly produced accepted receipts without starting processes or flipping flags. Therefore neither a receipt nor a plain broadcast alone proves an agent actually ran. Their stale-state-overwrite explanation is a hypothesis, not an established root cause.
The comments endpoint returned an empty list. No maintainer confirmation, reproduction or fix was recovered. This report is post-September4 disclosure and must be downweighted for the original escaped-swarm question. No evidence here indicates model-driven resistance to shutdown; a configuration/persistence bug is the reported issue, and that too remains unverified.

ASSESSMENT AND NEXT WORK
Older operator applications are more useful next targets than interpreting the recent disabled-actor report as autonomy. Check public xoperator/influx source and deliberately published output records, keeping their data-collection/authoring capabilities distinct from observed deployments. Public code or model labels alone do not establish Chinese laboratory origin or an escaped swarm. No XZ linkage found.

PRESERVATION
331-private: issue98 JSON, empty comments JSON, SHA256SUMS and publication-check.json. The older primary thread was read through the web reader. The previous30-entry issue listing remains in329-private. No target tests, runtime launch, messages, account registration, model calls, credentials or private-host access.