principles-disciple 1.245.2 → 2.0.0

package/dist/templates/langs/en/skills/pd-cli-operator/SKILL.md

@@ -20,7 +20,14 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
   trajectory evidence, candidates likely gated (`needs_evidence`) by the
   admission threshold — the CLI output warns about this.
 - `--session <id>` is validated up front; a missing session fails with
-  `session_not_found` before anything is written.
+  `session_not_found` before anything is written. When the binding is
+  verified but the trajectory evidence is empty or unreadable, the record
+  degrades honestly to bound + evidence-unavailable and the admission gate
+  decides — no evidence is fabricated.
+- A successful command returning a `painId` is only a record receipt; whether
+  the diagnosis produced candidates and whether they were admitted is decided
+  by `candidateIds` / `admissionResults` / `ledgerEntryIds` in the JSON
+  output. Activation is a separate stage that follows Owner approval.
 
 Success requires:
 - `status` is `succeeded`

package/dist/templates/langs/en/skills/pd-pain-signal/SKILL.md

@@ -6,10 +6,11 @@ disable-model-invocation: false
 
 # Pain Signal (Runtime V2)
 
-Session evidence is what makes a pain diagnosable. A pain recorded without a
-session carries no trajectory evidence, its candidates score below the
-admission threshold (0.5) and are gated as `needs_evidence` — the Owner's
-report is stored, but nothing is internalized.
+Session evidence is what lets a diagnosis carry real trajectory evidence. A
+pain recorded without a session is a legal unbound Owner report: it carries no
+trajectory evidence, its diagnosis confidence tends to be low, and its
+candidates are likely gated as `needs_evidence` by the admission gate — the
+Owner's report is stored, but usually nothing is internalized.
 
 ## In an OpenClaw session (preferred)
 
@@ -35,6 +36,11 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 
 - `--session <id>` is validated against the workspace trajectory: a missing
   session fails with `session_not_found` before anything is written.
+- When the `--session` binding is verified but the trajectory evidence is
+  empty or unreadable (the session is real), the record is submitted as an
+  honest bound + evidence-unavailable degrade: no evidence is fabricated and
+  the admission gate decides what empty evidence is worth, instead of a hard
+  refusal.
 - Recording without `--session` is allowed as an unbound Owner report, but it
   attaches no evidence and its candidates will likely be gated
   (`needs_evidence`) by the admission gate — the CLI output says so explicitly.
@@ -57,6 +63,9 @@ pd runtime flow show --workspace "<workspace>" --json
 
 Success requires admitted candidates, not merely generated ones: check
 `admissionResults` for `admitted` decisions and non-empty `ledgerEntryIds`.
+A successful command returning a `painId` is only a record receipt — it does
+not mean the diagnosis produced candidates or that anything was admitted.
 Candidates reported as `needs_evidence` or `deferred` were NOT internalized —
-if all candidates are gated, re-record with `/pd-pain` or `--session` so the
-diagnosis carries real trajectory evidence.
+if candidates are gated, re-record with `/pd-pain` or `--session` so the
+diagnosis carries real trajectory evidence. Activation is a separate stage
+that follows Owner approval; this flow never activates anything by itself.

package/dist/templates/langs/en/skills/pd-runtime-v2/SKILL.md

@@ -21,8 +21,11 @@ Manual:
 pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 `--session` binds the report to a recorded session (validated up front) so
-diagnosis carries real trajectory evidence; without it the record is an
-unbound Owner report with no evidence and candidates will likely be gated.
+diagnosis carries real trajectory evidence; when the binding is verified but
+the trajectory evidence is empty or unreadable, the record degrades honestly
+to bound + evidence-unavailable and the admission gate decides; without
+`--session` the record is a legal unbound Owner report with no evidence and
+its candidates will likely be gated.
 
 Forbidden:
 - Do not write `.state/.pain_flag`.
@@ -59,16 +62,25 @@ pd candidate show --candidate-id "<candidateId>" --workspace "<workspace>" --jso
 
 ## Success Criteria
 
+A pain travels through four stages: record receipt (`painId`) → diagnosis
+(produces candidates) → admission (`admitted`, into the ledger) → Owner
+approval and activation.
+
 A diagnosis is successful only when:
 - `status` is `succeeded`
 - `candidateIds` is non-empty
