Skip to main content

PVEP Experience Zones

1. Purpose​

The ProductVerse Experience Plane (PVEP) is organized into a set of experience zones. Each zone represents a distinct mode through which consumers, organizations, applications, AI agents, institutional agents, and products-as-consumers interact with the ProductVerse.

The zones are not separate products or mandatory applications. They are architectural areas of experience capability. A real implementation may realize multiple zones in a single portal, marketplace, agentic interface, dashboard, workbench, or embedded experience.

PVEP experience zones help UPOS distinguish between different forms of consumer-side product interaction:

  • discovering products,
  • evaluating products,
  • acquiring or requesting access,
  • consuming products,
  • navigating product relationships,
  • managing portfolio and entitlement state,
  • selecting and assembling product sets,
  • understanding trust and governance posture,
  • transitioning to PDEP when the intent becomes product creation.

The experience zones provide a structured way to design PVEP without collapsing it into a single marketplace or confusing it with the product-building responsibilities of PDEP.

2. Experience Zone Model​

PVEP contains seven primary experience zones.

ProductVerse Experience Plane (PVEP)
├─ Marketplace Experience Zone
├─ Consumption Experience Zone
│  └─ Consumer Experience Plane (CEP)
├─ Concierge & Agentic Discovery Zone
├─ Product Graph Navigation Zone
├─ Portfolio & Entitlement Experience Zone
├─ Product Select & Assembly Zone
└─ Governance & Trust Experience Zone

Each zone has a distinct architectural role, but the zones are designed to work together.

For example, a consumer may begin with a concierge request, review recommended products in a marketplace experience, inspect trust signals, check entitlement status, consume an output port, select related products into a product set, and then transition to PDEP if the intent becomes product creation.

3. Design Logic of the Zones​

The PVEP zones are based on the principle that consumers do not interact with products in only one way.

A product may be:

  • discovered,
  • evaluated,
  • acquired,
  • consumed,
  • compared,
  • trusted,
  • selected,
  • assembled into a candidate product set,
  • connected to other products,
  • governed,
  • replaced by substitutes,
  • paired with complements,
  • used as an input to future product creation.

The experience zone model separates these modes so that UPOS can assign clear responsibilities and architectural boundaries.

The most important boundary is with PDEP:

PVEP supports consumer-side selection, evaluation, consumption, navigation, and intent capture. PDEP owns product building, product composition, artifact generation, validation, versioning, and publication.

4. Marketplace Experience Zone​

4.1 Definition​

The Marketplace Experience Zone supports browse-first product discovery, evaluation, acquisition, onboarding, and commercial or organizational exchange.

It is the zone most similar to conventional product marketplaces, app stores, data marketplaces, model marketplaces, content marketplaces, or internal enterprise product catalogs.

However, within UPOS, the marketplace is only one zone of PVEP. It does not represent the entire ProductVerse experience.

4.2 Purpose​

The purpose of the Marketplace Experience Zone is to help consumers find, understand, compare, acquire, subscribe to, or request access to products.

4.3 Typical Capabilities​

Typical capabilities include:

  • product listings,
  • product search,
  • product filtering,
  • product detail pages,
  • product comparison,
  • provider profiles,
  • ratings and reviews,
  • pricing and licensing information,
  • subscription and acquisition flows,
  • trial or sandbox access,
  • product recommendations,
  • marketplace rankings,
  • onboarding flows,
  • access request initiation,
  • commercial terms,
  • usage terms,
  • product availability indicators.

4.4 Product Information Displayed​

The zone may display:

  • product name,
  • product description,
  • product category,
  • product type,
  • provider or owner,
  • available output ports,
  • usage patterns,
  • pricing model,
  • license terms,
  • subscription model,
  • quality indicators,
  • maturity indicators,
  • trust signals,
  • Digital Product Passport summary,
  • entitlement eligibility,
  • policy constraints,
  • support information,
  • related products.

4.5 Example Interactions​

Examples include:

  • A user searches for a trusted payment-risk data product.
  • A team compares three AI products for anomaly detection.
  • An agent filters products that are usable for a specific jurisdiction.
  • A consumer subscribes to a product.
  • A business user requests access to a restricted product.
  • A procurement agent compares cost, usage terms, and entitlement eligibility.

4.6 Key Artifacts​

