Skip to main content

PVEP Glossary

1. Purpose​

This glossary defines key terms used across the ProductVerse Experience Plane (PVEP) documentation.

PVEP is the UPOS experience mediation plane through which humans, organizations, applications, agents, and products-as-consumers discover, evaluate, acquire, consume, navigate, trust, select, assemble candidate product sets, request access, provide feedback, and transition to PDEP when product creation intent emerges.

This glossary is intended to keep terminology consistent across:

  • pvep-overview.md
  • pvep-architecture.md
  • pvep-experience-zones.md
  • marketplace-experience-zone.md
  • consumption-experience-zone.md
  • concierge-agent-mediated-discovery-zone.md
  • product-graph-navigation-zone.md
  • portfolio-entitlement-experience-zone.md
  • product-select-assembly-zone.md
  • governance-trust-experience-zone.md
  • pvep-pdep-boundary.md
  • pvep-governance-kernel-integration.md
  • pvep-artifacts.md
  • pvep-personas-and-actors.md
  • pvep-journeys.md
  • pvep-reference-model.md

2. Core PVEP Terms​

ProductVerse Experience Plane​

The ProductVerse Experience Plane, abbreviated PVEP, is the UPOS experience mediation plane through which ProductVerse participants discover, evaluate, acquire, consume, navigate, trust, select, assemble candidate product sets, request access, provide feedback, and transition to PDEP when product creation intent emerges.

PVEP is not merely a marketplace, catalog, portal, dashboard, or UI.

It is the governed experience layer between actors and the ProductVerse.

In short:

PVEP = governed experience mediation across the ProductVerse

Experience Mediation​

Experience Mediation is the act of translating ProductVerse entities, governance state, product relationships, output ports, marketplace offers, entitlement state, trust signals, and product journeys into usable human-, agent-, application-, and product-facing experiences.

PVEP mediates experience. It does not own all underlying authoritative state.

ProductVerse​

The ProductVerse is the total universe of productized entities, actors, relationships, markets, experiences, governance structures, trust artifacts, dependencies, and value-creation patterns.

PVEP is the experience plane through which participants interact with this universe.

ProductVerse Participant​

A ProductVerse Participant is any actor that participates in ProductVerse activity.

Participants may include:

  • human users,
  • teams,
  • organizations,
  • applications,
  • machine agents,
  • AI agents,
  • institutional agents,
  • products-as-consumers,
  • product producers,
  • product stewards,
  • governance actors,
  • auditors,
  • marketplace operators.

Product Experience​

A Product Experience is any user-, agent-, application-, or product-facing interaction with a product or product-related construct.

Examples include:

  • viewing a marketplace listing,
  • opening a dashboard,
  • invoking an API,
  • inspecting a DPP summary,
  • requesting access,
  • adding a product to a Product Set,
  • navigating product relationships,
  • checking trust state,
  • transitioning to PDEP.

Product Experience State​

Product Experience State is the current condition of an actor’s interaction with a product or Product Set inside PVEP.

Examples:

  • discovered,
  • evaluated,
  • shortlisted,
  • acquired,
  • access requested,
  • entitled,
  • not entitled,
  • consuming,
  • blocked,
  • trusted,
  • trust under review,
  • assembled into Product Set,
  • ready for PDEP handoff.

Journey Mediation​

Journey Mediation is PVEP’s role in guiding actors across non-linear product journeys such as discover, evaluate, acquire, consume, assemble, request access, trust-check, and transition to PDEP.

Journey mediation does not imply a single fixed process sequence.

Non-Linear Journey​

A Non-Linear Journey is a product experience path where actors may move back and forth across discovery, evaluation, trust-checking, access request, acquisition, portfolio review, graph navigation, product selection, consumption, and PDEP transition.

Example:

Discover → Trust-Check → Product Graph → Assemble → Request Access → Evaluate → PDEP Handoff

Experience Zone​

An Experience Zone is a logical PVEP capability area that groups related product experience functions.

PVEP zones include:

  • Marketplace Experience Zone,
  • Consumption Experience Zone,
  • Concierge & Agent-Mediated Discovery Zone,
  • Product Graph Navigation Zone,
  • Portfolio & Entitlement Experience Zone,
  • Product Select & Assembly Zone,
  • Governance & Trust Experience Zone.

