Skip to content

nWave Framework v4.1.0

Choose a tag to compare

@11PJ11 11PJ11 released this 04 Nov 05:36

Coming from 3.x? nWave 4 is a major release and a breaking change from 3.x. The old delivery runtime is removed, the 3.x delivery commands are replaced by the nwdes verbs, and Python 3.11 or newer is required. There is no converter for 3.x roadmaps or execution logs. Read the migration guide before you upgrade: https://github.com/nWave-ai/nWave/blob/main/docs/guides/migrating-from-3x.md.

nWave 4.1.0 is a feature release for 4.0.2. The nwdes closes ask for more
recorded facts before they accept, so a close that an earlier version accepted
can now be refused. Fixes for issues 101, 102 and 111 are included.

What changed

  • Closing a feature needs more recorded facts. A design close refuses
    until each code target of a slice has a reuse decision and an impact
    decision. Each decision is a recorded row or a reasoned not-applicable. The
    design also needs a decision on architectural tests and on contract tests,
    again a row or a reasoned not-applicable. Prose targets owe nothing. The
    product close asks for a scope-out line. An acceptance row must cite the
    promises it covers. An expectations row must cite the promises it judges.
  • The role prompts print the rule first. Each ask now prints the recording
    verb, the flags it takes and an example value, so a role reads what the
    close requires before the close refuses.
  • Hook logs and state are written at the project root (issue 111). Before,
    they were written relative to the working directory, so a session that moved
    between folders left one .nwave folder in each of them.
  • The DIVERGE wave records where each option name comes from (issue 101).
    A name is marked as the requester's own wording or as coined. Coined
    handles stay in the scoring table, and the decision statement uses the
    requester's words. Option generation also states a probability for each
    candidate and keeps the low-probability options in the set (issue 102).
    These probabilities are stated estimates, not measurements.

Upgrade

  • Upgrade the nwave-ai package with the Python package manager that
    installed it, then rerun nwave-ai install --platform <host> for your host.
  • Records made by an earlier version still open and read. When you close a
    design again and a slice has a code target, add the new decisions first.
  • Older sessions may have left a .nwave folder inside a subfolder. The new
    version no longer writes there. Look at what the folder holds before you
    delete it.

nWave Framework v4.1.0

Release Date: 2026-11-04

Promoted from: v4.1.0rc1

Full Changelog: v4.0.2...v4.1.0

Installation

uv (recommended):

uv tool install nwave-ai

pipx (fallback):

pipx install nwave-ai

Breaking Changes

0 changes

Features

5 changes

Bug Fixes

5 changes

Other Changes

29 changes

This repository's history is one commit per release, so individual changes are not listed here; the breaking changes are listed in the highlights above.

Migration decision SHA-256: f3fe80a4581d80825ed7fcc734c52a5f92389926ccd14402e0f505fa637340ff