Skip to content

v2026.8.14

Choose a tag to compare

View all tags
@jmagly jmagly released this 21 Aug 00:38
· 114 commits to main since this release
v2026.8.14
This tag was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 839584D0E25E5126
Verified
Learn about vigilant mode.
526a7b7
This commit was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 454C68C4A2174CE9
Verified
Learn about vigilant mode.

AIWG 2026.8.14 - Controlled output surfaces

Release date: 2026-08-20
Channel: stable

AIWG 2026.8.14 gives projects explicit control over how generated material is
presented. It adds composable runtime output modes while ensuring that optional
provider-native surfaces cannot silently replace canonical AIWG artifacts.

What changed

  • Output modes are now runtime-selectable and composable through a
    provider-neutral registry. The unchanged default is truly byte-preserving,
    and projects can combine built-in, project, user, and existing voice profiles
    in deterministic order.
  • Two advisory examples are included: an ASD-STE-oriented technical-writing
    mode and a Wittgenstein-inspired clarity mode. Protected literal content is
    preserved, and mandatory validators can fail or fall back safely.
  • aiwg output-mode supports invocation, session, and project selection, while
    aiwg run --output-mode passes the resolved stack to script and skill
    runtimes.
  • The new artifact_outputs policy keeps the AIWG artifact store canonical and
    makes provider-native destinations explicit-only by default.
  • Claude Design remains available when explicitly requested, but is treated as
    a derived presentation. Dual output records provenance back to the canonical
    artifact, and unknown provider destinations fail safe.

Verification

  • TypeScript, CLI build, schema compilation, and project configuration
    validation passed.
  • Focused output-mode and artifact-policy regression suites passed.
  • The release candidate passed 9,196 unit/integration tests and 107 UAT tests,
    plus the 38-query release-discovery and 3,299-item package gates.
  • Branch CI is required to pass before the signed release tag is created.

Package matrix

aiwg@2026.8.14
@aiwg/cli@2026.8.14
@aiwg/cockpit@2026.8.14

Upgrade

Upgrade all AIWG packages together, then regenerate provider context so the
artifact destination policy is compiled into current provider bootstrap files:

npm install -g aiwg@2026.8.14
aiwg regenerate

Existing projects retain the safe compatibility behavior: canonical AIWG
artifacts remain canonical and provider-native presentation is explicit-only.

Rollback

Roll all three npm packages back together to 2026.8.13, then regenerate
provider context. Project configuration using artifact_outputs should be
removed only if an older release rejects unknown configuration fields.

Assets 10
Loading