3. PVEP Experience Zone Terms​

Marketplace Experience Zone​

The Marketplace Experience Zone is the PVEP zone for browse-first and search-driven product interaction.

It supports:

  • discovery,
  • product listings,
  • product evaluation,
  • comparison,
  • pricing,
  • licensing,
  • acquisition,
  • subscription,
  • onboarding,
  • access request initiation.

It presents products as offerings that can be evaluated and acquired under governed conditions.

Consumption Experience Zone​

The Consumption Experience Zone is the PVEP zone through which actors use existing product output ports.

Consumption may occur through:

  • dashboards,
  • APIs,
  • SQL endpoints,
  • files,
  • event streams,
  • model endpoints,
  • readers,
  • workflows,
  • tool interfaces,
  • physical interfaces.

Consumption uses existing governed products. It does not create new products.

Concierge & Agent-Mediated Discovery Zone​

The Concierge & Agent-Mediated Discovery Zone is the PVEP zone where human, machine, AI, or institutional agents help actors discover, filter, compare, recommend, and understand products based on intent and context.

This zone supports intent-first discovery.

The term agent-mediated is preferred because agentic does not mean AI by default.

Product Graph Navigation Zone​

The Product Graph Navigation Zone is the PVEP zone for contextual exploration of product relationships.

It helps actors navigate:

  • dependencies,
  • inputs,
  • outputs,
  • substitutes,
  • complements,
  • bundles,
  • chains,
  • flows,
  • provenance,
  • lineage,
  • trust relationships,
  • entitlement relationships,
  • governance overlays.

Portfolio & Entitlement Experience Zone​

The Portfolio & Entitlement Experience Zone is the PVEP zone that shows what products an actor has, what the actor may do with them, and under what conditions.

It covers:

  • personal portfolios,
  • team portfolios,
  • organizational portfolios,
  • agent portfolios,
  • product-as-consumer portfolios,
  • entitlement state,
  • licenses,
  • subscriptions,
  • access requests,
  • delegated authority,
  • expiry,
  • revocation.

Product Select & Assembly Zone​

The Product Select & Assembly Zone is the PVEP zone where actors select, compare, organize, and assess products into candidate Product Sets.

It supports product selection and pre-assembly reasoning.

It does not create governed products.

Boundary:

PVEP assembles candidate product sets.
PDEP composes governed products.

Governance & Trust Experience Zone​

The Governance & Trust Experience Zone is the PVEP zone that renders Governance Kernel state into understandable trust, policy, entitlement, risk, evidence, DPP, lifecycle, and assurance experiences.

It supports:

  • trust posture,
  • DPP summary,
  • evidence summary,
  • policy explanation,
  • entitlement-aware trust,
  • risk explanation,
  • governance warnings,
  • remediation guidance.

4. Actor and Persona Terms​

Actor​

An Actor is any entity capable of participating in a ProductVerse interaction.

Actors may be:

  • humans,
  • teams,
  • organizations,
  • applications,
  • machine agents,
  • AI agents,
  • institutional agents,
  • products,
  • governance services.

Persona​

A Persona is a role-oriented abstraction used to describe actor goals, responsibilities, journeys, permissions, and experience needs.

A single actor may hold multiple personas depending on context.

Example:

A human user may be PCON while consuming products,
a product producer in PDEP,
and a steward while reviewing access requests.

PCON​

PCON, or Product Consumer, is the main product-kind-agnostic consumer persona in PVEP.

A PCON discovers, evaluates, acquires, consumes, trusts, selects, and provides feedback on products.

PCON may consume any product kind, including Data Products, AI Products, Software Products, Physical Products, Creative Products, Evidence Products, Governance Products, Infrastructure Products, and Agent Products.

Organizational Consumer​

An Organizational Consumer is an organization, enterprise unit, institution, team of record, mission group, agency, or legal entity that acquires, consumes, licenses, governs, or manages access to products.

Organizational consumers often operate through collective rights, subscriptions, budgets, licenses, policies, and delegated authority.