The Marketplace Experience Zone may create, consume, or display:

  • Product Listing,
  • Product Detail View,
  • Product Comparison View,
  • Product Evaluation Signal,
  • Access Request,
  • Subscription Request,
  • Trial Request,
  • Marketplace Activity Signal,
  • Consumption Intent Record, when discovery is intent-driven.

4.7 Boundaries​

The Marketplace Experience Zone does not own product runtime, product building, product validation, governance decisions, or entitlement authority.

It may initiate acquisition or access flows, but authoritative entitlement decisions come from entitlement services and the Governance Kernel.

5. Consumption Experience Zone​

5.1 Definition​

The Consumption Experience Zone supports the direct use of products through appropriate consumer-facing experiences.

This zone is the home of the Consumer Experience Plane (CEP) as a specialized sub-plane within PVEP.

5.2 Purpose​

The purpose of the Consumption Experience Zone is to allow entitled consumers to use product output ports, services, content, capabilities, insights, or interfaces in ways that are meaningful to their roles and tasks.

5.3 Typical Capabilities​

Typical capabilities include:

  • dashboards,
  • reports,
  • readers,
  • notebooks,
  • SQL workbenches,
  • API consoles,
  • file download experiences,
  • analytical applications,
  • inference playgrounds,
  • simulation interfaces,
  • embedded application views,
  • agent-facing tool interfaces,
  • product-specific viewers,
  • product usage monitoring,
  • feedback capture,
  • support requests,
  • consumption guidance,
  • contextual trust and policy display.

5.4 Product Output Ports​

Consumption experiences may interact with product output ports such as:

  • APIs,
  • SQL endpoints,
  • event streams,
  • batch extracts,
  • files,
  • dashboards,
  • model inference endpoints,
  • reader views,
  • agent tools,
  • visual interfaces,
  • embedded services.

The experience consumes the output port; it does not redefine the product.

5.5 Example Interactions​

Examples include:

  • A data analyst opens a governed SQL workbench for a Data Product.
  • A business user views a dashboard powered by a Data Product.
  • A compliance analyst reviews an evidence package.
  • A reader consumes a Comic Product in a reader interface.
  • An AI agent invokes an API output port.
  • A developer tests a product API using an API console.
  • A user runs inference against an AI Product in a controlled playground.

5.6 Key Artifacts​

The Consumption Experience Zone may create, consume, or display:

  • Consumption Session,
  • Usage Record,
  • Consumption Feedback Record,
  • Runtime Interaction Log,
  • Value Signal,
  • Error Signal,
  • Support Request,
  • Product Usage Context,
  • Output Port Invocation Record.

5.7 Boundaries​

The Consumption Experience Zone does not create or publish new products.

If a consumer uses consumed product outputs to define a new reusable, governed, publishable product, the flow must transition to PDEP.

The key principle is:

Consumption experiences consume product ports; product creation belongs to PDEP.

6. Concierge & Agentic Discovery Zone​

6.1 Definition​

The Concierge & Agentic Discovery Zone supports intent-first discovery across the ProductVerse.

Instead of requiring consumers to browse or search manually, this zone allows them to express a need, question, goal, constraint, or desired outcome. A concierge, recommender, AI agent, institutional agent, or discovery service then helps identify suitable products or product sets.

6.2 Purpose​

The purpose of this zone is to translate consumer intent into product discovery, recommendation, evaluation, and guided next actions.

6.3 Typical Capabilities​

Typical capabilities include:

  • natural-language product discovery,
  • guided product recommendation,
  • policy-aware product matching,
  • trust-aware product matching,
  • entitlement-aware recommendation,
  • context-aware discovery,
  • semantic search,
  • conversational product discovery,
  • institutional agent discovery,
  • personal-shopper-style product assistance,
  • product substitute suggestions,
  • product complement suggestions,
  • candidate product-set recommendation,
  • intent refinement,
  • explanation of recommendations,
  • handoff to marketplace, graph, consumption, portfolio, or PDEP flows.

6.4 Consumption Intent Record​

This zone is a natural origin point for the Consumption Intent Record (CIR).

A CIR may capture:

  • consumer identity or subject context,
  • role,
  • organizational context,
  • business purpose,
  • desired outcome,
  • constraints,
  • jurisdiction,
  • policy context,
  • trust requirements,
  • cost constraints,
  • freshness requirements,
  • quality expectations,
  • preferred product type,
  • usage mode,
  • required output port type.

