SeevoMap graph audit: hypotheses, five-link structure and community comparison Reviewed September 6, 2026 UTC. Read-only artifact analysis. PRIMARY DATA https://huggingface.co/datasets/akiwatanabe/seevomap-graph/blob/e4404986f5a63abee7280e60f5e98f692f181a65/map.json Downloaded and parsed 5,685,314 bytes. The map has 4,273 unique nodes and 21,365 edges. Every node has exactly five outgoing edges. Edges expose source, target and weight, not observed message IDs, transmission times or retrieval receipts. This regular structure is consistent with a similarity graph, but the graph-construction code was not located, so the exact generation method is unresolved. Do not count these edges as agent communications. RECONCILING THE DATASET COUNTS Report305 counted3,076 individual node JSON files from dataset metadata. Map statuses are3,073 approved and1,200 hypothesis. The1,200 map IDs absent from individual node-file metadata are exactly800 ScivBook/IdeaMiner/science and400 ScivBook/IdeaMiner/ai4s entries, all status=hypothesis. Three individual file IDs are absent from the map. Thus the README's4,000+ count can reflect map entries, but those entries are not uniformly demonstrated experiment executions. A sampled hypothesis proposes a phase-field simulation of stress-corrosion cracking under deep-sea conditions; its metric is novelty_score=8.83 and its model label is deepseek-v3. That is an idea/score entry, not a preserved physical experiment or verified code run. No sample project code was executed. Six Automated-AI-Researcher source labels account for3,033 map entries: Claude Opus/Sonnet and GPT5 labels across nanogpt and GRPO tasks. These are source/model metadata supplied by the dataset, not authenticated agents. Other labels include benchmark and leaderboard imports. The model field even contains names associated with leaderboard contributors; do not interpret its distinct values as model counts or agent identities. SOLO AND COMMUNITY PAIR https://huggingface.co/datasets/akiwatanabe/seevomap-graph/blob/e4404986f5a63abee7280e60f5e98f692f181a65/nodes/88054cbd.json Source BotResearchNet/parameter-golf/solo; date2026-03-23T03:00:28Z; reported SwiGLU change, val_bpb1.19237152 versus baseline1.2259, success=false because the narrated artifact size24.26MB exceeds16MB. https://huggingface.co/datasets/akiwatanabe/seevomap-graph/blob/e4404986f5a63abee7280e60f5e98f692f181a65/nodes/a21cb385.json Source BotResearchNet/parameter-golf/community; date2026-03-23T03:20:52Z; proposed wider MLP plus stronger compression, val_bpb1.20361969, success=false with narrated20.09MB size. It explicitly says community leaderboard submissions inspired the idea, but supplies no identified retrieved record, retrieval trace or measured message exchange. Both label the model claude-opus-4-6, hardware4xH200 and wallclock1080 seconds. Both contain prose Code Changes rather than a code_diff field. These two self-described records cannot establish the benefit of community knowledge: different proposals, failed constraints, and no controlled repeated comparison. Their value is as leads to an underlying run and possible knowledge-reuse evidence. PUBLIC SPACE SOURCE https://huggingface.co/spaces/akiwatanabe/seevomap/tree/8063270d17be659a3caa454ec24c1d0c984b9ee0 Metadata, app.py and seevomap/space_backend.py preserved. The source contains cosine-similarity search over embeddings and loads map.json for visualization; visualization displays at most5,000 edges. This supports distinguishing visualized connections from logged collaboration, but does not establish how the stored edges were generated. No Space RPC, model invocation, upload or contribution was performed. The README-linked https://github.com/Zhouzone/seevomap could not be checked via its main recursive-tree API: HTTP404. This might reflect branch choice, removal or access; it is not proof the repository never existed. ASSESSMENT AND NEXT ACTIONS The public corpus is materially useful, but its map blends experiment summaries and hypothesis entries. The current evidence supports an aggregated research-memory resource, not4,273 autonomous agents or21,365 communications. No escaped-swarm or Xinzhai link is established. Next trace Automated-AI-Researcher provenance and source revisions, seek raw execution logs or a reproducible community-context retrieval record, and inspect the three file/map discrepancies. Do not treat branded model names or success booleans as independently verified results. PRESERVATION investigation/china/306-private/: map.json, map-analysis.json, space-metadata.json, app.py, seevomap_space_backend.py, comparison-map-nodes.json, node-88054cbd.json, node-a21cb385.json, upstream-tree.json (404 response). Raw captures private. SHA256SUMS and publication checks retained. No additional infrastructure required for these public reads.