-- `ledgerEntryIds` is non-empty
+- `admissionResults` contains `admitted` decisions with non-empty
+  `ledgerEntryIds`
 
-Task creation alone is not success. A run without candidates or ledger entries is failed/retried/incomplete.
+Task creation alone, candidate generation alone, or a ledger entry alone is
+not success — candidates without an `admitted` decision were never admitted.
+Activation is a separate stage that follows Owner approval; `pd pain record`
+never activates anything by itself.
 
 ## If Manual Diagnosis Is Needed
 
 1. Use `pd pain record`.
 2. Inspect JSON output.
-3. If `candidateIds` or `ledgerEntryIds` is empty, treat it as not completed.
+3. If `candidateIds` or `ledgerEntryIds` is empty, or candidates are gated as
+   `needs_evidence` / `deferred`, treat it as not completed (not internalized).
 4. Use `pd candidate list/show` and `pd runtime flow show` for follow-up.

package/dist/templates/langs/zh/skills/pd-cli-operator/SKILL.md

@@ -18,7 +18,11 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 - 不带 `--session` 的记录是诚实的 unbound Owner 报告：没有轨迹证据，
   候选大概率被准入阈值拦为 `needs_evidence` —— CLI 输出会明确警告。
 - `--session <id>` 会先校验；会话不存在时以 `session_not_found` 失败，
-  不会写入任何内容。
+  不会写入任何内容。会话验证通过但轨迹证据为空或不可读时，按
+  bound + 证据不可用诚实降级提交，由 admission gate 评判，不会伪造证据。
+- 命令成功返回 `painId` 只代表记录回执；诊断是否产出候选、候选是否被
+  准入，以 JSON 输出中的 `candidateIds` / `admissionResults` /
+  `ledgerEntryIds` 为准。激活是 Owner 批准之后的独立阶段。
 
 成功标准：
 - `status` 是 `succeeded`

package/dist/templates/langs/zh/skills/pd-pain-signal/SKILL.md

@@ -6,9 +6,10 @@ disable-model-invocation: false
 
 # Pain Signal（Runtime V2）
 
-会话证据决定一条痛苦能否被诊断。未绑定会话的记录不携带任何轨迹证据，
-候选 confidence 低于准入阈值（0.5），全部被 admission gate 拦为
-`needs_evidence` —— Owner 的报告被保存，但不会进入内化。
+会话证据决定诊断能否携带真实轨迹证据。未绑定会话的记录是合法的 unbound
+Owner 报告：它不携带轨迹证据，诊断 confidence 通常偏低，候选大概率被
+admission gate 拦为 `needs_evidence` —— Owner 的报告被保存，但通常不会进入
+内化。
 
 ## 在 OpenClaw 会话中（首选）
 
@@ -32,6 +33,9 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 
 - `--session <id>` 会先对工作区轨迹做校验：会话不存在时以
   `session_not_found` 失败，不会写入任何内容。
+- `--session` 验证通过但轨迹证据为空或不可读（会话真实存在）时，记录按
+  bound + 证据不可用诚实降级提交：不伪造证据，由 admission gate 评判空
+  证据的价值，而不是直接拒绝。
 - 不带 `--session` 的记录是允许的 unbound Owner 报告，但不附带证据，
   候选大概率被 admission gate 拦为 `needs_evidence` —— CLI 输出会明确
   提示这一点。
