Skip to main content

Specialization Guide

UPOS is specialized into domain architectures (and domain specifications).
This section describes how to derive a domain architecture such as HDIP while preserving UPOS invariants.

A useful mental model:

  • UPOS defines the universal planes, artifact discipline, governance kernel posture, and ProductVerse-scale experience assumptions.
  • A domain architecture specializes UPOS by adding domain semantics, obligations, port forms, and implementation patterns-without breaking invariants.

What stays invariant (UPOS invariants)​

Domain specializations MUST preserve:

1) Plane discipline​

  • PDEP: creator intent authoring, stewardship, lifecycle commands (not artifact authoring)
  • PFI: intent compilation into artifacts + realization (digital, physical, hybrid)
  • PVEP: umbrella experience plane for discovery + acquisition + entitlements + consumption experiences
    (Marketplace experiences and CEP experiences are PVEP sub-experiences)
  • Signals & feedback: closed-loop evolution informing stewardship decisions

2) Governance Kernel posture (cross-cutting)​

Governance must remain kernel-based, spanning PDEP/PFI/PVEP through:

  • policy bundles and enforceable controls
  • deterministic gates and promotion decisions
  • evidence models (DPP) and provenance
  • entitlements and purpose-bound access
  • continuous assurance signals

Specializations may deepen governance; they must not “remove it” into manual committee processes.

3) Descriptor separation​

  • PROD (semantic meaning) is distinct from
  • PDS (realization/deployment) and
  • DPP (trust/evidence/provenance)

Domain profiles may extend each, but must not collapse them into a single artifact.

4) Versioning and provenance​

  • Product Versions are immutable
  • change produces a new version with provenance linkage
  • evidence and signals are attributable to a specific version

5) ProductVerse posture​

  • products exist as a graph of relationships (inputs, dependencies, compositions, substitutes/complements)
  • consumption can lead to composition and new product creation

Naming hygiene (critical)​

UPOS specializations must keep intent artifacts unambiguous:

  • PIR = Product Intent Record (creation-side intent, compiled in PFI from PDEP intent)
  • CIR = Consumption Intent Record (consumption-side intent, created at intent capture by PCON or PCON-delegate in PVEP experiences)

This matters because PVEP may span multiple marketplaces; CIR is portable and not owned by a single marketplace.

What gets specialized (domain responsibilities)​

Domain specializations define:

1) Domain semantics​

  • what “meaning” looks like in the domain
  • domain ontologies/taxonomies and semantic constraints
  • what PROD must contain for the domain

2) Domain governance obligations (kernel extensions)​

  • domain risk models and obligation matrices
  • evidence requirements and DPP content
  • policy compilation rules and mandatory gates

3) Domain port forms and consumer archetypes​

  • port types (e.g., SQL tables, inference endpoints, streams, files, physical delivery interfaces)
  • consumer modes and experience expectations within PVEP (browse-first, intent-first, concierge)

4) Domain realization patterns (PFI blueprint library)​

  • blueprint catalog (how products are realized)
  • capability registry mappings (tools/platforms/locations permitted)
  • automation patterns for provisioning, packaging, and operational posture

5) Domain signals and assurance model​

  • quality/health metrics relevant to the domain
  • trust signals and continuous assurance checks
  • FinOps/value measurement approach (where applicable)

Example: deriving HDIP from UPOS​

HDIP specializes UPOS for Data & AI by adding:

Domain semantics​

  • data/AI semantic models, domain descriptors and contracts

Domain governance kernel extensions​

  • data governance obligations (freshness, quality, lineage, controls)
  • AI governance obligations (risk tiers, safety obligations, evaluation/evidence models)

Domain port forms​

  • analytical ports (SQL/query, federated query)
  • system ports (APIs, streams, events)
  • AI ports (inference endpoints, feature ports, evaluation artifacts)

Domain PFI blueprint library​

  • transformation and orchestration patterns (data)
  • training/inference deployment patterns (AI)
  • policy compilation patterns (purpose-bound access, controls)

Domain signals​

  • data signals (freshness, DQ, timeliness, incident posture)
  • AI signals (drift, evaluation results, safety/behavioral signals)
  • economic signals (cost attribution and value proxies)

HDIP is UPOS made concrete for Data & AI while preserving UPOS invariants (plane discipline, governance kernel, descriptor separation, versioning, ProductVerse posture).

Specialization checklist (for any new domain architecture)​

Use this checklist to derive a new domain architecture from UPOS:

  1. Declare the domain product kinds
  • Define domain product types and their boundaries.
  1. Define descriptor profiles
  • Specify required domain fields for PROD, PDS, and DPP (and how they are validated).
  1. Extend the Governance Kernel
  • Define domain obligations, required gates, evidence requirements, and policy compilation rules.
  1. Define port forms
  • Enumerate allowed port/interface forms for the domain and how consumers experience them in PVEP.
  1. Define PFI blueprints
  • Create blueprint templates and capability mappings for how products are realized (digital/physical/hybrid).
  1. Define PVEP experience expectations
  • Specify how the domain participates in PVEP:
    • browse-first marketplace experiences
    • intent-first/concierge discovery
    • consumption experiences (CEP adapters)
    • portfolio views and ProductVerse navigation
  1. Define signals and continuous assurance
  • Specify usage, quality, trust, cost/value signals and how they feed stewardship decisions.
  1. Lock intent hygiene
  • Confirm PIR (creation) and CIR (consumption) naming and provenance rules.
  1. Document conformance posture
  • Decide conformance level (Aligned/Conformant/Strict) and publish conformance criteria for the domain.

Summary​

UPOS specialization is not “copy and paste.”
It is a controlled refinement process:

  • preserve UPOS invariants (planes, governance kernel, descriptors, versioning, ProductVerse),
  • specialize domain semantics, obligations, port forms, blueprints, and signals,
  • and ensure PVEP experiences work across the ProductVerse-supporting both browse-first and intent-first discovery while keeping PIR/CIR discipline intact.