{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-obj-017","code":"wm-obj-017-product-configuration-variant","url":"https://ver.cy/models/wm-obj-017-product-configuration-variant/","name":"Product Configuration / Variant","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"aggregate","plane":"","domain":["PHY.OBJ.TYPE"],"industry":["Cross-industry"],"navPath":"NAV.PHY.OBJ.TYPE","tags":["product","configuration","variant","phy.obj.type"],"facets":{}},"whatItIs":"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.","purpose":"Describe a reusable configured product definition between product family and physical instance, including selections, qualified direct properties, capabilities and contextual evidence.","scope":{"in":["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":["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"],"boundaries":[{"neighbor":"WM-OBJ-002 Product Type / Catalog Item","distinction":"Family and option-space masters are referenced by revision; this root owns one reusable selection definition."},{"neighbor":"WM-OBJ-001 Physical Object / Item","distinction":"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."},{"neighbor":"WM-OBJ-018 Engineering Design / Product Definition and WM-OBJ-019 Component Type / Engineering BOM","distinction":"Engineering masters retain designs and composition. This definition binds selected revisions and applicability, not their independent lifecycles."},{"neighbor":"Offer, order, inventory and configuration session","distinction":"Pricing, availability, customer intent and temporal selections remain separately mastered context; a session may yield a reusable definition but is not that definition."}]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"variant-identity","name":"Variant identity and family","description":"Separate the reusable definition from the product family and its physical instances.","layers":[{"id":"family-binding","name":"Family and state binding","description":"Bind one definition revision to a family revision; a session is not the reusable root.","findings":[{"id":"family-binding-record","name":"Family and state binding record","description":"Bind one definition revision to a family revision; a session is not the reusable root.","questions":[{"text":"Which issuer-qualified definition ID and immutable revision are being described?","id":"family-binding-q01","kind":"identity"},{"text":"Which family and option-space revision determine the meaning of these selections?","id":"family-binding-q02","kind":"relationship"},{"text":"Is this a partial definition, a resolved configuration or an approved reusable variant?","id":"family-binding-q03","kind":"state"},{"text":"Can instances reference this revision without copying their serial numbers or current location into the variant?","id":"family-binding-q04","kind":"classification"}]}]},{"id":"identifier-crosswalk","name":"Commercial identifier scope","description":"Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.","findings":[{"id":"identifier-crosswalk-record","name":"Commercial identifier scope record","description":"Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.","questions":[{"text":"Who issued each SKU or trade identifier and within which catalogue is it unique?","id":"identifier-crosswalk-q01","kind":"identity"},{"text":"If a CPV is present, which GTIN qualifies it and why does the change not require a new GTIN under the consulted rules?","id":"identifier-crosswalk-q02","kind":"constraint"},{"text":"When did each alias become applicable and can an older alias still resolve its historical definition?","id":"identifier-crosswalk-q03","kind":"temporal"},{"text":"Which commercial offers reference this variant without turning a price change into an engineering revision?","id":"identifier-crosswalk-q04","kind":"relationship"}]}]}]},{"id":"feature-selections","name":"Feature selections and origin","description":"Make values interpretable before attempting configuration evaluation.","layers":[{"id":"option-domain","name":"Typed feature domain","description":"Reference the family's feature dictionary and record local restrictions without overwriting its master.","findings":[{"id":"option-domain-record","name":"Typed feature domain record","description":"Reference the family's feature dictionary and record local restrictions without overwriting its master.","questions":[{"text":"Which versioned feature concept does the option name denote?","id":"option-domain-q01","kind":"definition"},{"text":"Which datatype, unit, precision and allowed range make the selected value comparable?","id":"option-domain-q02","kind":"measurement"},{"text":"How many values may be chosen and when does the option become mandatory?","id":"option-domain-q03","kind":"requirement"},{"text":"Who approved a new option value and does it extend the family or remain a local proposal?","id":"option-domain-q04","kind":"authority"}]}]},{"id":"selection-origin","name":"Explicit, inherited and computed values","description":"Store a typed value separately from its origin and absence reason; freeze released values.","findings":[{"id":"selection-origin-record","name":"Explicit, inherited and computed values record","description":"Store a typed value separately from its origin and absence reason; freeze released values.","questions":[{"text":"Was the value chosen, inherited, defaulted or calculated and which source revision produced it?","id":"selection-origin-q01","kind":"provenance"},{"text":"Does no recorded value mean unknown, unresolved, not applicable or genuinely omitted rather than false?","id":"selection-origin-q02","kind":"state"},{"text":"Which unfinished configurations must be reevaluated after a family default changes?","id":"selection-origin-q03","kind":"lifecycle"},{"text":"Can the released selection be reconstructed without rereading a mutable default or rerunning an unpinned formula?","id":"selection-origin-q04","kind":"evidence"}]}]}]},{"id":"configuration-evaluation","name":"Compatibility and resolution","description":"Keep rules, verdicts and explanations distinct; never treat feasibility as permission.","layers":[{"id":"rule-binding","name":"Pinned constraints and calculations","description":"Reference the applicable rule set; evaluation occurs only in an authorized adapter.","findings":[{"id":"rule-binding-record","name":"Pinned constraints and calculations record","description":"Reference the applicable rule set; evaluation occurs only in an authorized adapter.","questions":[{"text":"Which requires, excludes or group-cardinality rule applies to this component and its selected features?","id":"rule-binding-q01","kind":"constraint"},{"text":"Does an absent compatibility-table combination mean forbidden or merely unknown?","id":"rule-binding-q02","kind":"exception"},{"text":"Which declared engine understands this rule language and how are cycles, unsupported types or evaluation limits reported?","id":"rule-binding-q03","kind":"process"},{"text":"Are imported expressions treated as data until an authorized bounded adapter evaluates the pinned version?","id":"rule-binding-q04","kind":"security"}]}]},{"id":"resolution-report","name":"Completeness and satisfiability evidence","description":"Report independent dimensions of evaluation rather than a single overloaded valid flag.","findings":[{"id":"resolution-report-record","name":"Completeness and satisfiability evidence record","description":"Report independent dimensions of evaluation rather than a single overloaded valid flag.","questions":[{"text":"Is the selection complete independently of whether a feasible completion exists?","id":"resolution-report-q01","kind":"validation"},{"text":"Which selected values and constraints explain a contradiction, and is the explanation complete or only partial?","id":"resolution-report-q02","kind":"exception"},{"text":"Can another approved evaluator reproduce the verdict from the same inputs, rules and engine profile?","id":"resolution-report-q03","kind":"evidence"},{"text":"Is an alternative merely technically feasible, actually available, or also authorized for this context?","id":"resolution-report-q04","kind":"decision"}]}]}]},{"id":"resolved-properties","name":"Physical definition and usable capabilities","description":"Describe nominal reality without inventing measurements or assuring safe operation.","layers":[{"id":"physical-signature","name":"Nominal physical and recognition signature","description":"Proposed Vercy extension: qualified direct properties supplement product classification and context.","findings":[{"id":"physical-signature-record","name":"Nominal physical and recognition signature record","description":"Proposed Vercy extension: qualified direct properties supplement product classification and context.","questions":[{"text":"Which physical class and material definition apply to the configured product?","id":"physical-signature-q01","kind":"classification"},{"text":"What nominal dimensions, mass, density or hardness are actually supported, in which units and under which conditions?","id":"physical-signature-q02","kind":"measurement"},{"text":"Which visible features distinguish this variant from siblings and where would recognition remain ambiguous?","id":"physical-signature-q03","kind":"quality"},{"text":"Which location, orientation or condition claims must come from an observed instance rather than this reusable definition?","id":"physical-signature-q04","kind":"spatial"}]}]},{"id":"capability-envelope","name":"Functions, interfaces and use envelope","description":"Proposed capability contract stores evidence and operating limits, not automatic actuation authority.","findings":[{"id":"capability-envelope-record","name":"Functions, interfaces and use envelope record","description":"Proposed capability contract stores evidence and operating limits, not automatic actuation authority.","questions":[{"text":"What actions can this variant support and which inputs, outputs and preconditions describe them?","id":"capability-envelope-q01","kind":"definition"},{"text":"Which interface revision and evidence justify a claimed compatible connection?","id":"capability-envelope-q02","kind":"interoperability"},{"text":"Within which load, temperature, power and handling limits are the declared functions supported?","id":"capability-envelope-q03","kind":"constraint"},{"text":"Which qualification evidence supports those limits and which claims still require inspection of the built item?","id":"capability-envelope-q04","kind":"evidence"}]}]}]},{"id":"baseline-lifecycle","name":"Design baseline and lifecycle","description":"Connect definition to engineering and manufacturing masters without replacing them.","layers":[{"id":"design-effectivity","name":"Design, selected composition and effectivity","description":"Bind exact engineering baselines and qualify where they apply.","findings":[{"id":"design-effectivity-record","name":"Design, selected composition and effectivity record","description":"Bind exact engineering baselines and qualify where they apply.","questions":[{"text":"Which engineering design and selected BOM revision define this configuration?","id":"design-effectivity-q01","kind":"composition"},{"text":"Which component alternatives or quantities are unresolved and therefore prevent baseline release?","id":"design-effectivity-q02","kind":"exception"},{"text":"Which effective dates, production contexts or serial ranges include this baseline and how are boundary instants interpreted?","id":"design-effectivity-q03","kind":"temporal"},{"text":"Where are the manufacturing, installation and sale conditions mastered rather than duplicated?","id":"design-effectivity-q04","kind":"relationship"}]}]},{"id":"release-change","name":"Approval, revision and replacement","description":"Released revisions stay reproducible when defaults, designs or commercial mappings change.","findings":[{"id":"release-change-record","name":"Approval, revision and replacement record","description":"Released revisions stay reproducible when defaults, designs or commercial mappings change.","questions":[{"text":"Who approved this baseline and which requirements and evaluation receipts support the release?","id":"release-change-q01","kind":"authority"},{"text":"Does the change require a new variant identity or a revision under the declared allocation policy?","id":"release-change-q02","kind":"lifecycle"},{"text":"In which direction is a successor a permitted substitute and which fit or function differences prevent interchangeability?","id":"release-change-q03","kind":"constraint"},{"text":"After retirement, which historical revision and service obligations must remain resolvable for existing items?","id":"release-change-q04","kind":"retention"}]}]}]},{"id":"governed-exchange","name":"Governance and loss-aware exchange","description":"Preserve authority and meaning across Dimensions and representations.","layers":[{"id":"mastership-disclosure","name":"Definition mastership and confidential selections","description":"Vercy policy: local adaptation cannot silently replace organization-owned product definition.","findings":[{"id":"mastership-disclosure-record","name":"Definition mastership and confidential selections record","description":"Vercy policy: local adaptation cannot silently replace organization-owned product definition.","questions":[{"text":"Which organization or Dimension controls the definition and who may propose versus release extensions?","id":"mastership-disclosure-q01","kind":"ownership"},{"text":"Which options expose confidential design or customer requirements and who may read each scope?","id":"mastership-disclosure-q02","kind":"access"},{"text":"Can an agent reference organizational context without copying a private customer selection into a public variant?","id":"mastership-disclosure-q03","kind":"privacy"},{"text":"What minimal tombstone preserves dependent-item interpretation after authorized deletion without retaining unnecessary personal data?","id":"mastership-disclosure-q04","kind":"retention"}]}]},{"id":"projection-loss","name":"Versioned projections and semantic loss","description":"Mappings require tests; a common name does not prove identity or equivalent constraint semantics.","findings":[{"id":"projection-loss-record","name":"Versioned projections and semantic loss record","description":"Mappings require tests; a common name does not prove identity or equivalent constraint semantics.","questions":[{"text":"Which source and target releases and dictionary permissions govern this projection?","id":"projection-loss-q01","kind":"interoperability"},{"text":"Does the Schema.org projection preserve grouping exceptions instead of assuming transitive feature inheritance?","id":"projection-loss-q02","kind":"constraint"},{"text":"Which rules, effectivity expressions or provenance facts cannot survive the target format and how is that loss exposed?","id":"projection-loss-q03","kind":"quality"},{"text":"Which round-trip fixtures demonstrate preserved variant identity and which constructs remain unverified?","id":"projection-loss-q04","kind":"validation"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["Releasing a variant as a reusable baseline.","Accepting a configuration that a rule marks as an exception.","Retiring a released variant."]},"ethics":{"considerations":["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."],"affectedParties":["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":{"steward":"Declare the accountable Dimension owner and authorized product-definition masters.","roles":[{"name":"Dimension owner","responsibilities":["Sets storage, namespace and federated access policy."]},{"name":"Product definition steward","responsibilities":["Owns family binding, identifier allocation and proposed changes."]},{"name":"Configuration author","responsibilities":["Records selections and provenance without releasing an unapproved variant."]},{"name":"Engineering reviewer","responsibilities":["Checks rule verdict, nominal-property evidence, composition and effectivity."]},{"name":"Release authority","responsibilities":["Approves immutable baseline within delegated scope."]},{"name":"Projection maintainer","responsibilities":["Tests mappings and reports semantic loss without changing source meaning."]}],"masterSystems":[]},"relations":[{"target":"WM-OBJ-002","type":"references","note":"Resolve the versioned family and option-space master."},{"target":"WM-OBJ-001","type":"references","note":"CLASSIFIES configured physical instances without owning their identity or state; explicit projection of frozen registry relation."},{"target":"WM-OBJ-018","type":"references","note":"Bind the selected engineering design revision."},{"target":"WM-OBJ-019","type":"references","note":"Bind selected BOM occurrences, quantities and alternatives."},{"target":"Offer, order, inventory and configuration-session masters","type":"references","note":"Resolve commercial and customer context without copying private or volatile records."},{"target":"Schema.org ProductGroup and ProductModel; GS1 CPV 1.1; OASIS UBL 2.4","type":"aligned","note":"Candidate projections only; preserve identity scope and publish unsupported semantics and inheritance differences."},{"target":"WM-OBJ-002 Product Type / Catalog Item","type":"neighbor","note":"Family and option-space masters are referenced by revision; this root owns one reusable selection definition."},{"target":"WM-OBJ-001 Physical Object / Item","type":"neighbor","note":"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."},{"target":"WM-OBJ-018 Engineering Design / Product Definition and WM-OBJ-019 Component Type / Engineering BOM","type":"neighbor","note":"Engineering masters retain designs and composition. This definition binds selected revisions and applicability, not their independent lifecycles."},{"target":"Offer, order, inventory and configuration session","type":"neighbor","note":"Pricing, availability, customer intent and temporal selections remain separately mastered context; a session may yield a reusable definition but is not that definition."},{"target":"WM-OBJ-002","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system ID","Issuer-qualified UUID","Dimension UUID with immutable revision and digest"]},"properties":{"applicability":"required","items":["Nominal mass in kilograms, stated as unloaded or operating mass.","Nominal overall dimensions in millimetres, with the reference orientation stated.","Rated electrical, mechanical or thermal capacity in SI units, with the rating standard stated.","Operating environment limits such as temperature range in degrees Celsius.","Material and finish designations by referenced classification.","Source and evidence for each value, marked as nominal rather than measured."]},"recognition":{"applicability":"required","items":["A variant is identified by its family reference plus a resolved set of feature values and a revision.","Physical units are matched to it through model or part number, serial plate and configuration code.","Confused with the product type, the individual item, a configuration session and an order line."]},"capabilities":{"applicability":"required","items":["Resolve family and aliases: Resolve issuer scope and family revision before accepting a candidate definition.","Materialize selected values: Resolve inherited and computed inputs while preserving value origin and explicit unknowns.","Evaluate feasibility and completeness: Invoke a separately approved bounded evaluator and retain its verdict; this contract does not implement a solver.","Qualify nominal properties and capabilities: Attach evidence-backed direct properties and limits, leaving absent measurements unknown.","Release a reusable baseline: Record accountable approval only after completeness, feasibility, design applicability and policy checks.","Project a variant with loss report: Translate only supported assertions into a versioned target profile.","Retire with dependent-item continuity: Preserve historical interpretation while honoring authorized retention and minimization rules."]},"hazards":{"applicability":"required","items":["Building or shipping an infeasible or unvalidated combination.","Spare parts or service instructions applied to the wrong variant.","Stale effectivity causing a superseded variant to be sold or built.","Leak of confidential customer configurations."]},"interfaces":{"applicability":"required","items":["ISO 10303-242 (STEP AP242) for configured product structure.","ISO 10303-239 (PLCS) for configuration and effectivity.","IEC 61360 and ISO 13584 property dictionaries.","ECLASS classification and properties.","GS1 GTIN for trade item variants.","UN/CEFACT Recommendation 20 unit codes."]},"context":{"applicability":"required","items":["Market, identifier allocation, safety and retention obligations must be resolved under applicable owner policy and jurisdiction; this draft grants no legal approval."]}},"sources":[{"title":"ProductGroup","url":"https://schema.org/ProductGroup","note":"Schema.org"},{"title":"ProductModel","url":"https://schema.org/ProductModel","note":"Schema.org"},{"title":"Consumer Product Variant in GDSN implementation guideline","url":"https://ref.gs1.org/guidelines/cpv/1.1.0/","note":"GS1"},{"title":"Product configuration models overview","url":"https://learn.microsoft.com/en-us/dynamics365/supply-chain/pim/product-configuration-models","note":"Microsoft"},{"title":"Universal Business Language","url":"https://docs.oasis-open.org/ubl/UBL-2.4.html","note":"OASIS"},{"title":"PROV-DM","url":"https://www.w3.org/TR/prov-dm/","note":"W3C"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"},{"title":"Guidelines for configuration management","url":"https://www.iso.org/standard/70400.html","note":"ISO"},{"title":"Managed model-based 3D engineering","url":"https://www.iso.org/standard/84300.html","note":"ISO"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-obj-017-product-configuration-variant/spec.yaml","agents":"/models/wm-obj-017-product-configuration-variant/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-017"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-obj-017-product-configuration-variant/spec.yaml","ver-cy/world-models/card-supplements/wm-obj-017-product-configuration-variant.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-07T13:27:03Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}