Skip to main content

HDIP AI Product PDEP Stages — Spec C

This page defines the lifecycle-accurate Product Development and Evolution Process (PDEP) for AI Products in a mature HDIP ecosystem.

Spec C assumes the AIPS ontology defined elsewhere in this site:

  • Productness and AI Product Family qualification are separate questions.
  • AI Product qualification is version-specific and evidence-backed.
  • APT is resolved from the actual intelligence dependency graph.
  • Governance obligations are derived from the Product that actually exists.
  • AIPROD, AIPDS and AIPS-DPP bind to the same exact AI Product version.
  • Continuous Assurance monitors ontology currentness as well as runtime behavior.

Lifecycle principle: Intent is declared by the AIPRO; ontology, dependency, governance and deployment realization are compiled by the platform from authoritative registries and evidence.


1. Spec C at a glance​

The two qualification points serve different purposes:

  • Preliminary AI Qualification prevents clearly non-AI propositions from flowing deep into an AI-specific lifecycle.
  • Definitive AI Qualification proves AI Product Family membership from the resolved, version-specific constitution graph and produces the authoritative AI Qualification Evidence (AQE) and APT.

Preliminary qualification is therefore a screening gate, not a substitute for AQE.


2. Lifecycle artifact chain​

No later artifact may silently manufacture a different ontology from the one compiled at Stage 7.


3. Detailed stages

Stage 0 — Preconditions​

Row HeadingStage 0 Definition
Stage Number0
Stage NamePreconditions
Lifecycle PhaseEcosystem readiness
PurposeVerify that HDIP can resolve, govern, deploy and assure the proposed Product class
OutcomeVersioned Precondition Report
Primary InputsEnterprise registries and platform capabilities
Required Registries / ServicesProduct Registry, AI Primitive / Model Product registry capability, Data Product Catalog, Schema/Ontology Registry, Policy Registry, Capability Registry, Environment Registry, identity/authority, lineage, observability and trust services
Core ActivitiesValidate registry completeness, execution/evolution capabilities, policy engines, deployment targets and assurance services
Processing TypePlatform-driven
GateGate: Preconditions
AIPRO ResponsibilityNone beyond identifying the intended business context
Platform ResponsibilityProve ecosystem readiness or identify blocking gaps
Failure Modes / RisksMissing authoritative registrations, unsupported execution mechanism, unavailable control or assurance capability

Registry principle: in mature HDIP, if an AI Primitive, Model Product, upstream AI Product, policy, schema, capability or environment is not authoritatively registered, it cannot be relied upon during definitive compilation.


Stage 1 — Intent Record + Preliminary AI Qualification​

Row HeadingStage 1 Definition
Stage Number1
Stage NameIntent Record & Preliminary AI Qualification
Lifecycle PhaseBusiness declaration and family screening
PurposeCapture business-native Product intent and test whether AI Product Family qualification is plausible
OutcomeIntent Record + Preliminary AI Qualification Decision
Primary InputsBusiness need, intended value, consumers, intended intelligence proposition
Core ActivitiesDefine purpose/value; identify proposed value-bearing essence; state distinct intelligence proposition; establish direct/transitive AI Primitive hypothesis
Processing TypeAIPRO declaration + platform-assisted semantic validation
GateGate: Preliminary AI Qualification
Output ArtifactsIntent Record; Preliminary Qualification Record
AIPRO ResponsibilityDeclare what value is intended and what intelligence proposition is being productized
Platform ResponsibilityValidate Productness hypothesis, intelligence primacy, semantic coherence and plausible AI Primitive path
Failure Modes / RisksAI-enabled non-AI Product incorrectly entering AIPS; model/artifact mistaken for AI Product; no distinct intelligence proposition

Preliminary qualification questions​

A candidate proceeds only when the platform can establish a credible basis for all of the following:

  1. the candidate can qualify as a Product under BPS;
  2. artificial intelligence appears to be the value-bearing essence, not merely an enabling or constructional dependency;
  3. a distinct governed intelligence proposition is being proposed;
  4. at least one direct or transitive AI Primitive path is plausible and resolvable later.

