Vibe Mathematics: self-organizing research machinery, no verified problem result Reviewed September6,2026 UTC Primary source https://github.com/ChongCyrus/Vibe-Mathematics/tree/0d386346738ae7fac5e87dcb22802d0d1655b744 Bare blob-filtered clone preserved;35 current files and95 retained commits. Chinese README describes three maintained/experimental presets. V4 uses persistent researchers, messaging/meetings and unanimous votes rather than a central planner. Source supplies a concrete mechanism, not proof a particular mathematical problem was solved. Inspected source vibe-math-v4/vibe-math-v4.js, selfdrive-v4.mjs and e2e-business.test.mjs were read as data. The V4 verified-card writer sets truth/probability labels based on unanimity and refers readers back to the source card. Shared/debates/.md stores participants' probabilities and reasons. This promotion path is consensus, not a formal proof-checker certificate; Verified/ must not be interpreted as a correctness guarantee. Test boundary selfdrive-v4.mjs explicitly uses a mock host and simulated resident replies to drive the actual plugin's state transitions. e2e-business.test.mjs likewise mocks subagent services. These can test orchestration behavior but cannot authenticate mathematical reasoning or real model collaboration. No tests were executed here and no pass result is claimed. Artifacts and missing joins The35-file current tree contains implementation, docs, tests and illustration files; no actual Problems/Progress/Verified run directory is present. That narrow inventory does not exclude historical/release/private outputs. The published long screenshot 示例图/实际使用示例-长截图.png was fetched and opened, but the full-height rendered preview is too small for reliable transcription. No problem statement, answer or model identity was inferred from it. Preserve it for later higher-resolution inspection. Exact future fingerprints Shared/debates/.md; Verified/命题/.md; State/ plus per-resident Progress/Propos/Methods/Subproblems directories. Source comments mention a duplicated verification of p-r3-04 in test9, but no external run archive is linked by that comment. Search retrieved numerous catalog copies rather than an independent result; do not count those as separate observations. Adjacent lead https://github.com/joekytc/dsh-swarm also returned200; README describes a six-role workflow and structured delivery/review evidence. Source and actual events remain unreviewed. Its assertion that evidence fields prove tests ran needs examination, not acceptance on wording alone. Assessment Substantive Chinese-language swarm implementation, but still no authenticated problem-solving run or Chinese-lab escape attribution. Next prioritize the screenshot and actual output references, then the independent six-role workflow. Preservation 268-private holds two repository pages, Git clone/tree, three source files, example.png and SHA256SUMS. No investigated program installed/executed, model calls made, or external state changed. Public dashboard updated.