@@ -53,6 +57,8 @@ pd runtime flow show --workspace "<workspace>" --json
 ```
 
 成功标准是候选被**准入**（admitted），而不只是被生成：检查
-`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。
-`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若全部候选被拦截，
+`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。命令成功
+返回 `painId` 只代表记录回执，不代表诊断或准入成功。
+`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若候选被拦截，
 请用 `/pd-pain` 或 `--session` 重新记录，让诊断携带真实轨迹证据。
+激活（activation）是 Owner 批准之后的独立阶段，本流程不会直接产生激活。

package/dist/templates/langs/zh/skills/pd-runtime-v2/SKILL.md

@@ -21,7 +21,9 @@ disable-model-invocation: false
 pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 `--session` 把报告绑定到已记录的会话（先校验），让诊断携带真实轨迹
-证据；不带它则是无证据的 unbound Owner 报告，候选大概率被拦。
+证据；会话验证通过但轨迹证据为空或不可读时，按 bound + 证据不可用诚实
+降级提交，由 admission gate 评判；不带 `--session` 则是无证据的 unbound
+Owner 报告（合法），候选大概率被拦。
 
 禁止入口：
 - 不要写 `.state/.pain_flag`。
@@ -58,16 +60,22 @@ pd candidate show --candidate-id "<candidateId>" --workspace "<workspace>" --jso
 
 ## 成功标准
 
+一条痛苦的完整链路分四个阶段：记录回执（`painId`）→ 诊断（产出候选）→
+准入（`admitted`，进入 ledger）→ Owner 批准与激活（activation）。
+
 一次诊断只有在同时满足以下条件时才算成功：
 - `status` 是 `succeeded`
 - `candidateIds` 非空
-- `ledgerEntryIds` 非空
+- `admissionResults` 中出现 `admitted` 决策，且对应 `ledgerEntryIds` 非空
 
-只创建 task 不算成功。没有 candidate 或 ledger entry 的 run 是失败、重试或未完成。
+只创建 task、只生成候选或只有 ledger entry 都不算成功——没有 `admitted`
+决策的候选并未被准入。激活是 Owner 决策之后的独立阶段，`pd pain record`
+不会直接产生激活。
 
 ## 需要手动诊断时
 
 1. 使用 `pd pain record`。
 2. 检查 JSON 输出。
-3. 如果 `candidateIds` 或 `ledgerEntryIds` 为空，视为未完成。
+3. 如果 `candidateIds` 或 `ledgerEntryIds` 为空，或候选被拦为
+   `needs_evidence` / `deferred`，视为未完成（未内化）。
 4. 用 `pd candidate list/show` 和 `pd runtime flow show` 继续排查。

package/dist/utils/retry.d.ts

@@ -168,7 +168,7 @@ export declare function clampTimeout(ms: number): number;
  * This is the primary function used by WorkflowManager.
  *
  * @param dataSource - Source for historical duration data
- * @param workflowType - e.g. 'empathy-observer'
+ * @param workflowType - e.g. 'correction-observer'
  * @param defaultTimeout - Fallback when insufficient data (from spec)
  * @returns Computed timeout in milliseconds
  */

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
-  "version": "1.245.2",
+  "version": "2.0.0",
   "activation": {
     "onStartup": true,
     "onCapabilities": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "principles-disciple",
-  "version": "1.245.2",
+  "version": "2.0.0",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
   "type": "module",
   "main": "./dist/index.js",

package/templates/langs/en/skills/pd-cli-operator/SKILL.md

@@ -20,7 +20,14 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
   trajectory evidence, candidates likely gated (`needs_evidence`) by the
   admission threshold — the CLI output warns about this.
 - `--session <id>` is validated up front; a missing session fails with
-  `session_not_found` before anything is written.
+  `session_not_found` before anything is written. When the binding is
+  verified but the trajectory evidence is empty or unreadable, the record
+  degrades honestly to bound + evidence-unavailable and the admission gate
+  decides — no evidence is fabricated.
+- A successful command returning a `painId` is only a record receipt; whether
+  the diagnosis produced candidates and whether they were admitted is decided
+  by `candidateIds` / `admissionResults` / `ledgerEntryIds` in the JSON
+  output. Activation is a separate stage that follows Owner approval.
 
 Success requires:
 - `status` is `succeeded`

package/templates/langs/en/skills/pd-pain-signal/SKILL.md

@@ -6,10 +6,11 @@ disable-model-invocation: false
 
 # Pain Signal (Runtime V2)
 
-Session evidence is what makes a pain diagnosable. A pain recorded without a
-session carries no trajectory evidence, its candidates score below the
-admission threshold (0.5) and are gated as `needs_evidence` — the Owner's
-report is stored, but nothing is internalized.
+Session evidence is what lets a diagnosis carry real trajectory evidence. A
+pain recorded without a session is a legal unbound Owner report: it carries no
+trajectory evidence, its diagnosis confidence tends to be low, and its
+candidates are likely gated as `needs_evidence` by the admission gate — the
+Owner's report is stored, but usually nothing is internalized.
 
 ## In an OpenClaw session (preferred)
 
@@ -35,6 +36,11 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 
 - `--session <id>` is validated against the workspace trajectory: a missing
   session fails with `session_not_found` before anything is written.
+- When the `--session` binding is verified but the trajectory evidence is
+  empty or unreadable (the session is real), the record is submitted as an
+  honest bound + evidence-unavailable degrade: no evidence is fabricated and
+  the admission gate decides what empty evidence is worth, instead of a hard
+  refusal.
 - Recording without `--session` is allowed as an unbound Owner report, but it
   attaches no evidence and its candidates will likely be gated
   (`needs_evidence`) by the admission gate — the CLI output says so explicitly.
@@ -57,6 +63,9 @@ pd runtime flow show --workspace "<workspace>" --json
 
 Success requires admitted candidates, not merely generated ones: check
 `admissionResults` for `admitted` decisions and non-empty `ledgerEntryIds`.
+A successful command returning a `painId` is only a record receipt — it does
+not mean the diagnosis produced candidates or that anything was admitted.
 Candidates reported as `needs_evidence` or `deferred` were NOT internalized —
-if all candidates are gated, re-record with `/pd-pain` or `--session` so the
-diagnosis carries real trajectory evidence.
+if candidates are gated, re-record with `/pd-pain` or `--session` so the
+diagnosis carries real trajectory evidence. Activation is a separate stage
+that follows Owner approval; this flow never activates anything by itself.

package/templates/langs/en/skills/pd-runtime-v2/SKILL.md

@@ -21,8 +21,11 @@ Manual:
 pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 `--session` binds the report to a recorded session (validated up front) so
-diagnosis carries real trajectory evidence; without it the record is an
-unbound Owner report with no evidence and candidates will likely be gated.
+diagnosis carries real trajectory evidence; when the binding is verified but
+the trajectory evidence is empty or unreadable, the record degrades honestly
+to bound + evidence-unavailable and the admission gate decides; without
+`--session` the record is a legal unbound Owner report with no evidence and
+its candidates will likely be gated.
 
 Forbidden:
 - Do not write `.state/.pain_flag`.
@@ -59,16 +62,25 @@ pd candidate show --candidate-id "<candidateId>" --workspace "<workspace>" --jso
 
 ## Success Criteria
 
+A pain travels through four stages: record receipt (`painId`) → diagnosis
+(produces candidates) → admission (`admitted`, into the ledger) → Owner
+approval and activation.
+
 A diagnosis is successful only when:
 - `status` is `succeeded`
 - `candidateIds` is non-empty
-- `ledgerEntryIds` is non-empty
+- `admissionResults` contains `admitted` decisions with non-empty
+  `ledgerEntryIds`
 
-Task creation alone is not success. A run without candidates or ledger entries is failed/retried/incomplete.
+Task creation alone, candidate generation alone, or a ledger entry alone is
+not success — candidates without an `admitted` decision were never admitted.
+Activation is a separate stage that follows Owner approval; `pd pain record`
+never activates anything by itself.
 
 ## If Manual Diagnosis Is Needed
 
 1. Use `pd pain record`.
 2. Inspect JSON output.
-3. If `candidateIds` or `ledgerEntryIds` is empty, treat it as not completed.
+3. If `candidateIds` or `ledgerEntryIds` is empty, or candidates are gated as
+   `needs_evidence` / `deferred`, treat it as not completed (not internalized).
 4. Use `pd candidate list/show` and `pd runtime flow show` for follow-up.

package/templates/langs/zh/skills/pd-cli-operator/SKILL.md

@@ -18,7 +18,11 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 - 不带 `--session` 的记录是诚实的 unbound Owner 报告：没有轨迹证据，
   候选大概率被准入阈值拦为 `needs_evidence` —— CLI 输出会明确警告。
 - `--session <id>` 会先校验；会话不存在时以 `session_not_found` 失败，
-  不会写入任何内容。
+  不会写入任何内容。会话验证通过但轨迹证据为空或不可读时，按
+  bound + 证据不可用诚实降级提交，由 admission gate 评判，不会伪造证据。
+- 命令成功返回 `painId` 只代表记录回执；诊断是否产出候选、候选是否被
+  准入，以 JSON 输出中的 `candidateIds` / `admissionResults` /
+  `ledgerEntryIds` 为准。激活是 Owner 批准之后的独立阶段。
 
 成功标准：
 - `status` 是 `succeeded`

package/templates/langs/zh/skills/pd-pain-signal/SKILL.md

@@ -6,9 +6,10 @@ disable-model-invocation: false
 
 # Pain Signal（Runtime V2）
 
-会话证据决定一条痛苦能否被诊断。未绑定会话的记录不携带任何轨迹证据，
-候选 confidence 低于准入阈值（0.5），全部被 admission gate 拦为
-`needs_evidence` —— Owner 的报告被保存，但不会进入内化。
+会话证据决定诊断能否携带真实轨迹证据。未绑定会话的记录是合法的 unbound
+Owner 报告：它不携带轨迹证据，诊断 confidence 通常偏低，候选大概率被
+admission gate 拦为 `needs_evidence` —— Owner 的报告被保存，但通常不会进入
+内化。
 
 ## 在 OpenClaw 会话中（首选）
 
@@ -32,6 +33,9 @@ pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --s
 
 - `--session <id>` 会先对工作区轨迹做校验：会话不存在时以
   `session_not_found` 失败，不会写入任何内容。
+- `--session` 验证通过但轨迹证据为空或不可读（会话真实存在）时，记录按
+  bound + 证据不可用诚实降级提交：不伪造证据，由 admission gate 评判空
+  证据的价值，而不是直接拒绝。
 - 不带 `--session` 的记录是允许的 unbound Owner 报告，但不附带证据，
   候选大概率被 admission gate 拦为 `needs_evidence` —— CLI 输出会明确
   提示这一点。
@@ -53,6 +57,8 @@ pd runtime flow show --workspace "<workspace>" --json
 ```
 
 成功标准是候选被**准入**（admitted），而不只是被生成：检查
