Skip to main content

CEP Overlays — Consumer Experience Plane Projection Model


1. Purpose​

The Consumer Experience Plane (CEP) Overlay Model defines how a single, invariant product-consumption lifecycle is interpreted across personas and interaction modalities without changing Product ontology or duplicating the underlying flow.

CEP enables:

  • a unified consumption model across Data, Information, AI, Service and other HDIP-aligned Products;
  • persona-specific experiences without redefining Product Family;
  • explicit separation of discovery, acquisition/entitlement, consumption, experience, and post-consumption observation/value;
  • AI-specific trust, agency and Physical-AI interaction projections where relevant.

2. Core Principle​

Consumption flow is invariant. Experience is polymorphic.

  • SSCF (Self-Service Consumption Flow) defines how governed consumption happens.
  • CEP Overlay defines what each lifecycle node means for a particular persona and interaction context.
  • Marketplace supports discovery and acquisition; it is not the Product execution layer.
  • COVP observes usage, fitness, feedback and realized value after consumption; it does not redefine Product ontology.

3. Formal Definition​

A CEP Overlay is:

A semantic projection layer that maps invariant consumption-lifecycle nodes to persona-specific interaction models, trust interpretations, value semantics and usage patterns while preserving the authoritative Product Family, version and contracts.

CEP never turns a Model Product or an AI-enabled Product into an AI Product merely because an AI-oriented persona consumes it.


4. Architectural Pattern​

4.1 Separation of concerns​

LayerResponsibility
Product ontology / AIPRODDefines what the Product version is
MarketplaceDiscovery, comparison and acquisition/entitlement projection
AIPDS / Product portsProvides governed operational interfaces/packages
SSCFDefines the invariant consumption lifecycle
CEP OverlayProjects persona-specific interaction and experience semantics
COVPObserves usage, feedback, contextual fitness and realized value

4.2 Invariant consumption path​

The lifecycle is invariant; the experience projection changes with persona, Product Family, interaction mode and intended use.


5. Canonical CEP Personas​

5.1 Business / Decision Persona​

Intent Type: Decision-making and business outcomes
Interaction Model: Low technical abstraction
Primary Focus: Value, outcomes, confidence and governance

AspectInterpretation
ExperienceDashboards, narratives, alerts, recommendations
ValueBusiness outcome, fitness, realized value
TrustQualification, explainability, governance, currentness
InteractionGuided, outcome-oriented

5.2 Analytical / Information Persona​

Intent Type: Exploration and information analysis
Interaction Model: Query / analytical workflow
Primary Focus: Information utility, semantics and evidence

AspectInterpretation
ExperienceQuery, notebook, analytical view, report
ValueInformation utility and decision support
TrustQuality, semantics, lineage, freshness
InteractionFlexible, exploratory

5.3 AI / Intelligence Engineering Persona​

Intent Type: Build, integrate, evaluate or evolve intelligence capabilities
Interaction Model: Product, evaluation and execution workflows
Primary Focus: Intelligence behavior, fitness, dependencies and assurance

AspectInterpretation
ExperienceAI Product ports, Model Products, evaluation harnesses, rule/knowledge tools, agent/plan traces
ValueIntelligence fitness, quality, reuse and controlled evolution
TrustAQE/currentness, APT, dependency provenance, evaluation/assurance evidence
InteractionIterative and mechanism-aware; not limited to model training

This persona covers learned-model, symbolic/reasoning, agentic, hybrid and Physical-AI engineering. Model building is one possible activity, not the definition of the persona.

5.4 System / API Integration Persona​

Intent Type: Programmatic integration
Interaction Model: API, event, package or embedded interface
Primary Focus: Contract reliability, compatibility and performance

AspectInterpretation
ExperienceAPIs, events, packages, streams, embedded ports
ValueReliable machine-to-machine outcomes
TrustContract/version compatibility, SLOs, currentness
InteractionAutomated, deterministic at the contract boundary

5.5 Agentic / Workflow Persona​

Intent Type: Multi-step orchestration, reasoning and goal pursuit
Interaction Model: Workflow / agent-mediated
Primary Focus: Controlled outcome execution

