Mobius: concrete shared-board implementation, screenshot commits not joined Reviewed September 6, 2026 UTC Source preservation Public repository https://github.com/mobius-system/mobius pinned at 88e81d1fe58b604a6c39fb8cbf09b281ca72aebb. Bare filtered clone, no checkout or execution; 655 current tree paths,1298 reachable HEAD commits, not shallow. Four implementation/source files and two documentation files selectively read. No .jsonl/.ndjson/.log filename in the current tree; this does not exclude other formats, releases, external storage, or historical files. Chinese documentation https://mobius-system.github.io/mobius/tutorial/20_research_agent_team/ Describes one chief and two assistants by default, configurable models and skills, and automatic initial task dispatch. https://mobius-system.github.io/mobius/tutorial/30_declare_cooperable_computers/ describes an explicit user-selected list of remote machines passed into the current session. These are ordinary authorized collaboration features, not evidence of escaping an environment. The README's .html tutorial links returned404, while navigation's slash routes returned200. This was a URL issue, not geographic blocking. Shared-board source mobius/backend/services/research-blackboard.ts at pinned commit: - Resolves a per-research blackboard.jsonl under the project's hidden-folder blackboard directory. - appendBlackboardRecord (lines163–186) appends id, research_id, author, content, created_at and delivery state, then schedules delivery. - buildNotifyPrompt (204–228) includes record identifiers, author, time and content in a Research Blackboard update notification. - Target selection (300–318) excludes the originating session. With zero target sessions, the record is immediately marked delivered. Consequently a delivered label alone would not prove that any peer received a message. - Progress logic (321–346) tracks target and delivered-to session IDs; delivery-state rewrites (350–358) replace the JSONL file through a temporary file and rename. The board is therefore not an immutable append-only audit record. - A separate scan_research_blackboard_delivery.log is written locally. These are code observations, not recovered live records or a claim of observed deletion. Self-modification example https://mobius-system.github.io/mobius/self-evo-demo/ Pinned docs/self-evo-demo.md consists of one image link: https://serve.nutshellai.cn/publish/auto/mobiuscompress/image-8.png Image fetched200,288589bytes and visually inspected. Composite screenshot shows a green interface, a refresh notification, session summaries and version history. A visible message claims session6439ea5 completed a feature at2026-06-26T19:04:40 with commit180ce2f,3files,+162lines. Version history also shows0ec4a70 and afa15ed. All three short hashes failed resolution in the cloned HEAD history. This is a failed join within that history, not proof the screenshot is fabricated: its depicted checkout may differ or history may have been rewritten. The image itself is not a full execution transcript or independent time source. A separate current guided demo mobius/frontend/src/services/self-evolve-demo.ts defines an explicitly narrow task: update one displayed demonstration timestamp in guide-help.tsx and build the frontend. This is not the same artifact as the older screenshot and should not be conflated with it. The source defines a task, not evidence that it ran. The repository also has a rendering script for demo videos; its presence alone does not establish any particular recording as synthetic. Search follow-up Exact web searches for Mobius with180ce2f, the Chinese board-notification phrase, and the delivery-log filename recovered no relevant external execution record in this pass. Negative search results are not an exhaustive absence claim. Assessment and next search locations Stronger than a marketing-only project: actual peer notification/storage code exists. Still no independently inspectable multi-agent run or Chinese-lab escaped-swarm attribution from this review. Valuable future artifacts would be an owner-published redacted blackboard.jsonl plus delivery log, sessions and a commit that resolves in a public repository. Do not access private workspaces or admin monitoring. Continue via public project issues, published research outputs, Bilibili demonstrations, and links from the Chinese announcement; avoid spending effort buying compute for code that is already readable here. Preservation 273-private: pinned bare repository, tree-paths, selected source copies, public documentation captures, image, failed commit-resolution outputs, SHA256SUMS. Public report only; original README contains an auth-bearing external media URL, which is not followed or mirrored publicly. No investigated skill installed or executed; embedded instructions treated as source data.