Skip to main content

AIPS 0.1 Conformance Examples

The ontology-realigned AIPS 0.1 machine bindings include executable examples under static/spec/aips/0.1/examples.

CaseExpected resultWhat it proves
Primary fraud detectionValid AI Product VersionDirect learned-model primitive can support APT = Primary
Derived transaction interventionValid AI Product VersionMaterial upstream AI Product dependency yields APT = Derived
Composite transaction riskValid AI Product VersionMultiple upstream AI Products remain APT = Derived, Topology = Composite
Symbolic policy reasonerValid AI Product VersionML model dependency is not universally required
Qualification revalidationValid structural stateQualification currentness is version-specific and can require revalidation
Autonomous physical navigationValid AI Product VersionAutonomous physical action is R3+ and carries action/safety governance obligations
Autonomous physical R2Expected invalidPhysical autonomous action cannot be under-tiered or omit safety/action obligations
Enterprise autonomous R3Expected invalidEnterprise-orchestrated autonomous action requires R4 + escalation obligations
Model Product boundaryExpected invalid as AI Product VersionProductized model does not automatically qualify as an AI Product
Primitive-removal invalidationValid AQE recordINVALID qualification can record loss of the last qualifying primitive path
AIPROD examplesValidSemantic descriptor carries AQE, APT and orthogonal ontology dimensions
Publish projectionValidMarketplace surface exposes ontology-aligned classifications
Learned-model AIPDSValidRetraining remains supported where it genuinely applies
Symbolic AIPDSValidlearningMode = NONE and no training specification is valid
Physical-navigation AIPDSValidEmbedded + Continuous Physical AI carries safety and governance-control bindings
Missing-evolution AIPDSExpected invalidEvery deployment must explicitly state its learning/evolution posture
PDEP Primary fraud Stage 10Valid lifecycle recordPromotion binds current AQE/APT, governance, AIPROD, AIPDS and DPP
PDEP Composite Derived Stage 11Valid lifecycle/currentness stateContinuous Assurance may require revalidation without rewriting historical Product evidence
PDEP missing definitive qualificationExpected invalidStage 10 cannot bypass Stage 7 definitive AQE/APT compilation
PDEP stale promotionExpected invalidPromotion requires current qualification, dependencies, governance and assurance
Lifecycle current Primary closureValid lifecycle consistency recordAQE/AIPROD/AIPDS/DPP/Marketplace/COVP/PMDD/PDEP can close as one coherent Product version
Primitive-removal reclassificationValid conditional lifecycle recordNew non-AI version does not rewrite historical AI Product classification; only adopting downstream versions revalidate
Lifecycle failed-check closureExpected invalidCONSISTENT cannot coexist with failed cross-artifact checks
Cross-artifact DPP version driftExpected inconsistent bundleAn individually valid DPP can still contradict the Product version used by the rest of the lifecycle
Cross-artifact Marketplace APT driftExpected inconsistent bundleMarketplace cannot invent a different APT from the compiled/AIPROD/DPP ontology

Validation helper​

Run from the repository root:

python3 scripts/validate-aips-0.1.py

The helper validates Core, AIPROD, AIPDS, publish, AIPS-DPP, PDEP Spec C, Marketplace, COVP, PMDD and Lifecycle Closure JSON Schemas; parses their JSON-LD and Turtle artifacts; and parses all SHACL shapes. If pyshacl is installed, it executes the combined semantic constraints against positive RDF examples.

The negative cases are intentional ontology/deployment boundary tests and therefore count as passing when they fail their target JSON Schema as expected.