AIWG 2026.7.14 - "Provider-aware model routing and Fortemi conformance"

AIWG 2026.7.14 - "Provider-aware model routing and Fortemi conformance"

Released: 2026-07-20 Channel: stable (`npm install -g aiwg`)

AIWG 2026.7.14 delivers provider-aware model policy and worker routing across the supported provider set, while keeping provider installation—not a hard-coded model inventory—as the stable deployment boundary. It also promotes Fortemi Knowledge Shard portability from source-level compatibility to a profile-scoped, immutable conformance receipt exercised by both the pinned Core library and the Fortemi server.

Highlights

  • Provider-first runtime inventory (#1812, #1813) —

`aiwg runtime-info --providers` distinguishes configured, deployed, detected, available, and active providers. Dynamic model sources retain provenance and freshness without making live discovery a deployment dependency.

  • Safe model policy and worker wrappers (#1802–#1807, #1814) — canonical

role/tier/effort intent compiles to native provider controls where supported and explicit degraded or unsupported results everywhere else. Cross-provider wrappers are validated from generated output without launching paid sessions.

  • Observed Codex routing (#1185) — bounded CLI probes establish `gpt-5.5`

and `gpt-5.4-mini` mappings plus semantic reasoning-effort defaults; invalid or unavailable pins fail without silent fallback.

  • Fortemi `core-v1` conformance (#1797) — the exact

`@fortemi/[email protected]` converter output is digest-pinned and verified through clean PGlite and server import/re-export paths, with explicit capability/loss reporting and atomic rejection cases. Claims remain limited to the named `core-v1` profile.

  • Project-local deployment controls (#1788) — committed quickrefs,

provider-aware refresh, ownership-safe pruning, and project-local doctor checks make full and quick-reference deployment testable from output files.

  • Dedicated repository authority — ordinary commits, signed release tags,

Gitea tracker actions, and SSH transport now have separate project identities and fail-closed OpenBao-backed routing.

Upgrade

npm install -g aiwg@latest
cd your-project
aiwg regenerate

Run `aiwg use all` (or your selected framework/addon deploy commands) to refresh provider payloads and project-local quickrefs. No breaking changes.