devrites 4.1.0 → 4.2.0

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

@@ -1,131 +1,92 @@
-# Stop conditions: when autocomplete must pause for a human
-
-On these conditions, write `state.md` (`awaiting_human` or `blocked`), report
-the reason and one resume command when an actual human/safety/access action can
-change the state, notify if configured, and stop. Exhausted agent-owned
-technical recovery is terminal for its unchanged causal fingerprint: record
-`Next step: none` and no runnable recovery command. `--ship` cannot bypass them.
-Closure of a prior fingerprint is progress, not exhaustion. A separately evidenced
-Critical/Important failed invariant starts its own bounded fingerprint; it never
-resets or extends the budget of the one just closed.
-
-An exhausted consumptive-action authorization is not technical-recovery
-exhaustion. It blocks another real action, but retained evidence of a new
-Critical/Important fingerprint must enter offline caller-owned recovery while its
-own no-progress budget remains. After affected Vet is READY, pause for fresh action
-authorization; never execute from the old GO.
-
-## Always stop (irreversible-risk list: from `afk-hitl.md`)
-
-Regardless of `allow_gates` or `--ship`:
-- Destructive data migration (drop column/table, irreversible backfill).
-- Auth / authz boundary change.
-- Public-API break (response shape, removed endpoint, changed status semantics).
-- External-service contract change.
-- Filesystem destruction outside the workspace.
-
-Red checks are hard non-advance gates. Run bounded `devrites-debug-recovery`;
-on exhaustion, stop as a technical blocker unless human-owned.
-
-## Not a stop: agent-owned backtracking
-
-`NEEDS_REPLAN` is not a stop condition under an active Autocomplete caller. It
-blocks forward advancement, persists the return cursor, and immediately routes
-Plan repair plus Recovery Vet. The same applies to any intermediate nested
-`STOP`/`Next step` whose underlying decision is agent-owned.
-
-Agent-owned backtracking is not a stop condition while its causal-fingerprint
-budget remains. The active caller invokes the earlier phase inline, follows Vet
-and any bounded remediation, then resumes the originating phase. Persist
-`Next step` for crash recovery, but do not surface it as a command the human must
-submit. Use the repaired finding's narrow Vet recheck to distinguish resolution,
-the same decisive failure, and a genuinely new Critical/Important invariant.
-Stop only after three no-progress attempts on the exact same fingerprint or when
-the remaining choice is a real human/safety/access gate.
-
-On technical exhaustion, preserve the fingerprint, reproduction, attempts, and
-dead ends, then stop without `$rite-plan unblock` or another phase command.
-Reinvocation with unchanged evidence remains blocked and does not reset the cap.
-Here `unchanged` means the same fingerprint already has three recorded
-no-progress corrections. A retained fingerprint with remaining offline budget is
-not terminal merely because `state.md` was written by the failed action or a prior
-session ended.
-
-A pre-ownership workflow-artifact writer stop is not unchanged evidence when the
-current contract supplies controlling-root materialization. Prior drafter/wright refusals do not count
-as root materialization attempts. Reopen only when exact paths and executable
-behavior passed Vet and there is **no controlling-root materialization attempt**;
-record the routing migration so it cannot reset again. Missing product slices,
-unresolved protocol choices, or a recorded root attempt remain under their normal
-gate/fingerprint rules. The first controlling-root failure is not exhaustion: it
-is the first no-progress result for the materializer fingerprint. If all targets
-still equal their recorded preimages, no real action ran, and only admitted bound
-temporaries remain, reopen an incorrectly persisted one-shot `1/1` terminal,
-preserve its evidence as attempt one, clean/repair/preflight offline, and continue
-within the shared three-attempt cap.
-
-Past evidence being irretrievable is not by itself terminal. When an in-scope
-trusted diagnostic seam can make the next retained fingerprint uniquely
-actionable, Autocomplete must run diagnostic-amplification Plan repair and narrow
-Vet inline, then pause for a fresh GO before the single evidence-acquisition
-attempt. Use `Next: none` only after proving no safe in-scope amplification seam
-exists, a real human/risk/scope gate owns it, or bounded recovery is exhausted.
-
-## Stop on gate severity
-
-- `blocking` gate fires → synchronous pause.
-- `escalating` gate fires → pause, route to the specialist tag.
-- Any `questions.md` entry with `gate: validating` and `status: open` → pause (it is a
-  seal NO-GO by definition; stop before reaching seal).
-
-## Stop on strategic-review scope expansion (`$rite-temper`)
-
-- Any `expand` or added acceptance criterion pauses regardless of
-  `allow_gates`/`--ship`. Only `hold-rigor` and `reduce-to-MVP` auto-apply;
-  skipped low-stakes specs and those two modes do not pause.
-
-## Stop on incomplete decision coverage (`$rite-clarify`)
-
-- Stop on any material Partial/Missing/unowned row or low-confidence, high-consequence
-  assumption. Continue the up-front window with the next genuine decision packet; never arm
-  AFK or carry it into build. Resolve facts and reversible choices automatically.
-
-## Stop on workflow state
-
-- **NO-GO at seal** → stop; surface every blocker with `file:line` and the fix
-  direction. Do not round NO-GO up to GO.
-- **Spec Drift Guard fires** (`$rite-build` finds the plan is wrong and the change
-  alters product behaviour) → stop; route through `$rite-plan repair`.
-- **Budget exhausted with slices still pending:** any validated root-owned remaining
-  value of zero stops before the next dispatch. Report which bound won (pre-existing
-  remaining value, explicit flag, sentinel cap, or post-vet pending count) and the
-  unbuilt slices. A malformed value also fails closed. Zero with no pending slices is
-  normal completion → continue to `$rite-prove` without pausing.
-- **Resource envelope unavailable or exhausted:** stop before more work when the AFK
-  envelope is missing/malformed/expired; another run overlaps; native agent, token,
-  cost, or wall-time headroom is exhausted/unobservable despite a declared cap; or
-  unresolved review/gate backlog is above its cap. At the review cap, permit only
-  reconciliation that reduces the queue. Record the exact winning limit and observed
-  usage/count. A new activation gets fresh activation-local counters; it does not reset
-  durable slice/recovery budgets, expiry, or the recomputed queue.
-- **Still low-confidence after the interview:** the idea can't be pinned to testable
-  acceptance criteria → stop and ask, rather than guessing the product.
-- **Repeated failure:** bounded recovery exhausts → stop with reproduction.
-
-## The final type-GO
-
-- `--ship` / `--yolo` never authorizes Git. Continue through ship preflight,
-  disclose the exact plan, then stop for literal `GO` and native approval.
-- Without either flag, stop at seal GO with `$rite-ship` as the resume command.
-  Seal GO, AFK, prior approval, and flags never satisfy ship approval.
-
-## How to stop well
-
-State must be enough for a fresh agent to resume cold:
-- `state.md`: `Status`, the blocking reason, and either a single actionable
-  `Next step` command or the terminal `none — technical recovery exhausted`
-  marker.
-- The relevant `questions.md` / `drift.md` / `seal.md` entry that explains the pause.
-- A one-line user-facing message: *what* stopped it and, only when one exists,
-  *what human-owned action* resumes. A terminal technical blocker names no
-  routine Plan/Vet/retry command.
+# Stop conditions: when autocomplete pauses
+
+On a real stop, write `state.md` as `awaiting_human` or `blocked`, persist the
+reason, and include one resume command only when an actual human/safety/access
+action can change it. Exhausted agent-owned recovery records terminal
+`Next step: none` and no runnable recovery command. `--ship` never bypasses a
+stop.
+
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → keep Plan repair/affected Vet internal; no stop solely for topology/count.
+- `GUARD_AND_REPAIR` → enter Spec Drift Guard/Clarify; pause only at an existing human-owned gate; resume Plan/Vet internally.
+- `BLOCKED_INPUT` → no planning writes; stop internal branch; exact diagnostic; recover authority; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
+## Always stop
+
+Regardless of flags or AFK ceiling:
+
+- destructive data migration;
+- auth/authz boundary change;
+- public API break;
+- external-service contract change; or
+- filesystem destruction outside the workspace.
+
+Red proof cannot advance. Run bounded Debug Recovery; stop after proven
+exhaustion unless the remaining owner is human.
+
+## Not stops: internal technical routing
+
+`NEEDS_REPLAN` is not a stop condition under active Autocomplete. It blocks
+forward work, persists the return cursor, and invokes Plan repair plus Recovery
+Vet inline. The same applies to nested `STOP`/`Next step` when its decision is
+agent-owned.
+
+Agent-owned backtracking is not a stop condition while the exact causal
+fingerprint has budget. Invoke the earlier phase, affected Vet, remediation, and
+proof; then resume the origin. Stop only after three no-progress corrections of
+that exact fingerprint or a real human/safety/access gate. Preserve reproduction,
+attempts, and dead ends; never offer `$rite-plan unblock` or another routine
+phase command. Reinvocation with unchanged evidence does not reset the cap.
+`unchanged` means the same fingerprint already has three recorded no-progress
+corrections. Closure is progress; a separately evidenced Critical/Important
+invariant starts its own cap and cannot extend the closed one.
+
+Spent consumptive-action authorization is not technical-recovery exhaustion.
+It blocks another execution; retained new Critical/Important evidence still
+enters offline recovery. After affected Vet is READY, pause for fresh action
+authorization and never reuse old GO.
+
+Past evidence being irretrievable is not by itself terminal. If an in-scope
+trusted seam can uniquely discriminate the next failure, run diagnostic-
+amplification Plan repair and narrow Vet inline, then pause for fresh GO before
+one evidence-acquisition attempt. Use terminal none only when no safe in-scope
+seam exists, a real human/risk/scope gate owns it, or bounded recovery is
+exhausted.
+
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"classifier returns owner-busy, exhausted, or existing hard gate","action":"stop on exact WAIT_ACTIVE_OWNER, BLOCKED_EXHAUSTED, or BLOCKED_GATE result","return":"unchanged cursor plus fixed route-owned output"} -->
+## Other stop classes
+
+- **Gate severity:** blocking or escalating gate; any open validating question.
+- **Temper:** any `expand` or added acceptance criterion. `hold-rigor`,
+  `reduce-to-MVP`, and a justified skip do not pause.
+- **Clarify:** material Partial/Missing/unowned decision coverage or a
+  low-confidence high-consequence assumption. Continue the initial interview;
+  never arm AFK early.
+- **Seal:** NO-GO, with every blocker and fix direction. Never round up to GO.
+- **Reslice:** execute its marked action before deciding continue/stop.
+- **Slice budget:** any validated root-owned remaining value of zero stops before the next dispatch
+  when slices remain; malformed state also stops. Report whether the winning
+  bound was the pre-existing remaining value, explicit flag, sentinel cap, or post-vet pending count.
+  Zero with no pending slices is normal completion and proceeds to Prove.
+- **Resource envelope:** missing/malformed/expired AFK, overlapping run,
+  exhausted/unobservable declared agent/token/cost/time headroom, or review queue
+  above cap. At cap, only queue-reducing reconciliation may run. Persist winning
+  bound and observed usage; a new activation does not reset durable budgets or
+  expiry.
+- **Confidence:** intent still cannot become testable acceptance after interview.
+- **Repeated failure:** the exact fingerprint's bounded recovery is exhausted.
+
+## Final GO and durable stop
+
+`--ship`/`--yolo` never authorizes Git. With a flag, complete Ship preflight,
+disclose the exact plan, and stop for literal `GO` plus native approval. Without
+one, stop at Seal GO with `$rite-ship`. Seal GO, AFK, prior approval, and flags
+never satisfy Ship approval.
+
+A cold-resumable stop records `state.md` status, exact reason, and either one
+human-owned resume action or `none — technical recovery exhausted`; the owning
+question/drift/seal entry explains it. The user-facing line says what stopped
+and, only when applicable, what human action resumes it.

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

