# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-09T19:01:50Z", "synthesisSha256": "ccdaf674c49d870e85d3e89443ceb24253e3567aaabff903b8ea318cadadcf19", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-019", "registryId": "vr.wm-obj-019", "name": "Component Type / Engineering BOM", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.ASM" ], "tags": [ "component", "type", "engineering", "bom", "phy.obj.asm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-019-component-type-engineering-bom/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-019", "model": { "registry_id": "vr.wm-obj-019", "model_id": "WM-OBJ-019", "name": "Component Type / Engineering BOM", "entry_kind": "aggregate", "purpose": "Describe reusable type-level engineering composition distinctly from as-built assembly.", "scope_statement": "An engineering BOM revision owns occurrence relationships, quantities, applicability, selection, intended-property references and controlled exchange. Product types, designs, configured variants and physical items retain independent masters.", "in_scope": [ "Versioned engineering baseline and component occurrences", "Quantities, graph integrity, effectivity and selection", "Qualified nominal properties, functional contributions and governed change" ], "out_of_scope": [ "As-built item state, actual material consumption and inventory", "Production routes, procurement execution and software BOM", "Automatic physical action or certification from information validity" ], "boundary_notes": [ { "neighbor": "WM-OBJ-002 Product Type / Catalog Item", "distinction": "Frozen COMPOSE relation: occurrences reference reusable component types, not copied product masters.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-OBJ-018 Engineering Design / Product Definition", "distinction": "Design geometry and functional intent stay referenced, not remastered in the BOM.", "source_refs": [ "SRC-006", "SRC-007" ] }, { "neighbor": "WM-OBJ-017 Product Configuration / Variant", "distinction": "Selection binds applicability; candidate lines do not imply installed components.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Physical items and manufacturing masters", "distinction": "Engineering occurrence is not serialized item; manufacturing additions and process recursion require a separate view.", "source_refs": [ "SRC-001", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Bills of materials and formulas", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/production-control/bill-of-material-bom", "version_or_date": "2025-07-10", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "BOM views, version applicability, approval and subordinate references; vendor-specific implementation evidence." }, { "id": "SRC-002", "title": "About BOM Quantity", "organization": "Autodesk", "url": "https://help.autodesk.com/cloudhelp/2023/ENU/Inventor-Help/files/GUID-37BA8DB6-E39C-4C96-AAF1-E7B342F20D0E.htm", "version_or_date": "Inventor 2023", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Selected indexed quantity documentation; counts, unit amounts and overrides, not a universal calculation algorithm." }, { "id": "SRC-003", "title": "BOMRow Object", "organization": "Autodesk", "url": "https://help.autodesk.com/cloudhelp/2023/ENU/Inventor-API/files/BOMRow.htm", "version_or_date": "Inventor 2023 API", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Public property table: definitions, occurrences, merged and promoted rows; no adapter executed." }, { "id": "SRC-004", "title": "Electronics Bill of materials", "organization": "Autodesk", "url": "https://help.autodesk.com/cloudhelp/ENU/Fusion-ECAD/files/ECD-BOM-CPT.htm", "version_or_date": "Public page inspected 2026-09-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Electronics designators, footprints and flattened naming; not mandatory mechanical-BOM fields." }, { "id": "SRC-005", "title": "Recursiveness Check", "organization": "SAP", "url": "https://help.sap.com/docs/SAP_ERP/43fa3cddb00348beb3ed12212a94448f/dd05c453f57eb44ce10000000a174cb4.html", "version_or_date": "ERP 6.0 EHP8", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Indexed text only; direct opening returned empty shell. Group graph versus selected variant and bounded expansion." }, { "id": "SRC-006", "title": "Managed model-based 3D engineering", "organization": "ISO", "url": "https://www.iso.org/standard/84300.html", "version_or_date": "ISO 10303-242:2025 edition 4 public scope only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Candidate engineering structure alignment; licensed clauses and executable mappings uninspected." }, { "id": "SRC-007", "title": "Configuration Management", "organization": "NASA", "url": "https://www.nasa.gov/reference/6-5-configuration-management/", "version_or_date": "Handbook chapter 6.5 inspected 2026-09-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:59:00Z", "relevance": "Selected baseline and change-control guidance; domain-specific, not universal governance requirements." }, { "id": "SRC-008", "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:59:00Z", "relevance": "Selected attribution and derivation concepts; does not grant access or certify assertions." }, { "id": "SRC-009", "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:59:00Z", "relevance": "Seconds and explicit offset; timestamps are not collision-proof identities or interval definitions." } ], "structure": { "bundles": [ { "id": "bom-composition-authority", "name": "Composition authority", "description": "Engineering composition concerns: composition authority.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "bom-baseline", "name": "BOM identity, view and baseline", "description": "Proposed engineering-composition record for bom identity, view and baseline. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "bom-baseline-record", "name": "BOM identity, view and baseline record", "description": "Proposed engineering-composition record for bom identity, view and baseline. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "bom-baseline-q01", "text": "Which issuer-qualified BOM identity, immutable revision and engineering view define the composition being read?", "kind": "identity", "answer_data": [ "bom-baseline-identity" ] }, { "id": "bom-baseline-q02", "text": "Which parent product type and controlled design revision does this baseline describe, and which representations are authoritative?", "kind": "authority", "answer_data": [ "bom-baseline-subject" ] }, { "id": "bom-baseline-q03", "text": "Which required members or referenced revisions are missing, unresolved or intentionally withheld from this baseline?", "kind": "quality", "answer_data": [ "bom-baseline-baseline" ] } ], "data_elements": [ { "id": "bom-baseline-identity", "name": "identity", "description": "Proposed structured field group: issuer, bom_id, revision, view, master. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "bom-baseline-subject", "name": "subject", "description": "Proposed structured field group: WM-OBJ-002 reference, WM-OBJ-018 reference, representation authority. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "bom-baseline-baseline", "name": "baseline", "description": "Proposed structured field group: member IDs/revisions/digests, completeness criteria, absent status/reason. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "bom-baseline-evidence", "name": "BOM identity, view and baseline evidence", "description": "Revision-bound evidence references and receipts for bom identity, view and baseline, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "component-occurrence", "name": "Component types and occurrences", "description": "Proposed engineering-composition record for component types and occurrences. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "component-occurrence-record", "name": "Component types and occurrences record", "description": "Proposed engineering-composition record for component types and occurrences. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "component-occurrence-q01", "text": "Which component type and exact revision is referenced by each occurrence, independently of its displayed item number?", "kind": "relationship", "answer_data": [ "component-occurrence-component-binding" ] }, { "id": "component-occurrence-q02", "text": "How are repeated occurrences, hierarchical reference designators and merged display rows distinguished and reversibly mapped?", "kind": "composition", "answer_data": [ "component-occurrence-occurrence-map" ] }, { "id": "component-occurrence-q03", "text": "Which occurrence-specific placement, footprint or interface binding identifies its intended position without asserting an actual item's location?", "kind": "spatial", "answer_data": [ "component-occurrence-placement-definition" ] } ], "data_elements": [ { "id": "component-occurrence-component-binding", "name": "component-binding", "description": "Proposed structured field group: occurrence_id, component issuer/id/revision. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "component-occurrence-occurrence-map", "name": "occurrence-map", "description": "Proposed structured field group: parent occurrence, path, designators, display-row membership. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "component-occurrence-placement-definition", "name": "placement-definition", "description": "Proposed structured field group: design feature/frame/interface references, footprint, nominal transform or explicit unknown, not measured pose. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "component-occurrence-evidence", "name": "Component types and occurrences evidence", "description": "Revision-bound evidence references and receipts for component types and occurrences, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bom-quantified-assembly-graph", "name": "Quantified assembly graph", "description": "Engineering composition concerns: quantified assembly graph.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "quantity-basis", "name": "Quantity basis and dimensional meaning", "description": "Proposed engineering-composition record for quantity basis and dimensional meaning. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "quantity-basis-record", "name": "Quantity basis and dimensional meaning record", "description": "Proposed engineering-composition record for quantity basis and dimensional meaning. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "quantity-basis-q01", "text": "What component quantity and unit apply per declared parent base quantity, rather than per an assumed single finished item?", "kind": "measurement", "answer_data": [ "quantity-basis-quantity-basis" ] }, { "id": "quantity-basis-q02", "text": "Which item-count, per-occurrence amount, conversion, rounding and override rules produce a reported total, and what evidence supports them?", "kind": "provenance", "answer_data": [ "quantity-basis-calculation" ] }, { "id": "quantity-basis-q03", "text": "Which quantities are unknown, variable or outside the engineering view, including manufacturing scrap, yield and actual consumption?", "kind": "exception", "answer_data": [ "quantity-basis-quantity-state" ] } ], "data_elements": [ { "id": "quantity-basis-quantity-basis", "name": "quantity-basis", "description": "Proposed structured field group: component amount/unit, parent base amount/unit. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "quantity-basis-calculation", "name": "calculation", "description": "Proposed structured field group: count, unit amount, conversion registry/version, precision, rounding, override reason/authority. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "quantity-basis-quantity-state", "name": "quantity-state", "description": "Proposed structured field group: known/unknown/conditional, expression reference, excluded process terms and view-specific exceptions. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "quantity-basis-evidence", "name": "Quantity basis and dimensional meaning evidence", "description": "Revision-bound evidence references and receipts for quantity basis and dimensional meaning, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "assembly-graph", "name": "Subassembly reuse and traversal integrity", "description": "Proposed engineering-composition record for subassembly reuse and traversal integrity. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "assembly-graph-record", "name": "Subassembly reuse and traversal integrity record", "description": "Proposed engineering-composition record for subassembly reuse and traversal integrity. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "assembly-graph-q01", "text": "Which subordinate BOM revisions are reused, and which occurrence paths must remain distinct when the same subassembly appears more than once?", "kind": "composition", "answer_data": [ "assembly-graph-dependency-graph" ] }, { "id": "assembly-graph-q02", "text": "Is a detected cycle in the unfiltered family graph or the selected effective graph, and where must traversal stop safely?", "kind": "validation", "answer_data": [ "assembly-graph-cycle-analysis" ] }, { "id": "assembly-graph-q03", "text": "Which unresolved references, depth limits, access-denied branches or intentional recursive-process boundaries make an expansion incomplete?", "kind": "quality", "answer_data": [ "assembly-graph-expansion-completeness" ] } ], "data_elements": [ { "id": "assembly-graph-dependency-graph", "name": "dependency-graph", "description": "Proposed structured field group: parent/child occurrence, pinned child BOM, view. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "assembly-graph-cycle-analysis", "name": "cycle-analysis", "description": "Proposed structured field group: graph scope, selection context, cycle path, stop reason, declared handling policy. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "assembly-graph-expansion-completeness", "name": "expansion-completeness", "description": "Proposed structured field group: visited revisions, truncated paths, unavailable nodes, reason and responsible resolver. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "assembly-graph-evidence", "name": "Subassembly reuse and traversal integrity evidence", "description": "Revision-bound evidence references and receipts for subassembly reuse and traversal integrity, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bom-applicability-and-selection", "name": "Applicability and selection", "description": "Engineering composition concerns: applicability and selection.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009" ], "layers": [ { "id": "line-effectivity", "name": "Effectivity and revision resolution", "description": "Proposed engineering-composition record for effectivity and revision resolution. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ], "findings": [ { "id": "line-effectivity-record", "name": "Effectivity and revision resolution record", "description": "Proposed engineering-composition record for effectivity and revision resolution. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ], "questions": [ { "id": "line-effectivity-q01", "text": "Under which time, variant, site or other explicitly declared context predicates does a BOM revision or line apply?", "kind": "temporal", "answer_data": [ "line-effectivity-applicability" ] }, { "id": "line-effectivity-q02", "text": "Which resolver and pinned context selected each component revision, and how are overlapping or missing applicable revisions reported?", "kind": "decision", "answer_data": [ "line-effectivity-resolution" ] }, { "id": "line-effectivity-q03", "text": "How are approval time, recording time and effective boundaries preserved when a retrospective correction changes applicability?", "kind": "lifecycle", "answer_data": [ "line-effectivity-temporal-history" ] } ], "data_elements": [ { "id": "line-effectivity-applicability", "name": "applicability", "description": "Proposed structured field group: typed predicate, context dimensions, endpoint inclusivity, time offset. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] }, { "id": "line-effectivity-resolution", "name": "resolution", "description": "Proposed structured field group: rule/version, inputs, chosen revisions, ambiguous/missing outcomes. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] }, { "id": "line-effectivity-temporal-history", "name": "temporal-history", "description": "Proposed structured field group: recorded/approved/effective timestamps, superseding record, correction reason, historical query context. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "line-effectivity-evidence", "name": "Effectivity and revision resolution evidence", "description": "Revision-bound evidence references and receipts for effectivity and revision resolution, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "component-selection", "name": "Options, alternates and substitutes", "description": "Proposed engineering-composition record for options, alternates and substitutes. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "component-selection-record", "name": "Options, alternates and substitutes record", "description": "Proposed engineering-composition record for options, alternates and substitutes. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "component-selection-q01", "text": "Which optional or alternative component groups are available, and what cardinality and compatibility conditions constrain selection?", "kind": "constraint", "answer_data": [ "component-selection-choice-groups" ] }, { "id": "component-selection-q02", "text": "Which approved substitution is directional, context-limited or conditional on interface and capability evidence rather than universal interchangeability?", "kind": "evidence", "answer_data": [ "component-selection-substitution" ] }, { "id": "component-selection-q03", "text": "Which selected option set and explicit exclusions belong to the configured engineering composition, without treating every candidate as installed?", "kind": "state", "answer_data": [ "component-selection-configured-selection" ] } ], "data_elements": [ { "id": "component-selection-choice-groups", "name": "choice-groups", "description": "Proposed structured field group: members, min/max selections, constraints, unresolved predicates. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "component-selection-substitution", "name": "substitution", "description": "Proposed structured field group: from/to revisions, direction, applicability, qualification evidence, approver. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "component-selection-configured-selection", "name": "configured-selection", "description": "Proposed structured field group: WM-OBJ-017 binding, selected occurrences, not-selected/unknown reasons, evaluation receipt. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "component-selection-evidence", "name": "Options, alternates and substitutes evidence", "description": "Revision-bound evidence references and receipts for options, alternates and substitutes, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bom-intended-characteristics", "name": "Intended characteristics", "description": "Engineering composition concerns: intended characteristics.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "nominal-properties", "name": "Component properties and recognition references", "description": "Proposed engineering-composition record for component properties and recognition references. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ], "findings": [ { "id": "nominal-properties-record", "name": "Component properties and recognition references record", "description": "Proposed engineering-composition record for component properties and recognition references. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "nominal-properties-q01", "text": "Which versioned material, nominal size, mass and other physical-property definitions belong to each component type, with units and conditions?", "kind": "definition", "answer_data": [ "nominal-properties-nominal-properties" ] }, { "id": "nominal-properties-q02", "text": "Which distinguishing features, markings, footprints or interface references help identify the intended component class, and what recognition uncertainty remains?", "kind": "classification", "answer_data": [ "nominal-properties-recognition" ] }, { "id": "nominal-properties-q03", "text": "Which aggregate property is derived from the selected composition, using what method and exclusions, instead of being mistaken for a measured assembly property?", "kind": "measurement", "answer_data": [ "nominal-properties-aggregate-derivation" ] } ], "data_elements": [ { "id": "nominal-properties-nominal-properties", "name": "nominal-properties", "description": "Proposed structured field group: property ID, value/unit, conditions, source revision, unknown. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "nominal-properties-recognition", "name": "recognition", "description": "Proposed structured field group: feature/design references, identifier namespace, distinguishing evidence, ambiguity. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "nominal-properties-aggregate-derivation", "name": "aggregate-derivation", "description": "Proposed structured field group: target property, method/version, selected inputs, exclusions, uncertainty, evidence. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "nominal-properties-evidence", "name": "Component properties and recognition references evidence", "description": "Revision-bound evidence references and receipts for component properties and recognition references, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "functional-contribution", "name": "Functional contribution and assembly constraints", "description": "Proposed engineering-composition record for functional contribution and assembly constraints. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "functional-contribution-record", "name": "Functional contribution and assembly constraints record", "description": "Proposed engineering-composition record for functional contribution and assembly constraints. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "functional-contribution-q01", "text": "What intended functional role does an occurrence contribute, and which design or requirement master defines that role?", "kind": "relationship", "answer_data": [ "functional-contribution-role-binding" ] }, { "id": "functional-contribution-q02", "text": "Which mating, material, load or environmental constraints must hold for components to function together in this composition?", "kind": "constraint", "answer_data": [ "functional-contribution-assembly-constraints" ] }, { "id": "functional-contribution-q03", "text": "Which unverified capability, prohibited use or unresolved compatibility issue prevents an agent from claiming the assembly is fit for a requested action?", "kind": "evidence", "answer_data": [ "functional-contribution-capability-disposition" ] } ], "data_elements": [ { "id": "functional-contribution-role-binding", "name": "role-binding", "description": "Proposed structured field group: occurrence, function/class reference, design revision. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "functional-contribution-assembly-constraints", "name": "assembly-constraints", "description": "Proposed structured field group: endpoints, predicate, operating envelope, verification evidence. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "functional-contribution-capability-disposition", "name": "capability-disposition", "description": "Proposed structured field group: claim, evidence status, limitations, prohibited uses, unresolved reviewer decision. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "functional-contribution-evidence", "name": "Functional contribution and assembly constraints evidence", "description": "Revision-bound evidence references and receipts for functional contribution and assembly constraints, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bom-change-and-realization-boundary", "name": "Change and realization boundary", "description": "Engineering composition concerns: change and realization boundary.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "composition-change", "name": "Approval, change and where-used impact", "description": "Proposed engineering-composition record for approval, change and where-used impact. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "findings": [ { "id": "composition-change-record", "name": "Approval, change and where-used impact record", "description": "Proposed engineering-composition record for approval, change and where-used impact. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "questions": [ { "id": "composition-change-q01", "text": "Who may approve or retire this engineering baseline, and which open findings prevent release under the owning Dimension's policy?", "kind": "authority", "answer_data": [ "composition-change-release" ] }, { "id": "composition-change-q02", "text": "Which changed occurrence, quantity or revision affects which parent baselines and configured variants according to a context-qualified where-used query?", "kind": "relationship", "answer_data": [ "composition-change-impact" ] }, { "id": "composition-change-q03", "text": "What expected-base check, decision and history preserve concurrent edits and approved deviations without silently rewriting released composition?", "kind": "lifecycle", "answer_data": [ "composition-change-change-control" ] } ], "data_elements": [ { "id": "composition-change-release", "name": "release", "description": "Proposed structured field group: authority, gates, findings, decision, timestamp. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "composition-change-impact", "name": "impact", "description": "Proposed structured field group: changed IDs, reverse-reference graph scope, affected parent revisions, unknown consumers, review disposition. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "composition-change-change-control", "name": "change-control", "description": "Proposed structured field group: expected digest, before/after revisions, reason, conflict, scoped deviation and approval. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "composition-change-evidence", "name": "Approval, change and where-used impact evidence", "description": "Revision-bound evidence references and receipts for approval, change and where-used impact, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "realization-handoff", "name": "Engineering-to-manufacturing handoff", "description": "Proposed engineering-composition record for engineering-to-manufacturing handoff. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "realization-handoff-record", "name": "Engineering-to-manufacturing handoff record", "description": "Proposed engineering-composition record for engineering-to-manufacturing handoff. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "realization-handoff-q01", "text": "Which engineering occurrences map to which manufacturing BOM or process-master records, including split, merged, phantom or omitted representations?", "kind": "interoperability", "answer_data": [ "realization-handoff-cross-view-map" ] }, { "id": "realization-handoff-q02", "text": "Which make-or-buy intention or manufacturing-only addition is recorded as a qualified handoff assumption rather than an engineering component fact?", "kind": "decision", "answer_data": [ "realization-handoff-realization-assumptions" ] }, { "id": "realization-handoff-q03", "text": "What receiving-system acknowledgement and discrepancy disposition preserve the original engineering baseline when the production or as-built view differs?", "kind": "event", "answer_data": [ "realization-handoff-handoff-receipt" ] } ], "data_elements": [ { "id": "realization-handoff-cross-view-map", "name": "cross-view-map", "description": "Proposed structured field group: source/target revisions, occurrence mappings, transform kind, loss. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "realization-handoff-realization-assumptions", "name": "realization-assumptions", "description": "Proposed structured field group: make/buy status, authority, process/material additions, target view. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "realization-handoff-handoff-receipt", "name": "handoff-receipt", "description": "Proposed structured field group: recipient, package digest, time, acceptance, divergence and change decision references. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "realization-handoff-evidence", "name": "Engineering-to-manufacturing handoff evidence", "description": "Revision-bound evidence references and receipts for engineering-to-manufacturing handoff, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bom-governed-composition-exchange", "name": "Governed composition exchange", "description": "Engineering composition concerns: governed composition exchange.", "rationale": "Subject-specific grouping of two authored records, separating reusable intent from installed reality.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "composition-stewardship", "name": "Mastership, disclosure and preservation", "description": "Proposed engineering-composition record for mastership, disclosure and preservation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-007", "SRC-008" ], "findings": [ { "id": "composition-stewardship-record", "name": "Mastership, disclosure and preservation record", "description": "Proposed engineering-composition record for mastership, disclosure and preservation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-007", "SRC-008" ], "questions": [ { "id": "composition-stewardship-q01", "text": "Which Dimension and engineering authority own the baseline while external component masters retain their own stewardship?", "kind": "ownership", "answer_data": [ "composition-stewardship-authority-map" ] }, { "id": "composition-stewardship-q02", "text": "Which occurrence details and artifacts may each recipient read or export, and how is a withheld branch distinguished from an empty assembly?", "kind": "access", "answer_data": [ "composition-stewardship-disclosure" ] }, { "id": "composition-stewardship-q03", "text": "Which retention triggers, holds and preserved dependency references keep retired BOM revisions interpretable without retaining unnecessary protected content?", "kind": "retention", "answer_data": [ "composition-stewardship-preservation" ] } ], "data_elements": [ { "id": "composition-stewardship-authority-map", "name": "authority-map", "description": "Proposed structured field group: owner, author, component master, custodian. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "composition-stewardship-disclosure", "name": "disclosure", "description": "Proposed structured field group: recipient, purpose, scope, authorization, redaction/completeness status. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "composition-stewardship-preservation", "name": "preservation", "description": "Proposed structured field group: retention trigger, hold, historical dependency policy, readability checks, minimized tombstone. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "composition-stewardship-evidence", "name": "Mastership, disclosure and preservation evidence", "description": "Revision-bound evidence references and receipts for mastership, disclosure and preservation, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "exchange-fidelity", "name": "Exchange fidelity and semantic validation", "description": "Proposed engineering-composition record for exchange fidelity and semantic validation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "findings": [ { "id": "exchange-fidelity-record", "name": "Exchange fidelity and semantic validation record", "description": "Proposed engineering-composition record for exchange fidelity and semantic validation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "exchange-fidelity-q01", "text": "Which source and target profile versions, exact-byte digests and transformation provenance bind an exported composition?", "kind": "provenance", "answer_data": [ "exchange-fidelity-exchange" ] }, { "id": "exchange-fidelity-q02", "text": "Which occurrence identity, unit, effectivity, selection or reference-designator semantics are lost or changed by flattening or row merging?", "kind": "interoperability", "answer_data": [ "exchange-fidelity-semantic-loss" ] }, { "id": "exchange-fidelity-q03", "text": "Which declared acceptance fixtures and rejection rules establish a usable mapping while keeping unsupported constructs visible?", "kind": "validation", "answer_data": [ "exchange-fidelity-acceptance" ] } ], "data_elements": [ { "id": "exchange-fidelity-exchange", "name": "exchange", "description": "Proposed structured field group: profiles/versions, translator, source/target digest, provenance. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "exchange-fidelity-semantic-loss", "name": "semantic-loss", "description": "Proposed structured field group: construct, affected paths, severity, sidecar or reject disposition. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "exchange-fidelity-acceptance", "name": "acceptance", "description": "Proposed structured field group: fixture/version, criteria, results, limitations. Preserve explicit unknowns and referenced master authority; executable nested schema is deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "exchange-fidelity-evidence", "name": "Exchange fidelity and semantic validation evidence", "description": "Revision-bound evidence references and receipts for exchange fidelity and semantic validation, without copying protected masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system ID first, then issuer-qualified UUID; revision and exact-byte digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-bom", "name": "Resolve applicable baseline", "description": "Resolve one engineering baseline under explicit context, preserving ambiguity.", "inputs": [ "BOM identity", "Applicability context" ], "outputs": [ "Pinned baseline or unresolved outcome" ], "preconditions": [ "Authorized access and declared resolver" ], "effects": [ "Never silently select latest" ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "expand-composition", "name": "Expand bounded composition", "description": "Traverse occurrences without flattening identity or looping.", "inputs": [ "Pinned graph", "Selection context" ], "outputs": [ "Expanded paths and completeness report" ], "preconditions": [ "Pinned dependencies and bounded traversal policy" ], "effects": [ "Stop on unresolved branch or cycle; no manufacturing recursion solver implied" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "qualify-quantity", "name": "Qualify engineering quantities", "description": "Describe dimensional calculation and override provenance; this contract supplies no calculation engine.", "inputs": [ "Occurrence quantities", "Units and parent basis" ], "outputs": [ "Qualified totals or explicit unknowns" ], "preconditions": [ "Compatible units and declared conversion/rounding policy" ], "effects": [ "Do not count excluded alternatives or manufacturing scrap as intrinsic composition" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "select-components", "name": "Bind configured selection", "description": "Record constrained choices and qualified substitutions.", "inputs": [ "WM-OBJ-017 selection", "Component evidence" ], "outputs": [ "Selected occurrence set and open conflicts" ], "preconditions": [ "Approved applicable choices and interface evidence" ], "effects": [ "No universal interchangeability or installation inferred" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "review-bom-change", "name": "Review and release composition change", "description": "Assess where-used impact and baseline authority.", "inputs": [ "Proposed revision", "Expected base", "Reviewer findings" ], "outputs": [ "Release decision and affected references" ], "preconditions": [ "No unresolved blocking conflict; approver authorized" ], "effects": [ "Keep history, deviations and unknown downstream consumers visible" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "exchange-bom", "name": "Exchange composition with loss report", "description": "Preserve source identity through target-view mappings.", "inputs": [ "Source baseline", "Authorized target profile" ], "outputs": [ "Derivative artifact, mapping and loss report" ], "preconditions": [ "Disclosure permission and tested mapping criteria" ], "effects": [ "Reject required unsupported semantics; never overwrite source with projection" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "composition": [ { "target": "WM-OBJ-002", "relation": "COMPOSE", "purpose": "Frozen type-level component composition relation.", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "WM-OBJ-018", "relation": "REFERENCE", "purpose": "Resolve controlled geometry and intended definition.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "WM-OBJ-017", "relation": "REFERENCE", "purpose": "Bind selected variants without merging lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-OBJ-001", "relation": "REFERENCE", "purpose": "Link as-built discrepancies without treating intent as observation.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Manufacturing BOM, routing and procurement masters", "relation": "REFERENCE", "purpose": "Preserve independent realization views and permissions.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "ISO 10303-242:2025 public scope", "relation": "ALIGN", "purpose": "Candidate exchange alignment only; licensed clauses and crosswalk deferred.", "required": false, "source_refs": [ "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify Dimension owner and composition authority.", "Declare namespaces and component/BOM master registries.", "Declare delegated release, federation, access and retention policies." ], "namespace_guidance": "Issuer-qualified BOM IDs with immutable revisions and local occurrence IDs; displayed row numbers and filenames are not master identity.", "registry_links": [ "Dimension model registry", "Component type registry", "Engineering baseline registry", "Change and evidence registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve distinct occurrences, pinned revisions, engineering view and explicit unknowns.", "A flattened projection never overwrites authoritative occurrence topology." ], "patch_rules": [ "Authorized append-only revision or namespaced extension with expected-base digest; reject concurrent conflicts.", "Reassess quantities, applicability, selection and where-used impact before release." ], "compatibility_rules": [ "Changed engineering meaning requires a controlled revision, not silent replacement.", "Preserve prior versions and explicit cross-view loss; deviations have bounded authority and applicability." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system ID", "Governed issuer-qualified UUID", "Dimension UUID with revision and digest" ], "timestamp_rule": "RFC 3339 with seconds and UTC Z or numeric offset; distinguish recorded, approved and effective time.", "serial_naming_rule": "Evidence type plus opaque master ID and revision; dates alone are insufficient.", "integrity_rule": "Verify exact-byte digests and pinned dependencies. Never execute imported formulas, scripts, macros or instructions automatically." }, "policies": [ "Information validity is not physical fit, safety, certification or authority to manufacture.", "Do not sum alternatives or propagate incompatible units; incomplete and withheld branches remain explicit.", "Vendor examples motivate proposed fields, not universal normative compliance." ], "crud": { "read": [ "Read AGENTS.md and owner policy; resolve baseline/view/context before traversing authorized component references." ], "create": [ "Reuse the active authorized Dimension and existing product masters; create explicit partial engineering composition with stable occurrence IDs." ], "update": [ "Apply expected-base checks and change review; preserve release history and reverse dependency impact." ], "delete": [ "Retire first; respect retention and legal hold, dependent interpretation and authorized deletion. Preserve a minimized tombstone." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Defines namespace, storage and delegated access." ] }, { "name": "Composition authority", "responsibilities": [ "Owns baseline and approves applicability and change." ] }, { "name": "Engineering author", "responsibilities": [ "Maintains component bindings, quantities and evidence." ] }, { "name": "Reviewer", "responsibilities": [ "Checks selection, units, cycles and unresolved assertions." ] }, { "name": "Custodian", "responsibilities": [ "Preserves authorized readable dependencies without becoming owner." ] } ], "access": { "default_rule": "Deny unless owning Dimension authorizes the exact scope and purpose.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Explicit time-limited delegated exception only; no privilege inheritance from component containment." ], "audit_requirements": [ "Record actor, purpose, scope, baseline, decision and disclosure receipt without secrets." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Dimension owner and access policy", "Pinned BOM baseline and view", "Selection/effectivity and component dependencies", "Evidence, validation and change rules" ] } }, "coverage": { "claim": "Proposed engineering-composition information contract with twelve subject-specific records and thirty-six authored questions. No independent external review, operational solver or normative conformance is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "BOM revision versus component type versus occurrence." }, { "dimension": "lifecycle", "status": "covered", "notes": "Baseline approval, revision and retirement." }, { "dimension": "relationships", "status": "covered", "notes": "COMPOSE product type and referenced design/variant masters." }, { "dimension": "temporal", "status": "covered", "notes": "Applicable versus recorded and approved time." }, { "dimension": "provenance", "status": "covered", "notes": "Quantity overrides and transformation evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Composition owner versus component master and custodian." }, { "dimension": "validation", "status": "covered", "notes": "Cycles, unresolved references and acceptance fixtures as proposed requirements." }, { "dimension": "access", "status": "covered", "notes": "Scoped disclosure with explicit withheld branches." }, { "dimension": "interoperability", "status": "covered", "notes": "Occurrence preservation, view transformation and semantic losses." }, { "dimension": "direct properties", "status": "covered", "notes": "Qualified nominal properties, not observed item state." }, { "dimension": "recognition", "status": "covered", "notes": "Features, designators and footprint references with ambiguity." }, { "dimension": "capabilities", "status": "covered", "notes": "Functional contribution and evidence-limited compatibility." }, { "dimension": "retention", "status": "covered", "notes": "Historical dependency interpretation and holds." }, { "dimension": "Executable conformance", "status": "gap", "notes": "Nested schema, solver and real-product fixtures deferred." } ], "known_omissions": [ "No independent external research/review: Claude and Grok each timed out once. Codex-only owner waiver requires reviewable-draft assurance.", "SAP support is indexed text only; licensed ISO clauses unread. Source-to-field normative compliance is not established.", "Vendor documentation is selected and domain-specific, not exhaustive industry coverage. Alternate/substitute rules are proposed Vercy design needing specialist review.", "Nested field groups are not an executable instance schema. No BOM solver, unit engine, CAD adapter or real-product round-trip fixtures delivered.", "Actual physical properties and capability require design/component evidence; safety and certification are outside this contract.", "Adopters must instantiate actual authority, retention, access, effectivity predicates and acceptance criteria." ], "conflicts": [], "regional_assumptions": [ "Owning Dimension must declare contract, sector and jurisdiction requirements; no legal or manufacturing authorization inferred." ], "adversarial_checks": [ "Reject component types conflated with installed serial items.", "Reject row merging that destroys repeated occurrence identity.", "Reject unknown quantities interpreted as zero or incompatible units multiplied.", "Reject every alternate counted as simultaneously selected.", "Distinguish group graph cycles from selected graph; stop bounded traversal.", "Reject nominal aggregate property as measured safety or capability proof.", "Reject silent latest revision, unauthorized disclosure or stale-base 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": "The engineering BOM revision owns a coherent occurrence graph and controlled applicability. Product types, design, configured variants and installed items retain independent masters; frozen COMPOSE WM-OBJ-002 is preserved." }, "decisions": [ { "concept": "Type, occurrence and projection", "disposition": "accepted", "rationale": "Stable occurrence bindings remain distinct from product-type identity, displayed item numbers, merged rows and physical serial items." }, { "concept": "Quantities and choices", "disposition": "accepted", "rationale": "Parent base quantity, units, overrides, unknowns and exclusions are explicit. Alternate candidates are not counted as installed; substitution is directional and evidence-qualified." }, { "concept": "Recursion and applicability", "disposition": "accepted with limitations", "rationale": "Family graph and selected effective graph differ. Traversal stops with explicit incompleteness; process recursion is not physical self-containment or an implemented recursion solver." }, { "concept": "Physical properties and function", "disposition": "accepted with limitations", "rationale": "Nominal design references, recognition uncertainty and functional contributions do not establish actual assembly condition, hardness, safe actuation or certification." }, { "concept": "Governance and historical meaning", "disposition": "accepted", "rationale": "Controlled revisions, expected-base checks, where-used scope, withheld branches and retention preserve authority and provenance. Actual permission policy must be instantiated." }, { "concept": "Evidence depth and runtime completeness", "disposition": "deferred", "rationale": "Selected vendor docs and public ISO scope motivate proposals, not normative field compliance. SAP indexed text, unread licensed clauses, nested schema, adapters and real fixtures remain explicit holds." }, { "concept": "Provider attribution", "disposition": "accepted with mandatory hold", "rationale": "Both external research attempts timed out once. This is a separate frozen no-tools Codex self-audit, not independent external review or provider evidence." } ], "publicationHolds": [ "No independent external research or reviewer: Claude and Grok each have one terminal timeout. Codex research and a separate no-tools self-check remain reviewable-draft, never canonical.", "SAP recursion evidence was inspected through indexed text; licensed ISO clauses and source-to-field normative mappings were not inspected.", "Vendor documentation is selected and domain-specific. Alternate-group/substitution semantics and sector-specific composition rules need specialist review.", "No executable nested instance schema, BOM resolver, unit engine, CAD adapter, real-product fixture or verified round-trip translation is delivered.", "Physical properties and capabilities require component/design evidence; model validity is not assembly certification or physical-action authority.", "Adopters must configure actual owner/delegation, access, retention, applicability predicates and acceptance criteria.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Independent external review.", "Executable field-level schemas and negative fixtures for units, cycles, alternatives and concurrent revisions.", "Licensed standards and sector-specific alternate/substitution qualification.", "Real multi-level mechanical and electronics examples with loss-aware round trips." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }