devrites 6.3.0 → 6.4.1

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [6.4.1](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.0...v6.4.1) (2026-10-16)
+
+### Fixed
+
+* **devrites:** never message a running read-only leaf ([#115](https://github.com/ViktorsBaikers/DevRites/issues/115)) ([bd0428b](https://github.com/ViktorsBaikers/DevRites/commit/bd0428bd7bdce9c604198a1f8baf809df7e863cf))
+
+## [6.4.0](https://github.com/ViktorsBaikers/DevRites/compare/v6.3.0...v6.4.0) (2026-10-16)
+
+### Added
+
+* **devrites:** let Satisfies: none slices stay deferred ([#114](https://github.com/ViktorsBaikers/DevRites/issues/114)) ([d5bf85a](https://github.com/ViktorsBaikers/DevRites/commit/d5bf85a926f856625131ba297679f5db4d6be909))
+
 ## [6.3.0](https://github.com/ViktorsBaikers/DevRites/compare/v6.2.0...v6.3.0) (2026-10-16)
 
 ### Added

package/README.md

@@ -31,7 +31,7 @@ history can't lose it. After you clear the conversation, switch hosts, or hand
 the feature to another engineer, the next session reads the same plan,
 decisions, and evidence before it continues.
 
-**Status:** [`v6.3.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.3.0): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v6.4.1`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.4.1): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 

package/pack/.claude/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/.claude/skills/rite-autocomplete/reference/loop.md

@@ -66,7 +66,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `/rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
 | 10 | `/rite-seal` | GO/NO-GO; no Git |

package/pack/.claude/skills/rite-build/SKILL.md

@@ -110,7 +110,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](../rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/.claude/skills/rite-define/SKILL.md

@@ -131,7 +131,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](../rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/.claude/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/.claude/skills/rite-prove/SKILL.md

@@ -64,7 +64,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/.claude/skills/rite-vet/reference/artifacts.md

@@ -138,8 +138,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](../../rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/pack/generated/claude/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/claude/skills/rite-autocomplete/reference/loop.md

@@ -68,7 +68,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `/rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
 | 10 | `/rite-seal` | GO/NO-GO; no Git |

package/pack/generated/claude/skills/rite-build/SKILL.md

@@ -110,7 +110,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](../rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/generated/claude/skills/rite-define/SKILL.md

@@ -131,7 +131,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](../rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/generated/claude/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/generated/claude/skills/rite-prove/SKILL.md

@@ -64,7 +64,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/generated/claude/skills/rite-vet/reference/artifacts.md

@@ -140,8 +140,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](../../rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/pack/generated/codex/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is $rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/codex/skills/rite-autocomplete/reference/loop.md

@@ -68,7 +68,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `$rite-define` | approved plan/tasks/traceability |
 | 5 | `$rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `$rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `$rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `$rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `$rite-polish` | re-prove after code edits |
 | 9 | `$rite-review` | in-scope correction then fresh proof |
 | 10 | `$rite-seal` | GO/NO-GO; no Git |

package/pack/generated/codex/skills/rite-build/SKILL.md

@@ -110,7 +110,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](../rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/generated/codex/skills/rite-define/SKILL.md

@@ -131,7 +131,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](../rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/generated/codex/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/generated/codex/skills/rite-prove/SKILL.md

@@ -64,7 +64,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/generated/codex/skills/rite-vet/reference/artifacts.md

@@ -140,8 +140,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](../../rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/pack/generated/devin/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/devin/skills/rite-autocomplete/reference/loop.md

@@ -68,7 +68,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `/rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
 | 10 | `/rite-seal` | GO/NO-GO; no Git |

package/pack/generated/devin/skills/rite-build/SKILL.md

@@ -109,7 +109,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](../rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/generated/devin/skills/rite-define/SKILL.md

@@ -130,7 +130,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](../rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/generated/devin/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/generated/devin/skills/rite-prove/SKILL.md

@@ -63,7 +63,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/generated/devin/skills/rite-vet/reference/artifacts.md

@@ -140,8 +140,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](../../rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/pack/generated/omp/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/omp/skills/rite-autocomplete/reference/loop.md

@@ -68,7 +68,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `/rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
 | 10 | `/rite-seal` | GO/NO-GO; no Git |

package/pack/generated/omp/skills/rite-build/SKILL.md

@@ -110,7 +110,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](skill://devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](skill://rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/generated/omp/skills/rite-define/SKILL.md

@@ -131,7 +131,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](skill://rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](skill://rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](skill://rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/generated/omp/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/generated/omp/skills/rite-prove/SKILL.md

@@ -64,7 +64,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](skill://rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/generated/omp/skills/rite-vet/reference/artifacts.md

@@ -140,8 +140,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](skill://rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/pack/generated/pi/skills/devrites-lib/reference/standards/agents.md

@@ -83,6 +83,9 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 ## Independence
 
 - A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet. Canonical workspace artifacts in the engine-generated `--role` read-set (state cursor, decisions, `strategy.md` scores, prior review records) are inputs, not seeding: a verdict they record is a historical claim the reviewer re-verifies, never this pass's conclusion. The same holds for status, readiness-checklist, or gate lines inside a read-set artifact (e.g. a `spec.md` `Status:`/`Spec gate:` line from an older workspace). Never hand-edit installed read-sets or swap them for excerpts to strip that history.
+- Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
+  Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
+  leaf gap it would close (e.g. "no independent runtime run") closes there.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/pi/skills/rite-autocomplete/reference/loop.md

@@ -68,7 +68,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
 | 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); refill per landing; charge once per landed slice |
-| 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
+| 7 | `/rite-prove` | all slices built except deferred (`Satisfies: none`); approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
 | 10 | `/rite-seal` | GO/NO-GO; no Git |

package/pack/generated/pi/skills/rite-build/SKILL.md

@@ -110,7 +110,8 @@ or canonical transaction, return inspection, independent code/doubt/test analysi
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
 [`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
-the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
+the next slice automatically; AFK obeys remaining budget; Prove requires every slice built except a
+[deferred slice](../rite-plan/reference/slicing.md#deferred-slice).
 
 ## Phase exit
 

package/pack/generated/pi/skills/rite-define/SKILL.md

@@ -131,7 +131,7 @@ Pull these via `Read` when shaping the plan:
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
    ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
-   criterion. Every proof row quotes the spec line it proves (`Proves`); proof that proves
+   criterion except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Every proof row quotes the spec line it proves (`Proves`); proof that proves
    none goes to `test-plan.md` `## Deferred hardening`, never into a slice
    ([artifacts.md](../rite-vet/reference/artifacts.md)). Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each

package/pack/generated/pi/skills/rite-plan/reference/slicing.md

@@ -173,3 +173,10 @@ Slices sharing a file never build side by side: put a hub file's shared edit
 (registry, command table, test harness) in one seam slice the others depend on.
 `check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
 writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.
+
+## Deferred slice
+A slice with `Satisfies: none` is an optional follow-up: plan-invented hardening or
+owner-moved scope kept with its preserved source and contracts. It carries no acceptance
+(every AC still maps to a required slice), is never dispatched (`check slice` refuses
+it), and never counts toward "all slices built", Prove, or Seal. The owner elects it
+later through a plan change that gives it an AC.

package/pack/generated/pi/skills/rite-prove/SKILL.md

@@ -64,7 +64,7 @@ test changes.
    and no-progress corrections before accepting terminal none; a distinct
    fingerprint below cap resumes offline triage without another real action.
 2. **Freeze scope.** Read spec, tasks, state, test plan, and full diff. Require
-   every slice built. Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
+   every slice built except a [deferred slice](../rite-plan/reference/slicing.md#deferred-slice). Missing `test-plan.md` returns to Vet inline (Prove stays the controlling
    caller) and resumes here; it never authorizes ad hoc proof.
 3. **Approve commands.** If absent, use
    [test-command-discovery](reference/test-command-discovery.md) over repository

package/pack/generated/pi/skills/rite-vet/reference/artifacts.md

@@ -140,8 +140,9 @@ none is plan-invented hardening: move it to `Deferred hardening`.
 |---|---|---|---|
 | D1 | <proof or mechanism> | <reason> | <the spec line an owner would add> |
 
-Deferred rows are an optional follow-up slice: not built, proven, or gating in this
-feature; this table is their follow-up record. Nothing is deleted.
+Deferred rows, like a [deferred slice](../../rite-plan/reference/slicing.md#deferred-slice),
+are not built, proven, or gating in this feature; this table is their follow-up record.
+Nothing is deleted.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.3.0",
+  "version": "6.4.1",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, pi, and Devin CLI",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",