AspectInterpretation
ExperienceTool use, workflow execution, plans, delegated tasks
ValueOutcome efficiency and completion quality
TrustBounded agency, permitted actions, evidence, intervention/override controls
InteractionDynamic, multi-step, adaptive

5.6 Operator / Physical-AI Persona​

Intent Type: Operate, supervise or intervene in embodied intelligence
Interaction Model: Human-machine operational control
Primary Focus: Physical safety, mission state, intervention and recovery

AspectInterpretation
ExperienceOperator console, mission view, physical-state telemetry, intervention controls
ValueSafe and effective physical-world task completion
TrustEmbodiment (EM), agency (AR), physical effect (IE), safety controls and currentness
InteractionSupervisory, intervention-capable, sometimes continuous

6. Node-Level Semantic Projection​

CEP overlays operate at the node level of the invariant consumption lifecycle.

6.1 Discovery​

PersonaProjection
BusinessOutcome, intended use, trust and value evidence
AnalyticalSemantic scope, content, quality and lineage
AI / Intelligence EngineeringListing kind, APT, IC, dependencies, AQE and assurance
System / APIPort/package contracts and compatibility
Agentic / WorkflowTool/action affordances and agency boundaries
Operator / Physical AIEmbodiment, physical effects and safety envelope

Discovery preserves marketplace listing-kind boundaries: AI Product, Model Product and AI-enabled Product are not interchangeable.

6.2 Consumption Port / Package​

PersonaProjection
BusinessGoverned application/experience
AnalyticalQuery/view/export contract
AI / Intelligence EngineeringAI Product interface, Model Product package, evaluation or knowledge/rule interface
System / APIAPI/event/package contract
Agentic / WorkflowTool/action contract
Operator / Physical AICommand, telemetry and intervention boundary

6.3 Experience​

PersonaProjection
BusinessDashboard, recommendation, narrative, alert
AnalyticalQuery, notebook, analytical information view
AI / Intelligence EngineeringEvaluation, reasoning/plan trace, intelligence execution or controlled evolution workflow
System / APIAPI/event interaction
Agentic / WorkflowGoal/task execution and tool orchestration
Operator / Physical AIMission and physical-world supervision

6.4 Usage / Feedback Signals​

PersonaProjection
BusinessAdoption, feedback, intended-use fitness
AnalyticalQuery/use patterns and information utility feedback
AI / Intelligence EngineeringEvaluation evidence, behavior/quality signals, dependency/evolution observations
System / APICalls, events, SLO/SLA observations
Agentic / WorkflowRuns, interventions, action/tool outcomes
Operator / Physical AIMissions, overrides, incidents, safe-state transitions

These signals flow to COVP and Continuous Assurance. They do not rewrite PIN, Product Family, APT or risk by popularity.

6.5 Value​

PersonaProjection
BusinessBusiness outcome and realized value
AnalyticalInformation utility and decision contribution
AI / Intelligence EngineeringIntelligence fitness, reuse and quality improvement
System / APIReliability and integration efficiency
Agentic / WorkflowGoal achievement and task efficiency
Operator / Physical AISafe physical task completion and operational effectiveness

COVP records value evidence with explicit attribution confidence; adoption is not itself proof of value.


7. Relationship to Product Families and AI-Ecosystem Listing Kinds​

CEP is Product-Family agnostic. It can project experiences for:

  • Data Products;
  • Information Products;
  • AI Products;
  • Service Products;
  • Physical / Engineered Products;
  • Compound Products;
  • other BPS-recognized Product Families or kinds.

Within the AI ecosystem, CEP must preserve the marketplace distinction between:

  • AI Product — intelligence is the value-bearing essence and AI qualification is current;
  • Model Product — productized learned computational capability;
  • AI-enabled Product — another Product Family remains primary while AI contributes materially.

Product Family does not define the consumption flow; persona and intent shape the experience. Product Family still remains authoritative and must not be overwritten by the experience layer.


8. Relationship to AI Products (AIPS)​

