/nw-nwdes

name: nw-nwdes
description: nwdes routes and verbs for host-led delivery of a Request.
user-invocable: false

nwdes

Route

• The root writes product facts and promises itself.
• Every new product slice cites existing Request promises with repeatable --promise P<n>; add a justified Request promise with product promise add, or split unrelated outcomes into a separate nwdes feature new. Product close requires every slice linked and every Request promise covered; independent slices and every work size remain valid.
• Ask the product owner only on ambiguity or a genuine scope or trade-off question.
• When the Request already states the outcome, no product owner turn or Quint model is required as a product prerequisite.
• There is no separate oracle review beyond the independent approval of each public oracle before craft, an artifact-quality check of that oracle alone; no per-slice charter.
• Prose-only change: a change whose every target is a Markdown or template prose asset is recorded as a prose-only slice: `nwdes slice set` with its targets and promise references and none of `--oracle`, `--stimulus`, `--expected`, `--falsifier`, `--command` or `--support`. nwdes records its acceptance as `NotTested` with reason `prose, verified by EXAMINE`; no acceptance designer is run for it, and EXAMINE plus the whole-candidate review verify it.
• Never couple prose to tests: never write a test that pins the wording of a prose target. Exact public text is pinned only for a machine contract of a shipped surface (schema, table grammar, CLI output format, parse rule), per `nw-test-design-mandates` (3.7, pin no prose).
• Run a separate design review only when a shared decision or ADR changes, as nwdes delta computes; otherwise no separate design review is needed. Its bundle: save the delta text with nwdes delta --previous P --new H, then run nwdes prompt --role nw-solution-architect-reviewer --handoff H --diff DELTA --root-context DESIGN_FILES; the bundle records its verdicts with nwdes review --subject design verbs.
• Review scopes: Embedded refinement review of a GREEN slice is optional feedback that reduces risk; build it with --diff from the slice's base commit and --slice S<n>, and record it with --subject slice --slice S<n>. The one required review is a fresh independent whole-candidate review after all slices are built, recorded with --subject candidate; it never consults embedded review records, and an embedded approval never counts as it. One source-blind EXAMINE judges the complete Feature, never an individual slice; the examiner never receives producer discussions or embedded findings and returns its verdicts once on the assembled candidate revision before integrate. The independent approval of each oracle before craft stays.
• Smaller slices: Use one slice by default when one behaviour suffices; each slice delivers one observable behaviour a reviewer judges in one short pass. A feature has at most 5 slices. The first slice is the one walking skeleton and every later slice extends it with explicit dependencies. The Request keeps its whole value and shared design. A technical layer or mocked interaction is not a slice.
• Start a slice once the slices it declares as dependencies are GREEN. Independent slices may proceed in parallel, but a slice's review judges only its own declared paths (oracle, supports, targets): in one shared checkout, parallel slices close their own reviews only while their declared paths are disjoint, and a slice whose tests import another slice's uncommitted files needs its own lane. An uncommitted change outside a slice's declared paths does not block its review; a commit landing between observation and close moves HEAD and refuses the close, so observe again. A declared directory, absolute or backslash path, symlink, path under a symlinked directory, or git-ignored path refuses the review with UnprovableScope. The whole-candidate review requires every slice committed and the scope clean. Keep every test file collectable.
• Code facts: read nw-code-analysis-port and use code-fact first for callers, readers, file atoms and never-wired paths; use Read or Grep only where it cannot answer, including indeterminate, and identify fallback facts.
• Jev: use nw-typesafe-system-one only when authorized and available, after mechanical code facts; its advice is not a verdict. Otherwise record typesafe: unavailable and continue locally.
• If an installed role cannot run, stop with its cause. Only human authorization permits the host's default agent to run the exact generated role prompt and verb contract instead; report that substitution, never do the role's work yourself.
• Review evidence: Each verification has one owner. Each review's responsible reviewer owns selection and sufficiency of the touched-file selected tests for its declared phase scope; the final reviewer alone owns the assembled whole-candidate scope. It reuses a complete applicable native result (host, CI or the normal commit hook) whose source, test, argv and runtime inputs are unchanged, citing its original operator and run; it executes only missing or affected checks, once, and records argv, exit status, stdout and stderr of each run it executes with nwdes review observation add. Reuse never waives a check. nwdes never selects or runs tests, and the root never runs a duplicate readiness round. Scope: oracle/support files since slice base for oracle review; slice files since slice base for embedded review; assembled candidate files since feature base for final review; design files named in root-context for design review only when a shared decision or ADR changes. Missing touched-file observations, host observations not run, or failing selected tests are findings. NotTested is not a waiver: absence of pytest does not remove an assigned observation. Immutable evidence named by the packet is readable by the reviewer before assessment; sealed examiner or private producer evidence stays closed.
• Oracle an