AIPS 0.1 Release Readiness
AIPS 0.1 ontology realignment is semantically complete and repository-conformant, with two environment-dependent release checks still requiring execution in a network-enabled development or CI environment: a full Docusaurus production build and executable SHACL validation.
Release posture
| Area | Status | Evidence |
|---|---|---|
| AI Product ontology / PIN alignment | Ready | Qualification, APT and orthogonal ontology dimensions are represented in docs and machine artifacts |
| Core / AIPROD / AIPDS schemas | Ready | JSON Schema, JSON-LD and RDF/Turtle validation pass |
| Governance & R0–R4 | Ready | Risk-driver and Governance Obligation Profile conformance cases pass |
| AIPS-DPP | Ready | Product-centric trust passport conformance passes, including conditional model evidence |
| PDEP Spec C | Ready | Stage 0–11 lifecycle and qualification/currentness cases pass |
| Marketplace / Consumption | Ready | AI Product, Model Product and AI-enabled Product boundaries are enforced |
| COVP | Ready | Usage, feedback, fitness and value evidence are kept separate from Product ontology |
| PMDD / AIPCH | Ready | Maturity is separated from Product/AI qualification and supports N/A applicability |
| Lifecycle Closure | Ready | Cross-artifact consistency and reclassification/downstream-impact cases pass |
| Static docs/config validation | Ready | Sidebar IDs, local links/imports, front matter and configuration guards pass |
| Docusaurus production build | Environment check outstanding | npm ci cannot complete without registry/network access in the review environment |
| Executable SHACL | Environment check outstanding | pyshacl is not installed and cannot be fetched without network access |
Release gate
AIPS 0.1 should be treated as release-candidate ready when the repository validator passes.
Before publication, CI or a connected development environment SHOULD additionally run:
npm ci
npm run build
python3 -m pip install pyshacl
python3 scripts/validate-aips-0.1.py
The final command automatically executes SHACL when pyshacl is available.
Required release invariants
A release candidate MUST preserve these invariants:
- Productness and AI Product qualification remain separate.
- AI Product Family membership is version-specific and evidence-backed.
- Model Product is not synonymous with AI Product.
- APT is limited to intelligence provenance (
Primary/Derived); capability, agency, embodiment, effect, mode and risk remain orthogonal. - Execution is universal; model inference is conditional. Evolution is universal; retraining is conditional.
- Marketplace presentation cannot create or preserve invalid AI Product qualification.
- PMDD maturity cannot create or revoke AI Product Family membership.
- Historical Product-version semantics are immutable; currentness and downstream impact are recomputed.
- Individually valid artifacts are insufficient when their cross-artifact Product story is inconsistent.
- AI-enabled and Compound Products do not inherit AI Product Family membership merely from an AI dependency.
Release artifact integrity
The file /spec/aips/0.1/aips-0.1.release-manifest.json records SHA-256 digests for the machine-readable AIPS 0.1 artifact set. The repository validator verifies these digests so accidental changes to release artifacts are detected.
Known compatibility vocabulary
Some legacy terms remain intentionally available for compatibility, but are no longer normative classification mechanisms. These include PrimaryArchetype and the historical LIC terminology. Their replacement semantics are documented in the Migration & Deprecation Guide.