@@ -8,92 +8,64 @@ user-invocable: true
 # $rite-build: one verified slice
 
 Build and prove one slice. HITL stops; a later user invocation starts the next.
-Explicit `.devrites/AFK` alone lets the controlling root chain pending slices,
-only under existing green-proof, cap, and pause rules. **Read the active workspace
-first**; if none, tell the user to run `$rite-spec <feature>`.
+Explicit `.devrites/AFK` alone lets the controlling root chain pending slices
+under green proof, caps, and pause rules. Every wright returns after it. Read the
+active workspace first; without one, route `$rite-spec <feature>`.
 
-The root owns gates/workspace; a
-fresh-context [`devrites-slice-wright`](.codex/agents/devrites-slice-wright.toml)
-writes product source and tests. Exact Vet-ready executable workflow artifacts use
+Root owns gates/bookkeeping. Fresh
+[`devrites-slice-wright`](.codex/agents/devrites-slice-wright.toml) writes product
+source/tests. Workflow Artifact paths use
 [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md).
-Apply the readiness, selection, host, HITL/AFK,
-dispatch, doubt, fail-on-red, record, and stop checks. See
+Execute [`reference/phase-contract.md`](reference/phase-contract.md); dispatch uses
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
 
-## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
-Read `.agents/skills/devrites-lib/reference/standards/core.md` first. The wright
-reads named on-demand rules while writing; root reads them for doubt/record gates:
-- `coding-style.md`: naming, function shape, guard clauses, comments, reuse-first.
-- `error-handling.md`: fail fast, no silent catches, fail closed.
-- `testing.md`: pyramid, behaviour over implementation, see-it-fail-first.
-- [`reference/tdd.md`](reference/tdd.md): the slice-level Red → Green → Refactor
-  and Prove-It contract.
-- `patterns.md`: composition over inheritance, avoid premature abstraction.
-- `principles.md`: the project invariants (`.devrites/principles.md`) the slice must honor; the wright reads them as **binding**, not priors.
-- `security.md`: when the slice touches user input, auth, data, or external integrations.
-- `repository-topology.md`: when targets span roots/languages/services or touch generated/vendor surfaces.
-- `data-integrity.md`: when the slice writes durable state or changes migration/concurrency/tenant/retention behavior.
-- `integration-reliability.md`: when the slice changes an API/webhook/queue/job/cache/cross-service boundary.
-- `definition-of-done.md`: standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
+## Required rules
 
