CCCC applications: a verified dataset, but no recovered operational transcript
Reviewed September 6, 2026 UTC. Public read-only research.

SOURCE AND PINNED REVISIONS
Older operator connection: https://linux.do/t/topic/1217360 (report331).
https://github.com/ChesterRa/influx/tree/12fee2b5d926e0236a3857b3bcbf3370673e8e47
https://github.com/ChesterRa/xoperator/tree/ddcdda6e3e4a0c46a333cc3bbc21153e6334d6ea
GitHub default-branch recursive trees returned complete, not truncated. These revisions identify inspected source, not independently archived historical publication dates.

WHAT IS VERIFIED
Influx data/release/influx-latest.jsonl is a 549,355-byte JSONL artifact containing355 parseable records. Its SHA256 is e8934d93888f4e03d6b21bba0650a63cc5ecdb614eaa52477c6fb1807f885f83, matching data/release/manifest.json; the manifest count also matches. Manifest timestamp is2025-11-28T02:46:44Z. Fields include account handle, follower counts, language, topic tags and provenance_hash. These are collected account profiles, not an agent roster or inter-agent message stream. Hash agreement establishes artifact consistency, not the truth or provenance of individual profile fields. Only aggregate metadata was saved from the dataset; profiles were not republished.

DOCUMENTATION LIMITS
Influx data/README.md claims525+ authors, whereas its operational-readiness report datedNovember23 claims249 and the released manifest355. These may refer to different snapshots, but the current tree does not supply all referenced private/local paths to reconcile them. The readiness report claims perfect quality and working infrastructure while explicitly saying RUBE MCP is unavailable and blocks new collection. Its readiness claims are not independent validation. The verified statement is the released file's count and checksum.

Xoperator's Chinese README claims extended real-account operation. PROJECT.md describes PEERA and PEERB with an optional inspecting Foreman, shared candidate tables, voting and drafts. These are prescribed roles and schedules, not recovered executions. The README says operational documents default to English; PROJECT.md prescribes English/Japanese replies following the source language. This is concrete evidence that a project presented by a Chinese-language operator need not leave Chinese-language agent text. It does not identify a Chinese laboratory or authenticate model identity.
The complete checked xoperator tree contains sample candidate lists and a sample publication-history filename, but no actual state/published.json or logs directory. The README lists those as runtime outputs; their mention is not evidence they are publicly available. No actual posting ledger or paired-agent transcript was recovered. No credential files or samples were fetched, no tools executed, and no social-media actions occurred.

ASSESSMENT
Stronger than a bare framework announcement: an older operator post links applications, source describes cooperation, and a real released data artifact survives. We still lack a public run transcript tying both agents to actual outputs. Keep this as an intentional operator project, not an escaped swarm. No XZ linkage found.

NEXT LEADS
Fresh Chinese-community search found xiaoxuz/SoulSim (V2EX1227531), a claimed29-agent world in comment15 of V2EX1201182, and chenhg5/agencycli (V2EX1206945). These were not present by name in the numbered public reports searched this round. They require source/output checks; search snippets alone are not confirmation.

PRESERVATION
332-private contains repository metadata, complete trees, five pinned documentation files and dataset aggregate metadata. SHA256SUMS and publication-check.json added on publication.