-`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。
-`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若全部候选被拦截，
+`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。命令成功
+返回 `painId` 只代表记录回执，不代表诊断或准入成功。
+`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若候选被拦截，
 请用 `/pd-pain` 或 `--session` 重新记录，让诊断携带真实轨迹证据。
+激活（activation）是 Owner 批准之后的独立阶段，本流程不会直接产生激活。

package/templates/langs/zh/skills/pd-runtime-v2/SKILL.md

@@ -21,7 +21,9 @@ disable-model-invocation: false
 pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 `--session` 把报告绑定到已记录的会话（先校验），让诊断携带真实轨迹
-证据；不带它则是无证据的 unbound Owner 报告，候选大概率被拦。
+证据；会话验证通过但轨迹证据为空或不可读时，按 bound + 证据不可用诚实
+降级提交，由 admission gate 评判；不带 `--session` 则是无证据的 unbound
+Owner 报告（合法），候选大概率被拦。
 
 禁止入口：
 - 不要写 `.state/.pain_flag`。
@@ -58,16 +60,22 @@ pd candidate show --candidate-id "<candidateId>" --workspace "<workspace>" --jso
 
 ## 成功标准
 
+一条痛苦的完整链路分四个阶段：记录回执（`painId`）→ 诊断（产出候选）→
+准入（`admitted`，进入 ledger）→ Owner 批准与激活（activation）。
+
 一次诊断只有在同时满足以下条件时才算成功：
 - `status` 是 `succeeded`
 - `candidateIds` 非空
-- `ledgerEntryIds` 非空
+- `admissionResults` 中出现 `admitted` 决策，且对应 `ledgerEntryIds` 非空
 
-只创建 task 不算成功。没有 candidate 或 ledger entry 的 run 是失败、重试或未完成。
+只创建 task、只生成候选或只有 ledger entry 都不算成功——没有 `admitted`
+决策的候选并未被准入。激活是 Owner 决策之后的独立阶段，`pd pain record`
+不会直接产生激活。
 
 ## 需要手动诊断时
 
 1. 使用 `pd pain record`。
 2. 检查 JSON 输出。
-3. 如果 `candidateIds` 或 `ledgerEntryIds` 为空，视为未完成。
+3. 如果 `candidateIds` 或 `ledgerEntryIds` 为空，或候选被拦为
+   `needs_evidence` / `deferred`，视为未完成（未内化）。
 4. 用 `pd candidate list/show` 和 `pd runtime flow show` 继续排查。