Skip to main content

Principles and Invariants

UPOS is flexible in implementation but strict on a small set of invariants.
These invariants ensure UPOS remains product-kind agnostic, governable, and scalable across digital, physical, and hybrid products.

Invariants (non-negotiable)​

  1. Products are first-class
    Products (not projects) are the unit of delivery, governance, and value measurement.

  2. Immutability by version
    A Product Version is immutable; change produces a new version with provenance linkage.

  3. Separation of concerns in descriptors
    Semantic meaning (PROD) is distinct from realization (PDS) and trust/evidence (DPP).
    Domain profiles may extend these, but the separation remains invariant.

  4. Ports, not UIs
    Products expose governed ports (interfaces/forms of delivery).
    Experiences live in PVEP (including CEP), and must not be embedded into product semantics.

  5. Governance is kernel-based and computable
    Governance is not a standalone plane in UPOS. It is a cross-cutting Governance Kernel expressed through:

    • policy bundles and enforceable controls,
    • lifecycle gates,
    • provenance and evidence (DPP),
    • entitlements and purpose-bound access,
    • continuous assurance signals.
      Governance must be machine-checkable, explainable, and audit-ready.

  6. Intent is the source; compilation is the mechanism
    Product creators express intent in PDEP; PFI compiles that intent into a publishable Product Version by generating the artifact chain (e.g., PIR → policy bundle → PROD/PDS/DPP) and realizing the product.

  7. PVEP is required for a product economy
    A scalable product economy requires an umbrella experience plane (PVEP) that supports:

    • discovery (browse-first and intent-first),
    • acquisition and entitlement,
    • consumption experiences (CEP),
    • portfolio and navigation across the ProductVerse.

  8. ProductVerse is the natural structure of product economies
    Products exist in a graph (inputs, dependencies, compositions, substitutes/complements).
    UPOS assumes recursive value creation: products are consumed as inputs to create other products.

  9. Closed-loop evolution is stewardship-driven
    Signals and feedback inform stewardship decisions (via PDEP).
    Evolution results in new versions; telemetry does not automatically mutate product definitions.

  10. Self-service is product-native
    UPOS self-service is for product creators and consumers (Symbiants and PCONs) in product language-not only for engineers in technology language.

Design principles (guiding, not absolute)​

  • Composability
    Products should be combinable without bespoke integration, enabling ProductVerse graph growth.

  • Progressive rigor
    Higher-risk products require stronger evidence, tighter gates, and stricter constraints.

  • Evidence by default
    Assurance is continuous and systemic (DPP + signals), not an audit scramble.

  • Minimal viable productization
    Start thin (one product kind, one blueprint, minimal PVEP experience), then expand domains and rigor.

  • Portability of intent
    Creation intent (PIR) and consumption intent (CIR) should be usable across contexts; consumers may share CIR across multiple marketplaces via PVEP experiences.

Anti-principles (what UPOS avoids)​

  • “Products” that are just projects with a new label.
  • Self-service that is only CI/CD for engineers.
  • UI/experience logic embedded into product semantics.
  • Telemetry auto-mutating product definitions without stewardship and versioning.
  • Treating a marketplace as a catalog UI without acquisition, entitlement, lifecycle state, and measurable consumption.
  • Treating product economies as lists rather than graphs (ignoring ProductVerse relationships).