Team Consumer​

A Team Consumer is a group that consumes or evaluates products for a shared purpose.

Examples:

  • analytics team,
  • operations team,
  • mission team,
  • product design team,
  • compliance team,
  • creative production team.

Application Consumer​

An Application Consumer is a software system or application that consumes product output ports or product metadata.

Examples:

  • reporting application,
  • workflow system,
  • API integration,
  • analytics tool,
  • external partner system,
  • mobile application.

Agentic Consumer​

An Agentic Consumer is any agent-like actor that discovers, evaluates, recommends, selects, invokes, or acts upon products under authority, scope, and purpose.

In UPOS, agentic does not mean AI by default.

Agentic consumers may include human agents, machine agents, AI agents, institutional agents, and products-as-consumers.

Machine Agent​

A Machine Agent is a non-human automated actor that performs actions through software, workflow logic, deterministic rules, scheduling, monitoring, or automation.

A Machine Agent may or may not use AI.

AI Agent​

An AI Agent is a machine agent that uses AI capabilities for reasoning, planning, generation, tool use, ranking, explanation, or adaptive behavior.

An AI Agent is one subclass of agentic actor.

Institutional Agent​

An Institutional Agent is an agent acting with formally delegated authority from an institution, organization, governance body, public authority, enterprise function, or mandate.

Institutional agents require explicit authority, scope, expiry, accountability, supervision, and auditability.

Product-as-Consumer​

A Product-as-Consumer is a product that consumes, invokes, depends on, derives from, or composes with another product.

Examples:

  • AI Product consumes Data Product,
  • Dashboard Product consumes Analytics Product,
  • Comic Product consumes Image Asset Product,
  • Evidence Product references Policy Product,
  • Rocket Telemetry Product consumes Sensor Product.

Producer Entering PDEP​

A Producer Entering PDEP is an actor who begins in PVEP as a consumer, evaluator, selector, or planner, and then transitions into PDEP when creation intent emerges.

The actor becomes a product creator, producer, owner, or steward in the product-building plane.

Product Steward​

A Product Steward is an actor responsible for maintaining product trust, evidence, quality, governance readiness, lifecycle health, and consumer confidence.

The steward may respond to evidence gaps, access requests, trust downgrades, and consumer feedback.

Governance Actor​

A Governance Actor is a person, team, service, institutional agent, or governance body responsible for reviewing, approving, monitoring, or assuring governance conditions.

Examples:

  • policy owner,
  • risk reviewer,
  • evidence reviewer,
  • entitlement approver,
  • DPP reviewer,
  • compliance reviewer,
  • safety authority,
  • exception approver.

Auditor​

An Auditor is an actor responsible for inspecting, verifying, or reporting on governance, trust, risk, evidence, lifecycle, entitlement, and decision history.

Auditors may be internal, external, regulatory, institutional, or automated.

Marketplace Operator​

A Marketplace Operator is an actor responsible for operating, curating, moderating, configuring, or governing marketplace experiences inside PVEP.

Marketplace operators manage the marketplace experience but do not replace the Governance Kernel as the source of governance truth.

5. PVEP Artifact Terms​

PVEP Artifact​

A PVEP Artifact is a structured record, view, request, signal, summary, or package used by PVEP to mediate product discovery, evaluation, acquisition, consumption, selection, governance understanding, entitlement, feedback, or transition to another UPOS plane.

PVEP artifacts mediate experience. They do not necessarily define authoritative product truth.

Consumption Intent Record​

A Consumption Intent Record, abbreviated CIR, is a structured artifact that captures a consumer’s intent to discover, evaluate, acquire, consume, or use one or more products for a stated purpose within a given context.

A CIR helps PVEP and the Governance Kernel understand:

who wants to use what,
for what purpose,
through which output port or experience,
under what context.

Consumption Feedback Record​

A Consumption Feedback Record, abbreviated CFR, is a structured artifact that captures feedback from a consumer, agent, application, or product-as-consumer after discovering, evaluating, acquiring, consuming, or attempting to use a product.

CFRs support closed-loop ProductVerse improvement.

Product Set Intent​

A Product Set Intent is a structured artifact that captures why a consumer or agent is selecting a group of products.

