dsh-vibe-math 2.6.0 → 2.7.1

package/vibe-math-v4//345/256/236/347/216/260/346/226/271/346/241/210.md

@@ -1,5 +1,11 @@
 # Vibe Math V4 —— 常驻自组织合作研究框架（架构设计与实现方案）
 
+> **状态说明（round-3 补记）**：本文是**设计期文档**，写于 `math_computation`（数学计算工具）、
+> `leanAsync`/`leanJobsMaxParallel`/`leanSearchPaths`（Lean 异步作业与复用）、`paperEditor` 与
+> `paper.lock.json`（最终论文定稿/写锁）等新功能之前；**功能与参数的权威描述以 `docs/` 为准**
+> （`docs/math-computation.md`、`docs/formal-verification.md`、`docs/final-paper.md`、`docs/test-timing.md`），
+> 参数表以 README 的双语「共用参数 / 各预设专属参数」表为准。本文保留其原始设计意图，不再逐条追平。
+
 > **一句话定位**：把 v3 的"中央规划器 + 确定性角色（explorer/solver/verifier/planner/method-keeper）"调度，升级为一组**持久化的常驻子代理**——它们之间**互相留言、集体开会**，自主决定接下来的一切任务（探索、尝试、验证、分工）。框架只做**媒介（消息总线/会议/任务板）、产物沉淀、共识验证、上下文管理、断点续跑**，**绝不分配任务**。像现实中的合作研究小组：人人有自己持续积累的笔记本与成果库，互相看、互相讨论、共同定论。
 
 ---

package/vibe-math-v5/agent.cordis.yml

@@ -98,9 +98,14 @@
         - vibe_v5_add_researcher / vibe_v5_remove_researcher — OFFICE only: add or dismiss a PERMANENT researcher (the academician can only propose those).
         - vibe_v5_paper {lang?, format?, editor?, force?} — write the FINAL PAPER: the permanent staff write their own parts, cross-review each other, then the editor finalises. lang/format/editor override this one paper only.
         - vibe_v5_finalize_paper {decision, note, conclusion?} — OFFICE only when paperEditor=office: consult the institute first (>=1 office message + >=1 meeting), then finalise and put the conclusion in note.
-        - vibe_v5_lean_run / vibe_v5_lean_archive / vibe_v5_lean_lib — Lean formal
-          verification (execute / archive / list the reuse library). Members use them
-          too; they work in every mode.
+        - vibe_v5_lean_run / vibe_v5_lean_archive / vibe_v5_lean_lib / vibe_v5_lean_read / vibe_v5_lean_job — Lean formal
+          verification (execute / archive / list the reuse library / read an archived file
+          verbatim / watch the background compile queue). Members use them too; they work in every mode.
+        - math_computation {op: probe|run|receipt|install, engine, mode: code|file|expr, …} — 先 probe 预检引擎/包/许可，再调引擎计算并把脚本与输出归档成可复核回执；缺引擎/缺包只报告与给安装指引/计划；shell 兜底不算归档。
+        - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>），你可以用普通文件工具打开并编辑它；编辑后用 mode:'file' 指向它重跑，会写出一份**新回执/新 attempt**（含新的 scriptHash）。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+        - Archive -> edit -> re-run: for mode:'code' the script original is at the receipt's scriptPath (Computation/<id>/script.<ext>) and you may open/edit it with your normal file tools; after editing, re-run it with mode:'file' to write a NEW receipt/attempt with a NEW scriptHash. **An old receipt is NOT evidence for edited code** - cite the receipt whose scriptHash matches the current code; the tool warns explicitly via scriptChanged / scriptChangedDuringRun.
+        - 替代必须声明（诚实性）：当替代方案改变了**精确性或结论强度**时（精确符号解 → 数值近似、闭式解 → 采样/求积、改了精度/容差/假设、换了算法类），结论里**必须写明**，不得读起来像得到了原本（精确/所要求的）结果；拿不到精确结果就直说。
+        - Declare substitutions (honesty): when an alternative changes EXACTNESS or conclusion strength (exact symbolic solution -> numerical approximation, closed form -> sampling/quadrature, changed precision/tolerances/assumptions, a different algorithm class), the conclusion MUST say so explicitly and must not read as if the original (exact/requested) result had been obtained; if the exact result is unavailable, say so plainly.
       A /v5 slash command mirrors these (configure|start|resume|pause|stop|status|report|members|message|meeting|hire|fire|add|remove|set|paper).
 
       LEAN FORMAL VERIFICATION (formalVerify, a tunable parameter):
@@ -116,6 +121,19 @@
           reported as LEAN_NOT_FOUND, a host with no subprocess service as NO_SUBPROCESS
           (on a timeout the process is terminated first), and in every one of those cases the
           code can still be written down and archived.
