Skip to main content
HDIP© Self-Service Product Consumption - Spec C (PCON + Platform View)
Step 1 of 8: 1. Declare consumption intent
Consumer (PCON)
Intent-driven consumption. No knowledge of data/AI internals required.
PCON
Product Consumer
actor
1. Declare intent
What / why / context
step
2. Discover products
Search product marketplace
step
3. Evaluate product fit and request access
Meaning + trust (DPP)
step
4. Acquire / onboard
Buy / request access
step
5. Access products
Ports provisioned
step
6. Consume/Experience
CEP interface
Dashboard
🔌🔑📜
step
7. Observe usage & value
Usage + cost + ROI
step
8. Feedback
ROI + issues
step
9. Decide next
Continue / stop / create
step
HDIP Platform
Resolves products, enforces policy, provisions access, computes value.
Intent interpreter + Normalizer
service
Product Discovery Orchestrator
service
Policy & Entitlement Evaluation
🧭🧩
service
Access provisioning
🧩🧭
service
CEP renderer
service
Observability engine
📦
service
FinOps engine
📡📜
service
Feedback processor
🧠📦
service
PDEP Entry
Create / compose product
🧠
event
Product resolution engine
🧭
service
Usage tracking
🔌📜🪟
service
Value computation
📡📦🧭📜
service
Enterprise Services
Marketplace, Policy, Access, CEP, Observability, FinOps.
Product Marketplace
service
Product Catalog
service
Policy Service
service
Access & Entitlements
service
Consumer Experience Plane
service
Observability
service
FinOps
service
Artifacts
Intent, access decisions, usage, cost, value, feedback.
CIR (intent + archetype)
Consumption Intent Record
artifact
Product resolution set
artifact
Access decision
artifact
Usage contract
artifact
Access descriptor
artifact
Consumption views
Aggregated KPIs
artifact
Usage Signals
Consumption patterns
artifact
Cost Records
artifact
Value Signals
ROI
artifact
CFR
Feedback record
artifact
Product Ports
API / SQL / stream / agent interface
artifact
Product Signal Bundle
Usage + cost + value
📡💷📈
artifact
Decision context
Continue / compose
📦
artifact
Note from KaizenXone - Dec 2017: PMDD © Enterprise tests would and should be part of Observability (see docs).