+Read `.agents/skills/devrites-lib/reference/standards/core.md` first. Load only
+rules triggered by the slice:
 
-## Operating rules
-- **One slice per wright dispatch.** Every wright returns after it. The controlling
-  root applies the mode rule above before another dispatch. Prefer the guarded serial
-  native-worktree pilot in `wright-dispatch.md` only when its committed-clean
-  preflight and explicit reconciliation path both hold; otherwise use the existing
-  serial same-worktree writer. Never run writers in parallel.
-- Evidence over confidence. Prefer existing conventions. Feature scope only: no
-  drive-by refactors.
-- **Record adjacent issues; do not edit them.** An issue outside the exact paths
-  stated in the dispatch task becomes an FYI follow-up in `decisions.md`. The slice summary states
-  what it deliberately left alone ([`git-workflow.md`](../devrites-lib/reference/standards/git-workflow.md)
-  "Things I didn't touch"). The root rejects a returned diff outside this boundary.
-- **Don't re-run an unchanged check.** The same build or test on unchanged code provides
-  no new evidence. Re-verify after an edit.
-- Surface material assumptions. Do not introduce an unplanned dependency or second design
-  system: route the objective plan gap to `$rite-vet` (or bounded recovery), not to a human.
-  Ask only if the newly exposed choice changes licensing/cost/security, product behavior,
-  or an explicit architecture policy. The
-  [Spec Drift Guard](reference/spec-drift-guard.md) is active throughout.
-- **Avoid AI slop while writing.** `devrites-slice-wright` applies the anti-slop charter
-  while writing. The canonical list is `rite-polish/reference/anti-ai-slop.md`; do not
-  duplicate it here. The wright follows project idioms and reuses existing code first.
-  **Verify the charter on return.** Do not correct source from the orchestrator.
-  The **prose you write yourself** (`evidence.md`, `decisions.md`, the slice report) follows
-  the human-voice charter (`.agents/skills/devrites-lib/reference/standards/prose-style.md`; depth in `devrites-prose-craft`): no
-  filler openers or marketing adjectives; preserve exact commands and identifiers.
-- **Honor declared project principles.** The wright reads `.devrites/principles.md` and treats
-  each invariant as **binding** (not a prior to weigh like a convention): a slice it cannot build
-  without breaking one is an **Escalation**, not a silent violation. On return **you verify no
-  principle was broken**; a fresh violation is handled like any irreversible-risk item: a
-  human-approved, scoped exception in the register or a stop, never folded into the slice. No
-  `.devrites/principles.md` → none declared → nothing to honor.
-- **You never edit product source/tests.** You write `.devrites/` bookkeeping and,
-  only through `workflow-artifacts.md`, an exact Vet-ready executable workflow-artifact set.
-  Follow the
-  host gate in `wright-dispatch.md` before every build or recovery dispatch. On a
-  supported host, the wright is the only writer of code and tests. Codex gives
-  the root workspace permission only so that native writer dispatch can execute;
-  never patch code from the root. Put the exact project-relative source/test path
-  list directly in the task, dispatch the exact `devrites-slice-wright`, then
-  compare `git diff --name-only` with those task paths. Any extra source file is
-  a hard STOP.
-- **Executable workflow-artifact branch.** If every implementation target is an
-  exact admitted path under the active `.devrites/work/<slug>/`, the controlling
-  root materializes and proves that atomic set itself. It does not dispatch the wright,
-  decrement/count a product slice, update the candidate manifest, or execute the
-  consumptive action. After narrow Vet, restore the caller cursor.
+- coding style, error handling, testing, [`reference/tdd.md`](reference/tdd.md),
+  patterns, and definition of done;
+- binding `.devrites/principles.md` invariants when present;
+- security for input/auth/data/integrations;
+- repository topology for multiple roots/languages or generated/vendor surfaces;
+- data integrity for durable state, migration, concurrency, tenancy, or retention;
+- integration reliability for API/webhook/queue/job/cache/service boundaries.
 
