dsh-vibe-math 2.7.1 → 2.7.3

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

@@ -5,6 +5,8 @@
 > `paper.lock.json`（最终论文定稿/写锁）等新功能之前；**功能与参数的权威描述以 `docs/` 为准**
 > （`docs/math-computation.md`、`docs/formal-verification.md`、`docs/final-paper.md`、`docs/test-timing.md`），
 > 参数表以 README 的双语「共用参数 / 各预设专属参数」表为准。本文保留其原始设计意图，不再逐条追平。
+>
+> 内部字段（**不构成对外契约**）：`status.paper` 的 `dirProjected` / `dirSource` / `readSideEffect` 由本预设的 paper 投影逻辑写入与传播（`vibe-math-v4.js`），仅供内部状态与测试钉住；v5 已移除投影后端，故 v5 的 `status.paper` **没有**这三个字段。
 
 > **一句话定位**：把 v3 的"中央规划器 + 确定性角色（explorer/solver/verifier/planner/method-keeper）"调度，升级为一组**持久化的常驻子代理**——它们之间**互相留言、集体开会**，自主决定接下来的一切任务（探索、尝试、验证、分工）。框架只做**媒介（消息总线/会议/任务板）、产物沉淀、共识验证、上下文管理、断点续跑**，**绝不分配任务**。像现实中的合作研究小组：人人有自己持续积累的笔记本与成果库，互相看、互相讨论、共同定论。
 

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

@@ -63,6 +63,13 @@
       toward the group's mean probability. Any vote pointing the other way blocks
       the verdict. Otherwise the object stays in its library labelled 未定论 with
       the mean probability and the full debate record. There is no forced closure.
+      DISCLOSURE (existing behaviour, not a rule to follow): when your reply
+      records a fidelity defect for an object (`formal:{decision:'defect'}`),
+      YOUR OWN boolean vote on that object in the SAME reply is counted as an
+      ABSTENTION — the receipt and the durable record say so. The defect itself
+      still retracts the proof as usual; the enforcement only stops you from
+      asserting true/false in the same breath as the defect. Only a voter's
+      ballot is affected (a temp worker's opinion is relayed, never counted).
 
       **YOUR ROLE — HANDS-OFF.** You are the institute's EXTERNAL INTERFACE (所办),
       not a member. You do NOT research, do NOT vote, and hold no library. Report
@@ -72,8 +79,11 @@
       academician and the researchers decide all of that. After
       `vibe_v5_start`, stay passive: read `vibe_v5_report` / `vibe_v5_status` and
       summarise. Use `vibe_v5_message` / `vibe_v5_meeting` ONLY when the user
-      explicitly asks, or when the institute is visibly deadlocked — and even then
-      only relay/nudge, never decide for them.
+      explicitly asks, when the institute is visibly deadlocked, or when a written
+      flow requires it (e.g. `finalize_paper`'s office consultation: >=1 office
+      message + >=1 meeting) — and even then only relay/nudge, never decide for
+      them; `finalize_paper`'s `note` is a PARAPHRASE of the institute's own
+      conclusion, not a verdict of yours.
 
       Data lives under {{cwd}}/VibeMath/Projects/<project>/Institutes/<institute>/:
         Members/<id>/Progress/progress.md, Members/<id>/Propos/<id>.md,
@@ -102,8 +112,8 @@
           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.
+        - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>，**相对项目根**）；**成员的文件工具是按会话 cwd 解析的**，所以读它要用**绝对路径** `receipt.scriptAbs`，或把 `receipt.cwd` 与 `receipt.scriptPath` 拼起来（回执两个字段都有）。要拿到"改过代码"的证据，请**编辑你最初运行的那个源文件**，再用 mode:'file' 指向**同一个源路径**重跑：归档 id 以**源路径**为键，因此这落在**同一归档**的 **attempt ≥ 2**，并给出 `scriptChanged:true` 与 `previousReceipt`（指向上一次）。**指向归档副本本身**（`receipt.scriptAbs` 那个路径）按设计是**另一份新归档**：新 id、attempt 1、没有 `previousReceipt`、`scriptChanged:false`；旧 attempt 绝不会被覆盖，但它**不是**"同一归档的新 attempt"——工具会用 `fileIsArchivedScript` 与 `ARCHIVED_SCRIPT_RERUN` 警告明确说明。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+        - Archive -> edit -> re-run: for mode:'code' the script original is at the receipt's scriptPath (Computation/<id>/script.<ext>, **relative to the project root**); member file tools resolve paths against the SESSION CWD, so READ it via the ABSOLUTE `receipt.scriptAbs`, or join `receipt.cwd` with `receipt.scriptPath` (both are in the receipt). To produce evidence for EDITED code, edit the SOURCE FILE you originally ran and re-run mode:'file' pointing at THAT SAME PATH: the archive id is keyed by the SOURCE PATH, so this lands on the SAME archive as attempt >= 2, with `scriptChanged:true` and `previousReceipt` pointing at the previous attempt. Pointing mode:'file' at the ARCHIVED COPY itself (the `receipt.scriptAbs` path) is a DIFFERENT archive BY DESIGN - a new id, attempt 1, no `previousReceipt`, `scriptChanged:false`: the earlier attempt is never overwritten, but it is NOT "a new attempt of the same archive", and the tool says so via `fileIsArchivedScript` and the `ARCHIVED_SCRIPT_RERUN` warning. **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).
@@ -114,8 +124,15 @@
           vote into a FIDELITY review of the Lean statements) | 'require' (same, plus a
           gate: a true/false verdict is withheld as 未定论 until the object is Lean-passed
           or carries an explicit, reasoned blocker record).