Possible outcomes are PASS, CONDITIONAL, or FAIL. CONDITIONAL means the candidate may proceed while explicit evidence gaps remain to be resolved before Stage 7. It is not current AQE.


Stage 2 — Authority Confirmation​

Row HeadingStage 2 Definition
Stage Number2
Stage NameAuthority Confirmation
PurposeConfirm ownership, mandate and accountability for the candidate Product/version
OutcomeAuthority Decision
Primary InputsIntent Record, organizational authority context, identity/entitlement evidence
Core ActivitiesValidate AIPRO mandate, domain accountability, publication authority and escalation ownership
GateGate: Authority
Failure Modes / RisksProduct creation without legitimate ownership or business mandate

Stage 3 — Intelligence Constitution, Behavior & Topology Profile​

Row HeadingStage 3 Definition
Stage Number3
Stage NameIntelligence Constitution, Behavior & Topology Profile
PurposeDescribe what intelligence is intended, how it behaves, and the candidate constitution required to realize it
OutcomeVersioned Constitution / Behavior / Topology Profile
Primary InputsIntent, preliminary qualification, authoritative registries
Core ActivitiesResolve candidate IC, IE, AR, EM, MO, topology; identify candidate Model Products, AI Primitives, upstream AI Products, Data Products, knowledge/rules/tools; record exact or resolvable version constraints
Output ArtifactsConstitution Profile; Behavior & Topology Profile
GateGate: Constitution & Topology
Key PrincipleThis stage describes and normalizes the candidate graph; it does not yet make the definitive APT/AQE claim
Failure Modes / RisksUnregistered dependency, ambiguous Product boundary, hidden upstream intelligence dependency, misleading autonomy/embodiment declaration

A Derived hypothesis may become visible here, but APT is authoritative only after Stage 7 compilation.


Stage 4 — Effective Risk Computation​

Row HeadingStage 4 Definition
Stage Number4
Stage NameEffective Risk Computation
PurposeCompute evidence-backed R0–R4 risk from the ontology/context that currently exists
OutcomeRisk Decision Record + Risk Driver Assessment
Primary InputsIC, AR, EM, IE, topology, impact evidence, intended uses, preliminary dependency information
Core ActivitiesApply AIPS risk floors and contextual risk rules; identify escalation requirements
GateGate: Risk Tier
Key PrincipleRisk is orthogonal to APT and must not be inferred from labels such as “generative” or “agentic” alone

Stage 5 — Structural Constraints & Escalation​

Row HeadingStage 5 Definition
Stage Number5
Stage NameConstraint Enforcement & Escalation
PurposeEnforce prohibited combinations, hard safety/policy constraints and risk-tier-specific requirements
OutcomeConstraint Validation Report; escalation artifact where required
Core ActivitiesValidate topology, authority, agency, embodiment, effects, prohibited uses, policy constraints and mandatory human/physical safety controls
GateGate: Constraints
Special CaseR4 requires the applicable executive escalation/approval artifact before progression

Stage 6 — Intelligence Behavior & Evolution Contract (IBEC)​

Row HeadingStage 6 Definition
Stage Number6
Stage NameIntelligence Behavior & Evolution Contract (IBEC)
PurposeDefine the enforceable behavioral, effect, evolution and safety contract without assuming that every AI Product learns or serves model inference
OutcomeVersioned IBEC
ScopeInputs/effects, execution behavior, permitted actions, human oversight, learning mode, evolution mechanisms, quality/evaluation, safety and prohibited behavior
Core ActivitiesDeclare behavioral invariants, evolution posture, validation obligations, effect/action boundaries and control requirements
GateGate: Intelligence Behavior Contract
Failure Modes / RisksUnbounded action, undeclared evolution, non-enforceable safety expectations, model-centric assumptions applied to symbolic/agentic/Physical AI

The historical Learning & Inference Contract (LIC) is retained as compatibility terminology for contracts that are specifically learning/inference-oriented. IBEC is the general lifecycle concept.