It explains whether the set is for comparison, acquisition, consumption planning, governance review, PDEP handoff, or another purpose.

Product Set​

A Product Set is a temporary, saved, shared, or structured collection of selected products organized around an intent.

A Product Set may be used for:

  • comparison,
  • acquisition planning,
  • direct consumption planning,
  • governance review,
  • product graph exploration,
  • agent recommendation,
  • PDEP handoff.

A Product Set is not automatically a governed product.

Product Selection Record​

A Product Selection Record captures why a specific product was added to a Product Set.

It may record:

  • selected product,
  • selector,
  • selection source,
  • role in set,
  • recommendation reason,
  • governance snapshot,
  • known restrictions.

Marketplace Listing​

A Marketplace Listing is a PVEP-facing artifact that presents a product for discovery, evaluation, acquisition, subscription, licensing, onboarding, or access request.

A Marketplace Listing is a projection of a product and its offering context. It is not the product itself.

Entitlement Record​

An Entitlement Record is a structured artifact that represents a subject’s governed right to perform an action on a product, output port, product relationship, or lifecycle event within a defined context.

PVEP may render entitlement records, but authoritative entitlement state belongs to the Governance Kernel or entitlement service.

Access Request​

An Access Request is a PVEP-facing artifact that captures a request to obtain entitlement to a product, output port, evidence view, DPP detail, marketplace offer, or product relationship.

An Access Request is not itself an entitlement.

Trust Signal​

A Trust Signal is a PVEP-facing representation of kernel-derived trust state.

It communicates whether a product, output port, relationship, Product Set, DPP, or claim is fit for reliance in a specific context.

Trust Signals should be contextual and evidence-backed.

DPP Summary​

A DPP Summary is a PVEP-facing summary of a Digital Product Passport.

It presents product identity, trust, evidence, risk, permitted-use, lifecycle, and assurance information at the appropriate visibility level.

The DPP Summary is not the full DPP.

Governance Explanation​

A Governance Explanation is a human- or machine-readable explanation of a governance state, decision, warning, restriction, trust posture, entitlement outcome, risk condition, evidence gap, DPP status, or lifecycle block.

Product Suitability Assessment​

A Product Suitability Assessment is a PVEP-facing artifact that evaluates whether a product or Product Set is suitable for a specified intent and context.

It may consider:

  • purpose fit,
  • entitlement,
  • policy,
  • trust,
  • risk,
  • evidence,
  • DPP,
  • licensing,
  • output-port availability,
  • lifecycle state,
  • relationship compatibility,
  • PDEP readiness.

Consumption Session Record​

A Consumption Session Record is a PVEP-facing record of a consumer’s use of a product output port during a session.

It may support experience continuity, observability, governance review, and feedback.

It is not necessarily the authoritative runtime enforcement log.

Agent Recommendation Record​

An Agent Recommendation Record captures a recommendation produced by a human, machine, AI, or institutional agent during PVEP discovery, selection, comparison, or acquisition.

It should record authority scope, rationale, constraints, and recommended next action.

Product Graph View Artifact​

A Product Graph View Artifact is a PVEP-facing projection of product graph relationships scoped to a user, intent, product, Product Set, agent, or governance context.

It is a scoped view, not the authoritative Product Graph.

Governance Warning​

A Governance Warning is a PVEP-facing artifact that presents an actionable warning derived from Governance Kernel state.

Warnings may concern entitlement, trust, risk, evidence, DPP, policy, lifecycle, licensing, relationships, agent authority, or runtime restrictions.

PVEP-to-PDEP Handoff Package​

A PVEP-to-PDEP Handoff Package is a structured artifact passed from PVEP to PDEP when a consumer’s intent shifts from discovery, selection, or consumption toward governed product creation, composition, validation, versioning, or publication.

It may include selected products, intent, product versions, trust state, risk state, entitlement state, evidence gaps, DPP state, inherited restrictions, licensing constraints, and recommended next actions.

6. Product and ProductVerse Entity Terms​

Product​

A Product is a productized entity that can be described, discovered, trusted, governed, consumed, exchanged, reused, composed, or evolved.

