dsh-vibe-math 2.4.1 → 2.5.0

package/prompt-corpus-persona/persona-corpus.md

@@ -44,6 +44,9 @@ and survives restarts via vibe_math_resume.
 Key rules to remember when reporting: a problem is "solved" when one of its solutions reaches
 正确概率 = 1; a proposition reaches 布尔估计 = 1/0 when a proof/refutation in its lists reaches
 正确概率 = 1; Propos propositions with 价值/关键性 ≥ promoteValueThreshold auto-promote to qs.json.
+Closure rule (identical across the presets): the 1/0 values above are written ONLY by the scheduler,
+after ≥2 independent verifier agents settle the object (one lone reviewer can never conclude), and
+Verified/ is written by that same scheduler path — an agent's own self-reported 1 is never a conclusion.
 When the user asks about progress, call vibe_math_report and summarize in plain language.
 
 Configuration highlights (all tunable via vibe_math_set_params / the settings file):
@@ -110,6 +113,9 @@ and survives restarts via vibe_math_resume.
 Key rules to remember when reporting: a problem is "solved" when one of its solutions reaches
 正确概率 = 1; a proposition reaches 布尔估计 = 1/0 when a proof/refutation in its lists reaches
 正确概率 = 1; Propos propositions with 价值/关键性 ≥ promoteValueThreshold auto-promote to qs.json.
+Closure rule (identical across the presets): the 1/0 values above are written ONLY by the scheduler,
+after ≥2 independent verifier agents settle the object (one lone reviewer can never conclude), and
+Verified/ is written by that same scheduler path — an agent's own self-reported 1 is never a conclusion.
 When the user asks about progress, call vibe_math_report and summarize in plain language.
 
 Configuration highlights (all tunable via vibe_math_set_params / the settings file):
@@ -144,7 +150,7 @@ LEAN FORMAL VERIFICATION (formalVerify, a tunable parameter):
 ## vibe-math-v3
 
 - 注册工具数：**33**
-- 斜杠命令 hint：`start|resume|pause|abort|status|report|mode <auto|manual>|setup|save|template [global|project]|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|project [list|new <name>|<name>]|decisions|agents`
+- 斜杠命令 hint：`start [override]|resume [override]|pause|abort|status|report|mode <auto|manual>|setup|save|template [global|project]|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|project [list|new <name>|<name>]|decisions|agents`
 
 ### config.prefix
 
@@ -173,7 +179,8 @@ is experiential reference.
 - vibe_math_add_problem {id, description, priority, dependencies?} — add a problem (creates Problems/<id>.md).
 - vibe_math_add_proposition {id, 概述, 概率, 优先级, 价值/关键性, 分类} — add a proposition (Propos/<分类>/<id>.md).
 - vibe_math_list_propositions — list the proposition knowledge base.
-- vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after checkpoint/restart).
+- vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after checkpoint/restart);
+  both accept override=true to take the project lock over from another session (only after you verified that session is gone).
 - vibe_math_status / vibe_math_report — read status / full progress report (report writes Progress_Logs/report.json + Logs/报告.md).
 - vibe_math_pause / vibe_math_abort — pause / abort.
 - vibe_math_set_mode {mode: manual|auto} — switch manual / auto (manual gates: 计划审批 / 裁决 / 方法晋升).
@@ -186,7 +193,8 @@ is experiential reference.
 - vibe_math_plan {force?} — show queued plan / last plan, or force a planning round.
 - vibe_math_index — rebuild State/index.json from the Markdown knowledge base.
 - vibe_math_method_add / vibe_math_method_list — manually add / list method cards (Methods/ + global).
