Skip to main content

AIPS 0.1 Migration & Deprecation Guide

This guide maps pre-realignment AIPS concepts to the ontology-aligned AIPS 0.1 model.

Migration map​

Earlier concept / assumptionAIPS 0.1 alignment
Packaged AI artifact automatically becomes an AI ProductProductness and AI Product qualification are separate; PIN + AQE determine AI Product Family membership
Raw model checkpoint can become an AI Product by adding metadata/interfacesA productized learned model is ordinarily a Model Product; it becomes an AI Product only if the Product's own value-bearing essence satisfies AI Product qualification
PrimaryArchetype = INFERENCE / GENERATIVE / AGENTICDeprecated as an umbrella classifier; use APT + IC + MO + IE + AR + EM + topology + risk
Capability Type mixes Model, Agent, Generative, Symbolic, AGI/ASIReplace with orthogonal dimensions; APT is Primary / Derived, while IC describes intelligence capability
Universal Learning & Inference Contract (LIC)IBEC — Intelligence Behavior & Evolution Contract is the general concept; LIC remains compatibility terminology for learning/inference-specific cases
Every AI Product retrains / continuously learnslearningMode = NONE is valid; evolution posture is mandatory, retraining is conditional
Inference serving is universalExecution/interaction is universal; inference serving is one execution specialization
Model drift is the universal monitoring modelUse mechanism-appropriate change/quality monitoring plus qualification, dependency, governance and assurance currentness
Model Card/training evidence required for every AIPS-DPPProduct trust evidence is universal; Model Card/training evidence is conditional on constitution/applicability
AI Product vs Data Product distinguished by dynamic vs static behaviorDistinguish by Product Intrinsic Nature / value-bearing essence
L0 = AI Asset in PMDDL0 = Emerging AI Product; candidates without CURRENT AQE are Not Assessable
Composite is a peer AI Product TypeComposite is a Derived topology, not APT03
Orchestration of multiple AI Products automatically creates another AI ProductA new distinct governed intelligence proposition is required for a Derived AI Product
Marketplace label establishes Product familyMarketplace projects verified semantics; it cannot create Product Family membership
AI Product classification is permanentQualification is version-specific and can become stale/invalid; historical versions retain their historical semantics
13-stage interactive Spec CNormative PDEP Spec C is 12 stages: Stage 0–11

Compatibility policy​

Deprecated vocabulary MAY remain in serialized or documented compatibility surfaces during the AIPS 0.1 transition, but new implementations SHOULD emit the ontology-aligned constructs.

Where both old and new representations exist, the ontology-aligned construct is authoritative.

PrimaryArchetype​

  • Status: deprecated compatibility vocabulary.
  • Do not use it to compute APT or governance obligations.
  • Replace with IC/AR/EM/IE/topology/risk-driver evidence as appropriate.

LIC​

  • Status: specialized compatibility terminology.
  • Use IBEC as the general lifecycle contract.
  • LIC may describe the learning/inference subset where that terminology remains useful.

Historical filenames and routes​

Some document/component filenames retain historical names to preserve stable routes, even where their semantic title has changed. For example, the AIPDS pages historically named around inference/retraining now document broader execution/evolution semantics. Route compatibility does not imply legacy semantics remain normative.

Migration sequence for an existing implementation​

  1. Establish explicit Product identity and Product-version boundaries.
  2. Add version-specific AI Qualification Evidence and AI Primitive evidence.
  3. Resolve APT (Primary / Derived) independently of IC/MO/IE/AR/EM/risk.
  4. Replace archetype-driven risk logic with Risk Driver Assessment + Governance Obligation Profile.
  5. Generalize deployment contracts from mandatory inference/retraining to Execution + Evolution specifications.
  6. Reissue AIPS-DPP as an AI Product Trust Passport with conditional model evidence.
  7. Align Marketplace listing kind/currentness and consumption-port projection.
  8. Add COVP evidence without allowing usage/value to rewrite ontology.
  9. Migrate PMDD to maturity-only semantics and applicability-aware scoring.
  10. Enforce lifecycle closure and cross-artifact consistency before promotion/publication.