Products may be physical, digital, data, AI, software, creative, evidence, governance, infrastructure, agentic, or hybrid.

Product Kind​

A Product Kind is the broad category or class of a product.

Examples:

  • Data Product,
  • AI Product,
  • Software Product,
  • Physical Product,
  • Creative Product,
  • Evidence Product,
  • Governance Product,
  • Infrastructure Product,
  • Agent Product.

Product Version​

A Product Version is a specific version of a product.

Trust, evidence, DPP, entitlement, risk, lifecycle, and output-port state should be product-version-aware.

Output Port​

An Output Port is a product’s exposed consumption interface.

Examples:

  • API,
  • SQL endpoint,
  • dashboard,
  • file download,
  • event stream,
  • model endpoint,
  • reader,
  • workflow,
  • tool interface,
  • physical interface.

PVEP renders output-port experiences. Product Fabric enforces output-port usage.

Product Relationship​

A Product Relationship is a typed connection between products or between products and related ProductVerse objects.

Examples:

  • consumes,
  • depends on,
  • composed from,
  • substitute for,
  • complements,
  • governed by,
  • evidenced by,
  • listed in,
  • entitled to use,
  • exposes,
  • derived from,
  • bundled with.

Product Graph​

The Product Graph is the formal node-edge representation of products and their typed relationships.

PVEP renders scoped Product Graph views through the Product Graph Navigation Zone.

Product Chain​

A Product Chain is an ordered sequence of products connected by dependency, transformation, production, consumption, supply, or value-creation relationships.

Product Flow​

A Product Flow is the dynamic movement of value, data, materials, energy, decisions, rights, trust evidence, signals, control, or feedback through products over time.

Product Bundle​

A Product Bundle is a grouped product offering or governed product collection that may be acquired, consumed, listed, or managed together.

A Product Bundle is different from a Product Set. A bundle is usually a more formal product or offering construct.

Product Portfolio​

A Product Portfolio is a collection of products associated with a subject, such as an individual, team, organization, agent, product, steward, or marketplace account.

Portfolio does not imply unrestricted entitlement.

Product Registry​

A Product Registry is an authoritative source for product identity, descriptors, metadata, lifecycle state, output ports, and relationships.

PVEP may render registry-derived views, but it should not replace the registry as the source of product truth.

7. Journey Terms​

PVEP Journey​

A PVEP Journey is a structured path through which an actor interacts with products across the ProductVerse.

Common PVEP journeys include:

  • discover,
  • evaluate,
  • acquire,
  • consume,
  • assemble,
  • request access,
  • trust-check,
  • transition to PDEP,
  • feedback.

Discover Journey​

The Discover Journey helps actors find relevant products across the ProductVerse.

Discovery may be search-based, browse-based, graph-based, intent-based, portfolio-based, or agent-mediated.

Evaluate Journey​

The Evaluate Journey helps actors determine whether a product is suitable for their intent.

Evaluation may include product fit, trust, risk, entitlement, evidence, DPP, license, lifecycle, cost, and output-port assessment.

Acquire Journey​

The Acquire Journey helps actors obtain rights to use a product through subscription, purchase, license acceptance, trial activation, onboarding, approval, or access provisioning.

Acquisition is not always the same as usable entitlement.

Consume Journey​

The Consume Journey helps actors use an existing product through one or more output ports.

Consumption uses existing products and belongs to PVEP plus Product Fabric.

It is not product creation.

Assemble Journey​

The Assemble Journey helps actors select and organize products into a Product Set for comparison, acquisition planning, consumption planning, governance review, or possible PDEP handoff.

Assembly in PVEP is not governed product composition.

Request Access Journey​

The Request Access Journey helps actors request specific rights to use a product, output port, evidence view, DPP detail, product relationship, or product capability.

A strong access request should capture purpose, output port, context, duration, and justification.

Trust-Check Journey​

The Trust-Check Journey helps actors inspect whether a product, output port, DPP, evidence claim, relationship, Product Set, or dependency can be relied upon in a specific context.

Transition to PDEP Journey​

The Transition to PDEP Journey occurs when a PVEP actor’s intent shifts from discovering, evaluating, acquiring, consuming, or selecting products to creating or changing a governed product.