+        - Daily eagerness is a SEPARATE knob: leanInitiative 'off' (no daily drive) |
+          'normal' (default; the reminder rides with formalVerify) | 'eager' (push valuable
+          small lemmas/propositions/definitions into the library even in ordinary rounds).
+        - Reuse first: check vibe_v5_lean_lib BEFORE writing a definition, reuse archived
+          content via `import Formal.Lib.<name>` / `import Formal.Proved.<name>` (the compile
+          gets `--search-path <VibeMath root>`, preceded by any leanSearchPaths), or copy the
+          exact text with vibe_v5_lean_read. Re-archiving identical content is de-duplicated.
+        - Compiles are ASYNC by default (leanAsync=true, leanJobsMaxParallel default 1):
+          vibe_v5_lean_run / vibe_v5_lean_archive enqueue and return at once; watch them with
+          vibe_v5_lean_job {jobId, waitMs} or vibe_v5_lean_lib.jobs, and NEVER treat an object
+          as passed before its job settles ok (exit 0, same content, same build context).
+        - Only formalize what you are confident about; when unsure record kind='blocked' with a
+          reason instead of dressing uncertainty up as a formalization.
         - vibe_v5_status / vibe_v5_report show the mode, per-object formal status and the
           formalization TODO. The framework never installs Lean and never judges fidelity.
 
@@ -196,9 +214,14 @@
         - vibe_v5_add_researcher / vibe_v5_remove_researcher — OFFICE only: add or dismiss a PERMANENT researcher (the academician can only propose those).
         - vibe_v5_paper {lang?, format?, editor?, force?} — write the FINAL PAPER: the permanent staff write their own parts, cross-review each other, then the editor finalises. lang/format/editor override this one paper only.
         - vibe_v5_finalize_paper {decision, note, conclusion?} — OFFICE only when paperEditor=office: consult the institute first (>=1 office message + >=1 meeting), then finalise and put the conclusion in note.
-        - vibe_v5_lean_run / vibe_v5_lean_archive / vibe_v5_lean_lib — Lean formal
-          verification (execute / archive / list the reuse library). Members use them
-          too; they work in every mode.
+        - vibe_v5_lean_run / vibe_v5_lean_archive / vibe_v5_lean_lib / vibe_v5_lean_read / vibe_v5_lean_job — Lean formal
+          verification (execute / archive / list the reuse library / read an archived file
+          verbatim / watch the background compile queue). Members use them too; they work in every mode.
+        - math_computation {op: probe|run|receipt|install, engine, mode: code|file|expr, …} — 先 probe 预检引擎/包/许可，再调引擎计算并把脚本与输出归档成可复核回执；缺引擎/缺包只报告与给安装指引/计划；shell 兜底不算归档。
+        - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>），你可以用普通文件工具打开并编辑它；编辑后用 mode:'file' 指向它重跑，会写出一份**新回执/新 attempt**（含新的 scriptHash）。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+        - Archive -> edit -> re-run: for mode:'code' the script original is at the receipt's scriptPath (Computation/<id>/script.<ext>) and you may open/edit it with your normal file tools; after editing, re-run it with mode:'file' to write a NEW receipt/attempt with a NEW scriptHash. **An old receipt is NOT evidence for edited code** - cite the receipt whose scriptHash matches the current code; the tool warns explicitly via scriptChanged / scriptChangedDuringRun.
+        - 替代必须声明（诚实性）：当替代方案改变了**精确性或结论强度**时（精确符号解 → 数值近似、闭式解 → 采样/求积、改了精度/容差/假设、换了算法类），结论里**必须写明**，不得读起来像得到了原本（精确/所要求的）结果；拿不到精确结果就直说。
+        - Declare substitutions (honesty): when an alternative changes EXACTNESS or conclusion strength (exact symbolic solution -> numerical approximation, closed form -> sampling/quadrature, changed precision/tolerances/assumptions, a different algorithm class), the conclusion MUST say so explicitly and must not read as if the original (exact/requested) result had been obtained; if the exact result is unavailable, say so plainly.
       A /v5 slash command mirrors these (configure|start|resume|pause|stop|status|report|members|message|meeting|hire|fire|add|remove|set|paper).
 
       LEAN FORMAL VERIFICATION (formalVerify, a tunable parameter):
@@ -214,6 +237,19 @@
           reported as LEAN_NOT_FOUND, a host with no subprocess service as NO_SUBPROCESS
           (on a timeout the process is terminated first), and in every one of those cases the
           code can still be written down and archived.
+        - Daily eagerness is a SEPARATE knob: leanInitiative 'off' (no daily drive) |
+          'normal' (default; the reminder rides with formalVerify) | 'eager' (push valuable
+          small lemmas/propositions/definitions into the library even in ordinary rounds).
+        - Reuse first: check vibe_v5_lean_lib BEFORE writing a definition, reuse archived
+          content via `import Formal.Lib.<name>` / `import Formal.Proved.<name>` (the compile
+          gets `--search-path <VibeMath root>`, preceded by any leanSearchPaths), or copy the
+          exact text with vibe_v5_lean_read. Re-archiving identical content is de-duplicated.
+        - Compiles are ASYNC by default (leanAsync=true, leanJobsMaxParallel default 1):
+          vibe_v5_lean_run / vibe_v5_lean_archive enqueue and return at once; watch them with
+          vibe_v5_lean_job {jobId, waitMs} or vibe_v5_lean_lib.jobs, and NEVER treat an object
+          as passed before its job settles ok (exit 0, same content, same build context).
+        - Only formalize what you are confident about; when unsure record kind='blocked' with a
+          reason instead of dressing uncertainty up as a formalization.
         - vibe_v5_status / vibe_v5_report show the mode, per-object formal status and the
           formalization TODO. The framework never installs Lean and never judges fidelity.