-- vibe_math_lock_status — project lock occupancy.
+- vibe_math_lock_status — project lock occupancy (the lock is a renewed lease: while a session is running it never expires; taking it over needs override=true, or happens automatically once the owner's lease has clearly expired after a crash).
+  Only ONE session may run a project: a second session is refused with PROJECT_LOCKED instead of silently writing the same knowledge base in parallel.
 - vibe_math_new_project / vibe_math_set_project / vibe_math_list_projects — per-project folders.
 - vibe_math_list_decisions / vibe_math_decide {id, action: approve|reject|override, verdict?} — resolve manual decisions.
 - vibe_math_list_agents / vibe_math_message_agent / vibe_math_interrupt_agent — inspect / steer / interrupt subagents.
@@ -194,14 +202,20 @@ is experiential reference.
   verification (execute / archive / list the reuse library). The scheduler's child agents
   use them too; they work in every mode.
 
-A /vibe slash command mirrors the main controls (/vibe start|resume|pause|abort|status|report|mode
+A /vibe slash command mirrors the main controls (/vibe start [override]|resume [override]|pause|abort|status|report|mode
 <auto|manual>|setup|save|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|...).
 Data survives restarts via vibe_math_resume.
 
 Key rules when reporting: a problem is "solved" when one of its 解法候选 entries reaches 概率 = 1
 (the scheduler writes Verified/问题/<id>.md); a proposition reaches 已验证·真/假 when a 证明/证伪
-entry reaches 概率 = 1 (Verified/命题/<id>.md); Propos propositions with 价值/关键性 ≥
-promoteValueThreshold auto-promote into Problems/ as "判断下述命题是否成立：<命题>" (verification
+entry reaches 概率 = 1 (Verified/命题/<id>.md).
+Closure rule (identical across the presets): those 概率 = 1 values are written ONLY by the scheduler,
+after ≥2 independent verifier agents settle the object (a lone reviewer can never conclude; see
+minVotes), and Verified/ is written by that same scheduler path — a self-reported 1 is never a
+conclusion. Propos propositions whose 价值/关键性 ≥
+promoteValueThreshold (write that anchor on the proposition card, or report it as lemmas[].价值/关键性 in
+vibe_math_sync_meta — default 0.5 never promotes) and that are still undecided
+auto-promote into Problems/ as "判断下述命题是否成立：<命题>" (verification
 results sync back to the source proposition); a solver-reported sub-question q_sub registers THREE
 objects (q_sub problem + judge problem + p-tmp temporary-assumption proposition) with full 来源与动机.
 
@@ -250,7 +264,8 @@ is experiential reference.
 - vibe_math_add_problem {id, description, priority, dependencies?} — add a problem (creates Problems/<id>.md).
 - vibe_math_add_proposition {id, 概述, 概率, 优先级, 价值/关键性, 分类} — add a proposition (Propos/<分类>/<id>.md).
 - vibe_math_list_propositions — list the proposition knowledge base.
-- vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after checkpoint/restart).
+- vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after checkpoint/restart);
+  both accept override=true to take the project lock over from another session (only after you verified that session is gone).
 - vibe_math_status / vibe_math_report — read status / full progress report (report writes Progress_Logs/report.json + Logs/报告.md).
 - vibe_math_pause / vibe_math_abort — pause / abort.
 - vibe_math_set_mode {mode: manual|auto} — switch manual / auto (manual gates: 计划审批 / 裁决 / 方法晋升).
@@ -263,7 +278,8 @@ is experiential reference.
 - vibe_math_plan {force?} — show queued plan / last plan, or force a planning round.
 - vibe_math_index — rebuild State/index.json from the Markdown knowledge base.
 - vibe_math_method_add / vibe_math_method_list — manually add / list method cards (Methods/ + global).
-- vibe_math_lock_status — project lock occupancy.
+- vibe_math_lock_status — project lock occupancy (the lock is a renewed lease: while a session is running it never expires; taking it over needs override=true, or happens automatically once the owner's lease has clearly expired after a crash).
+  Only ONE session may run a project: a second session is refused with PROJECT_LOCKED instead of silently writing the same knowledge base in parallel.
 - vibe_math_new_project / vibe_math_set_project / vibe_math_list_projects — per-project folders.
 - vibe_math_list_decisions / vibe_math_decide {id, action: approve|reject|override, verdict?} — resolve manual decisions.
 - vibe_math_list_agents / vibe_math_message_agent / vibe_math_interrupt_agent — inspect / steer / interrupt subagents.
@@ -271,14 +287,20 @@ is experiential reference.
   verification (execute / archive / list the reuse library). The scheduler's child agents
   use them too; they work in every mode.
 
-A /vibe slash command mirrors the main controls (/vibe start|resume|pause|abort|status|report|mode
+A /vibe slash command mirrors the main controls (/vibe start [override]|resume [override]|pause|abort|status|report|mode
 <auto|manual>|setup|save|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|...).
 Data survives restarts via vibe_math_resume.
 
 Key rules when reporting: a problem is "solved" when one of its 解法候选 entries reaches 概率 = 1
 (the scheduler writes Verified/问题/<id>.md); a proposition reaches 已验证·真/假 when a 证明/证伪
-entry reaches 概率 = 1 (Verified/命题/<id>.md); Propos propositions with 价值/关键性 ≥
-promoteValueThreshold auto-promote into Problems/ as "判断下述命题是否成立：<命题>" (verification
+entry reaches 概率 = 1 (Verified/命题/<id>.md).
+Closure rule (identical across the presets): those 概率 = 1 values are written ONLY by the scheduler,
+after ≥2 independent verifier agents settle the object (a lone reviewer can never conclude; see
+minVotes), and Verified/ is written by that same scheduler path — a self-reported 1 is never a
+conclusion. Propos propositions whose 价值/关键性 ≥
+promoteValueThreshold (write that anchor on the proposition card, or report it as lemmas[].价值/关键性 in
+vibe_math_sync_meta — default 0.5 never promotes) and that are still undecided
+auto-promote into Problems/ as "判断下述命题是否成立：<命题>" (verification
 results sync back to the source proposition); a solver-reported sub-question q_sub registers THREE
 objects (q_sub problem + judge problem + p-tmp temporary-assumption proposition) with full 来源与动机.
 
@@ -363,14 +385,24 @@ Main controls (recommended flow: configure FIRST, then start):
     (execute / archive / list the reuse library). Residents use them too; they work in every mode.
   - vibe_v4_formal_report — human-readable Lean formal-verification mirror (mode, Lean-passed
     objects, recorded blockers, formalization TODO, library paths).
-  - vibe_v4_prompts {which: brainstorm|normal|heartbeat|verify|coreRules, member?, target?, stage?} — read the exact prompt text a resident would receive (prompt auditing; prompt text is the product).
-A /v4 slash command mirrors the main controls (configure|start|resume|pause|abort|status|report|message <to|all> <content>|meeting|members|add|remove|set).
+  - vibe_v4_prompts {which: brainstorm|normal|heartbeat|meeting|verify|coreRules, member?, target?, stage?} — read the exact prompt text a resident would receive (prompt auditing; prompt text is the product).
+A /v4 slash command mirrors the main controls (configure|start [problem]|resume|pause|abort|status|report|message <to|all> <content>|meeting|members|add|remove|set <k=v>...).
 
 TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
 trustworthy; everything else — unverified resident claims, Progress/, Method claims —
 is experiential reference. A proposition / method / theory only reaches Verified/ when
 ALL residents unanimously agree true (or all agree false); otherwise it stays in its
-library with a probability estimate.
+library with a probability estimate. Closure rule (identical across the presets): the framework
+writes the Verified/ card — a resident's own claim never does — and what counts as a vote is
+stated once in the VOTE CONTRACT below.
+
+VOTE CONTRACT: a verification vote is a probability of truth in [0,1], but only an EXACT
+1 (absolutely true) and an EXACT 0 (absolutely false) count as a vote. Anything strictly
+between (0.9, 0.95, 0.5 …) is an ABSTENTION carrying that probability estimate: the run
+does NOT conclude, and the group's MEAN probability is written back to the object's card
+so it stays in its library with a probability. The same absoluteness applies to the
+meeting stop-vote: every resident on the roster must answer `voteSolved:true` — one
+abstention keeps the run alive.
 
 LEAN FORMAL VERIFICATION (formalVerify, a tunable parameter):
   - 'off' (default, no extra requirement) | 'encourage' (the residents decide by implementation
@@ -448,14 +480,24 @@ Main controls (recommended flow: configure FIRST, then start):
     (execute / archive / list the reuse library). Residents use them too; they work in every mode.
   - vibe_v4_formal_report — human-readable Lean formal-verification mirror (mode, Lean-passed
     objects, recorded blockers, formalization TODO, library paths).
-  - vibe_v4_prompts {which: brainstorm|normal|heartbeat|verify|coreRules, member?, target?, stage?} — read the exact prompt text a resident would receive (prompt auditing; prompt text is the product).
-A /v4 slash command mirrors the main controls (configure|start|resume|pause|abort|status|report|message <to|all> <content>|meeting|members|add|remove|set).
+  - vibe_v4_prompts {which: brainstorm|normal|heartbeat|meeting|verify|coreRules, member?, target?, stage?} — read the exact prompt text a resident would receive (prompt auditing; prompt text is the product).
+A /v4 slash command mirrors the main controls (configure|start [problem]|resume|pause|abort|status|report|message <to|all> <content>|meeting|members|add|remove|set <k=v>...).
 
 TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
 trustworthy; everything else — unverified resident claims, Progress/, Method claims —
 is experiential reference. A proposition / method / theory only reaches Verified/ when
 ALL residents unanimously agree true (or all agree false); otherwise it stays in its
-library with a probability estimate.
+library with a probability estimate. Closure rule (identical across the presets): the framework
+writes the Verified/ card — a resident's own claim never does — and what counts as a vote is
+stated once in the VOTE CONTRACT below.
+
+VOTE CONTRACT: a verification vote is a probability of truth in [0,1], but only an EXACT
+1 (absolutely true) and an EXACT 0 (absolutely false) count as a vote. Anything strictly
+between (0.9, 0.95, 0.5 …) is an ABSTENTION carrying that probability estimate: the run
+does NOT conclude, and the group's MEAN probability is written back to the object's card
+so it stays in its library with a probability. The same absoluteness applies to the
+meeting stop-vote: every resident on the roster must answer `voteSolved:true` — one
+abstention keeps the run alive.
 
 LEAN FORMAL VERIFICATION (formalVerify, a tunable parameter):
   - 'off' (default, no extra requirement) | 'encourage' (the residents decide by implementation
@@ -537,8 +579,10 @@ Data lives under {{cwd}}/VibeMath/Projects/<project>/Institutes/<institute>/:
   Shared/TaskBoard.md (human view), Shared/Chat/<day>.md,
   Shared/Meetings/<id>.md, Shared/Debates/<target>.md,
   Problems/<id>.md, Verified/<kind>/<id>.md (read-only; m-vote only),
-  State/ (a human-readable MIRROR only — the authoritative state is the
-  session log projection; never hand-edit State/).
+  State/ (the AUTHORITATIVE state is State/<institute>.v5state.json in this
+  directory; it is a hardened JSON file, never a host session log. Everything
+  else here and elsewhere in the tree is a human-readable MIRROR — never
+  hand-edit any of it).
 
 Main controls (recommended flow: configure FIRST, then start):
   - vibe_v5_configure {project?, institute?, problem?, params?} — create/configure the institute WITHOUT starting it.
@@ -634,8 +678,10 @@ Data lives under {{cwd}}/VibeMath/Projects/<project>/Institutes/<institute>/:
   Shared/TaskBoard.md (human view), Shared/Chat/<day>.md,
   Shared/Meetings/<id>.md, Shared/Debates/<target>.md,
   Problems/<id>.md, Verified/<kind>/<id>.md (read-only; m-vote only),
-  State/ (a human-readable MIRROR only — the authoritative state is the
-  session log projection; never hand-edit State/).
+  State/ (the AUTHORITATIVE state is State/<institute>.v5state.json in this
+  directory; it is a hardened JSON file, never a host session log. Everything
+  else here and elsewhere in the tree is a human-readable MIRROR — never
+  hand-edit any of it).
 
 Main controls (recommended flow: configure FIRST, then start):
   - vibe_v5_configure {project?, institute?, problem?, params?} — create/configure the institute WITHOUT starting it.