PVEP prepares the handoff. PDEP performs governed product creation.

Feedback Journey​

The Feedback Journey captures consumer, agent, or product-as-consumer feedback after discovery, evaluation, acquisition, consumption, or failed usage.

Feedback may generate CFRs and improvement signals.

8. Governance and Trust Terms in PVEP​

Governance Kernel​

The Governance Kernel is the UPOS computational governance core that evaluates, records, explains, and emits authoritative governance state.

PVEP renders Governance Kernel state.

Governance State​

Governance State is the evaluated condition of a product, actor, action, relationship, entitlement, policy, trust signal, risk state, evidence record, DPP, lifecycle state, or runtime interaction.

PVEP renders governance state as warnings, badges, explanations, access statuses, suitability assessments, and next actions.

Policy State​

Policy State describes which rules, obligations, permissions, prohibitions, and restrictions apply to a product, actor, purpose, output port, relationship, or lifecycle context.

Entitlement State​

Entitlement State describes whether a subject has a governed right to perform an action on a product, output port, relationship, or lifecycle event within a defined context.

Examples:

  • entitled,
  • not entitled,
  • approval required,
  • expired,
  • suspended,
  • revoked,
  • conditionally entitled.

Trust State​

Trust State describes whether a product, output port, relationship, Product Set, or claim is evidence-backed and fit for reliance in a specified context.

Trust should be contextual, not universal.

Risk State​

Risk State describes the evaluated risk posture of a product, actor, purpose, output port, relationship, Product Set, or lifecycle action.

PVEP may render risk as warnings, controls, required approvals, or suitability constraints.

Evidence State​

Evidence State describes whether required evidence exists, is current, sufficient, authoritative, visible, and applicable to the context.

DPP State​

DPP State describes the condition of a Digital Product Passport.

Examples:

  • valid,
  • incomplete,
  • expired,
  • superseded,
  • version mismatch,
  • unsuitable for purpose,
  • evidence missing.

Lifecycle State​

Lifecycle State describes the current lifecycle condition of a product or artifact.

Examples:

  • draft,
  • published,
  • active,
  • deprecated,
  • retired,
  • under review,
  • blocked,
  • recertification required.

Governance Signal​

A Governance Signal is a structured state change, alert, decision emission, warning, or assurance update emitted by the Governance Kernel or related governance service.

PVEP consumes signals to keep experiences fresh.

Examples:

  • DPP expired,
  • entitlement revoked,
  • trust downgraded,
  • risk tier changed,
  • evidence expired,
  • product deprecated.

Governance Badge​

A Governance Badge is a compact PVEP indicator of governance state.

Examples:

  • DPP valid,
  • trusted,
  • high risk,
  • approval required,
  • evidence expired.

Governance badges must be kernel-derived and explainable.

Governance Warning​

A Governance Warning is an actionable PVEP message indicating a governance concern.

Examples:

  • external sharing prohibited,
  • DPP expired,
  • API access requires approval,
  • evidence incomplete,
  • product deprecated.

Permitted Use​

A Permitted Use is a use of a product that is allowed under applicable policy, entitlement, license, trust, risk, and context.

Prohibited Use​

A Prohibited Use is a use of a product that is disallowed under applicable governance, legal, licensing, policy, risk, or trust conditions.

Restricted Use​

A Restricted Use is a use that may be allowed only under constraints, approvals, obligations, or runtime controls.

9. Boundary Terms​

PVEP–PDEP Boundary​

The PVEP–PDEP Boundary defines the separation between product experience and product creation.

PVEP supports discovery, evaluation, acquisition, consumption, trust, access, selection, and pre-assembly reasoning.

PDEP owns governed product authoring, composition, validation, versioning, publication, and lifecycle control.

PDEP​

The Product Development and Execution Plane, abbreviated PDEP, is the UPOS plane responsible for product authoring, composition, validation, lifecycle control, versioning, publication, deployment preparation, and product evolution.

Product Creation Intent​

Product Creation Intent is the actor’s intention to create, compose, publish, version, or materially change a governed product.