-## Workflow
+The wright also applies the canonical anti-slop list. Root verifies its return;
+it never patches source itself.
 
-Run the full execution contract in
-[`reference/phase-contract.md`](reference/phase-contract.md). It is not optional:
-it contains the gated one-slice workflow, including readiness, HITL/AFK handling,
-wright dispatch, doubt, fail-on-red, record gates, and stop behavior.
+## Invariants
 
-## Output
+- One slice per wright dispatch; writers are serial. Use the native-worktree pilot
+  only when `wright-dispatch.md`'s clean preflight and reconciliation both hold,
+  otherwise serial same-worktree writing.
+- Exact feature scope only. Record adjacent issues and Things I didn't touch;
+  reject any returned diff outside the task's explicit source/test paths.
+- Never rerun an unchanged check. Re-prove after edits.
+- Unplanned dependency, design system, objective technical gap, or repair stays
+  inside Vet/Spec Drift Guard. Ask only for licensing/cost/security/product or
+  explicit architecture-policy decisions.
+- Root never edits product source/tests. It writes canonical `.devrites/`
+  bookkeeping and applies the Workflow Artifact route only. The supported host's
+  wright is sole product writer. Put exact project-relative paths directly in the
+  task; compare returned file list and `git diff --name-only`; extras hard-stop.
+- Project principles are binding. An unavoidable conflict or irreversible risk
+  needs a human-approved scoped exception or stop, never silent balancing.
+- Evidence beats confidence. Never weaken a failing test, skip TDD, widen a
+  writer, or self-approve a wright return. Route drift through
+  [`reference/spec-drift-guard.md`](reference/spec-drift-guard.md); checkpoint
+  mode follows [`reference/checkpoint.md`](reference/checkpoint.md).
 
