Skip to main content

Interactions and Flows

This section describes UPOS interactions at two levels:

  • Executive flow (value narrative)
  • Technical flow (abstract control/interaction view)

UPOS is product-kind agnostic: the same interaction model applies to digital, physical, and hybrid products.

Executive flow (value narrative)​

A) Creation flow (Symbiant → product published into the ProductVerse)​

  1. Creator steers in PDEP
    A Symbiant (or other creator) expresses creation intent in PDEP (purpose, audience, outcomes, constraints, trust posture) and issues a lifecycle command such as Create/Compile.

  2. PFI compiles intent into artifacts + realization
    PFI consumes creation intent and generates the internal artifact chain: PIR → Policy Bundle → PROD / PDS / DPP (as applicable), then resolves blueprints/capabilities and realizes the product (digital runtime and/or physical realization mechanisms).

  3. Provisioned / realized product exists
    The product is now realized with: ports (delivery interfaces/forms), controls, evidence hooks, and operational posture.

  4. Product is made available through PVEP
    The product is published and exposed via the ProductVerse Experience Plane (PVEP), which includes marketplace experiences (listing, acquisition, entitlements, portfolio views) and consumption experiences (CEP).

B) Consumption flow (PCON discovers and consumes products through PVEP)​

UPOS supports two entry modes into PVEP, both converging to a Consumption Intent Record (CIR) before governed access and consumption:

Canonical Mode 1 — Intent-first

  1. PCON (or PCON-delegate such as a concierge/agent) declares consumption intent.
  2. The platform normalizes it into a CIR (Consumption Intent Record).
  3. PVEP resolves suitable products across the ProductVerse and marketplaces and presents a ranked candidate set.

Secondary Mode 2 — Browse-first

  1. PCON browses marketplace experiences inside PVEP.

  2. Before governed access and consumption proceed, PVEP infers or confirms a CIR (lightweight: “what is your purpose/context?”).

  3. Acquire / entitle / access
    PVEP performs acquisition and entitlement workflows and applies purpose-bound access posture.

  4. Consume via ports + CEP experiences
    PCON consumes through governed ports, rendered through CEP (dashboards, apps, APIs, agentic interfaces, etc.).

  5. Signals and feedback close the loop
    Usage, quality, trust, and cost/value signals are captured and made observable, informing:

    • consumer decisions (continue/stop/feedback),
    • marketplace portfolio signals,
    • and creator stewardship decisions in PDEP.

Technical flow (abstract)​

Responsibility boundaries (UPOS)​

  • PDEP owns: intent authoring (creation), stewardship decisions, lifecycle commands.
  • PFI owns: compilation, artifact generation (PIR + descriptors + policy bundle), realization/provisioning, readiness.
  • PVEP owns: discovery (browse-first and intent-first), acquisition, entitlements experience, consumption experiences (including CEP), and ProductVerse navigation.
  • Governance Kernel (cross-cutting) spans all planes via policy bundles, gates, entitlements, evidence (DPP), and continuous assurance signals.

Note on feedback semantics​

Signals do not “rewrite” product definitions directly. Signals inform stewardship decisions (via PDEP) that lead to new Product Versions and updated descriptors.

Naming hygiene (important)​

  • PIR is creation-side intent (compiled in PFI from creator intent in PDEP).
  • CIR is consumption-side intent (created at intent capture by PCON or PCON-delegate and used in PVEP for purpose-bound access and explainable resolution).