Examples:

  • learned-model Product: learningMode=TRIGGERED_RETRAINING;
  • symbolic reasoner: learningMode=NONE, evolution through rules/knowledge;
  • Derived agentic Product: evolution through upstream dependency, tool and policy changes;
  • Physical AI Product: closed-loop action and physical safety constraints.

Stage 7 — Ontology & Governance Compilation​

Row HeadingStage 7 Definition
Stage Number7
Stage NameOntology & Governance Compilation
Lifecycle PhaseAuthoritative compilation
PurposeCompile Stages 0–6 plus authoritative registries into the resolved Product ontology and enforceable governance posture
OutcomeDefinitive AQE + resolved APT + derivation topology + Governance Obligation Profile + compiled governance stack
Primary InputsIntent, authority, constitution profile, risk decision, constraints, IBEC, authoritative registries
Core ActivitiesResolve exact dependency versions; traverse direct/transitive AI Primitive paths; validate AI Product Family qualification; resolve Primary/Derived APT; resolve SingleUpstream/Composite topology; compute governance obligations; bind evidence provenance
Processing TypePlatform / Product Factory Intelligence compilation
GatesGate: Definitive AI Qualification; Gate: Governance Compilation
Failure Modes / RisksNo qualifying AI Primitive path, upstream Product no longer AI-qualified, APT mismatch, stale registry evidence, unsatisfied governance obligation

Definitive AI Qualification gate​

Stage 7 is the first point at which the platform has enough resolved evidence to issue authoritative AI Qualification Evidence (AQE).

If qualification fails, the candidate must not proceed as an AI Product. It may instead return to the wider BPS process for appropriate Product Family treatment.


Stage 8 — AIPROD Finalization​

Row HeadingStage 8 Definition
Stage Number8
Stage NameAIPROD Finalization
PurposeFinalize the immutable semantic descriptor for the exact AI Product version compiled at Stage 7
OutcomeAIPROD version
Core ActivitiesBind Product identity/version, intelligence proposition, AQE, APT/topology, IC/CS/PU/MO/IE/AR/EM, R0–R4 risk and Governance Obligation Profile
GateGate: AIPROD Finalization
Key PrincipleAIPROD records the compiled ontology; it does not self-declare or recompute a contradictory one

Stage 9 — AIPDS Generation​

Row HeadingStage 9 Definition
Stage Number9
Stage NameAIPDS Generation
PurposeGenerate the version-specific operational realization of the qualified AI Product
OutcomeAIPDS version
Core ActivitiesBind exact AI Product version and dependencies; compile execution/evolution configuration; bind Governance Obligation Profile to enforceable controls; configure observability and safety
GateGate: AIPDS Generation
Key PrincipleExecution is universal; model inference is conditional. Evolution is universal; retraining is conditional.

AIPDS must bind to the same Product version and current governance/qualification evidence used by AIPROD. Deployment configuration cannot preserve an AI classification invalidated at the semantic layer.


Stage 10 — Deployment, Registration & Trust Publication​

Row HeadingStage 10 Definition
Stage Number10
Stage NameDeploy, Register & Publish Trust
PurposeMaterialize the Product, register it, expose governed discovery/consumption surfaces and publish trust evidence
OutcomeRunning deployment + Catalog/Marketplace registration + AIPS-DPP
Core ActivitiesProvision runtime; verify control bindings; register exact Product/AIPROD/AIPDS versions; configure observability; issue AIPS-DPP; generate ontology-preserving Marketplace listing; bind entitlement and consumption-port projection
External DependenciesProduct Catalog/Registry, Marketplace, entitlement/access services, lineage, observability, FinOps, trust/signing services
GateGate: Promotion + Marketplace Eligibility
Promotion PreconditionsAI qualification CURRENT; dependency currentness CURRENT; governance profile current and controls bound; assurance sufficient; deployment validation successful
Marketplace PreconditionsListing kind and Product Family agree; AIPS-DPP is valid; trust currentness satisfies policy; exact consumption ports are bound to the Product version
Key PrinciplePublication exposes a trustable Product version and governed acquisition path, not merely a running endpoint

