@oevery/rsp 3.3.0 → 4.0.0

package/skills/{rsp-design → rsp-shape}/references/reversible-exploration.md

@@ -1,4 +1,4 @@
-# Reversible exploration
+# Reversible exploration (Shape design method)
 
 Use this procedure only when a material design conclusion depends on behavior that available code, tests, documentation, or runtime evidence does not establish.
 
@@ -12,7 +12,7 @@ Use this procedure only when a material design conclusion depends on behavior th
 
 - Keep disposable code outside production owners and name it clearly as temporary. Do not change public interfaces, migrations, persistent data, credentials, or delivery state.
 - Record the pre-probe file state and exact cleanup target. Avoid the probe when unrelated work makes safe cleanup uncertain.
-- Run only the minimum observation, capture the evidence, then remove every disposable artifact before returning. Verify cleanup without discarding unrelated work.
+- Run only the minimum observation and capture the evidence. If the probe fails, inspect actual effects before a repeat or cleanup; never replay a one-shot action or guess at an unknown mutation. Remove every disposable artifact within the exact authorized cleanup boundary before returning, and verify cleanup without discarding unrelated work. Report any cleanup that cannot safely be completed.
 
 ## Return evidence, not architecture
 

package/skills/rsp-verify/SKILL.md

@@ -1,40 +1,72 @@
 ---
 name: rsp-verify
-description: Verify one selected RSP Change against its declared evidence boundary without mutating product or workflow state.
+description: Collect and report one selected RSP WorkOwner's declared check evidence, including separately required independent verification. Read-only; fixed-scope semantic judgment belongs to Review even when it includes checks.
 license: MIT
 metadata:
   author: oevery
-  version: "2026.08.21.1"
+  version: "2026.10.12.1"
 ---
 
 # RSP Verify
 
-Run one bounded, read-only verification pass for an existing RSP WorkRef. Verify owns evidence collection and the verification result; it is a Discipline, not a router, controller, lifecycle owner, reviewer, or Git delivery capability.
+For tracked work, read the [shared work model](../rsp/references/work-model.md) when its identity and ownership definitions are missing from the current context. Use logical WorkRefs in commands and reports; cite file locations separately. Direct invocation needs no prior Core execution.
+
+Collect declared-check evidence for one existing RSP WorkOwner when requested or separately required. Return one bounded read-only result. Review may run supporting checks without invoking Verify. Honor combined requests and required independent evidence; this Skill supplies no host independence. Verify is a Discipline for evidence collection, not routing, control, lifecycle, semantic review or Git delivery.
 
 ## Require a declared boundary
 
-Require one explicit WorkRef or one unambiguous focus marker, the selected Change or Group context, its declared `Verify` boundary, the comparison baseline, and the authority to run the named checks. Stop when the owner, scope, baseline, required evidence, or environment is ambiguous. A Group Brief is context only; verify the selected executable child or the explicitly named integration boundary.
+Require one selected WorkOwner, declared boundary, comparison baseline and authority for the named checks. An explicit reference wins; otherwise resolve one FocusSet candidate from user intent and status. Multiple markers are valid.
+
+- **Change:** use its WorkRef and its `Verify` section for the declared boundary.
+- **Group:** use its Group reference and named `Integration:` condition in the Brief's `Completion Conditions`; child evidence stays with each child WorkRef. An explicit request may supply an in-progress temporary boundary, which must be written back before Group closeout.
 
-Read the nearest project instructions, Core or fallback, selected Change and Brief, relevant Specs and Decisions, current diff, blockers, and the smallest production path needed to understand the declared check. Do not invent checks from generic testability or replace an unexplained failure with a guessed assertion; route that case to `rsp-diagnose`.
+Stop for ambiguous owner, scope, baseline, required evidence or environment, or a Group without a named boundary for the requested verification.
+
+Read nearest project instructions and the available project protocol, selected Change and Brief, relevant Specs and Decisions, current diff, blockers, and the smallest production path needed to understand the declared check. This package needs no installed Core Skill. Do not invent checks from generic testability or replace an unexplained failure with a guessed assertion; return that symptom for read-only diagnosis.
 
 ## Preserve read-only authority
 
 Do not edit product files, Changes, Specs, Decisions, focus markers, archives, configuration, or Git state. Do not start publication, deployment, approval, or human-acceptance actions. Running a declared local test, build, typecheck, lint, browser check, or other environment check is evidence collection only and retains the authority required by that command.
 