When Product Creation Intent emerges in PVEP, the flow should transition to PDEP.

Candidate Product Set​

A Candidate Product Set is a Product Set being considered for a purpose, comparison, acquisition, consumption, governance review, or PDEP handoff.

It is not yet a governed product.

Governed Product​

A Governed Product is a product with identity, ownership, descriptors, lifecycle state, output ports, governance state, and possibly DPP and evidence.

Governed Products are created or evolved through PDEP, not simply by selecting items in PVEP.

Selection​

Selection is the act of choosing one or more products for a purpose.

Selection belongs to PVEP.

Assembly​

Assembly is the act of organizing selected products into a working set, shortlist, scenario, candidate collection, or planning view.

Assembly belongs to PVEP when no new governed product is created.

Composition​

Composition is the governed creation of a new product from selected products, components, assets, dependencies, or inputs.

Composition belongs to PDEP.

PDEP Handoff​

A PDEP Handoff is the structured transition from PVEP to PDEP when product creation intent emerges.

It should carry selected products, intent, governance state, evidence gaps, DPP state, risk, trust, entitlement, licensing, and inherited restrictions.

10. Runtime and Enforcement Terms​

Product Fabric​

The Product Fabric is the interoperability, governance, trust, identity, registry, policy, and integration substrate that allows independently produced products to work together safely and coherently.

In PVEP context, Product Fabric enforces runtime usage of product output ports.

Runtime Enforcement​

Runtime Enforcement is the operational enforcement of Governance Kernel decisions by Product Fabric or runtime systems.

Examples:

  • block access,
  • apply masking,
  • disable export,
  • enforce rate limits,
  • require audit logging,
  • block agent invocation.

Output-Port Invocation​

Output-Port Invocation is the act of using a product’s output port, such as calling an API, opening a dashboard, querying SQL, consuming a stream, or invoking a model endpoint.

Runtime Access​

Runtime Access is the ability to use a product output port at execution time under governed conditions.

Runtime access requires enforcement beyond PVEP UI display.

UI-Only Enforcement​

UI-Only Enforcement is the anti-pattern of relying only on buttons, visibility, or front-end controls to enforce governance decisions.

PVEP may disable an action, but Product Fabric must enforce runtime restrictions where needed.

11. Marketplace Terms​

Product Offer​

A Product Offer is the commercial, contractual, subscription, or access proposition associated with a product listing.

It may include pricing, plan, license, trial, usage limits, onboarding, and acquisition path.

Subscription​

A Subscription is a commercial or access arrangement granting access to a product or product offering under defined terms.

A subscription may initiate entitlement, but it is not always equivalent to runtime usability.

License​

A License defines rights, restrictions, obligations, permitted uses, prohibited uses, and conditions for using a product.

Licensing may affect entitlement, acquisition, derivative use, redistribution, and publication.

Trial​

A Trial is a temporary or limited-use entitlement or offer that allows evaluation or restricted product use.

Onboarding​

Onboarding is the process of helping an actor begin using a product after discovery, acquisition, entitlement, or approval.

Onboarding may involve guides, credentials, environment setup, API keys, tutorials, examples, or support links.

Acquisition​

Acquisition is the process of obtaining rights to use a product through purchase, subscription, approval, license acceptance, trial, or access provisioning.

Acquisition is not always the same as entitlement or runtime access.

12. Product Graph Terms​

Product Node​

A Product Node is a product represented as a node in the Product Graph.

Product Edge​

A Product Edge is a typed relationship between products or ProductVerse entities in the Product Graph.

Examples:

  • consumes,
  • depends on,
  • complements,
  • substitutes,
  • governed by,
  • evidenced by,
  • listed in.

Graph Projection​

A Graph Projection is a contextual view of the Product Graph that foregrounds certain relationships while hiding or minimizing others.

Examples:

  • dependency projection,
  • trust projection,
  • entitlement projection,
  • marketplace projection,
  • lifecycle projection,
  • product chain projection.

Graph Overlay​

A Graph Overlay is additional state rendered on top of a Product Graph view.

Examples:

  • trust overlay,
  • risk overlay,
  • entitlement overlay,
  • DPP overlay,
  • evidence overlay,
  • lifecycle overlay.

