# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-07T13:27:03Z", "synthesisSha256": "5b637e0a4a6918a8445aa8d8cb62bd20ecf9b5f3cccb8b275967631070fdc13c", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-017", "registryId": "vr.wm-obj-017", "name": "Product Configuration / Variant", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.TYPE" ], "tags": [ "product", "configuration", "variant", "phy.obj.type" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-017-product-configuration-variant/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-017", "model": { "registry_id": "vr.wm-obj-017", "model_id": "WM-OBJ-017", "name": "Product Configuration / Variant", "entry_kind": "aggregate", "purpose": "Describe a reusable configured product definition between product family and physical instance, including selections, qualified direct properties, capabilities and contextual evidence.", "scope_statement": "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" ], "boundary_notes": [ { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-009" ] }, { "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.", "source_refs": [ "SRC-004", "SRC-009" ] }, { "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.", "source_refs": [ "SRC-004", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ProductGroup", "organization": "Schema.org", "url": "https://schema.org/ProductGroup", "version_or_date": "development vocabulary inspected 2026-09-07", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Variant groups and explicit variation axes; projection inheritance has exceptions." }, { "id": "SRC-002", "title": "ProductModel", "organization": "Schema.org", "url": "https://schema.org/ProductModel", "version_or_date": "development vocabulary inspected 2026-09-07", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Base-model relationships are not transitive inheritance; model and individual remain distinct." }, { "id": "SRC-003", "title": "Consumer Product Variant in GDSN implementation guideline", "organization": "GS1", "url": "https://ref.gs1.org/guidelines/cpv/1.1.0/", "version_or_date": "1.1, November 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "CPV distinguishes consumer-relevant changes within GTIN scope; first consult GTIN management rules." }, { "id": "SRC-004", "title": "Product configuration models overview", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/pim/product-configuration-models", "version_or_date": "page updated 2026-05-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Implementation evidence for typed options, constraints, calculations and selected BOM references, not universal vendor semantics." }, { "id": "SRC-005", "title": "Universal Business Language", "organization": "OASIS", "url": "https://docs.oasis-open.org/ubl/UBL-2.4.html", "version_or_date": "2.4 pinned edition", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Catalogue item specification and pricing updates have different purposes; use explicit lossy projections." }, { "id": "SRC-006", "title": "PROV-DM", "organization": "W3C", "url": "https://www.w3.org/TR/prov-dm/", "version_or_date": "Recommendation 2013-04-30", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Entity, activity, agent, derivation and attribution vocabulary for selection and release evidence." }, { "id": "SRC-007", "title": "Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Timestamp syntax with seconds and offset; time does not substitute for unique identity." }, { "id": "SRC-008", "title": "Guidelines for configuration management", "organization": "ISO", "url": "https://www.iso.org/standard/70400.html", "version_or_date": "ISO 10007:2017 public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Configuration management scope only; licensed clauses were not inspected and conformance is not claimed." }, { "id": "SRC-009", "title": "Managed model-based 3D engineering", "organization": "ISO", "url": "https://www.iso.org/standard/84300.html", "version_or_date": "ISO 10303-242:2025 public scope only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:24:00Z", "relevance": "Engineering product-data exchange boundary only; no AP242 mapping or clause compliance claim." } ], "structure": { "bundles": [ { "id": "variant-identity", "name": "Variant identity and family", "description": "Separate the reusable definition from the product family and its physical instances.", "rationale": "Proposed Vercy decomposition: Separate the reusable definition from the product family and its physical instances.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "family-binding-q01", "text": "Which issuer-qualified definition ID and immutable revision are being described?", "kind": "identity", "answer_data": [ "family-binding-variant-id", "family-binding-revision" ] }, { "id": "family-binding-q02", "text": "Which family and option-space revision determine the meaning of these selections?", "kind": "relationship", "answer_data": [ "family-binding-family" ] }, { "id": "family-binding-q03", "text": "Is this a partial definition, a resolved configuration or an approved reusable variant?", "kind": "state", "answer_data": [ "family-binding-state" ] }, { "id": "family-binding-q04", "text": "Can instances reference this revision without copying their serial numbers or current location into the variant?", "kind": "classification", "answer_data": [ "family-binding-variant-id", "family-binding-family" ] } ], "data_elements": [ { "id": "family-binding-variant-id", "name": "variant-id", "description": "Issuer-qualified master ID; immutable across non-breaking revisions.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "family-binding-revision", "name": "revision", "description": "Immutable revision, not a mutable latest pointer.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "family-binding-family", "name": "family", "description": "WM-OBJ-002 identity, revision, option-space revision and master locator.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "family-binding-state", "name": "state", "description": "partial, resolved, released, superseded or retired. Resolution and release are separate gates.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "family-binding-evidence", "name": "Definition and family-binding manifest", "description": "Versioned evidence for family and state binding; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "identifier-crosswalk", "name": "Commercial identifier scope", "description": "Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "identifier-crosswalk-record", "name": "Commercial identifier scope record", "description": "Identifiers are scoped aliases; none is assumed equivalent to every engineering definition.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "identifier-crosswalk-q01", "text": "Who issued each SKU or trade identifier and within which catalogue is it unique?", "kind": "identity", "answer_data": [ "identifier-crosswalk-aliases" ] }, { "id": "identifier-crosswalk-q02", "text": "If a CPV is present, which GTIN qualifies it and why does the change not require a new GTIN under the consulted rules?", "kind": "constraint", "answer_data": [ "identifier-crosswalk-aliases", "identifier-crosswalk-identity-decision" ] }, { "id": "identifier-crosswalk-q03", "text": "When did each alias become applicable and can an older alias still resolve its historical definition?", "kind": "temporal", "answer_data": [ "identifier-crosswalk-aliases" ] }, { "id": "identifier-crosswalk-q04", "text": "Which commercial offers reference this variant without turning a price change into an engineering revision?", "kind": "relationship", "answer_data": [ "identifier-crosswalk-offer-links" ] } ], "data_elements": [ { "id": "identifier-crosswalk-aliases", "name": "aliases", "description": "Scheme, issuer, value, scope, validity interval and mapped revision for SKU, GTIN or CPV.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "identifier-crosswalk-identity-decision", "name": "identity-decision", "description": "Accountable decision, consulted allocation policy version and rationale for new ID versus alias.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "identifier-crosswalk-offer-links", "name": "offer-links", "description": "Separate seller offers and their own price and availability masters.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "identifier-crosswalk-evidence", "name": "Identifier allocation and crosswalk decision", "description": "Versioned evidence for commercial identifier scope; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "feature-selections", "name": "Feature selections and origin", "description": "Make values interpretable before attempting configuration evaluation.", "rationale": "Proposed Vercy decomposition: Make values interpretable before attempting configuration evaluation.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "layers": [ { "id": "option-domain", "name": "Typed feature domain", "description": "Reference the family's feature dictionary and record local restrictions without overwriting its master.", "source_refs": [ "SRC-001", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "option-domain-q01", "text": "Which versioned feature concept does the option name denote?", "kind": "definition", "answer_data": [ "option-domain-feature" ] }, { "id": "option-domain-q02", "text": "Which datatype, unit, precision and allowed range make the selected value comparable?", "kind": "measurement", "answer_data": [ "option-domain-domain" ] }, { "id": "option-domain-q03", "text": "How many values may be chosen and when does the option become mandatory?", "kind": "requirement", "answer_data": [ "option-domain-multiplicity" ] }, { "id": "option-domain-q04", "text": "Who approved a new option value and does it extend the family or remain a local proposal?", "kind": "authority", "answer_data": [ "option-domain-extensions" ] } ], "data_elements": [ { "id": "option-domain-feature", "name": "feature", "description": "Stable feature concept and versioned dictionary reference.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "option-domain-domain", "name": "domain", "description": "Primitive type, enum or range, quantity kind, unit URI, precision and valid bounds.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "option-domain-multiplicity", "name": "multiplicity", "description": "Minimum and maximum choices, conditional mandatory predicate and option group.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "option-domain-extensions", "name": "extensions", "description": "Namespaced proposed option values, approval state and family compatibility assessment.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "option-domain-evidence", "name": "Feature-domain restriction record", "description": "Versioned evidence for typed feature domain; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "selection-origin", "name": "Explicit, inherited and computed values", "description": "Store a typed value separately from its origin and absence reason; freeze released values.", "source_refs": [ "SRC-004", "SRC-006" ], "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.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "selection-origin-q01", "text": "Was the value chosen, inherited, defaulted or calculated and which source revision produced it?", "kind": "provenance", "answer_data": [ "selection-origin-origin", "selection-origin-derivation" ] }, { "id": "selection-origin-q02", "text": "Does no recorded value mean unknown, unresolved, not applicable or genuinely omitted rather than false?", "kind": "state", "answer_data": [ "selection-origin-value" ] }, { "id": "selection-origin-q03", "text": "Which unfinished configurations must be reevaluated after a family default changes?", "kind": "lifecycle", "answer_data": [ "selection-origin-default-impact" ] }, { "id": "selection-origin-q04", "text": "Can the released selection be reconstructed without rereading a mutable default or rerunning an unpinned formula?", "kind": "evidence", "answer_data": [ "selection-origin-value", "selection-origin-derivation" ] } ], "data_elements": [ { "id": "selection-origin-value", "name": "value", "description": "Typed selected value or explicit absence tag: unknown, unresolved, not-applicable or omitted. False remains a value.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "selection-origin-origin", "name": "origin", "description": "explicit, inherited, defaulted or computed; never infer origin from equality alone.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "selection-origin-derivation", "name": "derivation", "description": "Source revision, actor or activity, rule version and evidence reference; non-executing.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "selection-origin-default-impact", "name": "default-impact", "description": "Changed defaults and affected draft revisions; released values are retained.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "selection-origin-evidence", "name": "Selection provenance snapshot", "description": "Versioned evidence for explicit, inherited and computed values; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "configuration-evaluation", "name": "Compatibility and resolution", "description": "Keep rules, verdicts and explanations distinct; never treat feasibility as permission.", "rationale": "Proposed Vercy decomposition: Keep rules, verdicts and explanations distinct; never treat feasibility as permission.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "layers": [ { "id": "rule-binding", "name": "Pinned constraints and calculations", "description": "Reference the applicable rule set; evaluation occurs only in an authorized adapter.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "rule-binding-record", "name": "Pinned constraints and calculations record", "description": "Reference the applicable rule set; evaluation occurs only in an authorized adapter.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "rule-binding-q01", "text": "Which requires, excludes or group-cardinality rule applies to this component and its selected features?", "kind": "constraint", "answer_data": [ "rule-binding-rules" ] }, { "id": "rule-binding-q02", "text": "Does an absent compatibility-table combination mean forbidden or merely unknown?", "kind": "exception", "answer_data": [ "rule-binding-table-policy" ] }, { "id": "rule-binding-q03", "text": "Which declared engine understands this rule language and how are cycles, unsupported types or evaluation limits reported?", "kind": "process", "answer_data": [ "rule-binding-evaluation-context" ] }, { "id": "rule-binding-q04", "text": "Are imported expressions treated as data until an authorized bounded adapter evaluates the pinned version?", "kind": "security", "answer_data": [ "rule-binding-rules", "rule-binding-evaluation-context" ] } ], "data_elements": [ { "id": "rule-binding-rules", "name": "rules", "description": "Rule ID, revision, language, requires/excludes/cardinality/formula/table kind, component scope and digest.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "rule-binding-table-policy", "name": "table-policy", "description": "Closed or open world, meaning of absent rows and effective table snapshot.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "rule-binding-evaluation-context", "name": "evaluation-context", "description": "Engine/profile version, supported datatypes, bounded execution settings and input digest.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "rule-binding-evidence", "name": "Constraint-set binding and evaluation profile", "description": "Versioned evidence for pinned constraints and calculations; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "resolution-report", "name": "Completeness and satisfiability evidence", "description": "Report independent dimensions of evaluation rather than a single overloaded valid flag.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "resolution-report-record", "name": "Completeness and satisfiability evidence record", "description": "Report independent dimensions of evaluation rather than a single overloaded valid flag.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "resolution-report-q01", "text": "Is the selection complete independently of whether a feasible completion exists?", "kind": "validation", "answer_data": [ "resolution-report-completeness", "resolution-report-feasibility" ] }, { "id": "resolution-report-q02", "text": "Which selected values and constraints explain a contradiction, and is the explanation complete or only partial?", "kind": "exception", "answer_data": [ "resolution-report-explanation" ] }, { "id": "resolution-report-q03", "text": "Can another approved evaluator reproduce the verdict from the same inputs, rules and engine profile?", "kind": "evidence", "answer_data": [ "resolution-report-decision-context" ] }, { "id": "resolution-report-q04", "text": "Is an alternative merely technically feasible, actually available, or also authorized for this context?", "kind": "decision", "answer_data": [ "resolution-report-decision-context", "resolution-report-explanation" ] } ], "data_elements": [ { "id": "resolution-report-completeness", "name": "completeness", "description": "Complete or incomplete, missing mandatory features and rule-set scope.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "resolution-report-feasibility", "name": "feasibility", "description": "satisfiable, unsatisfiable, unknown, untested or error; timeout is unknown, never success.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "resolution-report-explanation", "name": "explanation", "description": "Conflicting inputs and rule references, alternatives and explanation completeness; no minimal-core claim without proof.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "resolution-report-decision-context", "name": "decision-context", "description": "Input/rule/engine digest, evaluation time, assumptions and separate availability and authorization decisions.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "resolution-report-evidence", "name": "Configuration evaluation receipt", "description": "Versioned evidence for completeness and satisfiability evidence; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "resolved-properties", "name": "Physical definition and usable capabilities", "description": "Describe nominal reality without inventing measurements or assuring safe operation.", "rationale": "Proposed Vercy decomposition: Describe nominal reality without inventing measurements or assuring safe operation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "layers": [ { "id": "physical-signature", "name": "Nominal physical and recognition signature", "description": "Proposed Vercy extension: qualified direct properties supplement product classification and context.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "findings": [ { "id": "physical-signature-record", "name": "Nominal physical and recognition signature record", "description": "Proposed Vercy extension: qualified direct properties supplement product classification and context.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "questions": [ { "id": "physical-signature-q01", "text": "Which physical class and material definition apply to the configured product?", "kind": "classification", "answer_data": [ "physical-signature-physical-class" ] }, { "id": "physical-signature-q02", "text": "What nominal dimensions, mass, density or hardness are actually supported, in which units and under which conditions?", "kind": "measurement", "answer_data": [ "physical-signature-nominal-properties" ] }, { "id": "physical-signature-q03", "text": "Which visible features distinguish this variant from siblings and where would recognition remain ambiguous?", "kind": "quality", "answer_data": [ "physical-signature-recognition" ] }, { "id": "physical-signature-q04", "text": "Which location, orientation or condition claims must come from an observed instance rather than this reusable definition?", "kind": "spatial", "answer_data": [ "physical-signature-instance-required" ] } ], "data_elements": [ { "id": "physical-signature-physical-class", "name": "physical-class", "description": "Physical-object class and material dictionary revision; unknown if unverified.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "physical-signature-nominal-properties", "name": "nominal-properties", "description": "Dimension, mass, density, hardness or material property: value, unit, tolerance, method, conditions and evidence; distinguish bulk from component values.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "physical-signature-recognition", "name": "recognition", "description": "Colour, finish, markings, geometry or distinguishing feature; sibling contrasts, ambiguity and evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "physical-signature-instance-required", "name": "instance-required", "description": "Location, damage, actual mass or other properties requiring a specific item observation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "artifacts": [ { "id": "physical-signature-evidence", "name": "Nominal property and recognition evidence", "description": "Versioned evidence for nominal physical and recognition signature; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "capability-envelope", "name": "Functions, interfaces and use envelope", "description": "Proposed capability contract stores evidence and operating limits, not automatic actuation authority.", "source_refs": [ "SRC-002", "SRC-009" ], "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.", "source_refs": [ "SRC-002", "SRC-009" ], "questions": [ { "id": "capability-envelope-q01", "text": "What actions can this variant support and which inputs, outputs and preconditions describe them?", "kind": "definition", "answer_data": [ "capability-envelope-capabilities" ] }, { "id": "capability-envelope-q02", "text": "Which interface revision and evidence justify a claimed compatible connection?", "kind": "interoperability", "answer_data": [ "capability-envelope-interfaces" ] }, { "id": "capability-envelope-q03", "text": "Within which load, temperature, power and handling limits are the declared functions supported?", "kind": "constraint", "answer_data": [ "capability-envelope-limits" ] }, { "id": "capability-envelope-q04", "text": "Which qualification evidence supports those limits and which claims still require inspection of the built item?", "kind": "evidence", "answer_data": [ "capability-envelope-qualification" ] } ], "data_elements": [ { "id": "capability-envelope-capabilities", "name": "capabilities", "description": "Functional class, supported action, input/output and manufacturer-declared preconditions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-009" ] }, { "id": "capability-envelope-interfaces", "name": "interfaces", "description": "Mechanical, electrical or protocol connector and revision with mating compatibility evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-009" ] }, { "id": "capability-envelope-limits", "name": "limits", "description": "Rated load, temperature, power, fragility, handling or prohibited-use limit with conditions and source.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-009" ] }, { "id": "capability-envelope-qualification", "name": "qualification", "description": "Applicable test or declaration references and unknowns; rating is not legal approval or present operability.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-009" ] } ], "artifacts": [ { "id": "capability-envelope-evidence", "name": "Capability and limit declaration", "description": "Versioned evidence for functions, interfaces and use envelope; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-002", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "baseline-lifecycle", "name": "Design baseline and lifecycle", "description": "Connect definition to engineering and manufacturing masters without replacing them.", "rationale": "Proposed Vercy decomposition: Connect definition to engineering and manufacturing masters without replacing them.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-009" ], "layers": [ { "id": "design-effectivity", "name": "Design, selected composition and effectivity", "description": "Bind exact engineering baselines and qualify where they apply.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ], "findings": [ { "id": "design-effectivity-record", "name": "Design, selected composition and effectivity record", "description": "Bind exact engineering baselines and qualify where they apply.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ], "questions": [ { "id": "design-effectivity-q01", "text": "Which engineering design and selected BOM revision define this configuration?", "kind": "composition", "answer_data": [ "design-effectivity-design", "design-effectivity-selected-bom" ] }, { "id": "design-effectivity-q02", "text": "Which component alternatives or quantities are unresolved and therefore prevent baseline release?", "kind": "exception", "answer_data": [ "design-effectivity-selected-bom" ] }, { "id": "design-effectivity-q03", "text": "Which effective dates, production contexts or serial ranges include this baseline and how are boundary instants interpreted?", "kind": "temporal", "answer_data": [ "design-effectivity-effectivity" ] }, { "id": "design-effectivity-q04", "text": "Where are the manufacturing, installation and sale conditions mastered rather than duplicated?", "kind": "relationship", "answer_data": [ "design-effectivity-context-links" ] } ], "data_elements": [ { "id": "design-effectivity-design", "name": "design", "description": "WM-OBJ-018 design identity, revision and source master.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] }, { "id": "design-effectivity-selected-bom", "name": "selected-bom", "description": "WM-OBJ-019 BOM revision and selected occurrence/quantity bindings; unresolved alternatives explicit.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] }, { "id": "design-effectivity-effectivity", "name": "effectivity", "description": "Predicate over date, production context, market or serial range with timezone, boundary inclusion and unresolved context.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] }, { "id": "design-effectivity-context-links", "name": "context-links", "description": "External manufacturing, installation and sale context references; no personal-order data copied.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "design-effectivity-evidence", "name": "Engineering baseline and applicability binding", "description": "Versioned evidence for design, selected composition and effectivity; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "release-change", "name": "Approval, revision and replacement", "description": "Released revisions stay reproducible when defaults, designs or commercial mappings change.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ], "findings": [ { "id": "release-change-record", "name": "Approval, revision and replacement record", "description": "Released revisions stay reproducible when defaults, designs or commercial mappings change.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ], "questions": [ { "id": "release-change-q01", "text": "Who approved this baseline and which requirements and evaluation receipts support the release?", "kind": "authority", "answer_data": [ "release-change-approval" ] }, { "id": "release-change-q02", "text": "Does the change require a new variant identity or a revision under the declared allocation policy?", "kind": "lifecycle", "answer_data": [ "release-change-change" ] }, { "id": "release-change-q03", "text": "In which direction is a successor a permitted substitute and which fit or function differences prevent interchangeability?", "kind": "constraint", "answer_data": [ "release-change-replacement" ] }, { "id": "release-change-q04", "text": "After retirement, which historical revision and service obligations must remain resolvable for existing items?", "kind": "retention", "answer_data": [ "release-change-retirement" ] } ], "data_elements": [ { "id": "release-change-approval", "name": "approval", "description": "Approver, authority, requirement and evaluation receipts, approval time and allowed release context.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "release-change-change", "name": "change", "description": "Before/after revision, reason, impact and identity decision; optimistic expected-base digest.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "release-change-replacement", "name": "replacement", "description": "Predecessor/successor, substitution direction, fit/function evidence and restrictions; no automatic equivalence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "release-change-retirement", "name": "retirement", "description": "Retirement state/time/reason, remaining service obligations and durable historical resolution.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "release-change-evidence", "name": "Release and change-control receipt", "description": "Versioned evidence for approval, revision and replacement; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governed-exchange", "name": "Governance and loss-aware exchange", "description": "Preserve authority and meaning across Dimensions and representations.", "rationale": "Proposed Vercy decomposition: Preserve authority and meaning across Dimensions and representations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-009" ], "layers": [ { "id": "mastership-disclosure", "name": "Definition mastership and confidential selections", "description": "Vercy policy: local adaptation cannot silently replace organization-owned product definition.", "source_refs": [ "SRC-006", "SRC-008" ], "findings": [ { "id": "mastership-disclosure-record", "name": "Definition mastership and confidential selections record", "description": "Vercy policy: local adaptation cannot silently replace organization-owned product definition.", "source_refs": [ "SRC-006", "SRC-008" ], "questions": [ { "id": "mastership-disclosure-q01", "text": "Which organization or Dimension controls the definition and who may propose versus release extensions?", "kind": "ownership", "answer_data": [ "mastership-disclosure-mastership" ] }, { "id": "mastership-disclosure-q02", "text": "Which options expose confidential design or customer requirements and who may read each scope?", "kind": "access", "answer_data": [ "mastership-disclosure-disclosure" ] }, { "id": "mastership-disclosure-q03", "text": "Can an agent reference organizational context without copying a private customer selection into a public variant?", "kind": "privacy", "answer_data": [ "mastership-disclosure-disclosure", "mastership-disclosure-mastership" ] }, { "id": "mastership-disclosure-q04", "text": "What minimal tombstone preserves dependent-item interpretation after authorized deletion without retaining unnecessary personal data?", "kind": "retention", "answer_data": [ "mastership-disclosure-retention-policy" ] } ], "data_elements": [ { "id": "mastership-disclosure-mastership", "name": "mastership", "description": "Dimension, accountable owner, source location, write authority and field-level stewardship.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "mastership-disclosure-disclosure", "name": "disclosure", "description": "Audience, purpose, confidentiality scopes and redaction policy; personal selections stay in their owning Dimension.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "mastership-disclosure-retention-policy", "name": "retention-policy", "description": "Retention period/event, hold, tombstone requirements and minimized provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "mastership-disclosure-evidence", "name": "Variant stewardship and disclosure contract", "description": "Versioned evidence for definition mastership and confidential selections; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "projection-loss", "name": "Versioned projections and semantic loss", "description": "Mappings require tests; a common name does not prove identity or equivalent constraint semantics.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ], "questions": [ { "id": "projection-loss-q01", "text": "Which source and target releases and dictionary permissions govern this projection?", "kind": "interoperability", "answer_data": [ "projection-loss-mapping" ] }, { "id": "projection-loss-q02", "text": "Does the Schema.org projection preserve grouping exceptions instead of assuming transitive feature inheritance?", "kind": "constraint", "answer_data": [ "projection-loss-inheritance-policy" ] }, { "id": "projection-loss-q03", "text": "Which rules, effectivity expressions or provenance facts cannot survive the target format and how is that loss exposed?", "kind": "quality", "answer_data": [ "projection-loss-loss-report" ] }, { "id": "projection-loss-q04", "text": "Which round-trip fixtures demonstrate preserved variant identity and which constructs remain unverified?", "kind": "validation", "answer_data": [ "projection-loss-conformance" ] } ], "data_elements": [ { "id": "projection-loss-mapping", "name": "mapping", "description": "Source and target schema releases, field mappings, transformation version and dictionary license.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] }, { "id": "projection-loss-inheritance-policy", "name": "inheritance-policy", "description": "Explicit handling of ProductGroup exceptions and non-transitive ProductModel inheritance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] }, { "id": "projection-loss-loss-report", "name": "loss-report", "description": "Dropped rules, units, provenance, effectivity or cardinality and reject/sidecar/manual-review disposition.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] }, { "id": "projection-loss-conformance", "name": "conformance", "description": "Fixture, validator version, round-trip result, known unsupported constructs and raw-source digest.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "projection-loss-evidence", "name": "Projection and round-trip loss report", "description": "Versioned evidence for versioned projections and semantic loss; preserves source references and unresolved assertions, without copying external master data.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; otherwise issuer-qualified UUID. Bind immutable variant revision, evidence scope and digest separately; timestamps are not sole IDs.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-family", "name": "Resolve family and aliases", "description": "Resolve issuer scope and family revision before accepting a candidate definition.", "inputs": [ "Master ID or qualified alias", "Authorized family registry" ], "outputs": [ "Unique family and revision or explicit ambiguity" ], "preconditions": [ "Read access is granted" ], "effects": [ "No identifier is silently merged" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "materialize-selection", "name": "Materialize selected values", "description": "Resolve inherited and computed inputs while preserving value origin and explicit unknowns.", "inputs": [ "Pinned family", "Typed choices and derivation evidence" ], "outputs": [ "Revision-bound selection snapshot" ], "preconditions": [ "Options and types resolve; calculations run only in an authorized adapter" ], "effects": [ "Existing released values remain unchanged" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "evaluate-configuration", "name": "Evaluate feasibility and completeness", "description": "Invoke a separately approved bounded evaluator and retain its verdict; this contract does not implement a solver.", "inputs": [ "Pinned rules, input digest and evaluator profile" ], "outputs": [ "Completeness, feasibility and explanation receipt" ], "preconditions": [ "Supported language, authorized evaluator and execution limits" ], "effects": [ "Timeout remains unknown; feasibility grants no release permission" ], "source_refs": [ "SRC-004" ] }, { "id": "qualify-properties", "name": "Qualify nominal properties and capabilities", "description": "Attach evidence-backed direct properties and limits, leaving absent measurements unknown.", "inputs": [ "Selection revision", "Authorized design and qualification evidence" ], "outputs": [ "Qualified physical signature and capability envelope" ], "preconditions": [ "Units, conditions and nominal versus observed scope are explicit" ], "effects": [ "No inferred present operability or safety certification" ], "source_refs": [ "SRC-002", "SRC-009" ] }, { "id": "release-baseline", "name": "Release a reusable baseline", "description": "Record accountable approval only after completeness, feasibility, design applicability and policy checks.", "inputs": [ "Evaluation receipt", "Design/BOM bindings", "Approval authority" ], "outputs": [ "Immutable released revision and change receipt" ], "preconditions": [ "No required unresolved selection; positive feasibility; release authority; expected-base match" ], "effects": [ "Historic revisions remain resolvable; conflicting updates are rejected" ], "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "project-variant", "name": "Project a variant with loss report", "description": "Translate only supported assertions into a versioned target profile.", "inputs": [ "Authorized variant revision", "Tested mapping and target version" ], "outputs": [ "Projection, digest and explicit loss report" ], "preconditions": [ "License and disclosure permit export; unsupported mandatory semantics cause rejection" ], "effects": [ "Source remains unchanged; round-trip differences are visible" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] }, { "id": "retire-variant", "name": "Retire with dependent-item continuity", "description": "Preserve historical interpretation while honoring authorized retention and minimization rules.", "inputs": [ "Retirement authority", "Dependency and hold review" ], "outputs": [ "Retired revision, successor links and minimized tombstone" ], "preconditions": [ "No prohibited deletion or unresolved hold" ], "effects": [ "Retired identity is never reassigned" ], "source_refs": [ "SRC-006", "SRC-008" ] } ], "composition": [ { "target": "WM-OBJ-002", "relation": "REFERENCE", "purpose": "Resolve the versioned family and option-space master.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "target": "WM-OBJ-001", "relation": "REFERENCE", "purpose": "CLASSIFIES configured physical instances without owning their identity or state; explicit projection of frozen registry relation.", "required": false, "source_refs": [ "SRC-002", "SRC-009" ] }, { "target": "WM-OBJ-018", "relation": "REFERENCE", "purpose": "Bind the selected engineering design revision.", "required": false, "source_refs": [ "SRC-009" ] }, { "target": "WM-OBJ-019", "relation": "REFERENCE", "purpose": "Bind selected BOM occurrences, quantities and alternatives.", "required": false, "source_refs": [ "SRC-004", "SRC-009" ] }, { "target": "Offer, order, inventory and configuration-session masters", "relation": "REFERENCE", "purpose": "Resolve commercial and customer context without copying private or volatile records.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "Schema.org ProductGroup and ProductModel; GS1 CPV 1.1; OASIS UBL 2.4", "relation": "ALIGN", "purpose": "Candidate projections only; preserve identity scope and publish unsupported semantics and inheritance differences.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the accountable Dimension owner and authorized product-definition masters.", "Register installed specification and immutable variant revisions with namespace and digest.", "Declare federation and disclosure policy before following organizational or personal links." ], "namespace_guidance": "Use owner-qualified variant IDs with stable local feature keys; a local patch keeps an explicit base revision and never impersonates the organization master.", "registry_links": [ "Dimension model registry", "Variant and family registry", "Engineering baseline registry", "Change and access event registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Freeze family/rule/value revisions; keep type, unit, absence and selection origin distinct.", "A released configuration requires completeness, successful feasibility evaluation and accountable release authority; none implies safety certification." ], "patch_rules": [ "Apply extension only to the authorized owning Dimension using an expected-base digest and namespaced IDs; reject conflicts rather than last-writer-wins.", "Validate option references, types, multiplicities, constraints, effectivity and mapping losses before release; append change evidence." ], "compatibility_rules": [ "Changed defaults never retroactively rewrite released values.", "Evaluate revision versus new identity under owner and adopted external identifier policy; preserve predecessor and substitution direction." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system ID", "Issuer-qualified UUID", "Dimension UUID with immutable revision and digest" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit UTC Z or numeric offset; preserve effective time separately from recording time.", "serial_naming_rule": "Use evidence-type plus opaque record ID and revision; never use a bare date as identity or customer data in filenames.", "integrity_rule": "Record exact-byte digest and media type; verify pinned references, refuse unsafe paths or automatic execution of imported expressions." }, "policies": [ "This specification describes data and proposed operations, not an implemented constraint solver or safety approval system.", "No public disclosure of confidential selections, design files or customer-specific configuration without authority.", "Physical properties and operating limits remain unknown until evidence is supplied; never infer hardness, density or safety from a class name." ], "crud": { "read": [ "Read AGENTS.md, owner policy, pinned specification and variant revision, then only authorized family/rule/design references." ], "create": [ "Reuse the active Dimension, resolve an existing family and allocate a source-qualified partial definition; record unknown values explicitly." ], "update": [ "Write a new revision under expected-base concurrency check; reevaluate affected constraints and retain evidence and historical baselines." ], "delete": [ "Retire by default. Check retention and legal holds and dependent instances before authorized deletion; preserve a minimized tombstone and historical resolution where required." ] }, "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." ] } ], "access": { "default_rule": "Deny undeclared access; public metadata does not grant access to confidential features or linked masters.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Time-limited approved disclosure must identify audience, purpose and redacted fields; retain provenance without revealing protected values." ], "audit_requirements": [ "Record actor, Dimension, target revision, operation, authority decision and RFC 3339 time for changes and protected reads." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Dimension", "Variant master", "Revision", "Policy URL" ], "read_order": [ "AGENTS.md and current Dimension owner/access policy", "Pinned model specification and variant revision", "Family, option/rule references and evaluation receipt", "Design/effectivity, release and permitted extension process" ] } }, "coverage": { "claim": "Source-grounded Vercy reviewable-draft specification of Product Configuration / Variant aggregate with 12 finding records, 7 functions, 48 questions and 9 qualified sources. Coverage includes identity, lifecycle, relationships, temporal, provenance, ownership, validation, access, interoperability, properties and retention dimensions. Operational implementation, real solver fixtures, executable instance schema, sector-specific profiles and licensed ISO clause inspection remain deferred. No external Claude or Grok research was admitted; single-provider result requires separate no-tools audit and publication hold visible in all artifacts.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Issuer-qualified stable ID, revision and scoped aliases" }, { "dimension": "lifecycle", "status": "covered", "notes": "Partial/resolved/released/superseded/retired states and explicit release gate" }, { "dimension": "relationships", "status": "covered", "notes": "Family, classifies-instance, design, BOM and commercial masters stay distinct" }, { "dimension": "temporal", "status": "covered", "notes": "Effectivity separate from recorded time and alias validity" }, { "dimension": "provenance", "status": "covered", "notes": "Selection origin and pinned derivation evidence" }, { "dimension": "ownership", "status": "covered", "notes": "Dimension and definition mastership with delegated release authority" }, { "dimension": "validation", "status": "covered", "notes": "Completeness, feasibility, source qualification and projection checks are separate" }, { "dimension": "access", "status": "covered", "notes": "Confidential design and customer selection policies at all scopes" }, { "dimension": "interoperability", "status": "covered", "notes": "Versioned mappings, non-transitive inheritance and loss reports" }, { "dimension": "physical properties", "status": "covered", "notes": "Nominal qualified properties and recognition, no fabricated observations" }, { "dimension": "functions", "status": "covered", "notes": "Capability and use limits distinct from actuation permission" }, { "dimension": "retention", "status": "covered", "notes": "Retired identities, dependent items and minimized tombstones" }, { "dimension": "Operational and domain conformance", "status": "gap", "notes": "No real manufacturer fixture, solver adapter, executable instance schema or certified projection implementation is supplied." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "Market, identifier allocation, safety and retention obligations must be resolved under applicable owner policy and jurisdiction; this draft grants no legal approval." ], "adversarial_checks": [ "Reject a GTIN/CPV/SKU or URL treated as universal engineering identity.", "Reject false collapsed with unknown or a changed default silently rewriting a released variant.", "Reject solver timeout as success, feasibility as release authority or technical compatibility as commercial availability.", "Reject nominal mass, hardness or capability as an observed instance property or permission to actuate.", "Reject transitive Schema.org inheritance, hidden projection loss or an unlicensed normative-conformance claim.", "Reject private customer selections copied into a public variant or a conflicting unguarded update." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "One reusable configuration revision owns selected assertions and evaluation bindings; family, design, BOM, item, session and offer keep their own masters. Packaging standalone-mm is a separate axis." }, "decisions": [ { "concept": "Aggregate boundary", "disposition": "accepted", "rationale": "One reusable configuration revision owns selected assertions and evaluation bindings; family, design, BOM, item, session and offer keep their own masters. Packaging standalone-mm is a separate axis." }, { "concept": "Frozen CLASSIFIES relation", "disposition": "accepted", "rationale": "REFERENCE explicitly carries CLASSIFIES semantics toward WM-OBJ-001 because the research relation enum has no CLASSIFIES value. No item identity or state is imported." }, { "concept": "Provider evidence attribution", "disposition": "corrected", "rationale": "This model has one 120-second timeout per research provider. Historical policy attempts are not model attempts. Haiku's separate no-tools audit succeeded but no external research result was admitted." }, { "concept": "Source inspection and conformance", "disposition": "corrected", "rationale": "Sources support proposed design choices at declared inspection depth. ISO public abstracts do not establish licensed-clause conformance; neither do vocabulary references establish tested implementation conformance." }, { "concept": "Physical and functional description", "disposition": "accepted", "rationale": "The proposed property and capability contracts require evidence, units and conditions. Nominal properties do not describe an instance's observed position, condition or safety." }, { "concept": "Engineering composition mastership", "disposition": "accepted", "rationale": "Four boundary notes retain external design and BOM authority. Selected composition references may qualify occurrences and quantities without taking ownership of the BOM." }, { "concept": "Evaluation and release", "disposition": "accepted", "rationale": "Completeness, feasibility, availability and authority are distinct results. Unknown or timed-out evaluation cannot authorize release. Imported expressions require an authorized bounded adapter." }, { "concept": "New solver or standards prescriptions", "disposition": "rejected", "rationale": "The no-tools audit cannot introduce new source claims or mandate named commercial solvers. Keep a vendor-neutral evaluator profile and defer uninspected domain standards." }, { "concept": "Interchange and retention", "disposition": "accepted", "rationale": "No universal lossless mapping is claimed. Required unsupported semantics cause rejection or explicit sidecar handling; retirement retains dependent-item interpretation under access and minimization policy." } ], "publicationHolds": [ "Independent Claude and Grok research is absent under owner authorization dated 2026-09-06. Each research attempt timed out once at 120 seconds. A separate Claude Haiku no-tools audit completed; its factual overstatements were corrected transparently by Codex. This remains reviewable-draft, not canonical.", "Source/version and claim-level verification remains qualified: Schema.org is a development vocabulary snapshot; ISO 10007 and AP242 were inspected only through public abstracts, not licensed clauses. No normative standards conformance is claimed.", "No real-product fixture, executable instance schema, deployed constraint evaluator or tested crosswalk is included. Adoption requires validated target-specific adapters and explicit loss reports.", "Physical properties, recognition and capability limits require sector-specific evidence, measurement conditions and uncertainty. The draft provides no certification or safe-actuation authority.", "Actual variant creation and release require an owning Dimension with declared roles, access policy, engineering authority and retention rules; the specification does not instantiate that governance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 7 } }