Published

Product Configuration / Variant

vr.wm-obj-017 · wm-obj-017-product-configuration-variant

Describe a reusable configured product definition between product family and physical instance, including selections, qualified direct properties, capabilities and contextual evidence.

World Models Physical world and living systems PHY.OBJ.TYPE

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 12 findings · 48 questions

Variant identity and family Separate the reusable definition from the product family and its physical instances.

Family and state binding

Bind one definition revision to a family revision; a session is not the reusable root.

Family and state binding record

Bind one definition revision to a family revision; a session is not the reusable root.

Which issuer-qualified definition ID and immutable revision are being described? identity
Which family and option-space revision determine the meaning of these selections? relationship
Is this a partial definition, a resolved configuration or an approved reusable variant? state
Can instances reference this revision without copying their serial numbers or current location into the variant? classification

Commercial identifier scope

Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.

Commercial identifier scope record

Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.

Who issued each SKU or trade identifier and within which catalogue is it unique? identity
If a CPV is present, which GTIN qualifies it and why does the change not require a new GTIN under the consulted rules? constraint
When did each alias become applicable and can an older alias still resolve its historical definition? temporal
Which commercial offers reference this variant without turning a price change into an engineering revision? relationship

Feature selections and origin Make values interpretable before attempting configuration evaluation.

Typed feature domain

Reference the family's feature dictionary and record local restrictions without overwriting its master.

Typed feature domain record

Reference the family's feature dictionary and record local restrictions without overwriting its master.

Which versioned feature concept does the option name denote? definition
Which datatype, unit, precision and allowed range make the selected value comparable? measurement
How many values may be chosen and when does the option become mandatory? requirement
Who approved a new option value and does it extend the family or remain a local proposal? authority

Explicit, inherited and computed values

Store a typed value separately from its origin and absence reason; freeze released values.

Explicit, inherited and computed values record

Store a typed value separately from its origin and absence reason; freeze released values.

Was the value chosen, inherited, defaulted or calculated and which source revision produced it? provenance
Does no recorded value mean unknown, unresolved, not applicable or genuinely omitted rather than false? state
Which unfinished configurations must be reevaluated after a family default changes? lifecycle
Can the released selection be reconstructed without rereading a mutable default or rerunning an unpinned formula? evidence

Compatibility and resolution Keep rules, verdicts and explanations distinct; never treat feasibility as permission.

Pinned constraints and calculations

Reference the applicable rule set; evaluation occurs only in an authorized adapter.

Pinned constraints and calculations record

Reference the applicable rule set; evaluation occurs only in an authorized adapter.

Which requires, excludes or group-cardinality rule applies to this component and its selected features? constraint
Does an absent compatibility-table combination mean forbidden or merely unknown? exception
Which declared engine understands this rule language and how are cycles, unsupported types or evaluation limits reported? process
Are imported expressions treated as data until an authorized bounded adapter evaluates the pinned version? security

Completeness and satisfiability evidence

Report independent dimensions of evaluation rather than a single overloaded valid flag.

Completeness and satisfiability evidence record

Report independent dimensions of evaluation rather than a single overloaded valid flag.

Is the selection complete independently of whether a feasible completion exists? validation
Which selected values and constraints explain a contradiction, and is the explanation complete or only partial? exception
Can another approved evaluator reproduce the verdict from the same inputs, rules and engine profile? evidence
Is an alternative merely technically feasible, actually available, or also authorized for this context? decision

Physical definition and usable capabilities Describe nominal reality without inventing measurements or assuring safe operation.

Nominal physical and recognition signature

Proposed Vercy extension: qualified direct properties supplement product classification and context.

Nominal physical and recognition signature record

Proposed Vercy extension: qualified direct properties supplement product classification and context.

Which physical class and material definition apply to the configured product? classification
What nominal dimensions, mass, density or hardness are actually supported, in which units and under which conditions? measurement
Which visible features distinguish this variant from siblings and where would recognition remain ambiguous? quality
Which location, orientation or condition claims must come from an observed instance rather than this reusable definition? spatial

Functions, interfaces and use envelope

Proposed capability contract stores evidence and operating limits, not automatic actuation authority.

Functions, interfaces and use envelope record

Proposed capability contract stores evidence and operating limits, not automatic actuation authority.