Contextual Navigation​

Contextual Navigation is product graph navigation shaped by actor intent, permissions, governance state, product kind, relationship type, and journey context.

Not every actor needs or should see every graph projection.

13. Feedback and Observability Terms​

Product Feedback​

Product Feedback is feedback about the usefulness, quality, usability, trust clarity, output-port experience, or value of a product.

Governance Feedback​

Governance Feedback is feedback about the clarity, usability, friction, or correctness of governance experiences.

Examples:

  • access denial unclear,
  • DPP summary confusing,
  • trust warning helpful,
  • approval process too slow.

Entitlement Friction​

Entitlement Friction is difficulty or delay caused by unclear, slow, restrictive, or confusing access and entitlement pathways.

Journey Signal​

A Journey Signal is an event emitted during a PVEP journey.

Examples:

  • product viewed,
  • DPP opened,
  • trust warning shown,
  • product added to set,
  • access request started,
  • PDEP handoff initiated,
  • product consumed,
  • CFR submitted.

Product Value Signal​

A Product Value Signal is an observed or declared indication that a product created value for a consumer, team, organization, agent, or downstream product.

Examples:

  • repeated use,
  • positive CFR,
  • workflow completion,
  • time saved,
  • downstream reuse,
  • renewal,
  • high adoption.

Governance Friction Signal​

A Governance Friction Signal is an indication that governance experience created confusion, delay, abandonment, or unnecessary effort.

Examples:

  • repeated denied access,
  • abandoned access request,
  • unexplained warning,
  • unclear DPP,
  • blocked PDEP handoff without remediation.

14. Common Boundary Statements​

This section records recurring PVEP boundary principles.

PVEP and Governance Kernel​

Governance Kernel computes governance truth.
PVEP renders governance truth.

PVEP and Product Fabric​

PVEP renders runtime actions.
Product Fabric enforces runtime actions.

PVEP and PDEP​

PVEP assembles candidate product sets.
PDEP composes governed products.

Product Set and Product​

A Product Set is not automatically a Product.

Marketplace and Governance​

Marketplace displays product offers.
Governance Kernel provides authoritative governance state.

Trust and Entitlement​

Trusted does not mean entitled.
Entitled does not mean trusted.

Visibility and Permission​

Seeing a product does not mean one may use, invoke, acquire, compose, or publish it.

Agentic and AI​

Agentic does not mean AI by default.
AI agents are one kind of agentic actor.

Acquisition and Runtime Use​

Acquisition does not automatically mean runtime usability.

Consumption and Creation​

Consumption uses existing product output ports.
Creation belongs to PDEP.

15. PVEP Anti-Pattern Terms​

Static Catalog Anti-Pattern​

The anti-pattern of treating PVEP as a simple product list or catalog rather than a governed journey mediation plane.

Decorative Trust Anti-Pattern​

The anti-pattern of showing trust badges or labels that are not backed by Governance Kernel state and evidence.

Binary Access Anti-Pattern​

The anti-pattern of representing entitlement as a simple “has access / does not have access” flag.

Entitlement should be contextual, action-specific, purpose-aware, output-port-aware, and time-aware.

Hidden Governance Anti-Pattern​

The anti-pattern of hiding policy, trust, risk, entitlement, DPP, license, or evidence constraints until late in the journey.

PVEP-as-PDEP Anti-Pattern​

The anti-pattern of allowing PVEP to create governed products, product descriptors, product versions, output ports, DPPs, or lifecycle state directly.

Product Set as Product Anti-Pattern​

The anti-pattern of treating a selected Product Set as a governed product without PDEP validation and product creation.

Agent Visibility as Permission Anti-Pattern​

The anti-pattern of assuming that an agent may recommend, invoke, acquire, compose, or publish a product simply because the agent can see it.

Marketplace as Governance Authority Anti-Pattern​

The anti-pattern of treating marketplace listing, acquisition, or subscription as equivalent to policy approval, entitlement, trust, or runtime usability.

UI-Only Governance Anti-Pattern​

The anti-pattern of treating PVEP display or UI controls as sufficient enforcement for governed runtime actions.