-Use [`reference/output.md`](reference/output.md) and the shared
-[`reply contract`](../devrites-lib/reference/reply-contract.md). They keep the
-HITL stop, bounded AFK chaining, and no-automatic-`$rite-prove` boundary explicit.
+## Workflow Artifact branch
+
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"Vet-ready admitted bytes require root authorship outside product wright","action":"ROOT_TRANSACTION; root writes only admitted .devrites/** targets","return":"saved Build slice cursor; wright product allowlist unchanged"} -->
+## Execute and reply
+
+Run every step in `reference/phase-contract.md`: readiness, one target, dispatch
+or canonical transaction, return inspection, independent doubt/test analysis,
+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 chains only within its durable remaining
+budget; Prove starts only after all slices are built.

package/pack/generated/codex/skills/rite-build/reference/phase-contract.md

@@ -16,28 +16,14 @@ See [`one-slice-cycle.md`](one-slice-cycle.md); candidate lifecycle is
    scope, or proof, use the Spec Drift Guard/plan recovery; a human-owned unknown
    stops. Resolve HITL before source work. AFK answers only permitted gates;
    human-owned or irreversible risk persists a question and stops for `$rite-resolve`.
-   If the target is only an exact Vet-ready executable workflow-artifact set under
-   the active feature workspace, apply
+   If the target is an exact Vet-ready Workflow Artifact set, apply
    [`workflow-artifacts.md`](../../devrites-lib/reference/standards/workflow-artifacts.md)
    instead of treating it as a product slice.
