# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-07T13:47:47Z", "synthesisSha256": "9614162f6f7a347b59ac1eb22dd06865d9f5d9650e401e2c784ca024d8c939c2", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-018", "registryId": "vr.wm-obj-018", "name": "Engineering Design / Product Definition", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.DES" ], "tags": [ "engineering", "design", "product", "definition", "phy.obj.des" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-018-engineering-design-product-definition/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-018", "model": { "registry_id": "vr.wm-obj-018", "model_id": "WM-OBJ-018", "name": "Engineering Design / Product Definition", "entry_kind": "aggregate", "purpose": "Represent an authoritative intended product definition with controlled revisions, requirement realization, engineering meaning, assurance evidence and lifecycle context.", "scope_statement": "Owns informational design identity, intended definition assertions, technical-package bindings, requirement and interface traceability, qualified nominal properties, review/release and change context. Product family, selected variant, engineering BOM, physical items, requirements and execution/test masters retain their own lifecycles.", "in_scope": [ "Design revision, representation authority and baseline package", "Requirement allocation, rationale, architecture, geometry, semantic PMI and intended behavior", "Scoped design assurance, controlled change, realization handoff, stewardship and loss-aware exchange" ], "out_of_scope": [ "Actual item location, mass, wear or present operating state; automated manufacturing or physical actuation", "Owning product family, variant configuration, BOM, requirement, workflow or test execution", "Claiming certified safety or standards compliance from a valid information model" ], "boundary_notes": [ { "neighbor": "WM-REC-006 Requirement", "distinction": "Preserve the frozen REFERENCE realization relation. Requirement content stays mastered there; linked design satisfaction needs separate qualified evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "neighbor": "WM-OBJ-002 Product Type / Catalog Item and WM-OBJ-017 Product Configuration / Variant", "distinction": "Family and selected variant retain their identity; a variant can bind this design revision without becoming the design itself.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-OBJ-019 Component Type / Engineering BOM", "distinction": "Reference reusable composition and selected occurrences; do not replace the independent engineering BOM master.", "source_refs": [ "SRC-004" ] }, { "neighbor": "WM-OBJ-001 Physical Object / Item", "distinction": "Design is informational intent. Nominal values and design assurance do not establish measured item condition or end-product certification.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "CAD file, drawing, document, analysis and inspection masters", "distinction": "Files are versioned representations and evidence; independent tool, document and execution lifecycles remain referenced.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Design Solution Definition", "organization": "NASA", "url": "https://www.nasa.gov/reference/4-4-design-solution-definition/", "version_or_date": "Systems Engineering Handbook web chapter 4.4 inspected 2026-09-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Design intent, alternatives, technical package and design assurance; NASA guidance is not a universal mandated workflow." }, { "id": "SRC-002", "title": "Technical Data Management", "organization": "NASA", "url": "https://www.nasa.gov/reference/6-6-technical-data-management/", "version_or_date": "Systems Engineering Handbook web chapter 6.6 inspected 2026-09-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Technical data identification, authority, access and long-term usability; proposed Vercy policies are not NASA compliance claims." }, { "id": "SRC-003", "title": "MBE PMI Validation and Conformance Testing Project", "organization": "NIST", "url": "https://www.nist.gov/ctl/smart-connected-systems-division/smart-connected-manufacturing-systems-group/mbe-pmi-validation", "version_or_date": "Historical project page inspected 2026-09-07; uses historical Y14 editions", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Semantic versus graphical PMI, native and derivative comparison and qualified fixtures; not proof of current CAD capabilities." }, { "id": "SRC-004", "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:39:00Z", "relevance": "Product-definition, engineering geometry, interface and lifecycle scope; no licensed clauses or conformance mapping inspected." }, { "id": "SRC-005", "title": "Requirements Interchange Format 1.2 release", "organization": "OMG", "url": "https://www.omg.org/spec/ReqIF/1.2/About-ReqIF", "version_or_date": "1.2, July 2016", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Pinned requirements-interchange release and normative artifacts; does not itself prove a design satisfies a requirement." }, { "id": "SRC-006", "title": "ReqIF XML schema", "organization": "OMG", "url": "https://www.omg.org/spec/ReqIF/20110401/reqif.xsd", "version_or_date": "20110401 schema linked by ReqIF 1.2 release", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Selected typed attribute and identifier/last-change declarations inspected; complete semantic mapping remains untested." }, { "id": "SRC-007", "title": "Configuration Management", "organization": "NASA", "url": "https://www.nasa.gov/reference/6-5-configuration-management/", "version_or_date": "Systems Engineering Handbook web chapter 6.5 inspected 2026-09-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-07T13:39:00Z", "relevance": "Controlled baselines, change authority and historical status; waiver is not automatically a baseline revision." }, { "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:39:00Z", "relevance": "Attribution and derivation references for engineering assertions and transformations; governance is separately declared." }, { "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:39:00Z", "relevance": "Seconds and explicit offset for recorded and effective times; timestamps are not unique design IDs." } ], "structure": { "bundles": [ { "id": "design-authority", "name": "Design authority and baselines", "description": "Establish exactly which intended definition and controlled package an agent is reading.", "rationale": "Proposed Vercy decomposition: Establish exactly which intended definition and controlled package an agent is reading.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "layers": [ { "id": "design-revision", "name": "Controlled revision and design subject", "description": "Separate the informational design from physical item, commercial variant and representation file.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "findings": [ { "id": "design-revision-record", "name": "Controlled revision and design subject record", "description": "Separate the informational design from physical item, commercial variant and representation file.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "design-revision-q01", "text": "Which authoritative design ID and revision denote the intended definition, independently of CAD filenames, exports and copies?", "kind": "identity", "answer_data": [ "design-revision-identity" ] }, { "id": "design-revision-q02", "text": "Which product family, intended configuration and design maturity are in scope?", "kind": "classification", "answer_data": [ "design-revision-design-subject" ] }, { "id": "design-revision-q03", "text": "Which representation is authoritative if a drawing and 3D model disagree, and who can resolve that disagreement?", "kind": "authority", "answer_data": [ "design-revision-representation-authority" ] } ], "data_elements": [ { "id": "design-revision-identity", "name": "identity", "description": "Issuer-qualified design ID, immutable revision, alias scope and authoritative master; never a filename alone.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "design-revision-design-subject", "name": "design-subject", "description": "Product family WM-OBJ-002 reference, configuration scope and maturity code; physical observations remain external.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "design-revision-representation-authority", "name": "representation-authority", "description": "Authoritative representation policy, competing drawing/model assertions and designated resolver; do not silently select newest.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "design-revision-evidence", "name": "Controlled revision and design subject evidence manifest", "description": "Revision-bound supporting records for controlled revision and design subject; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "baseline-package", "name": "Baseline and technical data package", "description": "Bind a maturity-appropriate package to an immutable baseline rather than an unqualified file collection.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "baseline-package-record", "name": "Baseline and technical data package record", "description": "Bind a maturity-appropriate package to an immutable baseline rather than an unqualified file collection.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "baseline-package-q01", "text": "Which exact file revisions and digests constitute this baseline?", "kind": "composition", "answer_data": [ "baseline-package-package-manifest" ] }, { "id": "baseline-package-q02", "text": "Which deliverables are required at this maturity and which are intentionally absent rather than accidentally missing?", "kind": "requirement", "answer_data": [ "baseline-package-completeness" ] }, { "id": "baseline-package-q03", "text": "Can a recipient retrieve the released package without following a mutable latest pointer or losing controlled external references?", "kind": "access", "answer_data": [ "baseline-package-retrievability" ] } ], "data_elements": [ { "id": "baseline-package-package-manifest", "name": "package-manifest", "description": "File or external record ID, revision, media type, exact-byte digest and role for each baseline constituent.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "baseline-package-completeness", "name": "completeness", "description": "Maturity-specific required deliverables, presence and explicit absence reasons; no universal fixed lifecycle gate.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "baseline-package-retrievability", "name": "retrievability", "description": "Pinned dependency graph, authorized resolver, offline preservation form and retrieval checks; unresolved references visible.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "baseline-package-evidence", "name": "Baseline and technical data package evidence manifest", "description": "Revision-bound supporting records for baseline and technical data package; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "design-intent", "name": "Intent and justification", "description": "Explain requirement realization and the selection of this solution over alternatives.", "rationale": "Proposed Vercy decomposition: Explain requirement realization and the selection of this solution over alternatives.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "requirement-allocation", "name": "Requirement allocation", "description": "Keep requirement content in WM-REC-006 and own only qualified realization and evidence bindings.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "requirement-allocation-record", "name": "Requirement allocation record", "description": "Keep requirement content in WM-REC-006 and own only qualified realization and evidence bindings.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "requirement-allocation-q01", "text": "Which WM-REC-006 requirement revision does each design element realize?", "kind": "relationship", "answer_data": [ "requirement-allocation-allocation" ] }, { "id": "requirement-allocation-q02", "text": "Which requirements remain unallocated or have conflicting allocations?", "kind": "exception", "answer_data": [ "requirement-allocation-allocation-gaps" ] }, { "id": "requirement-allocation-q03", "text": "Which evidence and responsible reviewer justify marking an allocation satisfied instead of merely linked?", "kind": "evidence", "answer_data": [ "requirement-allocation-satisfaction-evidence" ] } ], "data_elements": [ { "id": "requirement-allocation-allocation", "name": "allocation", "description": "WM-REC-006 requirement identity/revision to design-element identity/revision, relation direction and allocation status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "requirement-allocation-allocation-gaps", "name": "allocation-gaps", "description": "Unallocated requirements, ambiguous or conflicting assignments and responsible resolution role.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "requirement-allocation-satisfaction-evidence", "name": "satisfaction-evidence", "description": "Acceptance criterion, method, evidence, scoped status and accountable reviewer; a link is not proof of satisfaction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "requirement-allocation-evidence", "name": "Requirement allocation evidence manifest", "description": "Revision-bound supporting records for requirement allocation; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "design-rationale", "name": "Alternatives and rationale", "description": "Record why this solution was selected while keeping decision authority external and identifiable.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "design-rationale-record", "name": "Alternatives and rationale record", "description": "Record why this solution was selected while keeping decision authority external and identifiable.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "design-rationale-q01", "text": "Which alternative solutions were evaluated against which decision criteria?", "kind": "decision", "answer_data": [ "design-rationale-trade-study" ] }, { "id": "design-rationale-q02", "text": "Which assumptions or uncertain estimates could reverse the selected trade-off?", "kind": "quality", "answer_data": [ "design-rationale-assumptions" ] }, { "id": "design-rationale-q03", "text": "Which decision authority selected the solution and what triggers reconsideration?", "kind": "authority", "answer_data": [ "design-rationale-selection-decision" ] } ], "data_elements": [ { "id": "design-rationale-trade-study", "name": "trade-study", "description": "Candidate alternatives, versioned criteria, weights, objective values and rejected-option rationale.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "design-rationale-assumptions", "name": "assumptions", "description": "Assumption identity, uncertain estimate, sensitivity, evidence and conditions that could reverse preference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "design-rationale-selection-decision", "name": "selection-decision", "description": "Decision record with responsible authority, selected revision, rationale and reconsideration trigger.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "design-rationale-evidence", "name": "Alternatives and rationale evidence manifest", "description": "Revision-bound supporting records for alternatives and rationale; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "product-definition", "name": "Product definition and interfaces", "description": "Describe engineering structure and machine-interpretable geometry and annotations.", "rationale": "Proposed Vercy decomposition: Describe engineering structure and machine-interpretable geometry and annotations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "layers": [ { "id": "architecture-interface", "name": "Architecture and interface contract", "description": "Reference intended architecture and engineering composition without absorbing independent BOM masters.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "architecture-interface-record", "name": "Architecture and interface contract record", "description": "Reference intended architecture and engineering composition without absorbing independent BOM masters.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "architecture-interface-q01", "text": "Which functional elements map to which physical components and BOM revisions?", "kind": "composition", "answer_data": [ "architecture-interface-architecture-map" ] }, { "id": "architecture-interface-q02", "text": "Which interface endpoints, reference frames and mating conditions must agree?", "kind": "spatial", "answer_data": [ "architecture-interface-interface-contract" ] }, { "id": "architecture-interface-q03", "text": "Which external interface dependency remains unresolved and blocks release?", "kind": "constraint", "answer_data": [ "architecture-interface-interface-gaps" ] } ], "data_elements": [ { "id": "architecture-interface-architecture-map", "name": "architecture-map", "description": "Functional element to physical component and WM-OBJ-019 BOM occurrence/revision mappings.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "architecture-interface-interface-contract", "name": "interface-contract", "description": "Endpoint IDs, protocol or connector revision, datum/reference frames, mating predicates and compatible counterpart scope.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "architecture-interface-interface-gaps", "name": "interface-gaps", "description": "Unresolved external endpoint, version mismatch, constraint conflict and release-blocking disposition.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "architecture-interface-evidence", "name": "Architecture and interface contract evidence manifest", "description": "Revision-bound supporting records for architecture and interface contract; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "geometry-pmi", "name": "Geometry, material and semantic PMI", "description": "Represent intended geometric meaning, not merely visual resemblance or observed dimensions.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "geometry-pmi-record", "name": "Geometry, material and semantic PMI record", "description": "Represent intended geometric meaning, not merely visual resemblance or observed dimensions.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "geometry-pmi-q01", "text": "Which geometric features carry the nominal dimensions, datums and tolerances?", "kind": "measurement", "answer_data": [ "geometry-pmi-geometric-definition" ] }, { "id": "geometry-pmi-q02", "text": "Is an annotation machine-interpretable PMI or only a graphical presentation?", "kind": "interoperability", "answer_data": [ "geometry-pmi-pmi-status" ] }, { "id": "geometry-pmi-q03", "text": "Which units, material specification, surface conditions and measurement conventions qualify the intended values?", "kind": "definition", "answer_data": [ "geometry-pmi-material-surface" ] } ], "data_elements": [ { "id": "geometry-pmi-geometric-definition", "name": "geometric-definition", "description": "Stable feature IDs, geometry representation, nominal dimension/quantity, unit, datum references and tolerance expression.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "geometry-pmi-pmi-status", "name": "pmi-status", "description": "Semantic representation versus graphical presentation, feature associations, machine interpretation capability and unsupported annotations.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "geometry-pmi-material-surface", "name": "material-surface", "description": "Material specification/revision, surface condition, unit convention, test/measurement conditions and evidence; no guessed hardness or density.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "geometry-pmi-evidence", "name": "Geometry, material and semantic PMI evidence manifest", "description": "Revision-bound supporting records for geometry, material and semantic pmi; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "behavior-assurance", "name": "Intended behavior and assurance", "description": "Qualify what the intended product should do and what supports that assertion.", "rationale": "Proposed Vercy decomposition: Qualify what the intended product should do and what supports that assertion.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "behavior-envelope", "name": "Functional envelope and failure assumptions", "description": "Document intended behavior and limits as qualified design assertions, not physical actuation authority.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "behavior-envelope-record", "name": "Functional envelope and failure assumptions record", "description": "Document intended behavior and limits as qualified design assertions, not physical actuation authority.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "behavior-envelope-q01", "text": "What functions and modes are intended under which loads and environments?", "kind": "definition", "answer_data": [ "behavior-envelope-intended-behavior" ] }, { "id": "behavior-envelope-q02", "text": "Which failure modes, prohibited uses and interface limits constrain the design?", "kind": "constraint", "answer_data": [ "behavior-envelope-failure-envelope" ] }, { "id": "behavior-envelope-q03", "text": "Which declared capability still lacks analysis or test evidence and must not be treated as certified safe operation?", "kind": "evidence", "answer_data": [ "behavior-envelope-qualification-gap" ] } ], "data_elements": [ { "id": "behavior-envelope-intended-behavior", "name": "intended-behavior", "description": "Functional class, supported action/mode, inputs, expected outputs and load/environment preconditions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "behavior-envelope-failure-envelope", "name": "failure-envelope", "description": "Failure/hazard references, prohibited use, interface limits and expected mitigation/recovery assumptions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "behavior-envelope-qualification-gap", "name": "qualification-gap", "description": "Unsupported capability claim, required analysis/test and explicit uncertainty; no certification from model validity.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "behavior-envelope-evidence", "name": "Functional envelope and failure assumptions evidence manifest", "description": "Revision-bound supporting records for functional envelope and failure assumptions; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "design-assurance", "name": "Design verification and validation", "description": "Separate design requirements satisfaction from stakeholder-fit assessment and from end-product testing.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "design-assurance-record", "name": "Design verification and validation record", "description": "Separate design requirements satisfaction from stakeholder-fit assessment and from end-product testing.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "design-assurance-q01", "text": "What demonstrates that the definition satisfies its allocated requirements?", "kind": "validation", "answer_data": [ "design-assurance-verification" ] }, { "id": "design-assurance-q02", "text": "What separately demonstrates that the selected solution meets stakeholder intent in the intended use context?", "kind": "quality", "answer_data": [ "design-assurance-validation" ] }, { "id": "design-assurance-q03", "text": "Which design revision, analysis assumptions and unresolved findings limit each result, without claiming the manufactured item was verified?", "kind": "provenance", "answer_data": [ "design-assurance-assurance-scope" ] } ], "data_elements": [ { "id": "design-assurance-verification", "name": "verification", "description": "Design-target revision, allocated requirement, method, acceptance criterion, result and evidence; not manufactured-item verification.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "design-assurance-validation", "name": "validation", "description": "Stakeholder expectation, intended-use scenario, method, result, evidence and reviewer; separate from requirement verification.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "design-assurance-assurance-scope", "name": "assurance-scope", "description": "Exact design and analysis versions, assumptions, unresolved findings, method limitations and assurance kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "design-assurance-evidence", "name": "Design verification and validation evidence manifest", "description": "Revision-bound supporting records for design verification and validation; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "change-realization", "name": "Change and realization", "description": "Control approved revisions and preserve the boundary between design intent and built reality.", "rationale": "Proposed Vercy decomposition: Control approved revisions and preserve the boundary between design intent and built reality.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009" ], "layers": [ { "id": "release-effectivity", "name": "Review, release, change and effectivity", "description": "Preserve controlled release and change history; scoped deviations do not silently rewrite a baseline.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ], "findings": [ { "id": "release-effectivity-record", "name": "Review, release, change and effectivity record", "description": "Preserve controlled release and change history; scoped deviations do not silently rewrite a baseline.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ], "questions": [ { "id": "release-effectivity-q01", "text": "Who may approve this release and which unresolved findings prevent approval?", "kind": "authority", "answer_data": [ "release-effectivity-release-authority" ] }, { "id": "release-effectivity-q02", "text": "What changed between revisions, why, and which dependent definitions need review?", "kind": "lifecycle", "answer_data": [ "release-effectivity-revision-change" ] }, { "id": "release-effectivity-q03", "text": "For which dates, variants, production contexts or serial ranges is the revision or approved deviation applicable?", "kind": "temporal", "answer_data": [ "release-effectivity-effectivity-deviation" ] } ], "data_elements": [ { "id": "release-effectivity-release-authority", "name": "release-authority", "description": "Approver identity and delegated authority, gate criteria, open findings and release decision/time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] }, { "id": "release-effectivity-revision-change", "name": "revision-change", "description": "Before/after identities, expected-base digest, reason, impact set and required dependent reviews.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] }, { "id": "release-effectivity-effectivity-deviation", "name": "effectivity-deviation", "description": "Explicit applicability predicate over time/context/variant/serial range, boundary semantics and separately approved deviation/waiver scope.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "release-effectivity-evidence", "name": "Review, release, change and effectivity evidence manifest", "description": "Revision-bound supporting records for review, release, change and effectivity; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "realization-handoff", "name": "Manufacturing and inspection handoff", "description": "Deliver intended definition and reconcile realization evidence without overwriting intent.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "findings": [ { "id": "realization-handoff-record", "name": "Manufacturing and inspection handoff record", "description": "Deliver intended definition and reconcile realization evidence without overwriting intent.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "questions": [ { "id": "realization-handoff-q01", "text": "Which build-to and inspect-to documents and tooling references accompany release?", "kind": "process", "answer_data": [ "realization-handoff-handoff-content" ] }, { "id": "realization-handoff-q02", "text": "Which receiving organization acknowledged which exact package revision?", "kind": "event", "answer_data": [ "realization-handoff-acknowledgement" ] }, { "id": "realization-handoff-q03", "text": "Which as-built differences are approved deviations and which require an engineering change rather than silently rewriting the intended definition?", "kind": "exception", "answer_data": [ "realization-handoff-as-built-discrepancy" ] } ], "data_elements": [ { "id": "realization-handoff-handoff-content", "name": "handoff-content", "description": "Build-to and inspect-to document revisions plus tooling, process and inspection-master references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "realization-handoff-acknowledgement", "name": "acknowledgement", "description": "Receiving organization, purpose, exact package digest, receipt time and acceptance/rejection status.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "realization-handoff-as-built-discrepancy", "name": "as-built-discrepancy", "description": "Observed item/inspection reference, divergence from intended definition, approved deviation or engineering-change decision; no uncontrolled backwrite.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "realization-handoff-evidence", "name": "Manufacturing and inspection handoff evidence manifest", "description": "Revision-bound supporting records for manufacturing and inspection handoff; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "technical-exchange", "name": "Controlled technical exchange", "description": "Preserve authority, accessibility and engineering meaning across custodians and formats.", "rationale": "Proposed Vercy decomposition: Preserve authority, accessibility and engineering meaning across custodians and formats.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "technical-stewardship", "name": "Technical stewardship, access and retention", "description": "Keep owner, custodian, author and consumer roles distinct across Dimensions and tool lifetimes.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ], "findings": [ { "id": "technical-stewardship-record", "name": "Technical stewardship, access and retention record", "description": "Keep owner, custodian, author and consumer roles distinct across Dimensions and tool lifetimes.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ], "questions": [ { "id": "technical-stewardship-q01", "text": "Who owns the definition and who merely stores or consumes its representations?", "kind": "ownership", "answer_data": [ "technical-stewardship-mastership" ] }, { "id": "technical-stewardship-q02", "text": "Which proprietary or restricted fields may cross a Dimension boundary for the declared purpose and recipient?", "kind": "security", "answer_data": [ "technical-stewardship-disclosure" ] }, { "id": "technical-stewardship-q03", "text": "What must remain readable after tool obsolescence or product retirement, and which retention holds prohibit deletion?", "kind": "retention", "answer_data": [ "technical-stewardship-preservation" ] } ], "data_elements": [ { "id": "technical-stewardship-mastership", "name": "mastership", "description": "Owning Dimension, definition owner, author, custodian and controlled source references with distinct responsibilities.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ] }, { "id": "technical-stewardship-disclosure", "name": "disclosure", "description": "Field/artifact scope, recipient, purpose, proprietary/restricted classification and referenced authorization decision.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ] }, { "id": "technical-stewardship-preservation", "name": "preservation", "description": "Retention trigger, hold, obsolete-tool migration, readable preservation form, dependency continuity and minimized tombstone.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "technical-stewardship-evidence", "name": "Technical stewardship, access and retention evidence manifest", "description": "Revision-bound supporting records for technical stewardship, access and retention; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "engineering-fidelity", "name": "Transformation and engineering fidelity", "description": "A valid export file or matching rendering does not prove engineering-semantic equivalence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "engineering-fidelity-record", "name": "Transformation and engineering fidelity record", "description": "A valid export file or matching rendering does not prove engineering-semantic equivalence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "engineering-fidelity-q01", "text": "Which native and neutral schema releases and translator versions produced this exchanged representation?", "kind": "provenance", "answer_data": [ "engineering-fidelity-transformation" ] }, { "id": "engineering-fidelity-q02", "text": "Which geometry, feature associations, units or semantic PMI were lost or degraded even if the rendered model looks correct?", "kind": "interoperability", "answer_data": [ "engineering-fidelity-semantic-loss" ] }, { "id": "engineering-fidelity-q03", "text": "Which reference fixtures and comparison criteria justify acceptance, and when must the receiver reject the package instead of assuming equivalence?", "kind": "validation", "answer_data": [ "engineering-fidelity-acceptance-fixture" ] } ], "data_elements": [ { "id": "engineering-fidelity-transformation", "name": "transformation", "description": "Native and neutral format/releases, translator version, exact source/target digest and transformation provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "engineering-fidelity-semantic-loss", "name": "semantic-loss", "description": "Lost geometry, feature associations, tolerances, units, PMI or traceability with explicit severity and receiver disposition.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "engineering-fidelity-acceptance-fixture", "name": "acceptance-fixture", "description": "Reference fixture/version, geometry and semantic comparison criteria, results, unsupported constructs and reject/sidecar policy.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "engineering-fidelity-evidence", "name": "Transformation and engineering fidelity evidence manifest", "description": "Revision-bound supporting records for transformation and engineering fidelity; retain source and unresolved assertions without copying protected external masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative master-system evidence ID first, then issuer-qualified UUID; bind design revision, evidence scope and digest separately. A timestamp or filename alone is not identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-design-baseline", "name": "Resolve authoritative baseline", "description": "Resolve a design revision and representation authority before selecting package members.", "inputs": [ "Qualified design ID", "Authorized baseline registry" ], "outputs": [ "Pinned package or explicit ambiguity" ], "preconditions": [ "Owner access policy is satisfied" ], "effects": [ "Conflicting representations are not silently merged" ], "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "trace-requirement-realization", "name": "Trace requirement realization", "description": "Link exact requirement and design-element revisions; never infer satisfaction from link presence.", "inputs": [ "Requirement revision", "Design element", "Evidence reference" ], "outputs": [ "Qualified allocation and gap report" ], "preconditions": [ "Both masters are resolvable" ], "effects": [ "Unallocated or contradictory requirements remain visible" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "inspect-engineering-definition", "name": "Inspect intended engineering meaning", "description": "Check geometry, units, PMI associations and interface bindings through approved tooling; this contract does not implement it.", "inputs": [ "Pinned design package", "Declared engineering profile" ], "outputs": [ "Scoped inspection receipt and unsupported constructs" ], "preconditions": [ "Authorized non-executing read or approved sandboxed adapter" ], "effects": [ "Rendering equivalence is never substituted for semantic equivalence" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "assess-design-assurance", "name": "Assess design assurance evidence", "description": "Distinguish requirements verification and stakeholder-fit validation of design from end-product tests.", "inputs": [ "Design revision", "Scoped analysis/review evidence" ], "outputs": [ "Qualified design assurance and open findings" ], "preconditions": [ "Target revision and acceptance criteria are explicit" ], "effects": [ "No physical certification or safety authority is inferred" ], "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "release-controlled-revision", "name": "Release controlled revision", "description": "Record approval after required completeness, review and applicability checks.", "inputs": [ "Proposed revision", "Review findings", "Release authority" ], "outputs": [ "Immutable baseline and scoped release receipt" ], "preconditions": [ "Expected-base digest matches; required gates pass; no blocking finding" ], "effects": [ "Retain prior baseline and change-impact trace" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-009" ] }, { "id": "handoff-definition", "name": "Handoff definition and reconcile deviations", "description": "Transmit only authorized package members and record receiver acknowledgement and as-built discrepancies.", "inputs": [ "Pinned package", "Authorized recipient and purpose" ], "outputs": [ "Digest-bound receipt and discrepancy dispositions" ], "preconditions": [ "Disclosure and relevant external-write authority granted" ], "effects": [ "As-built differences never silently rewrite intended design" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "exchange-with-loss-report", "name": "Exchange with engineering loss report", "description": "Use versioned tested mappings and reject unsupported required semantics.", "inputs": [ "Native package", "Target profile", "Approved translator" ], "outputs": [ "Derivative artifact and explicit fidelity report" ], "preconditions": [ "License/access permit export; reference criteria are declared" ], "effects": [ "Keep source unchanged and preserve transformation provenance" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "retire-and-preserve-design", "name": "Retire and preserve historical interpretation", "description": "Retain controlled history and readable dependencies under retention and hold policy.", "inputs": [ "Retirement authority", "Dependencies and retention review" ], "outputs": [ "Retired revision and preservation/tombstone record" ], "preconditions": [ "No prohibited deletion or unresolved hold" ], "effects": [ "Never reassign a retired design ID" ], "source_refs": [ "SRC-002", "SRC-007" ] } ], "composition": [ { "target": "WM-REC-006", "relation": "REFERENCE", "purpose": "Preserve requirement-realization traceability from frozen relation ledger.", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "target": "WM-OBJ-002", "relation": "REFERENCE", "purpose": "Resolve family/master classification.", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-OBJ-017", "relation": "REFERENCE", "purpose": "Bind configured variants to intended engineering revision.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-OBJ-019", "relation": "REFERENCE", "purpose": "Reference engineering composition masters.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-OBJ-001", "relation": "REFERENCE", "purpose": "Resolve as-built instance context without importing observations as design truth.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "Document, analysis, inspection, workflow and decision masters", "relation": "REFERENCE", "purpose": "Reference authoritative representations, evidence and execution rather than duplicating lifecycles.", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] }, { "target": "ISO AP242 public scope and OMG ReqIF 1.2", "relation": "ALIGN", "purpose": "Candidate versioned engineering and requirement exchange profiles; exact mappings and normative conformance remain unverified.", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify the Dimension owner and authoritative engineering-definition masters.", "Declare namespaces, model/definition registries and immutable revision bindings.", "Declare release authority, access policy, federation rules and retention obligations." ], "namespace_guidance": "Use issuer-qualified design IDs and stable local feature IDs. Local extensions name their owning Dimension and pinned base; filenames are storage bindings.", "registry_links": [ "Dimension model registry", "Design and baseline registry", "Requirement and interface masters", "Change and evidence registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve intended definition separately from observed physical-item state.", "Pin every released package member; disagreement between representations remains contested until resolved by declared authority." ], "patch_rules": [ "Create an authorized new revision or namespaced extension with expected-base digest; reject concurrent conflicting changes.", "Assess requirement, geometry/PMI, interface, applicability and handoff impact before release; never silently rewrite historical baselines." ], "compatibility_rules": [ "A new representation format does not imply a new design identity; changed engineering meaning requires explicit controlled revision.", "A scoped waiver or deviation is not automatically a baseline change; preserve exact applicability and authority." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system ID", "Governed issuer-qualified UUID", "Dimension UUID with immutable revision and digest" ], "timestamp_rule": "Use RFC 3339 with seconds and UTC Z or explicit numeric offset; keep recording, approval and effectivity times distinct.", "serial_naming_rule": "Evidence type plus opaque master ID and revision; no sole date identifiers or confidential data in filenames.", "integrity_rule": "Verify exact bytes, media type and pinned dependency digests; imported CAD macros, expressions and external entities remain untrusted and are never automatically executed." }, "policies": [ "Design data validity is not manufactured-item fitness, certification, export permission or authority to actuate.", "Maintain the distinction between nominal engineering values and measured instance properties, with units and evidence.", "This information contract supplies no CAD translator, solver, PMI interpreter or executable instance conformance schema." ], "crud": { "read": [ "Read AGENTS.md and owner policy, pinned design revision and representation authority, then only authorized package and requirement references." ], "create": [ "Reuse the active authorized Dimension; create a partial design definition bound to family and requirement masters with explicit unknowns." ], "update": [ "Append a controlled revision under expected-base checks; review dependent requirements, features, interfaces and release evidence." ], "delete": [ "Retire first; evaluate retention/hold and dependent-item continuity before authorized deletion. Preserve minimized tombstone and required historical definition references." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Defines namespace, storage, delegation and federation." ] }, { "name": "Design authority", "responsibilities": [ "Owns intended definition and resolves representation conflicts." ] }, { "name": "Design author", "responsibilities": [ "Creates traceable changes and records assumptions without self-granting release." ] }, { "name": "Engineering reviewer", "responsibilities": [ "Checks requirement evidence, interfaces, geometry and unresolved findings." ] }, { "name": "Release approver", "responsibilities": [ "Authorizes an immutable baseline within delegated scope." ] }, { "name": "Technical data custodian", "responsibilities": [ "Maintains access, fixity and preservation without becoming design owner." ] }, { "name": "Exchange maintainer", "responsibilities": [ "Tests translations and exposes semantic loss." ] } ], "access": { "default_rule": "Deny undeclared access; a public model specification grants no access to an organization's actual technical package.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A scoped disclosure exception requires accountable authority, purpose, recipient, expiry and redaction policy; no automatic cross-Dimension copying." ], "audit_requirements": [ "Record actor, target design revision, operation, authority decision, time and affected package digest for controlled changes and protected access." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Dimension", "Design authority", "Revision", "Policy URL" ], "read_order": [ "AGENTS.md and Dimension owner/access policy", "Pinned specification and design revision with representation precedence", "Baseline manifest and authorized requirement/interface references", "Design assurance, release, change and retention process" ] } }, "coverage": { "claim": "Proposed source-grounded engineering-definition information contract with individually authored questions, typed field groups and qualified design boundaries. It is not exhaustive sector coverage, executable engineering tooling or an independently certified specification.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Design ID and immutable revision distinct from representation filename" }, { "dimension": "lifecycle", "status": "covered", "notes": "Maturity, baseline, controlled revision and retirement" }, { "dimension": "relationships", "status": "covered", "notes": "Requirement realization and external family/variant/BOM/item masters" }, { "dimension": "temporal", "status": "covered", "notes": "Recorded, approval and effective time separated" }, { "dimension": "provenance", "status": "covered", "notes": "Evidence and transformation attribution" }, { "dimension": "ownership", "status": "covered", "notes": "Design authority distinct from technical data custodian" }, { "dimension": "validation", "status": "covered", "notes": "Design verification, stakeholder validation and product testing distinct" }, { "dimension": "access", "status": "covered", "notes": "Scoped technical disclosure and federation" }, { "dimension": "interoperability", "status": "covered", "notes": "Semantic PMI and versioned transformation losses" }, { "dimension": "direct properties", "status": "covered", "notes": "Intended geometry, units, material and nominal parameters, not item observations" }, { "dimension": "recognition", "status": "covered", "notes": "Stable features and representation associations; visual similarity insufficient" }, { "dimension": "capabilities", "status": "covered", "notes": "Intended behavior and limits with evidence and explicit unknowns" }, { "dimension": "retention", "status": "covered", "notes": "Readable historical baselines and dependency continuity" }, { "dimension": "Operational conformance", "status": "gap", "notes": "No executable instance schema, CAD adapter, real design fixture or normative certification is delivered." } ], "known_omissions": [ "Claude and Grok research each timed out once at 120 seconds; no independent external research result is admitted. Visible owner-authorized provider waiver remains.", "ISO AP242 support is public scope only; ASME empty catalogue description was not admitted. Licensed clauses and sector-specific PMI/metrology semantics require specialist review.", "NIST fixtures are historical and selected; their old references to current standards are not 2026 version assertions or proof of present tool capability.", "NASA process guidance is domain-specific. Local lifecycle, disclosure and release policy must be declared; no universal four-baseline scheme is mandated.", "Nested field groups are an information contract, not a complete executable instance schema. CAD/PMI interpretation, real-product examples, target crosswalks and round-trip acceptance fixtures are deferred.", "Direct intended properties and capability assertions require product-specific evidence. Actual location, measured state, manufactured-item safety and legal certification remain outside this aggregate." ], "conflicts": [], "regional_assumptions": [ "Industry, contract and jurisdiction determine technical disclosure, retention and certification duties; this model does not grant permission or legal compliance." ], "adversarial_checks": [ "Reject informational design treated as a physical item with actual pose or wear.", "Reject requirement linkage as proof of satisfaction or design verification as end-product certification.", "Reject filenames, mutable latest links or renderings as authoritative engineering identity.", "Reject missing semantic PMI hidden behind a visually matching derivative.", "Reject unauthorized release, silent competing-representation resolution or conflicting expected-base update.", "Reject obsolete fixture editions as current standards or uninspected normative claims." ] }, "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 informational design revision owns coherent intended-definition assertions and baseline bindings. Product family, variant, BOM, physical item, requirement and execution masters remain external. Registry packaging standalone-mm is separate from the research aggregate classification." }, "decisions": [ { "concept": "Informational rather than physical root", "disposition": "accepted", "rationale": "The frozen result explicitly separates nominal engineering definition from observed location, mass, wear and operating state of an item. The former workstream's physical-subject assumption is not inherited." }, { "concept": "Frozen requirement relationship", "disposition": "accepted", "rationale": "REFERENCE to WM-REC-006 preserves design-realizes-requirement traceability. Allocation and scoped satisfaction evidence do not assume ownership of requirement content." }, { "concept": "Representation authority", "disposition": "accepted", "rationale": "Design identity is independent of filenames and exports. Competing drawing and model assertions stay contested until the declared design authority resolves them; the latest timestamp does not silently win." }, { "concept": "Design assurance versus end-product certification", "disposition": "accepted", "rationale": "Verification of requirements and validation against stakeholder intent are separately qualified for the design revision. Neither establishes manufactured-item safety or legal certification." }, { "concept": "Semantic PMI and visual rendering", "disposition": "accepted", "rationale": "The result distinguishes machine-interpretable feature associations and tolerances from graphical annotations. Matching rendered geometry is insufficient evidence of lossless engineering exchange." }, { "concept": "NASA and NIST applicability", "disposition": "accepted with limitations", "rationale": "NASA guidance is domain-specific and does not impose a universal baseline workflow. NIST selected historical fixtures do not establish current tool capability or exhaustive real-product conformance." }, { "concept": "Licensed normative standards", "disposition": "deferred", "rationale": "AP242 is supported only by its public scope. The empty ASME catalogue description is excluded. ReqIF release and selected XSD declarations do not establish a tested semantic mapping." }, { "concept": "Executable completeness", "disposition": "deferred", "rationale": "Nested field descriptions propose an information contract, not an executable instance schema. CAD/PMI adapters, real-product fixtures and calibrated acceptance criteria remain adoption work; no implementation success is claimed." }, { "concept": "Controlled change and governance", "disposition": "accepted", "rationale": "Expected-base checks, scoped release authority, separate deviation applicability, protected disclosure and retention preserve historical interpretation. A custodian does not become design owner." }, { "concept": "Provider attribution", "disposition": "accepted with mandatory hold", "rationale": "Both bounded external research attempts timed out. This audit is a separate frozen-result Codex self-check with no research tools, not an independent reviewer or a Claude/Grok answer." } ], "publicationHolds": [ "No independent external research or independent reviewer: Claude and Grok each timed out once at 120 seconds. Source-grounded Codex research and a separate frozen no-tools Codex self-audit are used under owner authorization. This remains reviewable-draft, not canonical.", "AP242 licensed clauses and sector-specific engineering/metrology standards were not inspected. ReqIF semantic mapping and source-to-field conformance are untested. No normative standards compliance is claimed.", "NIST PMI evidence uses historical selected fixtures and cannot demonstrate current software capability or universal product completeness. NASA process guidance requires local applicability decisions.", "No executable instance-validation schema, CAD interpreter, PMI adapter, real design fixture or verified round-trip translator is included. Nested field groups are proposed semantics requiring implementation and tests.", "Physical capabilities, tolerances, recognition and safe-use claims require product-specific evidence and qualified engineering review. Information-model validity never authorizes physical action or certification.", "The adopting Dimension must instantiate actual design authority, release roles, access controls and retention policy before live engineering records are created or released.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Executable field-level schema and failure fixtures for conflicting authority, stale baseline, unresolved requirement and concurrent change.", "Sector-specific engineering geometry, metrology, material, interface and physical-assurance evidence.", "Licensed standard inspection and version-specific CAD/PMI/ReqIF crosswalks with explicit unsupported constructs.", "Native-versus-derivative real-product tests for geometry, units, tolerances, semantic annotations and requirement traceability.", "Independent external research and adversarial review of the completed information contract." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 8 } }