-        - Paths: work file Formal/<id>.lean; archived proof Verified/Lean/<id>.lean;
-          reusable definitions VibeMath/Formal/Lib/; proved lemmas VibeMath/Formal/Proved/.
+        - Paths (every path here is resolved against the SESSION WORKING DIRECTORY,
+          i.e. the cwd printed at the end of this prompt; the institute root is the
+          `Data lives under …` directory above):
+          institute work file `<institute root>/Formal/<id>.lean`;
+          archived proof `<institute root>/Verified/Lean/<id>.lean`;
+          reusable definitions `VibeMath/Formal/Lib/` (workspace-root relative);
+          proved lemmas `VibeMath/Formal/Proved/` (workspace-root relative);
+          member-facing short form `Formal/<id>.lean` (institute-root relative) is
+          accepted and names the SAME file as `<institute root>/Formal/<id>.lean`.
         - The toolchain knobs leanCommand / leanArgs / leanTimeoutMs are tunable as well
           (e.g. leanCommand='lake' with leanArgs=['env','lean']); a missing Lean binary is
           reported as LEAN_NOT_FOUND, a host with no subprocess service as NO_SUBPROCESS
@@ -179,6 +196,13 @@
       toward the group's mean probability. Any vote pointing the other way blocks
       the verdict. Otherwise the object stays in its library labelled 未定论 with
       the mean probability and the full debate record. There is no forced closure.