-3. **Dispatch or materialize.** Product source/tests apply [`wright-dispatch.md`](wright-dispatch.md).
+3. **Dispatch or transact.** Product source/tests apply [`wright-dispatch.md`](wright-dispatch.md).
    Put the smallest exact project-relative source/test path list directly in the task;
    dispatch the exact `devrites-slice-wright` fresh. Root never writes those product
    paths, wright never widens, and a missing profile stops.
-   For the workflow-artifact branch, the controlling root writes only the admitted
-   `.devrites/work/<slug>/` paths. Before an active journal or target write, it
-   compiles the materializer and runs the exact transaction implementation in a
-   disposable same-layout fixture covering success, replacement failure, rollback,
-   retained-temporary cleanup, and rerun. It then proves the complete atomic set,
-   rechecks an
-   identical product candidate, records hashes/evidence, and runs narrow Vet. Do not
-   dispatch any agent as a substitute writer and do not charge a product slice.
-
-### Executable workflow-artifact branch
-
-The controlling root materializes the exact admitted workflow-artifact set and
-**does not dispatch the wright**. This branch never changes product slice state or
-the candidate manifest; it returns through narrow Vet before any consumptive action.
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"Build gate enters or resumes transaction","action":"invoke canonical operation table; reconcile exact result","return":"same slice/checkpoint cursor or Plan/Vet route"} -->
 4. **Inspect the return.** Wait; compare its file list and `git diff --name-only`
    with the contract. Reject stale, partial, malformed, or out-of-scope work.
    Preserve user work; source restoration uses the same bounded wright.

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

@@ -14,15 +14,20 @@ artifact-only**: reconcile
 editing source code.
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
-Pull `development-workflow.md` via `Read` when reshaping slice cadence or DoD criteria.
+Pull `development-workflow.md` via `Read` when reshaping slice cadence or DoD
+criteria.
 Load `repository-topology.md`, `data-integrity.md`, or `integration-reliability.md`
 when the spec applicability map or observed drift triggers them.