AIPS-DPP is the trust projection of the Product version and must bind the same AQE, ontology, risk, governance and assurance evidence established through the lifecycle.

The marketplace must preserve Product Family boundaries. AI Product, Model Product and AI-enabled Product listings are distinct. A Product version with stale, revalidation-required or invalid AI qualification cannot be surfaced as a current Active/Restricted AI Product; it may remain visible through a historical or revalidation surface where policy permits.

Marketplace acquisition is separate from consumption. Entitlement resolves the governed AIPDS-backed port/package that the consumer is permitted to use.


Stage 11 — Continuous Assurance & Evolution​

Row HeadingStage 11 Definition
Stage Number11
Stage NameContinuous Assurance & Evolution
PurposeContinuously validate runtime behavior, consumption fitness, realized value, safety and the current truth of Product qualification/governance claims
OutcomeAssurance signals, COVP evidence, currentness state, impact events and controlled evolution intents
ScopeRuntime quality, behavior, usage, consumer feedback, contextual fitness, value realization, incidents, dependency changes, qualification currentness, governance currentness, assurance currentness
Core ActivitiesObserve Product; collect governed COVP usage/feedback/fitness/value evidence; consume registry/dependency change events; recompute currentness; traverse downstream impact; trigger assurance or evolution/re-entry where material
Output ArtifactsCOVP Observation Set; Assurance Evidence; Currentness Record; Change/Impact Record; Evolution Intent
Feedback LoopRe-enter the earliest materially affected stage rather than blindly rerunning or mutating the Product in place

Currentness dimensions​

Continuous Assurance tracks at least:

  • Qualification currentness — does AQE still prove AI Product Family membership?
  • Dependency currentness — are the exact Product/Primitive/Data/Model/knowledge/tool bindings still valid and supported?
  • Governance currentness — do the Governance Obligation Profile and control bindings still match ontology/risk reality?
  • Assurance currentness — is evidence of fitness/safety/quality still sufficient?

COVP feedback loop​

Stage 11 integrates the Consumption Observation & Value Plane (COVP). COVP records version-bound usage telemetry, consumer feedback, intended-use-specific fitness and value-realization evidence.

COVP signals are intentionally orthogonal to Product ontology:

  • high adoption does not make a Product an AI Product;
  • low adoption does not invalidate AI qualification;
  • a high consumer rating does not change APT;
  • realized value does not lower risk tier;
  • adverse consumption evidence may, however, trigger assurance, governance or risk reassessment.

Fitness is always contextual. A Product can be FIT for one intended use and UNFIT or INSUFFICIENT_EVIDENCE for another.

Change routing​

ChangeTypical earliest re-entry
Business purpose / value proposition changes, including persistent value-realization gapStage 1
Ownership / mandate changesStage 2
IC, AR, EM, IE, topology or constitution changesStage 3
Risk evidence changes without constitution change, including material adverse-use evidenceStage 4
Policy / hard-constraint changeStage 5
Behavior/evolution contract changesStage 6
AI Primitive or upstream AI Product version changesStage 7 at minimum, and Stage 3 if constitution intent also changes
AIPROD-only publication metadata correction with unchanged semanticsStage 8 subject to immutability/versioning rules
Deployment-only realization change with unchanged Product semanticsStage 9

A change to an upstream Product does not rewrite downstream history. Only downstream versions that adopt or otherwise become affected by the changed dependency require requalification.


4. Stage/gate summary

StagePrimary gatePrincipal evidence/output
0PreconditionsPrecondition Report
1Preliminary AI QualificationIntent + preliminary qualification
2AuthorityAuthority Decision
3Constitution & TopologyConstitution/Behavior/Topology Profile
4Risk TierRisk Decision + drivers
5ConstraintsConstraint Report / escalation
6Intelligence Behavior ContractIBEC
7Definitive AI Qualification + Governance CompilationAQE + APT + derivation topology + Governance Obligation Profile
8AIPROD FinalizationImmutable AIPROD
9AIPDS GenerationImmutable AIPDS
10PromotionDeployment + registration + AIPS-DPP
11Continuous Assurancecurrentness + assurance + evolution signals