CEP projects, but does not recompute, the AIPS ontology dimensions needed by consumers:

  • APT — Primary / Derived;
  • IC — Intelligence Capability;
  • MO — Interaction / Execution Mode;
  • IE — Intelligence Effect;
  • AR — Agency / Autonomy;
  • EM — Embodiment;
  • RT — R0–R4 Risk Tier;
  • AI qualification and trust currentness.

8.1 Decision and recommendation experiences​

Business and analytical personas may consume intelligence as evidence or recommendations without changing the AI Product's agency classification.

8.2 Agentic experiences​

Agentic/workflow projections expose goals, actions, tools, evidence and intervention boundaries. Agentic interaction does not itself make a Product Derived or Composite.

8.3 Physical-AI experiences​

Operator overlays project embodiment, physical action/effect, safety envelope, telemetry and intervention semantics. Physical embodiment is orthogonal to APT.

8.4 Trust and currentness​

All personas may require trust evidence, but the presentation differs. Trust projection should use current AIPS-DPP and marketplace evidence rather than inventing a persona-specific truth.


9. Relationship to AIPCH Characteristics​

CEP operationalizes several AIPCH characteristics without redefining their normative meaning:

AIPCHConnection
AIPCH05 — DiscoverableMarketplace/CEP exposes governed discovery metadata
AIPCH07 — TrustworthyTrust signals, qualification and currentness are projected to the persona
AIPCH08 — ReusableThe same Product can support multiple governed personas/contexts
AIPCH09 — SLA/SLO Backed & ObservableSystem and operational overlays project reliability and observability
AIPCH13 — Consumption-Driven IntentPersona and intended use provide consumption context
AIPCH19 — Safe & Policy-Bound UsageAgentic/physical/system projections expose enforceable boundaries
AIPCH20 — Interoperable & ComposableCEP can project composition affordances without claiming a new Derived AI Product unless a new Product boundary exists
AIPCH21 — Human-Centered OversightBusiness and operator overlays expose intervention/oversight appropriate to AR/risk/governance obligations

Stage 11 will realign the AIPCH definitions themselves; this page preserves their current identifiers while correcting the CEP mappings.


10. Marketplace, Entitlement, CEP and COVP Boundary​

  • Marketplace answers what can I discover/acquire?
  • Entitlement answers what am I permitted to use?
  • Product port/package is the governed consumption boundary.
  • CEP answers how should this consumption experience be projected for this persona?
  • COVP answers what happened in use, was it fit, and what value was realized?

11. Key Design Outcomes​

11.1 Unified consumption model​

  • one invariant consumption lifecycle;
  • multiple persona interpretations;
  • no duplication of Product ontology.

11.2 Reduced cognitive load​

Consumers interact through familiar paradigms while authoritative Product semantics remain unchanged.

11.3 AI-mechanism neutrality​

CEP supports learned-model, symbolic/reasoning, agentic, hybrid and Physical AI without assuming that AI consumption means model training or inference only.

11.4 Trust-preserving experiences​

Qualification, APT, risk and currentness come from authoritative lifecycle/trust artifacts; CEP only projects them.

11.5 Closed feedback loop​

Consumption evidence flows to COVP and Continuous Assurance, allowing controlled evolution without allowing popularity or feedback to redefine ontology.


12. What CEP Overlay Is Not​

CEP Overlay is not:

  • a UI theme switch;
  • a separate Product ontology;
  • a different lifecycle for every persona;
  • a Product-family reclassification mechanism;
  • the marketplace itself;
  • COVP itself;
  • evidence that an AI-enabled Product is an AI Product.

CEP Overlay is:

A persona-specific semantic and interaction projection over a fixed, governed consumption lifecycle and authoritative Product boundary.


13. Canonical Statement​

The Consumer Experience Plane (CEP) Overlay Model enables a single, invariant governed consumption lifecycle to be interpreted across personas and interaction modalities by projecting authoritative Product, trust and port semantics into persona-appropriate experiences. CEP preserves Product Family and version boundaries, separates discovery/acquisition from consumption, and routes post-consumption evidence to COVP and Continuous Assurance without allowing experience or popularity to redefine Product Intrinsic Nature, AI Product Type or risk.