-Reuse the invoking Core or Manage contract. Core owns the single outer `ControlOutcome`, route, and continuation; Manage owns execution mode, delegation, result validation, acceptance, lifecycle closeout, and commit eligibility. Verify's canonical result is nested phase evidence, not a peer outer status. Verify does not select worker identity or isolation, derive `review-clean`, or claim `archiveReady`; any identity or independence evidence comes from the host.
+Use the caller's result contract when supplied, otherwise the direct result below. Core owns response coordination, dispatch, result validation, acceptance and closeout; Verify supplies evidence, never worker identity/isolation, `review-clean` or `archiveReady`. Identity and independence require host observations.
+
+## Collect the declared evidence
+
+Compare existing evidence with the declared baseline. Reuse traceable passes while their tested scope and relevant content, dependencies, configuration, tools, inputs and environment still apply. Run missing, failed or invalidated named checks and any explicitly required execution, current-environment observations or independent execution. Corrections and integration need fresh evidence for affected inputs or an enlarged boundary; a phase change alone requires no rerun.
+
+Compare each check's actual targets, inputs, coverage and completion with its declaration. Retain commands, scope, sources and results; distinguish reused evidence from new execution. Invocation errors or incomplete observations alone prove no product defect; exit status alone establishes no acceptance.
+
+For a tool-only obstacle, diagnose read-only and inspect actual effects before continuing:
+
+- Change a permitted collection method only with unchanged goal, owner, scope, baseline, authority and required evidence, and demonstrably safe replay.
+- Run a named mandatory command/check as required; substitutes supply no pass.
+- Do not repair product/workflow state, manually replace command-owned RSP operations, replay one-shot work or continue with unknown mutation effects.
 
 ## Return one bounded result
 
-Return exactly one canonical result:
+Return exactly one canonical result from the collected evidence, with observed failure taking precedence over unavailable coverage:
 
+- `fail`: at least one named required check has observed failure, even when another check is unavailable.
+- `unavailable`: no named required check has observed failure, but a required tool, dependency, service, credential, or environment could not be used.
 - `pass`: every named required check passed within the declared boundary.
-- `fail`: at least one named required check failed.
-- `unavailable`: a required tool, dependency, service, credential, or environment could not be used.
 
-Every result includes `evidence_delta: new | none` to state independently whether the pass, failure, or unavailability produced evidence that changes the next diagnosis or correction. It also includes `boundary: unchanged | changed` to state independently whether the observed owner, paths, baseline, behavior, interface, scope, or authority still matches the declared boundary. Include the WorkRef, lane objective, effective authority, named checks, comparison baseline, observed diff boundary, decisive evidence, omissions, and stop boundary. Preserve exact result and field values as machine-facing values; human-facing narration follows the invoking response-language contract.
+Report each check's outcome, including missing or unexecuted checks. Aggregation changes neither coverage nor stop conditions. Failure does not imply complete coverage; unavailable evidence does not erase observed failures.
+
+Include these independent fields and their evidence:
+
+- `evidence_delta: new | none`: whether the result changes the next diagnosis or correction.
+- `boundary: unchanged | changed`: whether observed owner, paths, baseline, behavior, interface, scope and authority still match the declared boundary.
+- WorkOwner and applicable Change WorkRef or Group `Integration:` condition; lane objective and effective authority.
+- Named checks, comparison baseline, observed diff, decisive evidence with reused versus newly executed results, omissions and stop boundary.
 
-`pass` proves only the declared verification boundary. It does not prove semantic review, durable writeback, archive readiness, commit eligibility, publication, deployment, approval, or human acceptance, and it does not grant lifecycle, Git, publication, or acceptance authority. Verify never self-reports worker identity or independence; Manage uses host observations when that distinction is required. Long-running verification remains active while its declared boundary and stop conditions hold; elapsed time, heartbeat, polling, and progress messages do not change the result.
+Preserve exact machine values and all required result information. Present them concisely without repeated logs or evidence; a requested machine schema remains exact. Human-facing narration follows a supplied response-language contract; otherwise use explicit user instruction, then personal instructions, then conversation language.
+
+`pass` proves only declared checks, not semantic review, writeback, archive/commit eligibility, publication, deployment, approval or human acceptance. It grants no lifecycle, Git, external or acceptance authority.
+
+Long-running verification remains active while its boundary and stop conditions hold. Elapsed time, heartbeat, polling and progress messages do not change the result.
 
 ## Stop and return
 
-Stop with the invoking contract's canonical stop reason when evidence is missing, the environment is unavailable, the boundary changes, or a required check cannot be observed. On cancellation, do not begin conflicting work until the command or owned process is observed stopped. Return to Core or Manage with the result, decisive evidence, omissions, and the next owner; never turn an unavailable check into success and never retry without new evidence and safe replay inside the declared boundary.
+Stop when evidence is missing, the environment is unavailable, the boundary changes or a required check cannot be observed. Use the caller's canonical stop reason only when supplied. For direct invocation, identify the missing input or changed boundary and the required next action; do not invent a completed verification result before the declared boundary is established.
+
+On cancellation, wait until the command or owned process is observed stopped before beginning conflicting work. Return the result, decisive evidence, omissions and next action to the caller or user. Retry only with new evidence and safe replay inside the declared boundary.