devrites 6.1.5 → 6.3.0

package/pack/generated/claude/skills/rite-build/reference/wright-dispatch.md

@@ -94,10 +94,14 @@ claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then r
 live foreign session releases the retained claim and stops the dispatch, per
 [`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
 is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
-Ask the host
-for the exact writer in fresh context and wait. Track it through the
-launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
-<slice-id> --role slice-wright --slice <SLICE-ID>`, then `start` with the host handle, `seal`, and
+Write the exact contract, with its `Writer-safe checks:` line, to
+`packets/<wave>.contract.md` and hand the wright that text verbatim. Ask the host
+for the exact writer in fresh context; a repair round on the same slice whose
+returned wright the host can still continue goes to that wright on its existing
+handle instead, so it does not re-read the slice from scratch. Wait, and track it
+through the launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
+<slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
+contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
 rounds on one slice, `open` blocks for a reslice review: propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per

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

@@ -131,7 +131,9 @@ 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. Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
+   criterion. 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
    `Existing behavior to preserve` row becomes a regression row whose current evidence is
    observed green on the unchanged baseline as a prerequisite of the first slice touching that

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

@@ -209,7 +209,9 @@ plan declares a root-authored executable workflow file, read
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
    must pass. Record the per-input drift baseline alongside it:
    `devrites-engine check drift <slug> --record` — a later stale binding then
-   names the exact artifact that moved instead of "something changed". Technical failure records reproduction, not qid. Human gap awaits
+   names the exact artifact that moved instead of "something changed". An `ADVISORY
+   proportion:` line names a slice whose proof outgrew its ACs: move its rows without a
+   `Proves` spec line to `Deferred hardening` before READY, never deepen them. Technical failure records reproduction, not qid. Human gap awaits
    Clarify. Optional cross-model follows `reference/cross-model.md` (trigger `cross-model`).
 
    With READY, no pending remediation, and a valid technical return cursor,

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

@@ -128,9 +128,20 @@ prove only their named static criterion.
 <the ASCII code-paths + user-flows diagram from review-axes.md, with COVERAGE / GAPS / REGRESSIONS line>
 
 ## Per-gap test requirements
-| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority |
-|---|---|---|---|---|---|---|
-| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** |
+| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority | Proves |
+|---|---|---|---|---|---|---|---|
+| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** | <AC/REQ/INV/PROH/DEC/EDGE ID or standard § + quoted line> |
+
+Every row's `Proves` quotes the spec line or standard rule it proves. A row that proves
+none is plan-invented hardening: move it to `Deferred hardening`.
+
+## Deferred hardening
+| ID | Hardening | Why no spec line needs it | Promote by |
+|---|---|---|---|
+| 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.
 
 ## 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/agents/devrites-code-reviewer.toml

@@ -159,7 +159,7 @@ Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <files read fully | hunk-level | skipped: name — reason>
-Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Contract: <applicable | not-applicable> — <basis: both sides read · crossing test>
 Tests: <adequate? gaps>

package/pack/generated/codex/agents/devrites-plan-drafter.toml

@@ -21,7 +21,9 @@ seams supplied by the orchestrator.
 Reuse existing seams and dependencies before proposing new ones. Build vertical
 slices in dependency order; put a hub file's shared edit in one seam slice
 ([slicing.md](.agents/skills/rite-plan/reference/slicing.md#slice-independence)). Map every REQ and AC to a slice and executable proof,
-name rollback and failure paths; keep acceptance-changing proposals separate. Durable
+name rollback and failure paths; keep acceptance-changing proposals separate. Each proof
+row quotes the spec line or standard rule it proves (`Proves`); proof that proves none
+goes to `test-plan.md` `## Deferred hardening`, never into a slice. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
 Reconcile `spec.md`'s applicability map against live evidence. When triggered, apply

package/pack/generated/codex/agents/devrites-plan-reviewer.toml

@@ -116,7 +116,10 @@ criterion, slice, or proof.
   `convergence_pressure` eligibility mechanical. Tag every Critical/Important
   `kind: contract` (an implementer could build it differently and still pass the
   planned tests) or `kind: mechanism` (a named test can discriminate the wrong
-  implementation; propose that case as the fix, not new plan prose).
+  implementation; propose that case as the fix, not new plan prose). Each
+  Critical/Important also quotes the spec line (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`)
+  or standard rule it breaks; hardening no spec line asks for is a Suggestion
+  ([agents.md](.agents/skills/devrites-lib/reference/standards/agents.md) § Result admission, Proportionality).
 - In a recheck, your verdict covers the listed fingerprints, the correction diff, and
   the dependents of each changed clause. Return an explicit correction-created
   regression verdict over the touched invariants and those dependents as

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

@@ -98,7 +98,7 @@ Each required reviewer/analyst/auditor starts with exactly one:
 ```text
 Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
-Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 ```
 
@@ -108,6 +108,13 @@ Basis: <files read · commands run to reach this finding>
   A Critical/Important row carries `conf <n>` in its severity cell and writes impact
   as `when <input/state/sequence> → <effect>`; missing either, root admits it as
   `Unverified: <claim> — missing trigger` (stays `gap`).
+- **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
+  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
+  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
+  quote like the `file:line` quote. No anchor, or one the defect does not break,
+  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
+  optional follow-up slice; it never drives a repair round. Hardening no spec line
+  asks for is a Suggestion, however plausible.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -112,6 +112,10 @@ armed AFK workspace whose exact scope, gates, and budgets permit it.
   run `devrites-engine check drift <slug>` before re-vetting: it names the
   exact input artifact that changed (or `missing`/`added`) since the recorded
   baseline, so the Spec Drift Guard or `$rite-vet` starts at the right file.
+- `check drift` and `check slice` print `ADVISORY proportion:` when a slice's proof
+  grew over 2x since the Vet baseline or carries over 3x the median proof per AC.
+  Repair by moving rows without a `Proves` spec line to `Deferred hardening`
+  ([agents.md](agents.md) § Result admission, Proportionality), not by adding proof.
 - Native notifications fire only after evidence and stop state are written.
 
 Use [`afk-hitl.md`](afk-hitl.md) for unattended authority and resource budgets,

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

@@ -29,8 +29,8 @@ Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
 Every wright contract names the writer-safe checks the wright runs (syntax/type/lint,
 unit and self-check suites, a narrow local smoke) and never forbids them; only
-artifact-producing, consumptive, or full canonical gates stay root-owned.
-Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
+artifact-producing, consumptive, or full canonical gates stay root-owned;
+`dispatch open --contract` refuses a contract that breaks this. Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
 contract says "skip tests mid-flight; root runs them after return", and the wright
 returns three unit failures that a 20 s `go test` would have caught in-round.
 

package/pack/generated/codex/skills/rite-build/reference/one-slice-cycle.md

@@ -23,7 +23,9 @@ DISPATCH  → hand the slice contract to devrites-slice-wright (fresh context).
             (independent claims, fresh contexts); wright fixes stay serial — writers share files
 PROVE     → root, concurrent with the reviews on the same frozen candidate:
             required build/browser/E2E (narrow self-check/smoke first, full gate only
-            after it is green, long runs in the background), then returned-diff/path recheck; fail-on-red
+            after it is green, long runs in the background; cancel one still running once
+            review or proof sends the candidate back, keeping its partial output as
+            diagnostics), then returned-diff/path recheck; fail-on-red
             (red/gap → repair wright, then re-review and re-prove; do not commit yet)
 RECORD    → orchestrator: after green verification, update state.md/evidence.md and
             upsert the authoritative candidate manifest from the actual scoped diff

package/pack/generated/codex/skills/rite-build/reference/wright-dispatch.md

@@ -94,10 +94,14 @@ claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then r
 live foreign session releases the retained claim and stops the dispatch, per
 [`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
 is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
-Ask the host
-for the exact writer in fresh context and wait. Track it through the
-launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
-<slice-id> --role slice-wright --slice <SLICE-ID>`, then `start` with the host handle, `seal`, and
+Write the exact contract, with its `Writer-safe checks:` line, to
+`packets/<wave>.contract.md` and hand the wright that text verbatim. Ask the host
+for the exact writer in fresh context; a repair round on the same slice whose
+returned wright the host can still continue goes to that wright on its existing
+handle instead, so it does not re-read the slice from scratch. Wait, and track it
+through the launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
+<slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
+contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
 rounds on one slice, `open` blocks for a reslice review: propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per

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

@@ -131,7 +131,9 @@ 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. Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
+   criterion. 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
    `Existing behavior to preserve` row becomes a regression row whose current evidence is
    observed green on the unchanged baseline as a prerequisite of the first slice touching that

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

@@ -209,7 +209,9 @@ plan declares a root-authored executable workflow file, read
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
    must pass. Record the per-input drift baseline alongside it:
    `devrites-engine check drift <slug> --record` — a later stale binding then
-   names the exact artifact that moved instead of "something changed". Technical failure records reproduction, not qid. Human gap awaits
+   names the exact artifact that moved instead of "something changed". An `ADVISORY
+   proportion:` line names a slice whose proof outgrew its ACs: move its rows without a
+   `Proves` spec line to `Deferred hardening` before READY, never deepen them. Technical failure records reproduction, not qid. Human gap awaits
    Clarify. Optional cross-model follows `reference/cross-model.md` (trigger `cross-model`).
 
    With READY, no pending remediation, and a valid technical return cursor,

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

@@ -128,9 +128,20 @@ prove only their named static criterion.
 <the ASCII code-paths + user-flows diagram from review-axes.md, with COVERAGE / GAPS / REGRESSIONS line>
 
 ## Per-gap test requirements
-| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority |
-|---|---|---|---|---|---|---|
-| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** |
+| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority | Proves |
+|---|---|---|---|---|---|---|---|
+| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** | <AC/REQ/INV/PROH/DEC/EDGE ID or standard § + quoted line> |
+
+Every row's `Proves` quotes the spec line or standard rule it proves. A row that proves
+none is plan-invented hardening: move it to `Deferred hardening`.
+
+## Deferred hardening
+| ID | Hardening | Why no spec line needs it | Promote by |
+|---|---|---|---|
+| 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.
 
 ## 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/agents/devrites-code-reviewer.md

@@ -163,7 +163,7 @@ Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <files read fully | hunk-level | skipped: name — reason>
-Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Contract: <applicable | not-applicable> — <basis: both sides read · crossing test>
 Tests: <adequate? gaps>

package/pack/generated/devin/agents/devrites-plan-drafter.md

@@ -26,7 +26,9 @@ seams supplied by the orchestrator.
 Reuse existing seams and dependencies before proposing new ones. Build vertical
 slices in dependency order; put a hub file's shared edit in one seam slice
 ([slicing.md](../skills/rite-plan/reference/slicing.md#slice-independence)). Map every REQ and AC to a slice and executable proof,
-name rollback and failure paths; keep acceptance-changing proposals separate. Durable
+name rollback and failure paths; keep acceptance-changing proposals separate. Each proof
+row quotes the spec line or standard rule it proves (`Proves`); proof that proves none
+goes to `test-plan.md` `## Deferred hardening`, never into a slice. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
 Reconcile `spec.md`'s applicability map against live evidence. When triggered, apply

package/pack/generated/devin/agents/devrites-plan-reviewer.md

@@ -120,7 +120,10 @@ criterion, slice, or proof.
   `convergence_pressure` eligibility mechanical. Tag every Critical/Important
   `kind: contract` (an implementer could build it differently and still pass the
   planned tests) or `kind: mechanism` (a named test can discriminate the wrong
-  implementation; propose that case as the fix, not new plan prose).
+  implementation; propose that case as the fix, not new plan prose). Each
+  Critical/Important also quotes the spec line (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`)
+  or standard rule it breaks; hardening no spec line asks for is a Suggestion
+  ([agents.md](../skills/devrites-lib/reference/standards/agents.md) § Result admission, Proportionality).
 - In a recheck, your verdict covers the listed fingerprints, the correction diff, and
   the dependents of each changed clause. Return an explicit correction-created
   regression verdict over the touched invariants and those dependents as

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

@@ -98,7 +98,7 @@ Each required reviewer/analyst/auditor starts with exactly one:
 ```text
 Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
-Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 ```
 
@@ -108,6 +108,13 @@ Basis: <files read · commands run to reach this finding>
   A Critical/Important row carries `conf <n>` in its severity cell and writes impact
   as `when <input/state/sequence> → <effect>`; missing either, root admits it as
   `Unverified: <claim> — missing trigger` (stays `gap`).
+- **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
+  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
+  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
+  quote like the `file:line` quote. No anchor, or one the defect does not break,
+  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
+  optional follow-up slice; it never drives a repair round. Hardening no spec line
+  asks for is a Suggestion, however plausible.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -112,6 +112,10 @@ armed AFK workspace whose exact scope, gates, and budgets permit it.
   run `devrites-engine check drift <slug>` before re-vetting: it names the
   exact input artifact that changed (or `missing`/`added`) since the recorded
   baseline, so the Spec Drift Guard or `/rite-vet` starts at the right file.
+- `check drift` and `check slice` print `ADVISORY proportion:` when a slice's proof
+  grew over 2x since the Vet baseline or carries over 3x the median proof per AC.
+  Repair by moving rows without a `Proves` spec line to `Deferred hardening`
+  ([agents.md](agents.md) § Result admission, Proportionality), not by adding proof.
 - Native notifications fire only after evidence and stop state are written.
 
 Use [`afk-hitl.md`](afk-hitl.md) for unattended authority and resource budgets,

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

@@ -28,8 +28,8 @@ Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
 Every wright contract names the writer-safe checks the wright runs (syntax/type/lint,
 unit and self-check suites, a narrow local smoke) and never forbids them; only
-artifact-producing, consumptive, or full canonical gates stay root-owned.
-Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
+artifact-producing, consumptive, or full canonical gates stay root-owned;
+`dispatch open --contract` refuses a contract that breaks this. Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
 contract says "skip tests mid-flight; root runs them after return", and the wright
 returns three unit failures that a 20 s `go test` would have caught in-round.
 

package/pack/generated/devin/skills/rite-build/reference/one-slice-cycle.md

@@ -23,7 +23,9 @@ DISPATCH  → hand the slice contract to devrites-slice-wright (fresh context).
             (independent claims, fresh contexts); wright fixes stay serial — writers share files
 PROVE     → root, concurrent with the reviews on the same frozen candidate:
             required build/browser/E2E (narrow self-check/smoke first, full gate only
-            after it is green, long runs in the background), then returned-diff/path recheck; fail-on-red
+            after it is green, long runs in the background; cancel one still running once
+            review or proof sends the candidate back, keeping its partial output as
+            diagnostics), then returned-diff/path recheck; fail-on-red
             (red/gap → repair wright, then re-review and re-prove; do not commit yet)
 RECORD    → orchestrator: after green verification, update state.md/evidence.md and
             upsert the authoritative candidate manifest from the actual scoped diff

package/pack/generated/devin/skills/rite-build/reference/wright-dispatch.md

@@ -94,10 +94,14 @@ claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then r
 live foreign session releases the retained claim and stops the dispatch, per
 [`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
 is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
-Ask the host
-for the exact writer in fresh context and wait. Track it through the
-launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
-<slice-id> --role slice-wright --slice <SLICE-ID>`, then `start` with the host handle, `seal`, and
+Write the exact contract, with its `Writer-safe checks:` line, to
+`packets/<wave>.contract.md` and hand the wright that text verbatim. Ask the host
+for the exact writer in fresh context; a repair round on the same slice whose
+returned wright the host can still continue goes to that wright on its existing
+handle instead, so it does not re-read the slice from scratch. Wait, and track it
+through the launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
+<slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
+contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
 rounds on one slice, `open` blocks for a reslice review: propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per

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

@@ -130,7 +130,9 @@ 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. Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
+   criterion. 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
    `Existing behavior to preserve` row becomes a regression row whose current evidence is
    observed green on the unchanged baseline as a prerequisite of the first slice touching that

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

@@ -208,7 +208,9 @@ plan declares a root-authored executable workflow file, read
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
    must pass. Record the per-input drift baseline alongside it:
    `devrites-engine check drift <slug> --record` — a later stale binding then
-   names the exact artifact that moved instead of "something changed". Technical failure records reproduction, not qid. Human gap awaits
+   names the exact artifact that moved instead of "something changed". An `ADVISORY
+   proportion:` line names a slice whose proof outgrew its ACs: move its rows without a
+   `Proves` spec line to `Deferred hardening` before READY, never deepen them. Technical failure records reproduction, not qid. Human gap awaits
    Clarify. Optional cross-model follows `reference/cross-model.md` (trigger `cross-model`).
 
    With READY, no pending remediation, and a valid technical return cursor,

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

@@ -128,9 +128,20 @@ prove only their named static criterion.
 <the ASCII code-paths + user-flows diagram from review-axes.md, with COVERAGE / GAPS / REGRESSIONS line>
 
 ## Per-gap test requirements
-| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority |
-|---|---|---|---|---|---|---|
-| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** |
+| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority | Proves |
+|---|---|---|---|---|---|---|---|
+| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** | <AC/REQ/INV/PROH/DEC/EDGE ID or standard § + quoted line> |
+
+Every row's `Proves` quotes the spec line or standard rule it proves. A row that proves
+none is plan-invented hardening: move it to `Deferred hardening`.
+
+## Deferred hardening
+| ID | Hardening | Why no spec line needs it | Promote by |
+|---|---|---|---|
+| 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.
 
 ## 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/agents/devrites-code-reviewer.md

@@ -159,7 +159,7 @@ Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <files read fully | hunk-level | skipped: name — reason>
-Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Contract: <applicable | not-applicable> — <basis: both sides read · crossing test>
 Tests: <adequate? gaps>

package/pack/generated/omp/agents/devrites-plan-drafter.md

@@ -22,7 +22,9 @@ seams supplied by the orchestrator.
 Reuse existing seams and dependencies before proposing new ones. Build vertical
 slices in dependency order; put a hub file's shared edit in one seam slice
 ([slicing.md](skill://rite-plan/reference/slicing.md#slice-independence)). Map every REQ and AC to a slice and executable proof,
-name rollback and failure paths; keep acceptance-changing proposals separate. Durable
+name rollback and failure paths; keep acceptance-changing proposals separate. Each proof
+row quotes the spec line or standard rule it proves (`Proves`); proof that proves none
+goes to `test-plan.md` `## Deferred hardening`, never into a slice. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
 Reconcile `spec.md`'s applicability map against live evidence. When triggered, apply

package/pack/generated/omp/agents/devrites-plan-reviewer.md

@@ -117,7 +117,10 @@ criterion, slice, or proof.
   `convergence_pressure` eligibility mechanical. Tag every Critical/Important
   `kind: contract` (an implementer could build it differently and still pass the
   planned tests) or `kind: mechanism` (a named test can discriminate the wrong
-  implementation; propose that case as the fix, not new plan prose).
+  implementation; propose that case as the fix, not new plan prose). Each
+  Critical/Important also quotes the spec line (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`)
+  or standard rule it breaks; hardening no spec line asks for is a Suggestion
+  ([agents.md](skill://devrites-lib/reference/standards/agents.md) § Result admission, Proportionality).
 - In a recheck, your verdict covers the listed fingerprints, the correction diff, and
   the dependents of each changed clause. Return an explicit correction-created
   regression verdict over the touched invariants and those dependents as

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

@@ -98,7 +98,7 @@ Each required reviewer/analyst/auditor starts with exactly one:
 ```text
 Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
-Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 ```
 
@@ -108,6 +108,13 @@ Basis: <files read · commands run to reach this finding>
   A Critical/Important row carries `conf <n>` in its severity cell and writes impact
   as `when <input/state/sequence> → <effect>`; missing either, root admits it as
   `Unverified: <claim> — missing trigger` (stays `gap`).
+- **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
+  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
+  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
+  quote like the `file:line` quote. No anchor, or one the defect does not break,
+  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
+  optional follow-up slice; it never drives a repair round. Hardening no spec line
+  asks for is a Suggestion, however plausible.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -112,6 +112,10 @@ armed AFK workspace whose exact scope, gates, and budgets permit it.
   run `devrites-engine check drift <slug>` before re-vetting: it names the
   exact input artifact that changed (or `missing`/`added`) since the recorded
   baseline, so the Spec Drift Guard or `/rite-vet` starts at the right file.
+- `check drift` and `check slice` print `ADVISORY proportion:` when a slice's proof
+  grew over 2x since the Vet baseline or carries over 3x the median proof per AC.
+  Repair by moving rows without a `Proves` spec line to `Deferred hardening`
+  ([agents.md](agents.md) § Result admission, Proportionality), not by adding proof.
 - Native notifications fire only after evidence and stop state are written.
 
 Use [`afk-hitl.md`](afk-hitl.md) for unattended authority and resource budgets,

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

@@ -29,8 +29,8 @@ Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
 Every wright contract names the writer-safe checks the wright runs (syntax/type/lint,
 unit and self-check suites, a narrow local smoke) and never forbids them; only
-artifact-producing, consumptive, or full canonical gates stay root-owned.
-Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
+artifact-producing, consumptive, or full canonical gates stay root-owned;
+`dispatch open --contract` refuses a contract that breaks this. Prior contracts in `evidence.md` are not a template for this. **Failing case:** the
 contract says "skip tests mid-flight; root runs them after return", and the wright
 returns three unit failures that a 20 s `go test` would have caught in-round.
 

package/pack/generated/omp/skills/rite-build/reference/one-slice-cycle.md

@@ -23,7 +23,9 @@ DISPATCH  → hand the slice contract to devrites-slice-wright (fresh context).
             (independent claims, fresh contexts); wright fixes stay serial — writers share files
 PROVE     → root, concurrent with the reviews on the same frozen candidate:
             required build/browser/E2E (narrow self-check/smoke first, full gate only
-            after it is green, long runs in the background), then returned-diff/path recheck; fail-on-red
+            after it is green, long runs in the background; cancel one still running once
+            review or proof sends the candidate back, keeping its partial output as
+            diagnostics), then returned-diff/path recheck; fail-on-red
             (red/gap → repair wright, then re-review and re-prove; do not commit yet)
 RECORD    → orchestrator: after green verification, update state.md/evidence.md and
             upsert the authoritative candidate manifest from the actual scoped diff

package/pack/generated/omp/skills/rite-build/reference/wright-dispatch.md

@@ -94,10 +94,14 @@ claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then r
 live foreign session releases the retained claim and stops the dispatch, per
 [`agents.md`](skill://devrites-lib/reference/standards/agents.md). `.devrites/**`
 is never a task path; see [Workflow Artifact admission](skill://devrites-lib/reference/standards/workflow-artifacts.md).
-Ask the host
-for the exact writer in fresh context and wait. Track it through the
-launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
-<slice-id> --role slice-wright --slice <SLICE-ID>`, then `start` with the host handle, `seal`, and
+Write the exact contract, with its `Writer-safe checks:` line, to
+`packets/<wave>.contract.md` and hand the wright that text verbatim. Ask the host
+for the exact writer in fresh context; a repair round on the same slice whose
+returned wright the host can still continue goes to that wright on its existing
+handle instead, so it does not re-read the slice from scratch. Wait, and track it
+through the launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
+<slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
+contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
 rounds on one slice, `open` blocks for a reslice review: propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per

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

@@ -131,7 +131,9 @@ 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. Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
+   criterion. 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
    `Existing behavior to preserve` row becomes a regression row whose current evidence is
    observed green on the unchanged baseline as a prerequisite of the first slice touching that

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

@@ -209,7 +209,9 @@ plan declares a root-authored executable workflow file, read
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
    must pass. Record the per-input drift baseline alongside it:
    `devrites-engine check drift <slug> --record` — a later stale binding then
-   names the exact artifact that moved instead of "something changed". Technical failure records reproduction, not qid. Human gap awaits
+   names the exact artifact that moved instead of "something changed". An `ADVISORY
+   proportion:` line names a slice whose proof outgrew its ACs: move its rows without a
+   `Proves` spec line to `Deferred hardening` before READY, never deepen them. Technical failure records reproduction, not qid. Human gap awaits
    Clarify. Optional cross-model follows `reference/cross-model.md` (trigger `cross-model`).
 
    With READY, no pending remediation, and a valid technical return cursor,

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

@@ -128,9 +128,20 @@ prove only their named static criterion.
 <the ASCII code-paths + user-flows diagram from review-axes.md, with COVERAGE / GAPS / REGRESSIONS line>
 
 ## Per-gap test requirements
-| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority |
-|---|---|---|---|---|---|---|
-| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** |
+| ID | Path / flow | Test file (match conventions) | Asserts (input → expected) | Kind | Slice | Priority | Proves |
+|---|---|---|---|---|---|---|---|
+| T1 | <path> | <path/to.test> | <empty list → 200 + []> | unit / E2E / eval | <slice> | P1 / **Regression-Critical** | <AC/REQ/INV/PROH/DEC/EDGE ID or standard § + quoted line> |
+
+Every row's `Proves` quotes the spec line or standard rule it proves. A row that proves
+none is plan-invented hardening: move it to `Deferred hardening`.
+
+## Deferred hardening
+| ID | Hardening | Why no spec line needs it | Promote by |
+|---|---|---|---|
+| 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.
 
 ## 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/agents/devrites-code-reviewer.md

@@ -160,7 +160,7 @@ Outcome: <findings | no-findings | gap>
 Counts: <n per severity or kind used in the rows below>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <files read fully | hunk-level | skipped: name — reason>
-Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | <minimum fix>
+Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Contract: <applicable | not-applicable> — <basis: both sides read · crossing test>
 Tests: <adequate? gaps>