AIWG 2026.8.2 - Git-native provenance exchange

Released: 2026-08-03 Channel: stable

AIWG 2026.8.2 adds a decentralized package exchange and verification layer around ordinary Git repositories. Packages remain independently hosted while their source identity, publisher claims, transformations, validation evidence, and installation results become reproducible and locally auditable.

Immutable package identity

Every marketplace envelope binds the package name and version to a canonical Git remote, immutable commit, source-tree and artifact digests, file inventory, wrapper and profile versions, provider support, dependencies, license, and an optional SBOM.

Movable tags and branches may be used for discovery, but AIWG resolves them to an immutable commit before deployment. Commit-keyed caches and lockfiles detect tag movement, altered source, archive divergence, rollback attempts, and dependency substitution.

Signed provenance and Fortemi receipts

The versioned envelope maps package entities, activities, and agents to W3C PROV and round-trips through Fortemi Knowledge Shard 2.0 `full-v1` without semantic loss. Publication, verification, installation, export, and import produce operation and conformance receipts.

Publisher trust uses Ed25519 roots with delegation, rotation, and revocation. Verification fails closed for unknown required fields, invalid signatures, digest mismatches, lossy conversion, or incomplete portable bundles.

Federated catalogs and direct Git parity

Multiple independently hosted signed catalogs can index the same package. Catalog inclusion is presented as an observation, not a safety endorsement, and removing a catalog does not invalidate an existing immutable lock.

Direct Git and catalog-mediated installation resolve to the same content and lock identity:

aiwg install https://host/owner/plugin.git --ref v1.0.0
aiwg marketplace install namespace/plugin --ref v1.0.0 --verify

Both project-local and global installation scopes maintain their corresponding package and Fortemi indices. Standalone `.aiwg/plugins/*` repositories deploy their complete agents, skills, and rules to the selected provider.

Offline verification and portable recovery

Once the source objects, package content, trust roots, and receipts are cached, verification works without network access. Portable export preserves normalized content, immutable coordinates, signatures, provenance, and prior receipts; import into a clean project reproduces the same lock identity before deployment.

The release gate exercised this flow against the BT6 plugin fixture, including Claude and Codex deployment, offline verification, export, clean-project import, and post-import verification.

Package matrix

All three packages publish in CalVer lockstep:

[email protected]
@aiwg/[email protected]
@aiwg/[email protected]

Upgrade

Follow the installation guide and select `2026.8.2` for the full local-corpus package or lightweight signed-web CLI. Existing project and global package indices remain compatible.

Rollback

Roll back all three packages together to `2026.8.1`. Existing immutable package caches, locks, trust roots, and receipts remain on disk and can still be verified by the version that created them.