+Before classifying any Reslice, read `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
 
 ## Operating rules
 - Update the spec when needed, but never plan around a known-wrong assumption.
-- For product behavior, scope, architecture, data, UX, security, or migration changes,
-  search facts then route human-owned contract decisions through `$rite-clarify`/Drift
-  Guard. Reversible technical repair is agent-owned, not a question.
 - Keep each slice small enough for one focused build → prove cycle.
 - **Derive slice count:** reslice when work cannot build+prove in one cycle, not to hit a
   requested tally. Treat counts as hints and explain honest differences; see
@@ -57,9 +62,8 @@ when the spec applicability map or observed drift triggers them.
    - **reorder:** fix the dependency order.
    - **split:** separate backend/frontend contracts (see `devrites-api-interface`).
    - **unblock:** a verification failed; re-route around the blocker.
-   - **course-correct:** deliberate mid-build user pivot. Classify impact on remaining slices,
-     choose rollback/forward-fix, and update spec/plan/tasks/decisions atomically. Acceptance or
-     behavior still needs the user first; an `MVP cut` is the pre-agreed retreat.
+   - **course-correct:** mid-build user pivot; apply the marked action, choose
+     rollback/forward-fix, and update permitted artifacts atomically (`MVP cut` is the named retreat).
    - **revise:** reconcile a requested artifact revision; propose/confirm its file set and
      **never edit source**. Only explicit `$rite-upgrade` with a `repairable` assessment naming
      rule, evidence, gate, paths, and delta can authorize its neutral workspace edit—not source/history.
@@ -105,19 +109,15 @@ when the spec applicability map or observed drift triggers them.
    reconfirm only after Clarify and Vet close it. If you stopped for drift,
    mark the `drift.md` entry resolved. Never remove or overwrite a valid caller
    return cursor while writing the Plan checkpoint.
-6. If product behavior/acceptance criteria change, confirm through `$rite-clarify` before
-   writing, re-close `decision-coverage.md`, then reconcile the plan. After any edit to
-   `brief.md`, `spec.md`, `decisions.md`, `assumptions.md`, or `questions.md`, including a
-   behavior-neutral technical rationale appended to `decisions.md`, re-scan the affected coverage
-   rows, assumption audit, residual uncertainty, and closed gates. Partial/Missing, an unowned
-   material assumption, or an open blocking/escalating question routes `$rite-clarify`/HITL.
-   Re-read every affected row and require current evidence before restoring `CLEAR`.
-   **Completion:** the change is classified, and every behavior/acceptance change has explicit
-   confirmation recorded before the artifacts are updated.
+6. Apply the marked action before writes and retain its decision/coverage evidence.
+   After editing `brief.md`, `spec.md`, `decisions.md`, `assumptions.md`, or `questions.md`,
+   re-scan affected coverage, assumptions, uncertainty, and gates. Partial/Missing, unowned
+   material assumption, or open blocking/escalating question routes `$rite-clarify`/HITL.
+   Restore `CLEAR` only from current evidence.
 7. **Done when:** every slice is sized (builds + proves in one cycle; no slice scoring >3
    left unjustified), the dependency order is acyclic, every `drift.md` entry you stopped for
    is marked resolved, revised artifacts agree with each other, no source files changed in
-   `revise` mode, behavior-change-vs-not is confirmed (`no`, or clarified), and every changed
+   `revise` mode, the marked action is complete, and every changed
    plan ends at `$rite-vet` rather than returning directly to build; horizon IDs stay stable,
    reclassifications cite evidence, and no unresolved item vanished. The `Shared contract proof`
    table or justified no-impact statement must still match the revised boundary set.

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

@@ -5,6 +5,14 @@ feels reluctance toward asking the user before a behavior change.
 
 Pack-wide rationalizations + red flags: see [standards/anti-patterns.md](../../devrites-lib/reference/standards/anti-patterns.md).
 
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
 ## Phase-specific rationalizations
 
 | Excuse | Rebuttal |
@@ -13,7 +21,9 @@ Pack-wide rationalizations + red flags: see [standards/anti-patterns.md](../../d
 | "I can fix the slice mid-build, no need to update tasks." | `tasks.md` is the contract `$rite-build` reads. A fix that isn't there isn't visible to the next phase. |
 | "Reordering slices is cosmetic." | Dependency order controls risk discovery; risk-first wins because it surfaces blockers early. |
 | "This drift is small enough to absorb silently." | Silent drift = unrecorded decision = future "why does this work?" debugging session. |
-| "I can change product behavior to make the plan fit." | Behavior change always asks the user first, no exceptions. |
+| "I can change product behavior to make the plan fit." | **RSLICE-PLAN-001** — Implementation convenience cannot rewrite product behavior. |
+| "Topology or a small criterion delta decides the route." | **RSLICE-PLAN-002** — Topology/count and “small” never override the canonical classifier; sufficient authoritative contract delta follows its mapped action. |
+| "Chat, stale material, or the convenient map is enough." | **RSLICE-PLAN-003** — Exact current byte-bound directives are authority; cached, remembered, summarized, paraphrased, or inferred chat and stale material are not. |
 
 ## Red Flags
 

package/pack/generated/codex/skills/rite-plan/reference/replan-and-repair.md

@@ -2,6 +2,14 @@
 
 `$rite-plan` runs in one of these modes. Pick from `$ARGUMENTS` or infer from state.
 
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
 ## decompose
 First (or fresh) breakdown into vertical slices. Use `task-breakdown.md` +
 `slicing.md`. Output: a populated `tasks.md` and an ordered `plan.md` graph.
@@ -20,8 +28,7 @@ A drift event stopped the build. Steps:
    reality. Adjust acceptance criteria if they were wrong.
 4. Mark the `drift.md` entry **resolved** with the resolution + date.
 5. Resume at the corrected slice.
-Never repair by quietly deleting the inconvenient requirement, if behavior changes,
-that was a user question.
+Never quietly delete a requirement; use the marked action before contract edits.
 
 ## reorder
 Dependency order is wrong or suboptimal. Recompute the graph (`dependency-graph.md`),
@@ -39,4 +46,4 @@ end and plan a new diagnosis/proof fingerprint. Never clear/reuse old one.
 
 ## Always
 Update `state.md` (phase, next step) and append a dated line to `decisions.md`
-explaining *why* the plan changed. Ask the user before any product-behavior change.
+explaining *why* the plan changed. Preserve mapped-action decisions.