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
| Concern | Primary authority | Typical projections / consumers |
|---|---|---|
| AI Product qualification | AQE compiled in PDEP | AIPROD, DPP, Marketplace, PMDD |
| APT / ontology | PDEP compilation + AIPROD | DPP, Marketplace |
| Semantic intent | AIPROD | DPP, Marketplace, CEP |
| Runtime realization | AIPDS | DPP, Marketplace ports, Continuous Assurance |
| Risk/governance | compiled risk + Governance Obligation Profile | AIPROD, AIPDS controls, DPP, Marketplace |
| Trust evidence | AIPS-DPP | Marketplace, consumers, auditors |
| Consumption evidence | COVP | Continuous Assurance, value/evolution decisions |
| Maturity | PMDD | governance/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:
IDENTITY_VERSIONAQE_APTAIPROD_SEMANTICSAIPDS_BINDINGDPP_TRUSTMARKETPLACE_PROJECTIONCOVP_BINDINGPMDD_BINDINGGOVERNANCE_BINDINGSUPERSESSION_HISTORYDOWNSTREAM_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.