nWave-ai NW-DELIVER
Interactive, one step at a time:
printf '%s' "$REQUEST" | des po --repo-root ROOT
For this feature Request, the LLM evaluates and revises an evidence-based S/M/L assessment, decides applicable waves or an upstream authority correction, and chooses each supported operation. NEXT is advisory and may be ignored; DES never maps size to a route or invokes it. Each step owns one thing — the Product Owner decomposition, design facts, public oracle, change, candidate/native evidence, separately selected reviewer and source-blind examiner, and integration — and returns. The sequence is yours; no command composes it. Role outcomes are observations, never admission. nw-auto owns that guidance. Public results are Success, Refusal, Retry, and Indeterminate.
Where an uncertain boundary remains, use those existing operations to exercise
an early concrete producer-to-consumer connection: semantic input, DES
constructor, executable public-port oracle and its RED observation, then the
implementation and observation it enables. The LLM chooses whether and when to
take that path; it does not turn NEXT into a mandatory order. If a consumer
cannot proceed, route its specific missing semantic question and counterexample
to the owning author before expanding the affected design or solution. Do not
introduce a cycle for an internal technical fragment.