However, CIR creation is not exclusive to this zone. A CIR may also arise in marketplace flows, embedded consumption flows, product graph navigation, portfolio workflows, or product select and assembly flows.

6.5 Example Interactions​

Examples include:

  • “Find me a reliable customer-risk data product for EU reporting.”
  • “Recommend a low-cost substitute for this AI Product.”
  • “Which products am I entitled to use for payment surveillance?”
  • “Find products that can be used together for regulatory evidence generation.”
  • “Suggest a product set for synthetic data generation.”
  • “Show me products with strong trust posture and no cross-border restrictions.”

6.6 Key Artifacts​

The Concierge & Agentic Discovery Zone may create, consume, or display:

  • Consumption Intent Record,
  • Intent Refinement Record,
  • Recommendation Set,
  • Product Match Explanation,
  • Candidate Product Set,
  • Discovery Session,
  • Policy-Aware Match Result,
  • Trust-Aware Match Result,
  • PDEP Transition Candidate.

6.7 Boundaries​

The Concierge & Agentic Discovery Zone guides consumers and agents, but it does not become the source of truth for governance decisions, product metadata, or product creation.

Its recommendations must be grounded in authoritative product, entitlement, trust, and governance data.

7. Product Graph Navigation Zone​

7.1 Definition​

The Product Graph Navigation Zone allows consumers and agents to explore the ProductVerse as a connected topology of productized entities and relationships.

This zone makes visible the fact that products are not isolated catalog entries. They exist within networks of dependency, provenance, composition, substitution, complementarity, entitlement, policy, trust, and usage.

7.2 Purpose​

The purpose of this zone is to help consumers understand product relationships, product impact, product context, and product topology.

7.3 Typical Capabilities​

Typical capabilities include:

  • product relationship visualization,
  • graph exploration,
  • dependency navigation,
  • upstream and downstream lineage,
  • product provenance views,
  • substitute discovery,
  • complement discovery,
  • bundle exploration,
  • product chain exploration,
  • product ecosystem views,
  • domain constellation views,
  • provider network views,
  • product-to-policy navigation,
  • product-to-DPP navigation,
  • product-to-agent relationship navigation,
  • product-to-marketplace navigation,
  • impact analysis,
  • relationship filtering,
  • topology projection selection.

7.4 ProductVerse Topologies​

The Product Graph Navigation Zone may expose different views of the ProductVerse, such as:

  • Product Graph,
  • Product Web,
  • Product Mesh,
  • Product Fabric,
  • Product Marketplace,
  • Product Ecosystem,
  • Product Constellation,
  • Product Chain,
  • Product Flow,
  • Product Portfolio,
  • Product Dependency Map.

These topologies are not alternatives to the ProductVerse. They are projections or structural interpretations within the ProductVerse.

7.5 Example Interactions​

Examples include:

  • A consumer explores what products depend on a Data Product.
  • A governance user reviews downstream products affected by a policy change.
  • An agent finds substitutes for a product that has a low trust score.
  • A product owner investigates which products consume their output ports.
  • A user explores a product chain from raw data to an AI insight product.
  • A consumer identifies products commonly bundled with a selected product.

7.6 Key Artifacts​

The Product Graph Navigation Zone may create, consume, or display:

  • Product Relationship View,
  • Product Graph Projection,
  • Dependency Map,
  • Lineage View,
  • Impact Analysis View,
  • Substitute Set,
  • Complement Set,
  • Bundle View,
  • Product Chain View,
  • Product Ecosystem View,
  • Relationship Exploration Signal.

7.7 Boundaries​

This zone visualizes and navigates product relationships. It does not itself become the authoritative product relationship registry unless explicitly integrated with governed registry workflows.

Authoritative relationship records remain in product relationship services, registries, lineage systems, or governance repositories.

8. Portfolio & Entitlement Experience Zone​

8.1 Definition​

The Portfolio & Entitlement Experience Zone helps consumers, teams, organizations, applications, and agents understand their relationship to products.

It answers questions such as:

  • What products do I have?
  • What products can I access?
  • What products am I denied from using?
  • What products are pending approval?
  • What products are expiring?
  • What products do my agents use?
  • What products are in my organization’s portfolio?
  • What obligations apply to my product usage?

8.2 Purpose​

The purpose of this zone is to provide subject-centric visibility into product access, ownership, entitlement, subscription, usage, cost, and obligation state.

8.3 Typical Capabilities​

