@memoarchitect/ontology 0.17.1 → 0.18.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (265) hide show
  1. package/README.md +1 -1
  2. package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +11 -18
  3. package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/views/connected_patient_monitor_overview.sysml +1 -3
  4. package/examples/connected-patient-monitor/model/methodology/project.sysml +2 -6
  5. package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +35 -47
  6. package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/views/embedded_infusion_pump_overview.sysml +1 -3
  7. package/examples/embedded-infusion-pump/model/methodology/project.sysml +2 -6
  8. package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +24 -36
  9. package/examples/functional-logical-physical/model/catalog/viewpoints/logical/views/functional_logical_physical_overview.sysml +1 -3
  10. package/examples/functional-logical-physical/model/methodology/project.sysml +2 -6
  11. package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +5 -19
  12. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +1 -5
  13. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +1 -5
  14. package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +1 -5
  15. package/examples/gastric-bypass-variants/model/methodology/project.sysml +2 -6
  16. package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
  17. package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
  18. package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
  19. package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
  20. package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
  21. package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
  22. package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
  23. package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
  24. package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
  25. package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
  26. package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
  27. package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
  28. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +45 -55
  29. package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
  30. package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
  31. package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
  32. package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
  33. package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
  34. package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
  35. package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
  36. package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
  37. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
  38. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
  39. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
  40. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
  41. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
  42. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
  43. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
  44. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
  45. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
  46. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
  47. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
  48. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
  49. package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
  50. package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
  51. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
  52. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
  53. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
  54. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
  55. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
  56. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
  57. package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
  58. package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
  59. package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
  60. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
  61. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
  62. package/examples/gpca-pump/model/methodology/project.sysml +1 -4
  63. package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
  64. package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
  65. package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
  66. package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
  67. package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
  68. package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
  69. package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
  70. package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
  71. package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
  72. package/examples/nested-architecture-dsm/README.md +5 -5
  73. package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
  74. package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
  75. package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
  76. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
  77. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
  78. package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
  79. package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
  80. package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
  81. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +18 -27
  82. package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
  83. package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
  84. package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
  85. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +2 -7
  86. package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
  87. package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
  88. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +1 -4
  89. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +4 -9
  90. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +4 -9
  91. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +4 -9
  92. package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
  93. package/examples/robot-platform/model/platform.sysml +1 -3
  94. package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
  95. package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
  96. package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
  97. package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
  98. package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
  99. package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
  100. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +32 -43
  101. package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
  102. package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
  103. package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
  104. package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
  105. package/examples/surgical-robot/model/methodology/project.sysml +2 -6
  106. package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
  107. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +8 -16
  108. package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
  109. package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
  110. package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
  111. package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
  112. package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
  113. package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
  114. package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
  115. package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
  116. package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
  117. package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
  118. package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
  119. package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
  120. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +5 -12
  121. package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
  122. package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
  123. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +43 -63
  124. package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
  125. package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
  126. package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
  127. package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
  128. package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
  129. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
  130. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
  131. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
  132. package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
  133. package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
  134. package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
  135. package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
  136. package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
  137. package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
  138. package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
  139. package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
  140. package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
  141. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
  142. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
  143. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
  144. package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
  145. package/extensions/README.md +2 -2
  146. package/extensions/aadl/memo.package.yaml +1 -1
  147. package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
  148. package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
  149. package/extensions/anatomy/memo.package.yaml +1 -1
  150. package/extensions/clinical/memo.package.yaml +1 -1
  151. package/extensions/cloud/memo.package.yaml +1 -1
  152. package/extensions/cloud/src/cloud_extension.sysml +2 -4
  153. package/extensions/container/memo.package.yaml +1 -1
  154. package/extensions/container/src/container_extension.sysml +2 -5
  155. package/extensions/messaging/memo.package.yaml +1 -1
  156. package/extensions/messaging/src/messaging_extension.sysml +4 -5
  157. package/extensions/ros/memo.package.yaml +1 -1
  158. package/extensions/ros/src/ros_extension.sysml +5 -10
  159. package/methodologies/default/memo.package.yaml +1 -1
  160. package/methodologies/gpca/memo.package.yaml +1 -1
  161. package/ontology/memo.package.yaml +1 -1
  162. package/package.json +1 -1
  163. package/profile/memo.package.yaml +1 -1
  164. package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
  165. package/src/architecture/functional/functions/memo_functions.sysml +31 -44
  166. package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
  167. package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
  168. package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
  169. package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
  170. package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
  171. package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
  172. package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
  173. package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
  174. package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
  175. package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
  176. package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
  177. package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
  178. package/src/architecture/operational/activities/memo_activities.sysml +2 -2
  179. package/src/architecture/operational/context/actors/memo_actors.sysml +8 -7
  180. package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
  181. package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
  182. package/src/architecture/operational/rollups/memo_rollups.sysml +5 -4
  183. package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
  184. package/src/architecture/operational/structure/memo_operational.sysml +3 -5
  185. package/src/architecture/operational/use_cases/memo_use_cases.sysml +18 -23
  186. package/src/architecture/operational/workflows/memo_workflows.sysml +4 -7
  187. package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
  188. package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
  189. package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
  190. package/src/artifacts/standards/cfr_21_820.sysml +0 -1
  191. package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
  192. package/src/artifacts/standards/iec_60601_1.sysml +0 -1
  193. package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
  194. package/src/artifacts/standards/iec_60812.sysml +0 -1
  195. package/src/artifacts/standards/iec_62304.sysml +0 -1
  196. package/src/artifacts/standards/iec_62366_1.sysml +0 -1
  197. package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
  198. package/src/artifacts/standards/iso_13485.sysml +0 -1
  199. package/src/artifacts/standards/iso_14971.sysml +0 -1
  200. package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
  201. package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
  202. package/src/assurance/cybersecurity/memo_cybersecurity.sysml +1 -0
  203. package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
  204. package/src/assurance/requirements/memo_requirements.sysml +6 -11
  205. package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
  206. package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
  207. package/src/assurance/safety_risk/memo_risk.sysml +19 -22
  208. package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
  209. package/src/core/annotations/memo_annotations.sysml +2 -2
  210. package/src/core/common/memo_common.sysml +40 -56
  211. package/src/core/dimensions/dimensions.sysml +9 -12
  212. package/src/core/enumerations/memo_enumerations.sysml +4 -12
  213. package/src/core/methodology_scope/methodology_scope.sysml +3 -6
  214. package/src/core/relationships/memo_relationships.sysml +54 -85
  215. package/src/memo_namespaces.sysml +3 -0
  216. package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
  217. package/src/methodology/core/memo_core.sysml +12 -12
  218. package/src/methodology/profiles/memo_profiles.sysml +9 -10
  219. package/src/methodology/workflow/memo_workflow.sysml +7 -8
  220. package/src/rules/closure/closure_rules.sysml +7 -9
  221. package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
  222. package/src/rules/ontology/ontology_invariants.sysml +63 -95
  223. package/src/rules/quantitative/quantitative_rules.sysml +0 -1
  224. package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
  225. package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
  226. package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
  227. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +0 -1
  228. package/src/viewpoints/context/context_viewpoint.sysml +0 -1
  229. package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
  230. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
  231. package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
  232. package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
  233. package/src/viewpoints/definitions/memo_view_layout.sysml +25 -3
  234. package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
  235. package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
  236. package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
  237. package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
  238. package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
  239. package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
  240. package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
  241. package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
  242. package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
  243. package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
  244. package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
  245. package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
  246. package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
  247. package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
  248. package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
  249. package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
  250. package/src/viewpoints/software/software_viewpoint.sysml +0 -1
  251. package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
  252. package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
  253. package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
  254. package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
  255. package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
  256. package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
  257. package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
  258. package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
  259. package/stage1/opensysml-ddad9e2794141c08532910cf.json.gz +0 -0
  260. package/stage1/syside-8176a62528c701f2f2e0fc7f.ids.gz +0 -0
  261. package/stage1/syside-8176a62528c701f2f2e0fc7f.json.gz +0 -0
  262. package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
  263. package/stage1/opensysml-78b939a8e298313dd51f9813.json.gz +0 -0
  264. package/stage1/syside-d48ff8bfaf540531526ec21a.ids.gz +0 -0
  265. package/stage1/syside-d48ff8bfaf540531526ec21a.json.gz +0 -0
