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 Heading | Stage 0 Definition |
|---|---|
| Stage Number | 0 |
| Stage Name | Preconditions |
| Lifecycle Phase | Ecosystem readiness |
| Purpose | Verify that HDIP can resolve, govern, deploy and assure the proposed Product class |
| Outcome | Versioned Precondition Report |
| Primary Inputs | Enterprise registries and platform capabilities |
| Required Registries / Services | Product 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 Activities | Validate registry completeness, execution/evolution capabilities, policy engines, deployment targets and assurance services |
| Processing Type | Platform-driven |
| Gate | Gate: Preconditions |
| AIPRO Responsibility | None beyond identifying the intended business context |
| Platform Responsibility | Prove ecosystem readiness or identify blocking gaps |
| Failure Modes / Risks | Missing 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 Heading | Stage 1 Definition |
|---|---|
| Stage Number | 1 |
| Stage Name | Intent Record & Preliminary AI Qualification |
| Lifecycle Phase | Business declaration and family screening |
| Purpose | Capture business-native Product intent and test whether AI Product Family qualification is plausible |
| Outcome | Intent Record + Preliminary AI Qualification Decision |
| Primary Inputs | Business need, intended value, consumers, intended intelligence proposition |
| Core Activities | Define purpose/value; identify proposed value-bearing essence; state distinct intelligence proposition; establish direct/transitive AI Primitive hypothesis |
| Processing Type | AIPRO declaration + platform-assisted semantic validation |
| Gate | Gate: Preliminary AI Qualification |
| Output Artifacts | Intent Record; Preliminary Qualification Record |
| AIPRO Responsibility | Declare what value is intended and what intelligence proposition is being productized |
| Platform Responsibility | Validate Productness hypothesis, intelligence primacy, semantic coherence and plausible AI Primitive path |
| Failure Modes / Risks | AI-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:
- the candidate can qualify as a Product under BPS;
- artificial intelligence appears to be the value-bearing essence, not merely an enabling or constructional dependency;
- a distinct governed intelligence proposition is being proposed;
- 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 Heading | Stage 2 Definition |
|---|---|
| Stage Number | 2 |
| Stage Name | Authority Confirmation |
| Purpose | Confirm ownership, mandate and accountability for the candidate Product/version |
| Outcome | Authority Decision |
| Primary Inputs | Intent Record, organizational authority context, identity/entitlement evidence |
| Core Activities | Validate AIPRO mandate, domain accountability, publication authority and escalation ownership |
| Gate | Gate: Authority |
| Failure Modes / Risks | Product creation without legitimate ownership or business mandate |
Stage 3 — Intelligence Constitution, Behavior & Topology Profile
| Row Heading | Stage 3 Definition |
|---|---|
| Stage Number | 3 |
| Stage Name | Intelligence Constitution, Behavior & Topology Profile |
| Purpose | Describe what intelligence is intended, how it behaves, and the candidate constitution required to realize it |
| Outcome | Versioned Constitution / Behavior / Topology Profile |
| Primary Inputs | Intent, preliminary qualification, authoritative registries |
| Core Activities | Resolve 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 Artifacts | Constitution Profile; Behavior & Topology Profile |
| Gate | Gate: Constitution & Topology |
| Key Principle | This stage describes and normalizes the candidate graph; it does not yet make the definitive APT/AQE claim |
| Failure Modes / Risks | Unregistered 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 Heading | Stage 4 Definition |
|---|---|
| Stage Number | 4 |
| Stage Name | Effective Risk Computation |
| Purpose | Compute evidence-backed R0–R4 risk from the ontology/context that currently exists |
| Outcome | Risk Decision Record + Risk Driver Assessment |
| Primary Inputs | IC, AR, EM, IE, topology, impact evidence, intended uses, preliminary dependency information |
| Core Activities | Apply AIPS risk floors and contextual risk rules; identify escalation requirements |
| Gate | Gate: Risk Tier |
| Key Principle | Risk is orthogonal to APT and must not be inferred from labels such as “generative” or “agentic” alone |
Stage 5 — Structural Constraints & Escalation
| Row Heading | Stage 5 Definition |
|---|---|
| Stage Number | 5 |
| Stage Name | Constraint Enforcement & Escalation |
| Purpose | Enforce prohibited combinations, hard safety/policy constraints and risk-tier-specific requirements |
| Outcome | Constraint Validation Report; escalation artifact where required |
| Core Activities | Validate topology, authority, agency, embodiment, effects, prohibited uses, policy constraints and mandatory human/physical safety controls |
| Gate | Gate: Constraints |
| Special Case | R4 requires the applicable executive escalation/approval artifact before progression |
Stage 6 — Intelligence Behavior & Evolution Contract (IBEC)
| Row Heading | Stage 6 Definition |
|---|---|
| Stage Number | 6 |
| Stage Name | Intelligence Behavior & Evolution Contract (IBEC) |
| Purpose | Define the enforceable behavioral, effect, evolution and safety contract without assuming that every AI Product learns or serves model inference |
| Outcome | Versioned IBEC |
| Scope | Inputs/effects, execution behavior, permitted actions, human oversight, learning mode, evolution mechanisms, quality/evaluation, safety and prohibited behavior |
| Core Activities | Declare behavioral invariants, evolution posture, validation obligations, effect/action boundaries and control requirements |
| Gate | Gate: Intelligence Behavior Contract |
| Failure Modes / Risks | Unbounded 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 Heading | Stage 7 Definition |
|---|---|
| Stage Number | 7 |
| Stage Name | Ontology & Governance Compilation |
| Lifecycle Phase | Authoritative compilation |
| Purpose | Compile Stages 0–6 plus authoritative registries into the resolved Product ontology and enforceable governance posture |
| Outcome | Definitive AQE + resolved APT + derivation topology + Governance Obligation Profile + compiled governance stack |
| Primary Inputs | Intent, authority, constitution profile, risk decision, constraints, IBEC, authoritative registries |
| Core Activities | Resolve 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 Type | Platform / Product Factory Intelligence compilation |
| Gates | Gate: Definitive AI Qualification; Gate: Governance Compilation |
| Failure Modes / Risks | No 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 Heading | Stage 8 Definition |
|---|---|
| Stage Number | 8 |
| Stage Name | AIPROD Finalization |
| Purpose | Finalize the immutable semantic descriptor for the exact AI Product version compiled at Stage 7 |
| Outcome | AIPROD version |
| Core Activities | Bind Product identity/version, intelligence proposition, AQE, APT/topology, IC/CS/PU/MO/IE/AR/EM, R0–R4 risk and Governance Obligation Profile |
| Gate | Gate: AIPROD Finalization |
| Key Principle | AIPROD records the compiled ontology; it does not self-declare or recompute a contradictory one |
Stage 9 — AIPDS Generation
| Row Heading | Stage 9 Definition |
|---|---|
| Stage Number | 9 |
| Stage Name | AIPDS Generation |
| Purpose | Generate the version-specific operational realization of the qualified AI Product |
| Outcome | AIPDS version |
| Core Activities | Bind exact AI Product version and dependencies; compile execution/evolution configuration; bind Governance Obligation Profile to enforceable controls; configure observability and safety |
| Gate | Gate: AIPDS Generation |
| Key Principle | Execution 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 Heading | Stage 10 Definition |
|---|---|
| Stage Number | 10 |
| Stage Name | Deploy, Register & Publish Trust |
| Purpose | Materialize the Product, register it, expose governed discovery/consumption surfaces and publish trust evidence |
| Outcome | Running deployment + Catalog/Marketplace registration + AIPS-DPP |
| Core Activities | Provision 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 Dependencies | Product Catalog/Registry, Marketplace, entitlement/access services, lineage, observability, FinOps, trust/signing services |
| Gate | Gate: Promotion + Marketplace Eligibility |
| Promotion Preconditions | AI qualification CURRENT; dependency currentness CURRENT; governance profile current and controls bound; assurance sufficient; deployment validation successful |
| Marketplace Preconditions | Listing kind and Product Family agree; AIPS-DPP is valid; trust currentness satisfies policy; exact consumption ports are bound to the Product version |
| Key Principle | Publication 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 Heading | Stage 11 Definition |
|---|---|
| Stage Number | 11 |
| Stage Name | Continuous Assurance & Evolution |
| Purpose | Continuously validate runtime behavior, consumption fitness, realized value, safety and the current truth of Product qualification/governance claims |
| Outcome | Assurance signals, COVP evidence, currentness state, impact events and controlled evolution intents |
| Scope | Runtime quality, behavior, usage, consumer feedback, contextual fitness, value realization, incidents, dependency changes, qualification currentness, governance currentness, assurance currentness |
| Core Activities | Observe 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 Artifacts | COVP Observation Set; Assurance Evidence; Currentness Record; Change/Impact Record; Evolution Intent |
| Feedback Loop | Re-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
| Change | Typical earliest re-entry |
|---|---|
| Business purpose / value proposition changes, including persistent value-realization gap | Stage 1 |
| Ownership / mandate changes | Stage 2 |
| IC, AR, EM, IE, topology or constitution changes | Stage 3 |
| Risk evidence changes without constitution change, including material adverse-use evidence | Stage 4 |
| Policy / hard-constraint change | Stage 5 |
| Behavior/evolution contract changes | Stage 6 |
| AI Primitive or upstream AI Product version changes | Stage 7 at minimum, and Stage 3 if constitution intent also changes |
| AIPROD-only publication metadata correction with unchanged semantics | Stage 8 subject to immutability/versioning rules |
| Deployment-only realization change with unchanged Product semantics | Stage 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
| Stage | Primary gate | Principal evidence/output |
|---|---|---|
| 0 | Preconditions | Precondition Report |
| 1 | Preliminary AI Qualification | Intent + preliminary qualification |
| 2 | Authority | Authority Decision |
| 3 | Constitution & Topology | Constitution/Behavior/Topology Profile |
| 4 | Risk Tier | Risk Decision + drivers |
| 5 | Constraints | Constraint Report / escalation |
| 6 | Intelligence Behavior Contract | IBEC |
| 7 | Definitive AI Qualification + Governance Compilation | AQE + APT + derivation topology + Governance Obligation Profile |
| 8 | AIPROD Finalization | Immutable AIPROD |
| 9 | AIPDS Generation | Immutable AIPDS |
| 10 | Promotion | Deployment + registration + AIPS-DPP |
| 11 | Continuous Assurance | currentness + 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.