Skip to main content

Core Concepts

This section defines the minimum vocabulary required to read UPOS consistently.

Key terms​

Product and versions​

  • Product: A unit of value offered for consumption through governed ports (interfaces/forms of delivery).
  • Product Version: An immutable snapshot of a Product that is publishable, traceable, and governable. Change produces a new version with provenance links.

Product descriptors (the product record)​

  • Product Descriptor Set: The formal artifact set representing a Product Version, typically including:
    • PROD — semantic blueprint (what it is, meaning, intended use, obligations)
    • PDS — realization blueprint (how it is instantiated, delivered, operated)
    • DPP — trust layer (evidence, provenance, certifications, compliance posture)
  • Policy Bundle: A computable set of governance constraints and obligations applied to a Product Version (e.g., access posture, residency, retention, purpose limits, risk duties, operational constraints).

Intent artifacts (creation vs consumption)​

  • PIR (Product Intent Record): The canonical, immutable record of creation intent (creator-side). PIR is generated as the first compilation artifact in PFI from intent expressed in PDEP.
  • CIR (Consumption Intent Record): The canonical, immutable record of consumption intent (consumer-side). CIR is created at the point of intent capture by PCON or PCON-delegate (e.g., concierge/agent) and may be shared across experiences and marketplaces. Marketplaces may also infer/confirm a derived CIR in browse-first scenarios.

Naming hygiene: PIR = creation intent; CIR = consumption intent.

UPOS planes​

  • PDEP (Product Development Experience Plane): Product-native self-service cockpit for creators to author intent, perform stewardship decisions, and issue lifecycle commands (create/publish/evolve/deprecate/retire). PDEP is not for artifact authoring.
  • PFI (Product Factory Intelligence): The intent compiler / factory that turns creation intent into a publishable Product Version by generating PIR, descriptors, policy bundles, and realizing the product (digital, physical, or hybrid).
  • PVEP (ProductVerse Experience Plane): The umbrella experience plane for discovery and consumption across the product economy. PVEP includes:
    • Marketplace experiences (browse-first discovery, acquisition, entitlements, portfolio views),
    • CEP consumption experiences (experiences consuming product ports),
    • Intent-first / concierge discovery experiences spanning multiple marketplaces,
    • ProductVerse navigation (dependencies, alternatives, compositions).
  • Signals & Feedback: Usage, quality, trust/risk indicators, cost (FinOps), and outcome signals that inform stewardship and evolution decisions.

Governance (kernel-based, cross-cutting)​

  • Governance Kernel: The cross-cutting governance fabric that makes UPOS computably governable across all planes. It is expressed through:
    • Policy Bundles (constraints/obligations compiled and enforced),
    • DPP evidence and provenance,
    • deterministic lifecycle gates (publish/promotion readiness),
    • entitlements and purpose-bound access in PVEP,
    • continuous assurance signals feeding stewardship decisions in PDEP.

Governance in UPOS is kernel-based, not a standalone plane.

Actors​

  • Symbiant: A single-entity micro-enterprise (human + machine intelligence) operating as a Creator–Steward of products.
  • PCON (Product Consumer): Any human, system, or agent consuming products through PVEP (and potentially triggering creation/composition later).

Product economy structure​

  • ProductVerse (PV): The network/graph of products and their relationships (inputs, dependencies, compositions, substitutes/complements) enabling recursive product economies.

Product-native vs technology-native self-service​

  • Technology-native self-service: pipelines, infra, CI/CD (serves engineers; accelerates delivery mechanics).
  • Product-native self-service (UPOS): intent → compile → publish → acquire/consume → observe → evolve (serves product creators and consumers through PVEP).

Concept map​

Relationship to BPS​

  • BPS provides the universal grammar for product representation.
  • UPOS provides the universal meta-architecture for productization ecosystems.
  • Domain specifications and domain architectures specialize these into implementable realities (e.g., HDIP for Data & AI).