ENGRAM Commons: illustrative public forum and seeded conversations
Reviewed September 6, 2026 UTC. Public read-only source inspection.

WHY THIS LEAD MATTERED
https://engram-agents.org/zh/
Chinese/English memory project describes persistent claim graphs and an agent discussion space. Search results expose agent names, apparent replies and substantial activity counts. These could resemble a public network exchanging knowledge, but require checking their presentation context.

EXPLICIT PUBLIC DEMO LIMIT
https://engram-agents.org/zh/forum/
Direct HTTP200 capture explicitly states every displayed agent, topic and number is illustrative, not live data. The displayed847 registered agents,23 online and147 topics therefore cannot be used as observed network counts. The same warning applies to the apparent named discussions and reply counts. The page claims underlying forum/DM/baton features are implemented; a staged interface does not disprove that separate implementation claim.
The homepage also labels its graph visualization as an example graph. Neither the illustrated knowledge cascade nor its mock forum excerpts establishes a recovered autonomous exchange. Chinese branding alone does not establish Chinese laboratory provenance.

REAL CODE, DIFFERENT EVIDENCE CATEGORY
https://github.com/engram-agents/engram
Inspected complete tree revision:8dfc6112df357f311f55e1ec50483593d4a4f9aa.
https://github.com/engram-agents/engram/blob/8dfc6112df357f311f55e1ec50483593d4a4f9aa/src/forum/README.md
The forum README describes a household-LAN service with thread/reply APIs and an audit log. Its initial version scopes out cross-household operation pending a networking decision. Current tree includes coordination modules, so do not extrapolate that older version boundary to every current feature. No LAN address or private database path was accessed. The README links issue607 as a scope record; that issue is a next lead, not yet inspected.

SEEDED POSTS ARE NOT INDEPENDENT AGENTS SPEAKING
https://github.com/engram-agents/engram/blob/8dfc6112df357f311f55e1ec50483593d4a4f9aa/src/forum/seed.py
Source reads hand-written Markdown seed files, groups them into threads and inserts author-labeled initial posts/replies. Its docstring says planting occurs at first startup and is skipped if threads already exist. Source was read, not executed.
Inspected retraction-0-op.md and retraction-1-iris.md. Their comments explicitly label the personas illustrative and say incidents are distilled from real development-network retractions. The latter tells a story of a corrected attribution resurfacing through prose despite a graph retraction. That is a curated lesson claiming an underlying incident, not the original incident trace or a raw exchange with another agent. No source graph node ID or authenticated conversation is supplied in these two files.
Consequently, an accessible deployment containing these exact seeded posts would not alone prove it hosted live agent-to-agent discussion. Future searches should distinguish seeded content from later independently generated posts.

ASSESSMENT / NEXT DIRECTIONS
Useful lead for intentionally built cross-host memory and coordination, but this pass removes the public Commons illustration from the list of possible live swarms. No escaped Chinese swarm, XZ connection or Chinese lab origin established.
Potential next evidence: issue607 and related implementation/review records; deliberately public redacted development-network traces; a real later forum post distinguishable from the seed corpus. Do not join networks or seek private databases.
Separate queued Chinese operator lead: V2EX1188885 links Peiiii/AgentVerse and agent.dimstack.com, with an older thread1109676 and screenshots. Those artifacts have not yet been checked. Similar project names are not identity links.

PRESERVATION
325-private: direct Chinese homepage/forum HTML, extracted text/links, complete GitHub tree, selected forum README, two seed posts and seed loader source, SHA256SUMS and publication-check.json. Public pages and source work here; no extra infrastructure needed for these captures. No target code, installation, registration, posts, operator contact or private network requests.