@@ -8,10 +8,8 @@
8
8
  // the traceability question is identical, only the enforceability differs, and
9
9
  // that difference is data on the clause rather than a second mechanism.
10
10
  //
11
- // Reference granularity is the guidance's own lettered section structure
12
- // (IV, V.A, …), not a decimal clause numbering — this document has none. The
13
- // templates previously cited decimal numbers ("3.2", "5.2") that match no
14
- // section of the published guidance; those were replaced when this pack landed.
11
+ // Reference granularity is the guidance's own lettered section structure (IV,
12
+ // V.A, …), not a decimal clause numbering — this document has none.
15
13
  package memo_artifacts_standards_fda_cybersecurity_2023 {
16
14
  private import ScalarValues::*;
17
15
  private import memo_core_enumerations::*;
@@ -19,7 +17,6 @@ package memo_artifacts_standards_fda_cybersecurity_2023 {
19
17
  private import memo_artifacts_standards_traceability::*;
20
18
 
21
19
  private import memo_core_common::*;
22
- private import memo_core_common::MemoIdentity;
23
20
  part fdaCybersecurity2023 : RegulatoryStandard {
24
21
  @MemoIdentity { :>> providedId = "STD-FDA-CYBER-2023"; }
25
22
  attribute :>> designation = "FDA Cybersecurity Guidance 2023";
@@ -16,7 +16,6 @@ package memo_artifacts_standards_iec_60601_1 {
16
16
  private import memo_artifacts_standards_traceability::*;
17
17
 
18
18
  private import memo_core_common::*;
19
- private import memo_core_common::MemoIdentity;
20
19
  part iec60601_1 : RegulatoryStandard {
21
20
  @MemoIdentity { :>> providedId = "STD-IEC-60601-1"; }
22
21
  attribute :>> designation = "IEC 60601-1:2005+AMD1:2012+AMD2:2020";
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iec_60601_1_2 {
11
11
  private import memo_artifacts_standards_traceability::*;
12
12
 
13
13
  private import memo_core_common::*;
14
- private import memo_core_common::MemoIdentity;
15
14
  part iec60601_1_2 : RegulatoryStandard {
16
15
  @MemoIdentity { :>> providedId = "STD-IEC-60601-1-2-COLLATERAL"; }
17
16
  attribute :>> designation = "IEC 60601-1-2:2014+AMD1:2020";
@@ -15,7 +15,6 @@ package memo_artifacts_standards_iec_60812 {
15
15
  private import memo_artifacts_standards_traceability::*;
16
16
 
17
17
  private import memo_core_common::*;
18
- private import memo_core_common::MemoIdentity;
19
18
  part iec60812 : RegulatoryStandard {
20
19
  @MemoIdentity { :>> providedId = "STD-IEC-60812"; }
21
20
  attribute :>> designation = "IEC 60812:2018";
@@ -17,7 +17,6 @@ package memo_artifacts_standards_iec_62304 {
17
17
  private import memo_artifacts_standards_traceability::*;
18
18
 
19
19
  private import memo_core_common::*;
20
- private import memo_core_common::MemoIdentity;
21
20
  part iec62304 : RegulatoryStandard {
22
21
  @MemoIdentity { :>> providedId = "STD-IEC-62304"; }
23
22
  attribute :>> designation = "IEC 62304:2006+AMD1:2015";
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iec_62366_1 {
11
11
  private import memo_artifacts_standards_traceability::*;
12
12
 
13
13
  private import memo_core_common::*;
14
- private import memo_core_common::MemoIdentity;
15
14
  part iec62366_1 : RegulatoryStandard {
16
15
  @MemoIdentity { :>> providedId = "STD-IEC-62366-1"; }
17
16
  attribute :>> designation = "IEC 62366-1:2015+AMD1:2020";
@@ -9,7 +9,6 @@ package memo_artifacts_standards_iec_81001_5_1 {
9
9
  private import memo_artifacts_standards_traceability::*;
10
10
 
11
11
  private import memo_core_common::*;
12
- private import memo_core_common::MemoIdentity;
13
12
  part iec81001_5_1 : RegulatoryStandard {
14
13
  @MemoIdentity { :>> providedId = "STD-IEC-81001-5-1"; }
15
14
  attribute :>> designation = "IEC 81001-5-1:2021";
@@ -67,5 +66,5 @@ package memo_artifacts_standards_iec_81001_5_1 {
67
66
 
68
67
 
69
68
 
70
-
69
+
71
70
  }
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iso_13485 {
11
11
  private import memo_artifacts_standards_traceability::*;
12
12
 
13
13
  private import memo_core_common::*;
14
- private import memo_core_common::MemoIdentity;
15
14
  part iso13485 : RegulatoryStandard {
16
15
  @MemoIdentity { :>> providedId = "STD-ISO-13485"; }
17
16
  attribute :>> designation = "ISO 13485:2016";
@@ -9,7 +9,6 @@ package memo_artifacts_standards_iso_14971 {
9
9
  private import memo_artifacts_standards_traceability::*;
10
10
 
11
11
  private import memo_core_common::*;
12
- private import memo_core_common::MemoIdentity;
13
12
  part iso14971 : RegulatoryStandard {
14
13
  @MemoIdentity { :>> providedId = "STD-ISO-14971"; }
15
14
  attribute :>> designation = "ISO 14971:2019";
@@ -13,7 +13,6 @@ package memo_artifacts_standards_iso_iec_ieee_42010 {
13
13
  private import memo_artifacts_standards_traceability::*;
14
14
 
15
15
  private import memo_core_common::*;
16
- private import memo_core_common::MemoIdentity;
17
16
  part isoIecIeee42010 : RegulatoryStandard {
18
17
  @MemoIdentity { :>> providedId = "STD-ISO-IEC-IEEE-42010"; }
19
18
  attribute :>> designation = "ISO/IEC/IEEE 42010:2022";
@@ -98,6 +98,7 @@ package memo_artifacts_standards_traceability {
98
98
  // =========================================================================
99
99
 
100
100
  connection def ConformsTo :> MemoRelationship {
101
+ attribute :>> isTrace = true;
101
102
  doc /* Any model element claims conformance to a standard clause.
102
103
  * This is the edge the standards traceability matrix and the
103
104
  * clause coverage report are computed over. */
@@ -115,6 +116,7 @@ package memo_artifacts_standards_traceability {
115
116
  }
116
117
 
117
118
  connection def TracesToDocument :> MemoRelationship {
119
+ attribute :>> isTrace = true;
118
120
  doc /* Where the evidence for a clause claim is written down. The target
119
121
  * is the existing controlled-artifact type — MEMO does not model a
120
122
  * separate Document/DocumentSection family, because
@@ -293,6 +293,7 @@ package memo_assurance_cybersecurity {
293
293
  :>> baseType = realizedByScenarioLinks meta SysML::Usage;
294
294
  }
295
295
  connection def ImpactsSafety :> MemoRelationship {
296
+ attribute :>> isTrace = true;
296
297
  attribute tracePurpose : String;
297
298
  end cyberElement : MemoPart :>> source;
298
299
  end safetyElement : RiskItem :>> target;
@@ -20,6 +20,7 @@ package memo_assurance_human_factors {
20
20
  }
21
21
 
22
22
  connection def CommitsUseError :> MemoRelationship {
23
+ attribute :>> isTrace = true;
23
24
  end task : OperativeAction :>> source;
24
25
  end useError : UseError :>> target;
25
26
  }
@@ -30,6 +31,7 @@ package memo_assurance_human_factors {
30
31
  :>> baseType = commitsUseErrorLinks meta SysML::Usage;
31
32
  }
32
33
  connection def EvaluatesTask :> MemoRelationship {
34
+ attribute :>> isTrace = true;
33
35
  end evaluation : MemoEvidence :>> source;
34
36
  end task : OperativeAction :>> target;
35
37
  }
@@ -41,13 +43,14 @@ package memo_assurance_human_factors {
41
43
  }
42
44
 
43
45
  // ── Relations owned by this package ─────────────────────────────
44
- // Moved out of memo_core_relationships: their ends are typed against
45
- // types declared here, and core must not depend on a domain package.
46
- // The source end is untyped for the reason `Validates`' is: a UI element
47
- // is a part and a task is an action (Track A0), so no one type spans both.
48
- // The target is the usability TEST — a validation case — and not the
49
- // evidence it produces; `ProducesEvidence` links the two.
46
+ // Declared here, not in memo_core_relationships: their ends are typed
47
+ // against types declared here, and core must not depend on a domain
48
+ // package. The source end is untyped for the reason `Validates`' is: a UI
49
+ // element is a part and a task is an action, so no one type spans both. The
50
+ // target is the usability TEST — a validation case — and not the evidence
51
+ // it produces; `ProducesEvidence` links the two.
50
52
  connection def TestedByUsability :> MemoRelationship {
53
+ attribute :>> isTrace = true;
51
54
  end uiElementOrTask :>> source;
52
55
  end usabilityTest : MemoVerificationCase :>> target;
53
56
  }
@@ -10,15 +10,11 @@ package memo_assurance_requirements {
10
10
  // What a requirement is about: the system, the software, the hardware, or
11
11
  // the instructions for use. One axis, and the members are its values.
12
12
  //
13
- // It carried a second axis until now. `systemSpecification`,
14
- // `softwareSpecification`, `hardwareSpecification` and `designControl` are
15
- // the design-control ROLE — input versus output, 21 CFR 820.30(c)/(d) and
16
- // ISO 13485 §7.3.3/§7.3.4 — multiplied into the subject. A requirement then
17
- // could not say "software" without also committing to a role, the grid was
18
- // incomplete by construction (there is no `ifuSpecification`, and there
19
- // would have to be one for every future pairing), and nothing ever used the
20
- // four: 250 requirements across the examples say system, software or
21
- // hardware. A role, if a project needs one, is its own attribute.
13
+ // The design-control ROLE — input versus output, 21 CFR 820.30(c)/(d) and
14
+ // ISO 13485 §7.3.3/§7.3.4 — is a different axis and is not here: multiplied
15
+ // into the subject, a requirement could not say "software" without also
16
+ // committing to a role. A role, if a project needs one, is its own
17
+ // attribute.
22
18
  //
23
19
  // The instructions for use are neither hardware nor software: the device
24
20
  // satisfies such a requirement with words rather than with a part or a
@@ -33,7 +29,6 @@ package memo_assurance_requirements {
33
29
 
34
30
  requirement def Requirement specializes MemoRequirement {
35
31
  attribute requirementType : RequirementTypeKind;
36
- attribute :>> statement : String;
37
32
  attribute sourceKind : RequirementSourceKind;
38
33
  attribute concernKind : ConcernKind;
39
34
  // Editorial state is the inherited `status : ElementStatusKind` — the
@@ -46,7 +41,7 @@ package memo_assurance_requirements {
46
41
  attribute assumptionSummary : String;
47
42
  attribute guaranteeSummary : String;
48
43
  // Authoring notation. `notation` selects the syntactic discipline the
49
- // `statement` follows; the slot attributes below carry the parsed clauses
44
+ // `doc` follows; the slot attributes below carry the parsed clauses
50
45
  // so tools can lint pattern conformance and render either style.
51
46
  attribute notation : RequirementNotationKind;
52
47
  attribute earsPattern : EarsPatternKind; // applies when notation = ears
@@ -1,8 +1,7 @@
1
- // Needs (§4). A Need is a problem-space expectation stated in stakeholder
2
- // language; requirements (memo_assurance_requirements) are the solution-space
3
- // obligations derived from needs. Need specializes the part-based
4
- // RequirementDriver so it can serve as a typed end of trace relations
5
- // (DerivesFrom, Motivates).
1
+ // Needs. A Need is a problem-space expectation stated in stakeholder language;
2
+ // requirements (memo_assurance_requirements) are the solution-space obligations
3
+ // derived from needs. Need specializes the part-based RequirementDriver so it
4
+ // can serve as a typed end of trace relations (DerivesFrom, Motivates).
6
5
  package memo_assurance_requirements_needs {
7
6
  private import ScalarValues::*;
8
7
 
@@ -188,6 +188,7 @@ package memo_assurance_safety_risk_analysis {
188
188
  :>> baseType = identifiesHazardLinks meta SysML::Usage;
189
189
  }
190
190
  connection def HasFailureMode :> MemoRelationship {
191
+ attribute :>> isTrace = true;
191
192
  end element : MemoPart :>> source;
192
193
  end failureMode : FailureMode :>> target;
193
194
  }
@@ -7,7 +7,7 @@ package memo_assurance_safety_risk {
7
7
  private import memo_core_enumerations::*;
8
8
  private import memo_assurance_requirements::*;
9
9
  // For HazardRelatedScenario below. Assurance may depend on architecture;
10
- // the reverse is what the string on the scenario was avoiding.
10
+ // the reverse is not allowed.
11
11
  private import memo_architecture_operational_scenarios::*;
12
12
 
13
13
  // ISO 14971 / IEC 62366-1 risk-analysis input. A model element so hazards,
@@ -45,15 +45,14 @@ package memo_assurance_safety_risk {
45
45
  attribute riskLevelMapping : String;
46
46
  attribute acceptabilityThresholds : String;
47
47
  }
48
- // `DesignControlRiskRow` was a denormalized spreadsheet transcription.
49
- // Risk rows now decompose into the ISO 14971 chain below: a Hazard,
50
- // SequenceOfEvents, HazardousSituation and Harm are independent elements, not
51
- // owned by a risk, because the same hazard is the hazard of many risks. A Risk
52
- // is linked to each by EstimatedFor, and the chain runs through TracesRisk /
53
- // LeadsToHarm, with ResidualRisk after mitigation. The risk itself is reached
54
- // by EstimatedFor / ReducedBy / EvaluatedIn below.
55
- // A device characteristic whose implementation, failure, or misuse can
56
- // affect safety. This is the modelable output of ISO 14971 §5.3.
48
+ // A risk decomposes into the ISO 14971 chain below: a Hazard,
49
+ // SequenceOfEvents, HazardousSituation and Harm are independent elements,
50
+ // not owned by a risk, because the same hazard is the hazard of many risks.
51
+ // A Risk is linked to each by EstimatedFor, and the chain runs through
52
+ // TracesRisk / LeadsToHarm, with ResidualRisk after mitigation. The risk
53
+ // itself is reached by EstimatedFor / ReducedBy / EvaluatedIn below. A
54
+ // device characteristic whose implementation, failure, or misuse can affect
55
+ // safety. This is the modelable output of ISO 14971 §5.3.
57
56
  part def SafetyRelatedCharacteristic specializes MemoPart {
58
57
  attribute characteristic : String;
59
58
  attribute safetyImpact : String;
@@ -128,6 +127,7 @@ package memo_assurance_safety_risk {
128
127
  // types declared here, and core must not depend on a domain package.
129
128
  // ISO 14971 risk chain — distinct sequence-of-events relations over risk elements.
130
129
  connection def TracesRisk :> MemoRelationship {
130
+ attribute :>> isTrace = true;
131
131
  end sourceRiskElement : RiskItem :>> source;
132
132
  end targetRiskElement : RiskItem :>> target;
133
133
  }
@@ -151,13 +151,11 @@ package memo_assurance_safety_risk {
151
151
  :>> baseType = leadsToHarmLinks meta SysML::Usage;
152
152
  }
153
153
  // IEC 62366-1 3.9's hazard-related use scenario: the scenario a hazard can
154
- // arise in. It is declared HERE rather than as a `hazardReference` string
155
- // on the scenario, which is what stood in for it: a string names nothing a
156
- // consumer can follow, and the layering is why it was written that way —
157
- // assurance may depend on architecture, and the scenario package cannot
158
- // see `Hazard`. On this side both ends are visible and the dependency runs
159
- // the direction it already runs.
154
+ // arise in. It is declared HERE because assurance may depend on
155
+ // architecture, and the scenario package cannot see `Hazard`. On this side
156
+ // both ends are visible.
160
157
  connection def HazardRelatedScenario :> MemoRelationship {
158
+ attribute :>> isTrace = true;
161
159
  end hazard : RiskItem :>> source;
162
160
  end scenario : OperativeScenario :>> target;
163
161
  }
@@ -178,12 +176,10 @@ package memo_assurance_safety_risk {
178
176
  :>> baseType = assessedAgainstLinks meta SysML::Usage;
179
177
  }
180
178
  // A risk is not a link in the chain (see RiskItem), so TracesRisk cannot
181
- // reach it — and until these three nothing else could either. A model had
182
- // no way to say which hazardous situation or harm a risk was estimated for
183
- // (ISO 14971 §5.5), which control reduced it to a residual risk (§7), or
184
- // which overall evaluation covered that residual (§8), so gpca-pump wrote
185
- // all three as TracesRisk into a Risk and the builder rejected every one.
186
- // Named from the risk's side, like AssessedAgainst.
179
+ // reach it. These three say which hazardous situation or harm a risk was
180
+ // estimated for (ISO 14971 §5.5), which control reduced it to a residual
181
+ // risk (§7), and which overall evaluation covered that residual (§8). Named
182
+ // from the risk's side, like AssessedAgainst.
187
183
  connection def EstimatedFor :> MemoRelationship {
188
184
  end risk : Risk :>> source;
189
185
  end riskElement : RiskItem :>> target;
@@ -227,6 +223,7 @@ package memo_assurance_safety_risk {
227
223
  enum fmeaAction;
228
224
  }
229
225
  connection def Mitigates :> MemoRelationship {
226
+ attribute :>> isTrace = true;
230
227
  attribute mitigationKind : MitigationKind;
231
228
  // Untyped: controls/hazards may be item defs (RiskControlMeasure, Hazard, …).
232
229
  end control :>> source;
@@ -12,18 +12,14 @@ package memo_assurance_verification_validation {
12
12
  private import memo_architecture_functional_functions::*;
13
13
  // Verification and validation cases are SysML v2 verification cases
14
14
  // (behaviours that check requirements), not verifiable structures — they
15
- // derive from the MemoVerificationCase foundation, not MemoPart.
16
- // `status` is NOT redeclared here. It used to be re-declared as a String,
17
- // which shadowed the `status : ElementStatusKind` every MEMO base carries
18
- // and let a verification case hold an editorial status no other element
19
- // could hold — against the "one status vocabulary in MEMO" rule stated in
20
- // memo_requirements.sysml. The values it actually held ("planned") were an
21
- // EXECUTION state, not an editorial one; execution state belongs in an
22
- // attribute of its own (see RiskControlMeasure.verificationStatus), not in
23
- // a second spelling of `status`.
24
- // Specializes the standard library verification case as well as MEMO's
25
- // base, rather than shadowing it — see the note on UseCase.
26
- // Reusable test action, distinct from a case's pass/fail criteria.
15
+ // derive from the MemoVerificationCase foundation, not MemoPart. `status`
16
+ // is NOT redeclared here: every MEMO base carries `status :
17
+ // ElementStatusKind`, the one status vocabulary in MEMO. An EXECUTION state
18
+ // such as "planned" belongs in an attribute of its own (see
19
+ // RiskControlMeasure.verificationStatus). Specializes the standard library
20
+ // verification case as well as MEMO's base, rather than shadowing it — see
21
+ // the note on UseCase. Reusable test action, distinct from a case's
22
+ // pass/fail criteria.
27
23
  action def TestStep specializes MemoAction {
28
24
  attribute stepAction : String;
29
25
  attribute expectedResult : String;
@@ -74,10 +70,10 @@ package memo_assurance_verification_validation {
74
70
  attribute acceptanceCriteria : String;
75
71
  attribute clinicalContext : String;
76
72
  }
77
- // Operational validation confirms the user's goal is achieved in the
78
- // use environment (§5): ValidationCase validates a UseCase.
79
- // Safety-critical functions must trace to verification (rules/coverage).
80
- // `ExecutesScenario` is native `perform` (2026-08-18): OperativeScenario
81
- // is an `action def`, so write `perform <scenario>;` inside the
82
- // verification case, as `InvolvesFunction` already does.
73
+ // Operational validation confirms the user's goal is achieved in the use
74
+ // environment: ValidationCase validates a UseCase. Safety-critical
75
+ // functions must trace to verification (rules/coverage). `ExecutesScenario`
76
+ // is native `perform`: OperativeScenario is an `action def`, so write
77
+ // `perform <scenario>;` inside the verification case, as `InvolvesFunction`
78
+ // already does.
83
79
  }
@@ -11,8 +11,8 @@
11
11
  //
12
12
  // Annotations attach to every metaclass — parts, actions, requirements, views,
13
13
  // connections, and MEMO specializations — so CommentsOn, RationaleFor, and
14
- // NotesOn leave their subject ends untyped, following the MemoLink precedent in
15
- // memo_core_relationships.
14
+ // NotesOn leave their subject ends untyped, as SysML's native `dependency`
15
+ // does (see memo_core_relationships).
16
16
  package memo_core_annotations {
17
17
  private import Metaobjects::SemanticMetadata;
18
18
  private import ScalarValues::*;
@@ -6,20 +6,13 @@
6
6
  // memo_core_dimensions rather than through a superclass.
7
7
  //
8
8
  // ─── Where identity lives ───────────────────────────────────────────────
9
- // Not in these bases. `@MemoIdentity`, below, is the one carrier: a
10
- // `metadata def` annotates an element of ANY metaclass, so it reaches the
11
- // action, port, item, requirement and connection families that KerML will
12
- // not let inherit from a part def. The bases used to re-declare an
13
- // "identification core" ten times over for exactly that reason, and ten
14
- // copies of one fact drifted every time (MemoPort carried no sourceReference
15
- // and no status; MemoRequirement and MemoNeed each invented their own status
16
- // attribute). One declaration replaced ten.
9
+ // Not in these bases. `@MemoIdentity`, below, is the one carrier: a `metadata
10
+ // def` annotates an element of ANY metaclass, so it reaches the action, port,
11
+ // item, requirement and connection families that KerML will not let inherit
12
+ // from a part def.
17
13
  //
18
- // `name` and `description` were the last two to go. Neither was ever MEMO's
19
- // to declare: every SysML element already has a native name, and `doc` is
20
- // already the native slot for prose. What the bases added was a second place
21
- // to write the same fact, and 188 of the 1373 elements that set `name` set it
22
- // to the identifier they were already declared under. Display text is now
14
+ // The bases declare no `name` or `description`: every SysML element already has
15
+ // a native name, and `doc` is the native slot for prose. Display text is
23
16
  // `@MemoIdentity { label }` and prose is `doc`.
24
17
  //
25
18
  // ─── Resources ──────────────────────────────────────────────────────────
@@ -55,8 +48,7 @@ package memo_core_common {
55
48
  // opt-in through `annotatedElement`, and this one declares none. That is
56
49
  // what the per-metaclass base definitions below cannot do: KerML will not
57
50
  // let an action, port, item, requirement or connection inherit from a part
58
- // def, which is why the identification core was once declared ten times
59
- // over. Metadata has no such limit, so one declaration replaced ten.
51
+ // def. Metadata has no such limit, so one declaration serves them all.
60
52
  //
61
53
  // An element has five identities and they are not interchangeable:
62
54
  //
@@ -70,13 +62,12 @@ package memo_core_common {
70
62
  // recorded in `memo.identity.yaml`: it is monotonic, gaps are kept, and a
71
63
  // retired number is never reused, so nothing authors it by hand.
72
64
  //
73
- // `label` is NOT a duplicate of the native name, which is the reading that
74
- // nearly deleted it: the native name is a lowerCamelCase identifier and
75
- // must be unique in its namespace, while a label is free text that
76
- // legitimately repeats — measured 2026-08-18, 1278 labels across the
77
- // ontology and examples share only 1216 distinct values, because seven
78
- // different ports are all correctly labelled "TLM_MODE_IN". A label
79
- // therefore cannot live in a name slot, native or otherwise.
65
+ // `label` is NOT a duplicate of the native name: the native name is a
66
+ // lowerCamelCase identifier and must be unique in its namespace, while a
67
+ // label is free text that legitimately repeats — measured 2026-08-18, 1278
68
+ // labels across the ontology and examples share only 1216 distinct values,
69
+ // because seven different ports are all correctly labelled "TLM_MODE_IN". A
70
+ // label therefore cannot live in a name slot, native or otherwise.
80
71
  //
81
72
  // `providedId` is the identifier an EXTERNAL system knows the element by,
82
73
  // and it exists because that system's scheme is not MEMO's: a customer
@@ -86,11 +77,11 @@ package memo_core_common {
86
77
  //
87
78
  // `uuid` is machine identity. Authored values win over the registry, which
88
79
  // wins over derivation — so an element whose file must move can pin its own
89
- // uuid, which is what the attribute always advertised.
80
+ // uuid.
90
81
  //
91
82
  // Deliberately absent: `name` and `description` (native name and `doc`),
92
- // `rationale` (standard `@Rationale`), and `id` — superseded by the
93
- // generated number id and by `providedId`.
83
+ // `rationale` (standard `@Rationale`), and `id` (the generated number id
84
+ // and `providedId`).
94
85
  metadata def MemoIdentity {
95
86
  attribute label : String[0..1];
96
87
  attribute providedId : String[0..1];
@@ -101,7 +92,7 @@ package memo_core_common {
101
92
 
102
93
  // Marks a definition as a KIND — an extension of the ontology — rather than a model element.
103
94
  // A project definition that specializes an ontology kind is, structurally, either a new kind
104
- // (`AfferaStakeholder`) or one particular thing (`HospitalEpRecordingSystem`); nothing in the
95
+ // (`ProjectStakeholder`) or one particular thing (`HospitalEpRecordingSystem`); nothing in the
105
96
  // SysML tells the two apart, so the author says which. A marked definition, and what is typed
106
97
  // by it, takes `idPrefix` as the family of its display ids (`<idPrefix>-1`). Anything unmarked
107
98
  // takes the family of the ontology kind it descends from.
@@ -118,20 +109,18 @@ package memo_core_common {
118
109
  //
119
110
  // Axis ownership (horizontal architecture layer vs. vertical assurance
120
111
  // discipline) is NOT an attribute — it is the element's owning package
121
- // (memo_architecture_* xor memo_assurance_*), enforced by CR-ONT-045.
122
- // The remaining dimensions are orthogonal to the axis: realization stage,
123
- // cross-cutting concern, and editorial status.
124
- // Deliberately NOT declared here: `name` and `description`. A name slot on
125
- // a MEMO base is a second spelling of the native name every SysML element
126
- // already has, and a description slot is a second spelling of `doc`. Both
127
- // were carried for years and both drifted: 1373 elements set `name`, and
128
- // 188 of them set it to the identifier they were already declared under.
129
- // The display label — free text, legitimately repeating — lives on
130
- // `@MemoIdentity { label }`, which annotates any metaclass and so reaches
131
- // the behaviours and views that cannot specialize a part. The long prose
132
- // lives in `doc`. `shortDescription` on `@MemoIdentity` remains the
133
- // one-line register a table cell or chip shows whole; it is a different
134
- // density, not a different authority.
112
+ // (memo_architecture_* xor memo_assurance_*), enforced by CR-ONT-045. The
113
+ // remaining dimensions are orthogonal to the axis: realization stage,
114
+ // cross-cutting concern, and editorial status. Deliberately NOT declared
115
+ // here: `name` and `description`. A name slot on a MEMO base is a second
116
+ // spelling of the native name every SysML element already has, and a
117
+ // description slot is a second spelling of `doc`. The display label — free
118
+ // text, legitimately repeating — lives on `@MemoIdentity { label }`, which
119
+ // annotates any metaclass and so reaches the behaviours and views that
120
+ // cannot specialize a part. The long prose lives in `doc`.
121
+ // `shortDescription` on `@MemoIdentity` remains the one-line register a
122
+ // table cell or chip shows whole; it is a different density, not a
123
+ // different authority.
135
124
  abstract part def MemoPart {
136
125
  // editorial status and lifecycle
137
126
  attribute status : ElementStatusKind;
@@ -168,13 +157,10 @@ package memo_core_common {
168
157
  attribute resultSummary : String;
169
158
  attribute evidenceType : String;
170
159
  attribute integrityStatus : String;
171
- // Promoted from the retired `UsabilityValidation` and
172
- // `FormativeEvaluation` specializations. The collapse in `02083c5`
173
- // deleted both subclasses without carrying their fields up, so an
174
- // IEC 62366-1 evaluation record lost what it actually reports.
175
- // Promoted on the standard's terms, not on in-tree usage: MEMO is a
176
- // library, so what its own examples happen to set says nothing about
177
- // what an adopter's usability file needs.
160
+ // What an IEC 62366-1 evaluation record reports. These are on the
161
+ // standard's terms, not on in-tree usage: MEMO is a library, so what
162
+ // its own examples happen to set says nothing about what an adopter's
163
+ // usability file needs.
178
164
  attribute participantProfile : String;
179
165
  attribute participantCount : Integer;
180
166
  attribute acceptanceCriteria : String;
@@ -256,13 +242,12 @@ package memo_core_common {
256
242
 
257
243
  // Requirement-family foundations. MemoNeed captures a problem-space
258
244
  // expectation in stakeholder language; MemoRequirement a testable
259
- // solution-space obligation.
260
- // Shared base of the requirement family. It exists so a relation end can
261
- // say "a need or a requirement" with one type name — before it, every end
262
- // that had to accept both was left untyped.
245
+ // solution-space obligation. Shared base of the requirement family. It
246
+ // exists so a relation end can say "a need or a requirement" with one type
247
+ // name. The text of a need or a requirement is its native `doc`, which SysML
248
+ // defines as the requirement's text.
263
249
  abstract requirement def MemoRequirementElement {
264
250
  attribute status : ElementStatusKind;
265
- attribute statement : String;
266
251
  }
267
252
 
268
253
  requirement def MemoNeed :> MemoRequirementElement {
@@ -278,10 +263,9 @@ package memo_core_common {
278
263
  // criteria and context. Domain layers specialize it; the medical-device
279
264
  // intended use (memo_architecture_operational_structure::IntendedUse) is a
280
265
  // MemoMission. It is a `requirement def` because a mission is the top
281
- // obligation everything below it derives from, not a structural thing —
282
- // it was a `part def` under MemoPart. The prose a document renders is
283
- // `doc`, and the one-line register a table cell shows is
284
- // `@MemoIdentity`'s `shortDescription`.
266
+ // obligation everything below it derives from, not a structural thing. The
267
+ // prose a document renders is `doc`, and the one-line register a table cell
268
+ // shows is `@MemoIdentity`'s `shortDescription`.
285
269
  abstract requirement def MemoMission :> MemoRequirementElement {
286
270
  attribute missionKind : String;
287
271
  attribute successCriteria : String;
@@ -37,19 +37,16 @@ package memo_core_dimensions {
37
37
  enum clinicalPerformance;
38
38
  }
39
39
 
40
- // Editorial status of the model element itself (distinct from the
41
- // lifecycle of the thing the element describes).
42
- // This is the ONE status vocabulary in MEMO: every element carries
43
- // `status : ElementStatusKind`, whatever its metaclass. The former
44
- // per-family variants (RequirementStatusKind, LinkStatusKind,
45
- // MemoNeed::needStatus) are gone — three overlapping status dropdowns on
46
- // one element was cognitive load, not precision.
40
+ // Editorial status of the model element itself (distinct from the lifecycle
41
+ // of the thing the element describes). This is the ONE status vocabulary in
42
+ // MEMO: every element carries `status : ElementStatusKind`, whatever its
43
+ // metaclass.
47
44
  //
48
- // The V&V states the requirement variant carried (implemented, verified,
49
- // validated) are deliberately NOT here: they are facts about links, not
50
- // editorial states. An element is implemented when a Realizes link exists,
51
- // verified when VerifiedBy does, validated when Validates does. Duplicating
52
- // them as an attribute lets the attribute disagree with the graph.
45
+ // The V&V states (implemented, verified, validated) are deliberately NOT
46
+ // here: they are facts about links, not editorial states. An element is
47
+ // implemented when a Realizes link exists, verified when VerifiedBy does,
48
+ // validated when Validates does. Duplicating them as an attribute lets the
49
+ // attribute disagree with the graph.
53
50
  enum def ElementStatusKind {
54
51
  enum proposed;
55
52
  enum draft;
@@ -162,21 +162,13 @@ package memo_core_enumerations {
162
162
  }
163
163
  // Direction of a flow across a boundary.
164
164
  //
165
- // Track A2 removed this from PORTS: a port usage says `in` / `out` /
166
- // `inout` natively, which is the language's own spelling and the only one
167
- // a conforming tool reads. The enum survives because three non-port
168
- // constructs still carry a direction and none of them is a port, so none
169
- // of them can use the keyword:
165
+ // A port usage says `in` / `out` / `inout` natively, which is the
166
+ // language's own spelling and the only one a conforming tool reads. This
167
+ // enum is for constructs that are not ports and so cannot use the keyword:
170
168
  //
171
169
  // Interface.direction / .directionality (interface def)
172
170
  // LogicalConnector.direction (connection def)
173
171
  // OperationalInteraction.direction (part def)
174
- //
175
- // Deleting it would have cost those three their direction; the reinvention
176
- // was only ever the port case. `LogicalExchange.direction` was a fourth and
177
- // went when the exchange became a flow between ports (2026-09-25), and
178
- // `ComponentExchange.direction` a fifth when the ports at its ends were held to
179
- // say it (2026-10-25, rule AR-EXCH-002).
180
172
  enum def DirectionKind {
181
173
  enum input;
182
174
  enum output;
@@ -471,7 +463,7 @@ package memo_core_enumerations {
471
463
  enum verificationStage;
472
464
  enum evidence;
473
465
  enum documents;
474
- // The stages of the default method's steps (plan O11), beyond the six above.
466
+ // The stages of the default method's steps, beyond the six above.
475
467
  enum operational;
476
468
  enum functional;
477
469
  enum logical;