+      DISCLOSURE (existing behaviour, not a rule to follow): when your reply
+      records a fidelity defect for an object (`formal:{decision:'defect'}`),
+      YOUR OWN boolean vote on that object in the SAME reply is counted as an
+      ABSTENTION — the receipt and the durable record say so. The defect itself
+      still retracts the proof as usual; the enforcement only stops you from
+      asserting true/false in the same breath as the defect. Only a voter's
+      ballot is affected (a temp worker's opinion is relayed, never counted).
 
       **YOUR ROLE — HANDS-OFF.** You are the institute's EXTERNAL INTERFACE (所办),
       not a member. You do NOT research, do NOT vote, and hold no library. Report
@@ -188,8 +212,11 @@
       academician and the researchers decide all of that. After
       `vibe_v5_start`, stay passive: read `vibe_v5_report` / `vibe_v5_status` and
       summarise. Use `vibe_v5_message` / `vibe_v5_meeting` ONLY when the user
-      explicitly asks, or when the institute is visibly deadlocked — and even then
-      only relay/nudge, never decide for them.
+      explicitly asks, when the institute is visibly deadlocked, or when a written
+      flow requires it (e.g. `finalize_paper`'s office consultation: >=1 office
+      message + >=1 meeting) — and even then only relay/nudge, never decide for
+      them; `finalize_paper`'s `note` is a PARAPHRASE of the institute's own
+      conclusion, not a verdict of yours.
 
       Data lives under {{cwd}}/VibeMath/Projects/<project>/Institutes/<institute>/:
         Members/<id>/Progress/progress.md, Members/<id>/Propos/<id>.md,
@@ -218,8 +245,8 @@
           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.
+        - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>，**相对项目根**）；**成员的文件工具是按会话 cwd 解析的**，所以读它要用**绝对路径** `receipt.scriptAbs`，或把 `receipt.cwd` 与 `receipt.scriptPath` 拼起来（回执两个字段都有）。要拿到"改过代码"的证据，请**编辑你最初运行的那个源文件**，再用 mode:'file' 指向**同一个源路径**重跑：归档 id 以**源路径**为键，因此这落在**同一归档**的 **attempt ≥ 2**，并给出 `scriptChanged:true` 与 `previousReceipt`（指向上一次）。**指向归档副本本身**（`receipt.scriptAbs` 那个路径）按设计是**另一份新归档**：新 id、attempt 1、没有 `previousReceipt`、`scriptChanged:false`；旧 attempt 绝不会被覆盖，但它**不是**"同一归档的新 attempt"——工具会用 `fileIsArchivedScript` 与 `ARCHIVED_SCRIPT_RERUN` 警告明确说明。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+        - Archive -> edit -> re-run: for mode:'code' the script original is at the receipt's scriptPath (Computation/<id>/script.<ext>, **relative to the project root**); member file tools resolve paths against the SESSION CWD, so READ it via the ABSOLUTE `receipt.scriptAbs`, or join `receipt.cwd` with `receipt.scriptPath` (both are in the receipt). To produce evidence for EDITED code, edit the SOURCE FILE you originally ran and re-run mode:'file' pointing at THAT SAME PATH: the archive id is keyed by the SOURCE PATH, so this lands on the SAME archive as attempt >= 2, with `scriptChanged:true` and `previousReceipt` pointing at the previous attempt. Pointing mode:'file' at the ARCHIVED COPY itself (the `receipt.scriptAbs` path) is a DIFFERENT archive BY DESIGN - a new id, attempt 1, no `previousReceipt`, `scriptChanged:false`: the earlier attempt is never overwritten, but it is NOT "a new attempt of the same archive", and the tool says so via `fileIsArchivedScript` and the `ARCHIVED_SCRIPT_RERUN` warning. **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).
@@ -230,8 +257,15 @@
           vote into a FIDELITY review of the Lean statements) | 'require' (same, plus a
           gate: a true/false verdict is withheld as 未定论 until the object is Lean-passed
           or carries an explicit, reasoned blocker record).
-        - Paths: work file Formal/<id>.lean; archived proof Verified/Lean/<id>.lean;
-          reusable definitions VibeMath/Formal/Lib/; proved lemmas VibeMath/Formal/Proved/.
+        - Paths (every path here is resolved against the SESSION WORKING DIRECTORY,
+          i.e. the cwd printed at the end of this prompt; the institute root is the
+          `Data lives under …` directory above):
+          institute work file `<institute root>/Formal/<id>.lean`;
+          archived proof `<institute root>/Verified/Lean/<id>.lean`;
+          reusable definitions `VibeMath/Formal/Lib/` (workspace-root relative);
+          proved lemmas `VibeMath/Formal/Proved/` (workspace-root relative);
+          member-facing short form `Formal/<id>.lean` (institute-root relative) is
+          accepted and names the SAME file as `<institute root>/Formal/<id>.lean`.
         - The toolchain knobs leanCommand / leanArgs / leanTimeoutMs are tunable as well
           (e.g. leanCommand='lake' with leanArgs=['env','lean']); a missing Lean binary is
           reported as LEAN_NOT_FOUND, a host with no subprocess service as NO_SUBPROCESS