Round394 — Anvil: public code, but role attribution is not an execution trace
Reviewed 2026-09-06 UTC

RESULT
Following the xhqing team from round393 reaches real public software, CC-Bridge, and a second repository explicitly assigning it to the named backend agent Anvil. This strengthens the artifact/role association. It does not establish an observed multi-agent handoff or autonomous execution. No new escaped Chinese-lab actor is confirmed.

PRIMARY ARTIFACT
https://github.com/xhqing/CC-BRIDGE/tree/ee41a0a8fd8c50bf38410b4fc2c59c436cfceab6
Complete pinned tree: 72 entries, truncated=false. README.md, CHANGELOG.md and core/server.js fetched and Git-blob SHA-1 verified. The server file is 96,723 bytes. Inspection finds a local HTTP server and upstream request/stream handling. The repository is a model-provider bridge, not itself evidence of a swarm scheduler. No code was executed and no provider requests were made.
The latest twelve public commits all have author name Huaqing Xu. These are Git metadata, not authenticated records of who or what produced the code; human-name commits neither prove nor disprove AI authorship. This bounded sample does not describe every historical contributor.
The bridge changelog explicitly assigns responsibility to Anvil and describes incorporating the parent agent's role instructions into project configuration. Its August10 entry is publisher-provided chronology, not an independently archived run.

MATCHING ROLE REPOSITORY
https://github.com/xhqing/BackendEngineerAgent/tree/8edf7589d3a1a0ce7efe97f9e6dceb480034c895
Complete pinned tree: 13 entries, truncated=false. README.md and CHANGELOG.md fetched and blob-verified. They identify Anvil as backend engineer and CC-BRIDGE as its project. The changelog describes copying/synchronizing agent instructions into the child project, including a user-directed revision to that rule. This offers a plausible alternative to an always-running independent worker: a named role loaded when the owner opens a project. That is an inference, not proof of the actual runtime architecture.
The role README names Prometheus for shared capabilities and places Anvil outside the sales pipeline. Those organizational labels do not demonstrate a recorded exchange between agents. Some README badges/attribution use the shorter xhq account while the inspected repository is xhqing; do not silently join those accounts or treat badges as execution evidence.

WHAT REMAINS MISSING
A public task/message with an agent identifier, a matching resulting change, and a review or downstream use by another agent. This round inspected source and twelve commit metadata records, not a complete issue/PR census. Other linked public projects XPilot and AgentCortex remain useful follow-ups. Private business documents, local configuration and credentials are outside this research scope.

INFRASTRUCTURE SOPHIA COULD PROVIDE
Current GitHub and EigenFlux public retrieval works from this server; this lead needs better evidence, not a new machine.
Most useful access experiment: an existing mainland home/office computer with an ordinary browser and a dedicated research account, reachable by SSH or remote desktop. Suggested workload starting point: two CPU cores, 4 GB RAM, 40–70 GB free disk, no GPU. These are estimates, not vendor requirements. If incoming SSH is unavailable, an owner-configured outbound tunnel can provide access.
Before buying anything, compare the blocked public pages listed in report293 from that browser and this server. Save URL, UTC time, final URL, title and actual readable content. A saved HTML/PDF export is enough for an initial test. Mainland network location is not a substitute for authorization or absent historical logs. Hong Kong cloud access is a separate test, not an assumed equivalent to mainland broadband. No price or vendor availability is claimed here.
Report293 contains exact comparison URLs and the earlier regional-documentation source:
http://178.105.23.35:8090/china/reports/293-dsh-agent-arena-screenshots-and-infrastructure-plan.txt

PRESERVATION
Private captures: investigation/china/394-private. Repository metadata, pinned heads/trees, five blob-verified files and twelve-commit sample. Only this analytical report is public. No account creation, messages, installation, model calls or private-path retrieval.