What actions can this variant support and which inputs, outputs and preconditions describe them? definition
Which interface revision and evidence justify a claimed compatible connection? interoperability
Within which load, temperature, power and handling limits are the declared functions supported? constraint
Which qualification evidence supports those limits and which claims still require inspection of the built item? evidence

Design baseline and lifecycle Connect definition to engineering and manufacturing masters without replacing them.

Design, selected composition and effectivity

Bind exact engineering baselines and qualify where they apply.

Design, selected composition and effectivity record

Bind exact engineering baselines and qualify where they apply.

Which engineering design and selected BOM revision define this configuration? composition
Which component alternatives or quantities are unresolved and therefore prevent baseline release? exception
Which effective dates, production contexts or serial ranges include this baseline and how are boundary instants interpreted? temporal
Where are the manufacturing, installation and sale conditions mastered rather than duplicated? relationship

Approval, revision and replacement

Released revisions stay reproducible when defaults, designs or commercial mappings change.

Approval, revision and replacement record

Released revisions stay reproducible when defaults, designs or commercial mappings change.

Who approved this baseline and which requirements and evaluation receipts support the release? authority
Does the change require a new variant identity or a revision under the declared allocation policy? lifecycle
In which direction is a successor a permitted substitute and which fit or function differences prevent interchangeability? constraint
After retirement, which historical revision and service obligations must remain resolvable for existing items? retention

Governance and loss-aware exchange Preserve authority and meaning across Dimensions and representations.

Definition mastership and confidential selections

Vercy policy: local adaptation cannot silently replace organization-owned product definition.

Definition mastership and confidential selections record

Vercy policy: local adaptation cannot silently replace organization-owned product definition.

Which organization or Dimension controls the definition and who may propose versus release extensions? ownership
Which options expose confidential design or customer requirements and who may read each scope? access
Can an agent reference organizational context without copying a private customer selection into a public variant? privacy
What minimal tombstone preserves dependent-item interpretation after authorized deletion without retaining unnecessary personal data? retention

Versioned projections and semantic loss

Mappings require tests; a common name does not prove identity or equivalent constraint semantics.

Versioned projections and semantic loss record

Mappings require tests; a common name does not prove identity or equivalent constraint semantics.

Which source and target releases and dictionary permissions govern this projection? interoperability
Does the Schema.org projection preserve grouping exceptions instead of assuming transitive feature inheritance? constraint
Which rules, effectivity expressions or provenance facts cannot survive the target format and how is that loss exposed? quality
Which round-trip fixtures demonstrate preserved variant identity and which constructs remain unverified? validation

Classifiers Filled

Family: World Models
Category: Physical world and living systems
Entry kind: aggregate
Navigation path: NAV.PHY.OBJ.TYPE
Domain: PHY.OBJ.TYPE
Industry: Cross-industry
Tags: productconfigurationvariantphy.obj.type

What it is Filled

The aggregate owns a versioned partial, resolved or released configuration definition and its selected-feature assertions, rule/evaluation bindings, nominal properties, lifecycle and mappings. The whole family option space, design, BOM, item, session, offer and order remain external masters.

In scope

Definition identity, scoped aliases, selections, rules and reproducible evaluation evidence
Nominal physical properties, recognition features, capabilities and explicit use limits
Design/BOM links, effectivity, release, stewardship and loss-aware interchange

Out of scope

Owning the full product family, solver implementation, engineering design, BOM, item instance, inventory, offer, order or session lifecycle
Automatic physical operation, certification, undisclosed customer data transfer or execution of imported rule code

Why it exists Filled

Describe a reusable configured product definition between product family and physical instance, including selections, qualified direct properties, capabilities and contextual evidence.

Distinguishing features Filled

Sits between a product family or catalog item and a physical item: one resolved set of feature choices, not the whole option space.
Holds nominal properties of the configured definition, not measured values of a built unit.
Differs from an engineering BOM: it records selected features and rule results, while the BOM records component occurrences.
Differs from a configuration session, offer or order: those are transactions that may reference a released variant.

What robots and AI may and may not do Filled

Must not

Declare a configuration buildable or safe without a retained evaluator verdict.
Infer physical limits, materials or certifications from the product class name.
Execute imported rule code from an external configurator.
Disclose customer-specific or confidential configurations without authority.
Release or retire a variant that existing items still depend on without continuity handling.

Only with a human decision

