Skip to main content

Cross-Artifact Consistency Contract

AIPS artifacts are independently versioned, but they are not semantically independent. A Product version is publishable only when the artifacts participating in its trust boundary are mutually consistent.

Authority and projection​

ConcernPrimary authorityTypical projections / consumers
AI Product qualificationAQE compiled in PDEPAIPROD, DPP, Marketplace, PMDD
APT / ontologyPDEP compilation + AIPRODDPP, Marketplace
Semantic intentAIPRODDPP, Marketplace, CEP
Runtime realizationAIPDSDPP, Marketplace ports, Continuous Assurance
Risk/governancecompiled risk + Governance Obligation ProfileAIPROD, AIPDS controls, DPP, Marketplace
Trust evidenceAIPS-DPPMarketplace, consumers, auditors
Consumption evidenceCOVPContinuous Assurance, value/evolution decisions
MaturityPMDDgovernance/product improvement; never ontology authority

A projection may be intentionally smaller than its source. It must not contradict its source.

Mandatory consistency checks​

The AIPS Lifecycle Closure profile defines the following check classes:

  1. IDENTITY_VERSION
  2. AQE_APT
  3. AIPROD_SEMANTICS
  4. AIPDS_BINDING
  5. DPP_TRUST
  6. MARKETPLACE_PROJECTION
  7. COVP_BINDING
  8. PMDD_BINDING
  9. GOVERNANCE_BINDING
  10. SUPERSESSION_HISTORY
  11. DOWNSTREAM_IMPACT

A closure decision of CONSISTENT cannot contain a failed mandatory check.

Strong consistency versus subset projection​

Some fields should match exactly across authoritative artifacts (for example Product version, APT, agency, embodiment and risk tier).

Other artifacts may intentionally expose a subset. For example a Marketplace card need not reproduce every lineage edge from AIPROD. In that case the rule is:

Projection ⊆ authoritative semantics and projection must not introduce contradictory values.

The Stage 12 repository validator uses the canonical Fraud Detection example to enforce the stronger equality set used by that example. Implementations may define more selective projections provided their profile documents the projection rules.

Closure decision​

A LifecycleConsistencyRecord can conclude:

  • CONSISTENT — required checks pass and no blockers remain;
  • CONDITIONAL — the current state is coherent but controlled follow-up/revalidation is outstanding;
  • INCONSISTENT — artifacts contradict one another or a required binding is invalid;
  • HISTORICAL_CLOSED — historical version remains immutable and is no longer current for consumption.

The consistency record is evidence about artifacts. It does not become a new source of Product ontology.