Typical capabilities include:

  • personal product portfolio,
  • team product portfolio,
  • organization product portfolio,
  • agent product portfolio,
  • subscribed products,
  • purchased products,
  • licensed products,
  • accessible products,
  • denied products,
  • pending access requests,
  • expiring entitlements,
  • renewal workflows,
  • revocation workflows,
  • usage quotas,
  • consumption limits,
  • cost and chargeback views,
  • FinOps views,
  • product access history,
  • entitlement explainability,
  • access request workflows,
  • portfolio governance.

8.4 Example Interactions​

Examples include:

  • A user views all products they are allowed to consume.
  • A manager reviews products used by a team.
  • An institutional agent checks its delegated product access.
  • A finance user reviews product usage cost.
  • A consumer renews an expiring product entitlement.
  • A governance user reviews access patterns for restricted products.
  • A product owner sees which organizations are subscribed to their product.

8.5 Key Artifacts​

The Portfolio & Entitlement Experience Zone may create, consume, or display:

  • Entitlement Record,
  • Access Request,
  • Access Decision View,
  • Subscription Record,
  • License Record,
  • Product Holding,
  • Portfolio View,
  • Usage Quota View,
  • Cost and Chargeback View,
  • Renewal Request,
  • Revocation Request,
  • Subject-Product Relationship Record.

8.6 Boundaries​

This zone renders and manages consumer-facing entitlement experiences. It does not become the authoritative identity, access, policy, or entitlement engine.

Authoritative decisions come from identity services, entitlement services, policy engines, and the Governance Kernel.

9. Product Select & Assembly Zone​

9.1 Definition​

The Product Select & Assembly Zone supports consumer-side product selection, grouping, shortlisting, comparison, and preparation of product sets for a purpose.

This zone allows consumers to assemble candidate product sets without implying that PVEP is responsible for product creation.

9.2 Purpose​

The purpose of this zone is to allow consumers, organizations, and agents to select products into meaningful sets for use, evaluation, acquisition, portfolio management, or potential transition to PDEP.

It supports selection and assembly intent, not governed product composition.

9.3 Typical Capabilities​

Typical capabilities include:

  • product shortlisting,
  • product carts,
  • product collections,
  • candidate product sets,
  • side-by-side comparison,
  • purpose-based grouping,
  • use-case-based selection,
  • constraint capture,
  • trust posture review,
  • entitlement posture review,
  • cost and feasibility preview,
  • product-set notes,
  • product-set sharing,
  • product-set approval initiation,
  • handoff to consumption flows,
  • handoff to acquisition flows,
  • handoff to PDEP when creation intent emerges.

9.4 Product Set Intent​

The primary artifact of this zone is a Product Set Intent.

A Product Set Intent may capture:

  • selected products,
  • purpose,
  • intended usage,
  • consumer context,
  • assumptions,
  • constraints,
  • required output ports,
  • entitlement posture,
  • trust posture,
  • cost considerations,
  • business outcome,
  • whether the product set is for consumption, evaluation, acquisition, or product creation.

If the intent becomes product creation, the Product Set Intent may become part of a PDEP Transition Package.

9.5 Example Interactions​

Examples include:

  • A consumer selects several data products for a reporting scenario.
  • An agent assembles a candidate product set for payment surveillance.
  • A team creates a product cart for procurement review.
  • A user groups a data product, AI product, and dashboard product for evaluation.
  • An organization compares two product-set options for cost and compliance posture.
  • A consumer initiates a PDEP transition to create a new governed product from selected inputs.

9.6 Key Artifacts​

The Product Select & Assembly Zone may create, consume, or display:

  • Product Set Intent,
  • Product Shortlist,
  • Product Cart,
  • Product Collection,
  • Candidate Product Set,
  • Product-Set Comparison View,
  • Preliminary Feasibility View,
  • PDEP Transition Package,
  • Product Selection Signal.

9.7 Boundaries​

The Product Select & Assembly Zone does not own product creation.

The key boundary is:

PVEP supports product selection and assembly intent. PDEP owns product composition and product building.

PVEP may help consumers assemble a candidate set of products, but PDEP is responsible for:

  • product authoring,
  • product composition,
  • semantic design,
  • artifact generation,
  • validation,
  • versioning,
  • publication,
  • lifecycle management.

10. Governance & Trust Experience Zone​

10.1 Definition​