Releasing a variant as a reusable baseline.
Accepting a configuration that a rule marks as an exception.
Retiring a released variant.

May

Resolve the product family and aliases before reading a variant.
Explain which selections, inherited values and rules produced a variant.
Request a feasibility check from an approved evaluator and store its verdict.
Compare variants and report differences in features and nominal properties.

Moral aspects Filled

Wrong nominal properties for a variant can reach buyers as safety or capacity claims.
Customer-specific configurations can reveal private needs, such as accessibility or medical adaptations.
Hidden option rules can steer buyers to costlier variants without explanation.

Who is affected

Buyers and users of the configured product
Engineers and release authorities accountable for the definition
Service and repair staff who rely on the variant record

Owners Filled

Steward

Declare the accountable Dimension owner and authorized product-definition masters.

Roles

Dimension owner: Sets storage, namespace and federated access policy.
Product definition steward: Owns family binding, identifier allocation and proposed changes.
Configuration author: Records selections and provenance without releasing an unapproved variant.
Engineering reviewer: Checks rule verdict, nominal-property evidence, composition and effectivity.
Release authority: Approves immutable baseline within delegated scope.
Projection maintainer: Tests mappings and reports semantic loss without changing source meaning.

Links to other meta-models Filled

references

WM-OBJ-002 - Resolve the versioned family and option-space master.
WM-OBJ-001 - CLASSIFIES configured physical instances without owning their identity or state; explicit projection of frozen registry relation.
WM-OBJ-018 - Bind the selected engineering design revision.
WM-OBJ-019 - Bind selected BOM occurrences, quantities and alternatives.
Offer, order, inventory and configuration-session masters - Resolve commercial and customer context without copying private or volatile records.

aligned

Schema.org ProductGroup and ProductModel; GS1 CPV 1.1; OASIS UBL 2.4 - Candidate projections only; preserve identity scope and publish unsupported semantics and inheritance differences.

neighbor

WM-OBJ-002 Product Type / Catalog Item - Family and option-space masters are referenced by revision; this root owns one reusable selection definition.
WM-OBJ-001 Physical Object / Item - Frozen registry relation CLASSIFIES is represented by a REFERENCE with explicit classifies meaning because the research schema lacks CLASSIFIES. Nominal properties are not observed instance state.
WM-OBJ-018 Engineering Design / Product Definition and WM-OBJ-019 Component Type / Engineering BOM - Engineering masters retain designs and composition. This definition binds selected revisions and applicability, not their independent lifecycles.
Offer, order, inventory and configuration session - Pricing, availability, customer intent and temporal selections remain separately mastered context; a session may yield a reusable definition but is not that definition.

parent

WM-OBJ-002

What else AI and robots need to interact with it Filled

Sources Filled

ProductGroup - Schema.org
ProductModel - Schema.org
Consumer Product Variant in GDSN implementation guideline - GS1
Product configuration models overview - Microsoft
Universal Business Language - OASIS
PROV-DM - W3C
Date and Time on the Internet: Timestamps - IETF
Guidelines for configuration management - ISO
Managed model-based 3D engineering - ISO

Open questions

Real manufacturer configuration fixtures with incomplete, contradictory, timeout, revised-default and released-baseline cases.
Vendor-neutral solver adapter and executable instance-validation schema with typed quantities, absence states and reproducible receipts.
Target-version mapping and round-trip fixtures, including explicit rule/effectivity sidecars or rejection of unsupported required semantics.
Sector metrology, recognition uncertainty, capability qualification and jurisdiction-specific evidence requirements.
Licensed engineering standards and dictionary inspection before any normative alignment or conformance assertion.
Claude and Grok research both timed out after one bounded attempt. No external research result was admitted; provider waiver remains visible even if separate no-tools review succeeds.
ISO 10007 and AP242 were inspected only through public abstracts/scopes, not licensed clauses. Dictionary, domain and normative mapping verification remains on hold.
Sector-specific automotive, medical, food, aerospace, building-product and regulated-market profiles require specialist evidence and fixtures.
The typed data elements are an information contract, not a complete executable instance-validation schema or constraint solver. No implementation conformance is claimed.
Broad physical properties and capability envelopes are proposed Vercy extensions. Every real property requires its own evidence, unit, conditions and uncertainty; no universal hardness, fragility or safety ontology is supplied.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-obj-017-product-configuration-variant/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-017-product-configuration-variant.json