AIWG 2026.10.4 - Inspectable rules and decision-offload visibility

AIWG 2026.10.4 makes it easier to inspect the rules that apply to a workspace, see whether bounded decision offload is configured and being used, and preserve that guidance as provider context is regenerated or compacted. It also adds direct signed-tag publication and optional qualification tools, improves deployment performance, and reduces session-import memory use.

Inspect the rules for your workspace

The scoped rule inventory lists provenance, activation, and fetch paths. You can filter by capability or provider and export complete rule bodies. The inventory separates available catalog rules from applicable rules; recorded deployment does not prove that a running provider session loaded a rule.

Try asking: “List the active rules for this workspace and show their full bodies.” See the CLI reference for command details.

See decision-offload readiness and adoption

Status, doctor, and steward expose offline readiness, recorded opportunities, answered calls, fallbacks, and unknown recording states. Diagnostic calls remain separate from ordinary adoption. Compact guidance survives regeneration and compaction when the addon and ask configuration are enabled.

Offload remains advisory. A missing or disabled service falls back to a local decision, and a recorded rule deployment is not a guarantee that every provider will follow it. See the observability guide.

Publish from a signed stable tag

Public npm publication runs through GitHub Actions from a signed stable tag. The workflow builds and smoke-tests the exact three package tarballs it publishes. Quarterly cross-provider qualification remains optional and does not gate release.

Upgrade

Update your installed AIWG package using your existing installation method, then refresh the frameworks and addons deployed to your workspace. Review custom rule pins and provider context after refreshing. See the changelog for the release changes and the versioning guide for release publication details.