Skip to main content
On 2026-04-13 both protocol SDKs — @mnemom/agent-alignment-protocol and @mnemom/agent-integrity-protocol — shipped 1.0.0. This is a stability commitment release: the public API surface is now locked, and breaking changes require a major bump to 2.0. The migration itself is small. There are no schema changes, no endpoint removals, and no signature changes on the customer-facing surface. Upgrading from 0.5.x is a version-string bump plus a rebuild.
Backward compatible. Existing 0.x alignment cards continue to work unchanged. The 1.0.0 server accepts every 0.x card shape. Update at your own pace.

​
The 1.0.0 stability commitment

The 1.0.0 release makes three explicit promises about what happens next:
  1. Breaking changes now require a major bump to 2.0. Field renames, removals, type changes, or required-parameter additions cannot ship within 1.x.
  2. Each major version is supported for 18 months from the release of its successor (see API versioning). That 18-month window is longer than most APIs and reflects our commitment to agentic callers that cannot self-update in response to deprecation notices.
  3. Deprecation signals are explicit. Deprecated versions return Deprecation, Sunset, and Link response headers, and API key owners receive email notifications at T+0, T+12 months, T+16 months, and T+17 months.
The 1.x line will receive bug fixes and strictness improvements. New card-format features are reserved for 2.0.

​
What changed

Nothing else changed. No alignment card schema edits, no endpoint removals, no signature changes.
AIP callers on 0.7.x or earlier: AIP 0.8.0 (also shipped 2026-04-13 as the pre-1.0 audit) removed WindowManager and createWindowState from the public exports. Window state is now managed internally by createClient(). If you import either symbol directly, migrate to createClient() before bumping to 1.0.0. The WindowState type remains exported.

​
Migration

​
Coming from 0.1.0? You can skip 0.5

The 0.x series was backward-compatible throughout — a 0.1.0 card is still accepted by the 1.0.0 server. If you are on 0.1.0, you do not need to pass through the 0.1.0 → 0.5.0 guide first. Bump directly to 1.0.0 using the steps above; replace "0.5.0" with "1.0.0" wherever it appears in that guide’s examples. The 0.5.0 guide remains online as a historical migration record (useful mainly for the YAML authoring and Trust Edges context it introduced, both of which carry forward unchanged).

​
What’s not in 1.0.0

Because 1.0.0 is a stability commitment rather than a redesign, several things you might expect are not here:
  • No new endpoints. The API surface is the same as 0.5.x.
  • No schema changes. Alignment card, AP-trace, and integrity checkpoint schemas are unchanged.
  • No deprecations yet. No Deprecation or Sunset headers are emitted on any endpoint as of the 1.0.0 cut. The deprecation machinery is in place for future use.
  • No unified agent card. The unified YAML agent card (AAP + CLPI) is a 2.0 target, not a 1.0 feature. See Forward-looking below.
  • No changes to ZK proof formats or Merkle tree structure. Those are versioned separately by the AAP/AIP protocol specs, not by the SDK semver.

​
Forward-looking: 2.0 roadmap

The 1.0.0 CHANGELOG entries include a forward-looking note: a 2.0 is planned that unifies AAP alignment cards and CLPI policy YAML into a single YAML agent card with runtime composition. The target is 6–12 months post-1.0, informed by production data from the 1.0 install base. Until then, 1.x receives bug fixes and strictness improvements only — new card-format features are reserved for 2.0. When 2.0 ships, the 1.x line will enter the standard 18-month deprecation window.
The forward-looking note in the AAP and AIP 1.0.0 CHANGELOGs predates the unified-cards model that describes the actual card model shipped in mnemom-api today. The 2.0 unified YAML agent card remains a planned future evolution on top of the unified-cards foundation.

​
Support window

Under our API versioning policy, each major version is supported for 18 months from the date its successor ships. In concrete terms:
  • 1.0.0 is the current major. It will be supported for at least 18 months after 2.0 ships.
  • When a new dated API version deprecates an endpoint or field in 1.0.0, you will receive Deprecation and Sunset response headers plus email notifications at T+0, T+12 months, T+16 months, and T+17 months.
  • Enterprise contracts may negotiate extended support; security vulnerabilities use an accelerated 30-day minimum window.
Pin your integrations to X-Mnemom-Version: 2026-04-13 in production so behavior stays stable until you choose to migrate. See API versioning for pinning details.

​
Checklist

​
FAQ

No. The 1.0.0 server accepts every 0.x card shape, and no endpoint signatures changed. 1.0.0 is a commitment that future breaking changes will require a 2.0 bump, not a redesign of the current surface.
No. Cards on different protocol versions coexist without issues. Roll the update at whatever cadence suits you.
AIP 0.8.0 (shipped the same day as 1.0.0 as the pre-1.0 audit) removed WindowManager and createWindowState from public exports. Switch to createClient(), which manages window state internally, before jumping to 1.0.0.
Bug fixes and strictness improvements, yes. New card-format features are reserved for 2.0 per the 1.0.0 CHANGELOG’s forward-looking note.
The 18-month clock for 1.0.0 starts the day 2.0 ships. Until then, 1.0.0 is the current major and receives ongoing support.

​
See also