The Governance & Trust Experience Zone exposes governance, policy, trust, assurance, accountability, and compliance information in consumer- and agent-usable form.

It is the PVEP-facing interpretation layer for Governance Kernel outputs.

10.2 Purpose​

The purpose of this zone is to help consumers answer questions such as:

  • Can I trust this product?
  • Am I allowed to use this product?
  • For what purpose can I use it?
  • What restrictions apply?
  • Who owns or stewards this product?
  • What evidence supports its claims?
  • What is the risk level?
  • What is the quality or maturity posture?
  • What obligations apply to my usage?

10.3 Typical Capabilities​

Typical capabilities include:

  • Digital Product Passport views,
  • trust badges,
  • maturity indicators,
  • certification views,
  • policy explainability,
  • entitlement explainability,
  • access rationale,
  • usage constraint display,
  • allowed-use and prohibited-use display,
  • data quality views,
  • model quality views,
  • AI risk tier display,
  • compliance posture,
  • lineage and provenance summaries,
  • evidence summaries,
  • audit evidence views,
  • exception status,
  • stewardship information,
  • ownership information,
  • accountability views,
  • obligation summaries.

10.4 Governance Kernel Relationship​

The Governance & Trust Experience Zone does not compute governance authority. It renders the state produced by the Governance Kernel and related authoritative services.

The Governance Kernel may provide:

  • policy decisions,
  • entitlement decisions,
  • risk tier,
  • trust posture,
  • quality status,
  • maturity state,
  • compliance status,
  • DPP state,
  • evidence state,
  • lineage and provenance,
  • permitted usage,
  • prohibited usage,
  • obligations and constraints.

PVEP turns this into clear, actionable experience.

10.5 Example Interactions​

Examples include:

  • A user opens the Digital Product Passport for a product.
  • An agent checks whether a product can be used for a specific purpose.
  • A consumer reviews an AI Product’s risk tier.
  • A data consumer reviews quality and freshness signals.
  • A governance user reviews evidence attached to a product.
  • A user requests an exception when a product is not currently permitted for a purpose.
  • A consumer compares trust posture across substitute products.

10.6 Key Artifacts​

The Governance & Trust Experience Zone may create, consume, or display:

  • DPP View,
  • Trust Signal,
  • Risk View,
  • Policy Explanation,
  • Entitlement Explanation,
  • Compliance View,
  • Evidence Summary,
  • Quality Scorecard,
  • Maturity View,
  • Exception Request,
  • Usage Constraint View,
  • Stewardship View.

10.7 Boundaries​

This zone explains and displays governance state. It does not become the authoritative governance engine.

The key principle is:

The Governance Kernel is the decision and assurance engine. PVEP is the experiential interpretation layer.

11. Cross-Zone Journeys​

PVEP zones are designed to operate together.

11.1 Discover, Evaluate, and Acquire​

Concierge & Agentic Discovery
  → Marketplace Experience
  → Governance & Trust Experience
  → Portfolio & Entitlement Experience

A consumer expresses an intent, receives recommended products, evaluates product details and trust posture, and requests access or acquisition.

11.2 Consume and Provide Feedback​

Portfolio & Entitlement Experience
  → Consumption Experience
  → Governance & Trust Experience
  → Consumption Feedback Record

An entitled consumer accesses a product, consumes it through a suitable interface, sees relevant usage constraints, and provides feedback.

11.3 Navigate and Select​

Product Graph Navigation
  → Marketplace Experience
  → Product Select & Assembly
  → Governance & Trust Experience

A consumer explores related products, evaluates them, selects a candidate set, and checks policy, trust, and entitlement posture.

11.4 Select and Transition to PDEP​

Product Select & Assembly
  → PDEP Transition Package
  → PDEP

A consumer assembles a product set and decides to create a governed product. At that point, the flow transitions to PDEP.

11.5 Trust-Aware Discovery​

Concierge & Agentic Discovery
  → Governance & Trust Experience
  → Marketplace Experience
  → Product Select & Assembly

An agent recommends products only if they meet policy, risk, quality, entitlement, and trust constraints.

12. Experience Zone Interdependencies​

The zones are distinct but interdependent.