5. Product-version binding rule

The following artifacts must identify the same exact Product version or an explicitly traceable successor version:

AI Product Version
├── AQE
├── APT / derivation topology
├── Risk Decision
├── Governance Obligation Profile
├── AIPROD
├── AIPDS
└── AIPS-DPP

A mutable latest dependency is not sufficient where a dependency can change AI qualification, APT, risk or governance obligations.


6. Glossary additions and lifecycle meanings

AI Qualification Evidence (AQE)​

Version-specific evidence proving why a Product currently qualifies for the AI Product Family, including value-bearing essence, distinct intelligence proposition and current direct/transitive AI Primitive evidence.

AI Product Type (APT)​

Family-specific intrinsic classification resolved at Stage 7. Primary has no material upstream AI Product dependency; Derived materially depends on one or more upstream AI Products. Composite is a Derived topology, not a third APT.

AIPRO​

AI Product Owner. Accountable for Product intent, intended outcomes, acceptable-use posture and business authority. The AIPRO does not manually construct dependency graphs or assign APT by preference.

AIPROD​

Immutable, version-specific AI Product semantic descriptor. It records the ontology/governance outcome compiled for the Product version, including AQE, APT and Governance Obligation Profile exposure.

AIPDS​

Immutable, version-specific operational realization descriptor. It binds execution, evolution, observability, safety and governance-control implementation to the exact qualified Product version.

AIPS-DPP​

AI Product Trust Passport. The signed/trustable projection used by consumers, marketplaces, governance services and auditors to inspect qualification, ontology, risk, governance, currentness and assurance for the Product version.

Artificial Intelligence Primitive​

A computational intelligence-producing capability such as a learned model, symbolic reasoner, planner or other qualifying mechanism. A Product version must have a current direct or transitive primitive path to qualify as an AI Product.

Definitive AI Qualification​

The Stage 7 evidence-backed determination of AI Product Family membership after the constitution graph and authoritative dependency versions have been resolved.

Governance Obligation Profile​

The version-specific set of governance obligations computed from the actual Product ontology/context and effective R0–R4 risk posture.

Intelligence Behavior & Evolution Contract (IBEC)​

The general Stage 6 contract governing behavior, effects, actions, evolution/learning posture, safety, oversight and quality/evaluation. It does not assume model ownership or retraining.

Learning & Inference Contract (LIC)​

Legacy/specialized compatibility term for learning/inference-oriented behavior contracts. It is not the universal lifecycle abstraction for all AI Products.

Preliminary AI Qualification​

Stage 1 screening decision that establishes whether the candidate plausibly belongs in the AI-specific lifecycle. It is not authoritative AQE.

Product Factory Intelligence (PFI)​

The platform intelligence that compiles declarative Product intent and authoritative registry knowledge into resolved ontology, governance, semantic, deployment and trust artifacts. PFI is not the Product Owner.

Qualification Currentness​

State describing whether AI Qualification Evidence still reflects the Product version and its bound dependency graph: CURRENT, STALE, REVALIDATION_REQUIRED, or INVALID.

Continuous Assurance​

Stage 11 lifecycle discipline covering runtime behavior and ontology/trust currentness. It includes dependency-change impact analysis and controlled PDEP re-entry.


7. Machine-readable lifecycle binding

AIPS 0.1 publishes an informative authoring/validation profile for Spec C under:

https://aips.kivanura.org/spec/aips/pdep/0.1/

The lifecycle record binds stage evidence, preliminary qualification, definitive AQE/APT, governance profile, AIPROD, AIPDS, AIPS-DPP and currentness without duplicating the canonical content of those artifacts.

Final principle: PDEP does not turn an AI-related artifact into an AI Product by ceremony. It progressively gathers and compiles evidence until AI Product qualification, governance, realization and trust can be proven for a specific Product version.