Skip to main content

UPOS Planes

UPOS organizes productization into canonical planes. Planes define responsibilities and boundaries, not specific technologies.

In UPOS, governance is kernel-based (cross-cutting) rather than a separate plane.

Plane 1: PDEP - Product Development Experience Plane (Creator Cockpit)​

PDEP is the product-native self-service cockpit for creators (including Symbiants).
It is where product intent is authored, stewardship decisions are taken, and lifecycle commands are issued.

PDEP responsibilities:

  • Author creation intent in product language (purpose, audience, outcomes, constraints, trust posture)
  • Perform stewardship (ownership, accountability, trade-offs)
  • Issue lifecycle commands (create/compile, publish, evolve, deprecate, retire)
  • Observe signals and steer evolution decisions

Boundary rule: PDEP is not for authoring technical artifacts (PIR, PROD, PDS, DPP, policy bundles). Those are generated by PFI.

Plane 2: PFI - Product Factory Intelligence (Intent Compiler)​

PFI is the intent compiler/factory of UPOS.
Its primary input is creation intent from PDEP. PFI compiles intent into a publishable Product Version by generating the artifact chain and realizing the product (digital, physical, or hybrid).

PFI responsibilities:

  • Generate PIR (Product Intent Record) as the first compilation artifact
  • Derive Policy Bundle and generate PROD / PDS / DPP as applicable
  • Resolve blueprints/capabilities and provision realization mechanisms
  • Realize products through:
    • digital runtimes/ports (services, APIs, pipelines, streams, etc.)
    • physical realization mechanisms (robotics, assembly lines, 3D printing, manual factory workflows, future mechanisms)
  • Configure evidence hooks and observability baselines
  • Prepare publication readiness and bindings for the experience layer (PVEP)

Boundary rule: PFI compiles and realizes products; it does not own consumer experiences.

Plane 3: PVEP - ProductVerse Experience Plane (Discovery + Consumption Umbrella)​

PVEP is the umbrella experience plane for the product economy.
It makes the ProductVerse usable by providing discovery and consumption experiences across products and marketplaces.

PVEP includes (as sub-experiences/capabilities):

3.1 Marketplace Experiences (PVEP)​

Marketplace experiences enable:

  • browse-first discovery and comparison
  • acquisition / onboarding
  • entitlements and access posture exposure
  • portfolio views (adoption, trust posture, lifecycle status, cost/value signals)
  • lifecycle exposure (published, deprecated, retired)

3.2 CEP - Consumer Experience Plane (PVEP)​

CEP is the set of consumer experiences that consume product ports:

  • dashboards, notebooks, apps, embedded UIs
  • system and agent interfaces calling product ports
  • partner integrations and experience adapters

Boundary rule: products expose ports; CEP provides experiences consuming ports. CEP is not embedded in product semantics.

3.3 Intent-first / Concierge Experiences (PVEP)​

PVEP also supports intent-first discovery and navigation (concierge / agentic shopping):

  • a PCON (or PCON-delegate) expresses consumption intent
  • the platform normalizes that intent into a CIR (Consumption Intent Record)
  • products are resolved across one or many marketplaces and presented as a ranked, explainable candidate set

Important: CIR is created at the point of intent capture by the PCON or PCON-delegate; a marketplace may infer/confirm a derived CIR in browse-first mode, but CIR is not exclusively owned by any single marketplace.

Cross-cutting: Signals & Feedback (Closed-loop Evolution)​

Signals connect PVEP consumption back to stewardship:

  • usage/adoption
  • quality and health indicators
  • trust/risk indicators
  • FinOps cost/ROI signals
  • explicit feedback

Signals inform stewardship decisions in PDEP and trigger new version evolution that PFI compiles.

Cross-cutting: Governance Kernel​

UPOS governance is expressed as a Governance Kernel spanning PDEP, PFI, and PVEP:

  • In PDEP: capture governance posture as intent (obligations, constraints, trust expectations) and steward accountability
  • In PFI: compile governance into policy bundles, enforce controls, apply deterministic gates, bind evidence hooks, and produce provenance-linked artifacts (DPP)
  • In PVEP: apply purpose-bound entitlement, acquisition constraints, and consumption enforcement through governed ports and usage posture
  • Via signals: continuously assure, detect drift/violations, and trigger governance interventions and evolution decisions

Kernel rule: governance must be computable, explainable, and evidence-backed-not committee-driven.

Plane boundaries (quick rules)​

  • PDEP owns: intent authoring, stewardship decisions, lifecycle commands.
  • PFI owns: compilation, artifact generation, realization/provisioning, readiness.
  • PVEP owns: discovery, acquisition, entitlements experience, consumption experiences (Marketplace + CEP + concierge/intent-first).
  • Governance Kernel spans all planes through policy bundles, gates, entitlements, evidence, and signals.