ZoneDepends OnProvides
Marketplace ExperienceProduct metadata, listings, trust signals, entitlement eligibilityDiscovery, comparison, acquisition signals
Consumption ExperienceEntitlements, output ports, runtime access, usage constraintsUsage records, feedback, value signals
Concierge & Agentic DiscoveryIntent, product metadata, graph, trust, policy, recommendationsCIR, recommendations, guided next actions
Product Graph NavigationProduct relationships, lineage, dependencies, topology dataRelationship views, impact analysis, substitute/complement discovery
Portfolio & EntitlementIdentity, entitlement, access, subscription, usage, cost dataPortfolio visibility, access workflows, entitlement awareness
Product Select & AssemblyCandidate products, intent, trust, entitlement, graph dataProduct-set intent, selection signals, PDEP transition package
Governance & TrustGovernance Kernel, DPP, policy, risk, evidence, quality dataTrust interpretation, policy explainability, decision support

13. Common Actor Patterns​

Different actors may use the same zones differently.

13.1 Human Consumer​

A human consumer may search, compare, consume, review trust, request access, and select products into a product set.

13.2 Organizational Consumer​

An organization may manage product portfolios, review subscriptions, govern access, track value, and approve product sets.

13.3 Application Consumer​

An application may discover products through APIs, check entitlements, consume output ports, and emit usage signals.

13.4 AI / Agentic Consumer​

An AI agent may use machine-readable product descriptors, policy-aware discovery, entitlement checks, DPP retrieval, and runtime output ports.

13.5 Institutional Agent​

An institutional agent may act with delegated authority, requiring authority profiles, audit trails, policy-bound actions, and supervisor relationships.

13.6 Product as Consumer​

A product may consume another product as an input, dependency, or service. In such cases, PVEP may expose machine-oriented discovery, entitlement, and relationship navigation capabilities.

14. Implementation Guidance​

A UPOS implementation does not need to build seven separate applications.

The zones may be implemented as:

  • separate applications,
  • modules within a unified portal,
  • marketplace tabs,
  • embedded widgets,
  • APIs,
  • agent tools,
  • graph explorers,
  • dashboards,
  • workbenches,
  • mobile experiences,
  • workflow steps,
  • contextual panels.

The architectural requirement is not physical separation. The requirement is clear responsibility separation.

For example:

  • A marketplace page may include trust signals from the Governance & Trust Experience Zone.
  • A graph explorer may allow product selection into the Product Select & Assembly Zone.
  • A consumption dashboard may show entitlement and policy context.
  • A concierge agent may route the user into marketplace, graph, portfolio, or PDEP transition workflows.

15. Anti-Patterns​

PVEP should avoid the following anti-patterns.

15.1 Marketplace as the Whole ProductVerse​

Treating the marketplace as the entire experience plane hides consumption, trust, graph navigation, portfolio, entitlement, and agentic discovery needs.

15.2 PVEP as Product Builder​

Allowing PVEP to author, compose, validate, version, or publish governed products collapses the boundary with PDEP.

15.3 Trust as UI Decoration​

Displaying manually curated trust badges without Governance Kernel backing creates weak and potentially misleading governance experiences.

15.4 Entitlement-Blind Discovery​

Recommending or displaying products without considering access rights, policy constraints, and usage limitations may create poor or non-compliant user experiences.

15.5 Human-Only Design​

Designing PVEP only for human portals ignores applications, AI agents, institutional agents, and products-as-consumers.

15.6 Flat Catalog Thinking​

Representing products only as list items misses the ProductVerse reality of product relationships, dependencies, substitutes, complements, bundles, chains, and ecosystems.

16. Summary​

PVEP experience zones provide a structured model for consumer-side interaction with the ProductVerse.

The seven zones are:

  1. Marketplace Experience Zone - discover, evaluate, acquire, and onboard products.
  2. Consumption Experience Zone - use products through output ports and consumer interfaces.
  3. Concierge & Agentic Discovery Zone - express intent and receive guided, policy-aware product recommendations.
  4. Product Graph Navigation Zone - explore product relationships and ProductVerse topologies.
  5. Portfolio & Entitlement Experience Zone - understand product holdings, rights, subscriptions, access, obligations, usage, and cost.
  6. Product Select & Assembly Zone - select and group product sets for a purpose, while handing product creation to PDEP.
  7. Governance & Trust Experience Zone - understand trust, policy, risk, quality, evidence, accountability, and permitted usage.

Together, these zones make the ProductVerse visible, navigable, trustworthy, and usable.

The essential boundary remains:

PVEP is where consumers experience and select products. PDEP is where products are built.