​

Upgrading to AAP & AIP 1.0.0

​

The 1.0.0 stability commitment

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 and ADR-006). 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.

​

What changed

​

Migration

npm install @mnemom/agent-alignment-protocol@1.0.0 \
            @mnemom/agent-integrity-protocol@1.0.0

pnpm add @mnemom/agent-alignment-protocol@1.0.0 \
         @mnemom/agent-integrity-protocol@1.0.0

pip install 'agent-alignment-protocol==1.0.0' \
            'agent-integrity-proto==1.0.0'

uv pip install 'agent-alignment-protocol==1.0.0' \
               'agent-integrity-proto==1.0.0'

curl -X PUT https://api.mnemom.ai/v1/agents/$AGENT_ID/alignment-card \
  -H "X-Mnemom-Api-Key: $MNEMOM_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "card_version": "unified/2026-04-15",
    "card_id": "ac-your-card-id",
    "agent_id": "mnm-550e8400-e29b-41d4-a716-446655440000",
    "issued_at": "2026-04-13T00:00:00Z",
    "expires_at": "2026-10-13T00:00:00Z",
    "principal": { "type": "human", "relationship": "delegated_authority" },
    "values": {
      "declared": ["transparency", "honesty", "harm_prevention"],
      "hierarchy": "lexicographic"
    },
    "autonomy": {
      "bounded_actions": ["inference", "read", "write"],
      "forbidden_actions": ["exfiltrate_data"]
    },
    "audit": {
      "trace_format": "ap-trace-v1",
      "retention_days": 90,
      "queryable": true,
      "tamper_evidence": "append_only"
    }
  }'

# JSON
sed -i '' 's/"aap_version": "0.5.0"/"aap_version": "1.0.0"/' alignment-card.json

# YAML
sed -i '' 's/aap_version: "0.5.0"/aap_version: "1.0.0"/' alignment-card.yaml

# Validate and publish
mnemom card validate alignment-card.yaml
mnemom card publish alignment-card.yaml

# TypeScript
npm ci && npm run build

# Python
pip install -r requirements.txt

import { AIP_VERSION } from '@mnemom/agent-integrity-protocol';

console.log(AIP_VERSION);
// → "1.0.0"

import aap
from aip import AIP_VERSION

print(aap.__version__)   # → "1.0.0"
print(AIP_VERSION)       # → "1.0.0"

curl -i https://api.mnemom.ai/v1/agents/$AGENT_ID/alignment-card \
  -H "X-Mnemom-Api-Key: $MNEMOM_API_KEY" \
  -H "X-Mnemom-Version: 2026-04-13" | grep -i x-mnemom-version
# → X-Mnemom-Version: 2026-04-13

curl https://api.mnemom.ai/v1/agents/$AGENT_ID/alignment-card \
  -H "X-Mnemom-Api-Key: $MNEMOM_API_KEY" | jq '.aap_version'
# → "1.0.0"

​

Coming from 0.1.0? You can skip 0.5

​

What’s not in 1.0.0

• 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

​

Support window

• 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.

​

Checklist

​

FAQ

​

See also

• API versioning — Pinning to a specific X-Mnemom-Version date header and understanding the support window.
• Alignment Card Management — Creating, claiming, and linking cards.
• Alignment Cards — Schema reference for the card model 1.0.0 locks in.
• Upgrading to AAP 0.5.0 — Historical migration record for the 0.1.0 → 0.5.0 jump.
• Changelog — Full release history.