/nw-design

name: nw-design
description: "Establishes durable architecture, reuse, boundaries, cross-layer algebra, residual stress behavior, paradigm, and prefactoring decisions for deterministic minimal handover construction."
user-invocable: true
argument-hint: '[bounded design question] --paradigm=[auto|oop|fp|procedural] [--residuality]'

> **Code facts** — resolve structural facts through `code-fact`; degrade > LOUD when its provider-neutral adapters cannot answer.

NW-DESIGN

Use `nw-human-collaboration` for interactive refinement with the human. Honor an already selected final-review or full-delegation mode; the LLM manages the dialogue and progression.

Load `nw-cross-cutting-invariants` and apply `flow:findings-go-to-the-owner-directly` when exchanging findings or questions between roles.

Authority

DESIGN updates durable architecture brief/ADRs, never a per-delivery narrative, plan or duplicate contract. Product value is decomposed once into an ordered graph; no downstream competence reslices it. DISTILL asks the existing CLI/software producer to derive one minimum executable whole-Request handover from Git and the existing durable product/design/oracle authorities. Every independently observable and shippable value slice represented in that graph gets one oracle and an independent acceptance-test review before craft and RED/GREEN. The Request gets one fresh independent whole-candidate final review after all slices are GREEN, plus embedded per-slice refinement reviews for early feedback. Source-blind EXAMINE where applicable and integration close the Request once; internal technical shards, packages, layers and steps get no mini-cycle.

**Requested scope, designed scope and unresolved shared decisions are distinct.** For a feature with several values, first establish or confirm existing common contracts, dependencies and observation of the whole requested result, then design per-slice deltas; a slice is not ready until the shared decisions it depends on are resolved. Inherit epic/project decisions when present; never invent them. A one-value or local change reuses adequate existing architecture: no full upfront local implementation design, repeated boilerplate or universal gate. Resolve a shared contract the slice needs first; an independent slice proceeds when inherited architecture suffices, and that does not make the feature design complete. Honor an explicit human instruction to design shared decisions first. A single-value Request needs no shared section. A value oracle covers the slice delta and references inherited common constraints and feature walking-skeleton obligations by stable ids, without copying definitions; it does not attest feature completeness. This paragraph is the sole owner of this rule; other roles and skills reference it.

Resolve cited `Proposed` decisions by confirming or changing them with a reason. For each `Open` item assigned to DESIGN, supply its decision or the reason it remains open and its owner. Preserve the product's original actors and scope.

When an uncertain boundary needs exercise, orient the existing delegation toward one concrete producer-to-consumer connection: semantic design facts to an executable oracle on the real public port. Let that consumer's specific missing semantic question and counterexample return to its decision owner before expanding the affected design or solution. This tests one uncertainty in an existing value-level connection; it neither shrinks the requested architecture scope nor attests that feature DESIGN is complete, and it creates no technical-fragment cycle or additional delivery phase.

The coordinating architect owns the Required Design Pass, self-falsification and complete design values. Consulted specialists supply plain owned advice; integrate platform advice into the same coherent design authority.

Route application/component to `nw-solution-architect`, domain boundaries to `nw-ddd-architect`, scale/distribution to `nw-system-designer`, deployment to `nw-platform-architect`. Invoke only risk-required lenses. Algebra, certainty and formal verification are owner-scoped lenses, never replacement routes. Code-level structure stays downstream unless a public contract needs a boundary.

For an independent operational review of a selected platform lens, the outer native caller follows `nw-role-invocation` and consumes `nw-platform-architect-reviewer`'s actual recorded findings and outcome. Keep the evidence; builder success is not reviewer approval.

**Consultation policy (short).** The application/component architect owns coherent design decisions by default — no fanout for routine work. Involve the system designer only for a genuinely consequential distribution, capacity, scaling, or availability trade-off. Involve the DDD architect only when language, bounded context, aggregate, or invariant boundaries are actually contested. Pattern/style selection (e.g. hexagonal, CQRS, event-driven) applies only when system structure is actually in scope for the change at hand — not by default on every design pass. The LLM chooses which consult(s) to make and integrates their input into one coherent decision.

Required Design Pass

Performed by the coordinating architect, not the outer host or a consulted lens. Apply `design:simplest-design-that-delivers` in `nw-cross-cutting-invariants` throughout this pass.

1. **Intent and constraints** — bind product identities/observations; name uncertainty, never invent a requirement. Carry every cited input bound, range and explicit absence of a bound into `constraints`; explain each narrower or wider design as a deviation, never silently adapt the authority to a storage representation or generator. 2. **Code facts and reuse** — map responsibilities/callers/ports/dependencies; choose evidence-backed `REUSE`, `EXTEND`, `REPLACE` or `CREATE_NEW` for each. Check specifically for a SEMANTIC duplicate authority or a parallel implementation independently de