@memoarchitect/ontology 0.16.5 → 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 (273) 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/memo.identity.yaml +6 -0
  12. package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +16 -30
  13. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/viewpoint.sysml +8 -0
  14. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +16 -0
  15. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/viewpoint.sysml +8 -0
  16. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +16 -0
  17. package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +4 -23
  18. package/examples/gastric-bypass-variants/model/methodology/project.sysml +3 -6
  19. package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
  20. package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
  21. package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
  22. package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
  23. package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
  24. package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
  25. package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
  26. package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
  27. package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
  28. package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
  29. package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
  30. package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
  31. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +50 -60
  32. package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
  33. package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
  34. package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
  35. package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
  36. package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
  37. package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
  38. package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
  39. package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
  40. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
  41. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
  42. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
  43. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
  44. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
  45. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
  46. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
  47. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
  48. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
  49. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
  50. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
  51. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
  52. package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
  53. package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
  54. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
  55. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
  56. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
  57. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
  58. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
  59. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
  60. package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
  61. package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
  62. package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
  63. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
  64. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
  65. package/examples/gpca-pump/model/methodology/project.sysml +1 -4
  66. package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
  67. package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
  68. package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
  69. package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
  70. package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
  71. package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
  72. package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
  73. package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
  74. package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
  75. package/examples/nested-architecture-dsm/README.md +5 -5
  76. package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
  77. package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
  78. package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
  79. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
  80. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
  81. package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
  82. package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
  83. package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
  84. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +21 -30
  85. package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
  86. package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
  87. package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
  88. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +3 -8
  89. package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
  90. package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
  91. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +3 -6
  92. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +6 -11
  93. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +6 -11
  94. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +6 -11
  95. package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
  96. package/examples/robot-platform/model/platform.sysml +1 -3
  97. package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
  98. package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
  99. package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
  100. package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
  101. package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
  102. package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
  103. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +34 -45
  104. package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
  105. package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
  106. package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
  107. package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
  108. package/examples/surgical-robot/model/methodology/project.sysml +2 -6
  109. package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
  110. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +13 -21
  111. package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
  112. package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
  113. package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
  114. package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
  115. package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
  116. package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
  117. package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
  118. package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
  119. package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
  120. package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
  121. package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
  122. package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
  123. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +14 -21
  124. package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
  125. package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
  126. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +45 -65
  127. package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
  128. package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
  129. package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
  130. package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
  131. package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
  132. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
  133. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
  134. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
  135. package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
  136. package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
  137. package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
  138. package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
  139. package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
  140. package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
  141. package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
  142. package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
  143. package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
  144. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
  145. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
  146. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
  147. package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
  148. package/extensions/README.md +2 -2
  149. package/extensions/aadl/memo.package.yaml +1 -1
  150. package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
  151. package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
  152. package/extensions/anatomy/memo.package.yaml +1 -1
  153. package/extensions/clinical/memo.package.yaml +1 -1
  154. package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +12 -1
  155. package/extensions/cloud/memo.package.yaml +1 -1
  156. package/extensions/cloud/src/cloud_extension.sysml +2 -4
  157. package/extensions/container/memo.package.yaml +1 -1
  158. package/extensions/container/src/container_extension.sysml +2 -5
  159. package/extensions/messaging/memo.package.yaml +1 -1
  160. package/extensions/messaging/src/messaging_extension.sysml +4 -5
  161. package/extensions/ros/memo.package.yaml +1 -1
  162. package/extensions/ros/src/ros_extension.sysml +5 -10
  163. package/methodologies/default/memo.package.yaml +1 -1
  164. package/methodologies/gpca/memo.package.yaml +1 -1
  165. package/ontology/memo.package.yaml +1 -1
  166. package/package.json +1 -1
  167. package/profile/memo.package.yaml +1 -1
  168. package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
  169. package/src/architecture/functional/functions/memo_functions.sysml +31 -44
  170. package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
  171. package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
  172. package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
  173. package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
  174. package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
  175. package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
  176. package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
  177. package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
  178. package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
  179. package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
  180. package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
  181. package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
  182. package/src/architecture/operational/activities/memo_activities.sysml +2 -2
  183. package/src/architecture/operational/context/actors/memo_actors.sysml +8 -7
  184. package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
  185. package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
  186. package/src/architecture/operational/rollups/memo_rollups.sysml +24 -8
  187. package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
  188. package/src/architecture/operational/structure/memo_operational.sysml +3 -5
  189. package/src/architecture/operational/use_cases/memo_use_cases.sysml +32 -26
  190. package/src/architecture/operational/workflows/memo_workflows.sysml +13 -60
  191. package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
  192. package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
  193. package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
  194. package/src/artifacts/standards/cfr_21_820.sysml +0 -1
  195. package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
  196. package/src/artifacts/standards/iec_60601_1.sysml +0 -1
  197. package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
  198. package/src/artifacts/standards/iec_60812.sysml +0 -1
  199. package/src/artifacts/standards/iec_62304.sysml +0 -1
  200. package/src/artifacts/standards/iec_62366_1.sysml +0 -1
  201. package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
  202. package/src/artifacts/standards/iso_13485.sysml +0 -1
  203. package/src/artifacts/standards/iso_14971.sysml +0 -1
  204. package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
  205. package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
  206. package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
  207. package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
  208. package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
  209. package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
  210. package/src/artifacts/templates/dhf/iec-62366/use-spec.md +1 -1
  211. package/src/assurance/cybersecurity/memo_cybersecurity.sysml +1 -0
  212. package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
  213. package/src/assurance/requirements/memo_requirements.sysml +6 -11
  214. package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
  215. package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
  216. package/src/assurance/safety_risk/memo_risk.sysml +19 -22
  217. package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
  218. package/src/core/annotations/memo_annotations.sysml +2 -2
  219. package/src/core/common/memo_common.sysml +40 -56
  220. package/src/core/dimensions/dimensions.sysml +9 -12
  221. package/src/core/enumerations/memo_enumerations.sysml +4 -12
  222. package/src/core/methodology_scope/methodology_scope.sysml +3 -6
  223. package/src/core/relationships/memo_relationships.sysml +54 -85
  224. package/src/core/relationships/memo_workspace_membership.sysml +0 -2
  225. package/src/memo_namespaces.sysml +9 -0
  226. package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
  227. package/src/methodology/core/memo_core.sysml +12 -12
  228. package/src/methodology/profiles/memo_profiles.sysml +9 -10
  229. package/src/methodology/workflow/memo_workflow.sysml +7 -8
  230. package/src/rules/closure/closure_rules.sysml +7 -9
  231. package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
  232. package/src/rules/ontology/ontology_invariants.sysml +97 -105
  233. package/src/rules/quantitative/quantitative_rules.sysml +0 -1
  234. package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
  235. package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
  236. package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
  237. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +24 -0
  238. package/src/viewpoints/context/context_viewpoint.sysml +0 -1
  239. package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
  240. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
  241. package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
  242. package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
  243. package/src/viewpoints/definitions/memo_view_layout.sysml +27 -3
  244. package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
  245. package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
  246. package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
  247. package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
  248. package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
  249. package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
  250. package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
  251. package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
  252. package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
  253. package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
  254. package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
  255. package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
  256. package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
  257. package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
  258. package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
  259. package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
  260. package/src/viewpoints/software/software_viewpoint.sysml +0 -1
  261. package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
  262. package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
  263. package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
  264. package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
  265. package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
  266. package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
  267. package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
  268. package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
  269. package/stage1/opensysml-ddad9e2794141c08532910cf.json.gz +0 -0
  270. package/stage1/syside-8176a62528c701f2f2e0fc7f.ids.gz +0 -0
  271. package/stage1/syside-8176a62528c701f2f2e0fc7f.json.gz +0 -0
  272. package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
  273. package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
@@ -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;
@@ -1,11 +1,8 @@
1
1
  // Methodology scope helpers.
2
2
  //
3
- // `MethodologyScope` and `MethodologyLayerSet` were removed when the semantic
4
- // contract flipped. A methodology's effective selection is declared on
5
- // `MethodologyDefinition` itself — `scopeMode` plus the `included*` lists — so
6
- // that one element answers "what is in scope". A second scope part sitting
7
- // beside the methodology meant two authorities for the same question, and the
8
- // tools read the one the methodology definition did not declare.
3
+ // A methodology's effective selection is declared on `MethodologyDefinition`
4
+ // itself — `scopeMode` plus the `included*` lists — so that one element answers
5
+ // "what is in scope".
9
6
  package memo_core_methodology_scope {
10
7
  private import ScalarValues::*;
11
8
 
@@ -21,31 +21,24 @@ package memo_core_relationships {
21
21
  //
22
22
  // A relation is a MEMO element like any other, so it carries the same
23
23
  // identification core as the part/action/item/requirement bases in
24
- // memo_core_common — with four exceptions, R10-S5 (2026-08-13). `name`,
25
- // `description`, `rationale` and `status` were declared here too, and a
26
- // tree measurement found them dead weight: across every connection usage
27
- // in src/ and examples/ (876 of them, 77 with a body at all), exactly one
28
- // ever set `rationale` and none ever set `name`, `description` or
29
- // `status`. The former `linkStatus` (planned/active/verified/obsolete) is
30
- // already gone for the same reason: a link being "verified" was never an
31
- // editorial state.
24
+ // memo_core_common — with four exceptions: `name`, `description`,
25
+ // `rationale` and `status` are native.
32
26
  //
33
- // The replacement is native, not a MEMO-authored substitute:
34
- // - `name` → the connection usage's own declared name
35
- // (`connection linkFoo : Bar …`), which every usage already has.
36
- // - `description` → `doc /* … */` on the usage.
37
- // - `rationale` → standard `Rationale` metadata: `@Rationale { :>> text
38
- // = "…"; }` (ModelingMetadata.sysml:95). `text` is exported into
39
- // `rel.attributes.rationale` by the builder, same key as before.
40
- // - `status` → standard `StatusInfo` metadata: `@StatusInfo { :>>
41
- // status = StatusKind::…; }` (ModelingMetadata.sysml:60). StatusKind
42
- // (open/tbd/tbr/tbc/done/closed) is NOT ElementStatusKind
43
- // (proposed/draft/inReview/approved/released/deprecated/retired) — the
44
- // mapping between them, and why no MEMO-side conversion code exists, is
45
- // recorded in docs/reference/naming-and-native-constructs.md. Exported
46
- // into `rel.attributes.status`.
47
- // Both metadata defs live in the standard `ModelingMetadata` package;
48
- // `private import ModelingMetadata::*;` wherever they are applied.
27
+ // Their native forms: - `name` → the connection usage's own declared
28
+ // name (`connection linkFoo : Bar …`), which every usage already has. -
29
+ // `description` → `doc /* … */` on the usage. - `rationale` → standard
30
+ // `Rationale` metadata: `@Rationale { :>> text = "…"; }`
31
+ // (ModelingMetadata.sysml:95). `text` is exported into
32
+ // `rel.attributes.rationale` by the builder. - `status` → standard
33
+ // `StatusInfo` metadata: `@StatusInfo { :>> status = StatusKind::…; }`
34
+ // (ModelingMetadata.sysml:60). StatusKind (open/tbd/tbr/tbc/done/closed) is
35
+ // NOT ElementStatusKind
36
+ // (proposed/draft/inReview/approved/released/deprecated/retired) — the
37
+ // mapping between them, and why no MEMO-side conversion code exists, is
38
+ // recorded in docs/reference/naming-and-native-constructs.md. Exported into
39
+ // `rel.attributes.status`. Both metadata defs live in the standard
40
+ // `ModelingMetadata` package; `private import ModelingMetadata::*;`
41
+ // wherever they are applied.
49
42
  //
50
43
  // isReflexive/isUnique are structural properties of the relation itself,
51
44
  // declared here so authoring and validation read them from the ontology
@@ -70,6 +63,11 @@ package memo_core_relationships {
70
63
  * satisfaction links are not. Unset is read as false. Interface and flow usages are connectors by
71
64
  * their language construct and need no value. */
72
65
  attribute isConnector : Boolean;
66
+ doc /* True when this relation records where an element's obligation comes from or how it is answered:
67
+ * a link to a requirement, a risk, a verification, a standard or a controlled document. Authoring
68
+ * surfaces offer these as traces, and a coverage report reads them as traceability. Structure,
69
+ * allocation, deployment and context links are not. Unset is read as false. */
70
+ attribute isTrace : Boolean;
73
71
  }
74
72
 
75
73
  // ─── Typed dependencies ─────────────────────────────────────────────
@@ -89,47 +87,31 @@ package memo_core_relationships {
89
87
  // (see the note above on metaclass-neutral ends).
90
88
  abstract metadata def MemoTypedDependency;
91
89
 
92
- // ─── Metaclass-neutral ends (Track A0) ──────────────────────────────
90
+ // ─── Metaclass-neutral ends ──────────────────────────────
93
91
  //
94
92
  // An end is left UNTYPED (`:>> source` / `:>> target`) wherever its
95
93
  // legitimate endpoints do not share a MEMO base, and a rule in
96
- // memo_rules_ontology states the constraint the type used to state.
94
+ // memo_rules_ontology states the constraint.
97
95
  //
98
96
  // The reason is structural, not stylistic. KerML will not let a port or a
99
97
  // behaviour specialize a part-based type, so a `MemoPart`-typed end forces
100
- // everything it accepts to be a part. That is what made PhysicalPort and
101
- // SoftwarePort part defs (so they could terminate exchanges), what made
102
- // SystemFunction a part def with its behaviour stapled on through a
103
- // separate action def, and what makes `allocate <function> to <actor>` —
104
- // ARCADIA's own System Analysis mechanism — illegal, since Actor is a
105
- // MemoPart but not a narrower part subtype.
98
+ // everything it accepts to be a part. It would also make `allocate
99
+ // <function> to <actor>` — ARCADIA's own System Analysis mechanism —
100
+ // illegal, since Actor is a MemoPart but not a narrower part subtype.
106
101
  //
107
- // Several of the relaxed ends were ALREADY being violated by real content
108
- // before they were relaxed: `composes` links parts to OperativeAction
109
- // (an action def) and to SoftwarePort/PhysicalPort;
110
- // `precedes` links OperativeAction to OperativeAction; `allocatedTo`
111
- // has ActionUsage sources; `bindsToInterface` targets an `interface def`,
112
- // which an InterfaceElement-typed end cannot hold. The types were not
113
- // buying the strictness they appeared to buy.
114
- //
115
- // What is NOT relaxed stays typed on purpose: `verificationCase` and
102
+ // Ends that are typed are typed on purpose: `verificationCase` and
116
103
  // `validationCase` are verification defs, `performed` and `enabled` are
117
104
  // MemoActions, `targetRequirement` is a MemoRequirementElement. Those ends
118
105
  // name one metaclass and mean it.
119
106
  //
120
- // The strictness did not evaporate — see CR-ONT-060..CR-ONT-071 in
121
- // src/rules/ontology/ontology_invariants.sysml. Relaxing the ends without
122
- // those rules would have been a silent loss of every constraint the ends
123
- // were carrying.
124
- //
125
- // The general relation that can join any two model elements, whatever
126
- // their metaclass. MemoLink leaves both ends untyped and adds no
127
- // domain-specific semantics, which is what makes it universal.
107
+ // The constraints on untyped ends are rules: see CR-ONT-060..CR-ONT-071 in
108
+ // src/rules/ontology/ontology_invariants.sysml.
128
109
  //
129
- // It is deliberately the weakest relation in the ontology. Reach for it
130
- // only when no specific relation carries the meaning, and say why in the
131
- // inherited `rationale` — an untyped link with no stated reason is an
132
- // audit gap, not a model fact.
110
+ // There is no general MEMO relation joining any two elements whatever
111
+ // their metaclass: SysML's native `dependency` already is one. Use
112
+ // `dependency` when no specific relation carries the meaning, and say why
113
+ // in a comment — an untyped link with no stated reason is an audit gap,
114
+ // not a model fact.
133
115
 
134
116
  // An item belongs to the scope of one system or system of systems: a need,
135
117
  // requirement, risk or verification case that describes, constrains or
@@ -152,6 +134,7 @@ package memo_core_relationships {
152
134
  }
153
135
 
154
136
  connection def DerivesFrom :> MemoRelationship {
137
+ attribute :>> isTrace = true;
155
138
  // Drivers span metaclasses — a need is a requirement def, a hazard an
156
139
  // item, a threat an item — so the source end stays untyped. The target
157
140
  // is now typed: since Requirement re-rooted onto MemoRequirement, one
@@ -165,17 +148,12 @@ package memo_core_relationships {
165
148
  :> annotatedElement : SysML::ConnectionUsage;
166
149
  :>> baseType = derivesFromLinks meta SysML::Usage;
167
150
  }
168
- // `Realizes` (realizing/concrete element → realized/abstract element) is
169
- // native `#refinement dependency` (R10-S6): write
170
- // `#refinement dependency <realizing> to <realized>;` instead. It used to
171
- // unify RealizesInterface, RealizesComponentExchange,
172
- // RealizedByArchitecture, RealizesScenario, ModuleRealizesLogical,
173
- // ComponentRealizesModule, PhysicalModuleRealizesLogical,
174
- // Implements{Component,Procedure}, UIRealizesFunctional,
175
- // FunctionalRealizesOper{ative,ational} and ScenarioRealizesUseCase; the
176
- // native form keeps that reach, since `#refinement` places no metaclass
151
+ // A realization (realizing/concrete element → realized/abstract element) is
152
+ // native `#refinement dependency`: write `#refinement dependency
153
+ // <realizing> to <realized>;`. `#refinement` places no metaclass
177
154
  // restriction on either end.
178
155
  connection def ProducesEvidence :> MemoRelationship {
156
+ attribute :>> isTrace = true;
179
157
  end producer : MemoVerificationCase :>> source;
180
158
  end producedEvidence : MemoEvidence :>> target;
181
159
  }
@@ -185,12 +163,10 @@ package memo_core_relationships {
185
163
  :> annotatedElement : SysML::ConnectionUsage;
186
164
  :>> baseType = producesEvidenceLinks meta SysML::Usage;
187
165
  }
188
- // `Precedes` is native `succession` (`first a then b;`), R10-S6.
189
- // `sameStepRequired`/`precedenceRationale` had zero usages anywhere in
190
- // the tree (same free-deletion shape R10-S5 found for `rationale`), so
191
- // there was no content to carry forward.
166
+ // Precedence is native `succession` (`first a then b;`).
192
167
 
193
168
  connection def DerivesCyberRequirement :> MemoRelationship {
169
+ attribute :>> isTrace = true;
194
170
  end sourceThreatOrRisk : RequirementDriver :>> source;
195
171
  end targetRequirement : MemoRequirementElement :>> target;
196
172
  }
@@ -213,6 +189,7 @@ package memo_core_relationships {
213
189
  }
214
190
 
215
191
  connection def Validates :> MemoRelationship {
192
+ attribute :>> isTrace = true;
216
193
  // Validation targets include use cases and other behavioural elements,
217
194
  // so the target remains untyped across SysML metaclass families.
218
195
  end validationTarget :>> source;
@@ -225,16 +202,12 @@ package memo_core_relationships {
225
202
  :>> baseType = validatesLinks meta SysML::Usage;
226
203
  }
227
204
 
228
- // Enables unifies the former EnablesWorkflow / EnablesActivity synonyms
229
- // (an enabling system/function enables a workflow/activity).
230
- // `Enables` is native `dependency` (2026-08-18): write
231
- // `dependency from <enabling> to <enabled>;`. Same call as `Supports`,
232
- // which was deleted as a duplicate of both `dependency` and `Enables`.
205
+ // An enabling system or function enabling a workflow or activity is a
206
+ // native `dependency`: write `dependency from <enabling> to <enabled>;`.
233
207
 
234
- // A processing node hosted by an assembly is allocated to it. The end
235
- // NAMES were already right; two of the three usages wrote them in reverse
236
- // order, and the builder binds by position, so those two edges pointed the
237
- // wrong way. See the reversed-end-name lint in memo-tools.
208
+ // A processing node hosted by an assembly is allocated to it. The builder
209
+ // binds ends by position, so write them in this order. See the
210
+ // reversed-end-name lint in memo-tools.
238
211
  allocation def HostedBy :> MemoRelationship, Allocations::Allocation {
239
212
  end processingNode : MemoPart :>> source;
240
213
  end hostAssembly : MemoPart :>> target;
@@ -249,17 +222,13 @@ package memo_core_relationships {
249
222
 
250
223
 
251
224
 
252
- // `Composes` is deleted (R10-S7). Containment is NESTING — the child is
253
- // declared inside the parent — which is how SysML v2 models composition:
254
- // composite feature ownership, not a link. The relation specialized
255
- // `Connections::BinaryConnection`, "a link between two things WITHIN some
256
- // containing structure", so it was the wrong category for the containment
257
- // itself, and the corpus has no composition connection to specialize.
225
+ // Containment is NESTING — the child is declared inside the parent — which
226
+ // is how SysML v2 models composition: composite feature ownership, not a
227
+ // link.
258
228
  //
259
- // Nothing is lost: the builder synthesizes a `composes` edge from every
260
- // nested part and item, so rules, the DSM and traceability read exactly the
261
- // graph they read before. The edge type is registered natively in
262
- // memo-tools' relationship registry.
229
+ // The builder synthesizes a `composes` edge from every nested part and
230
+ // item, so rules, the DSM and traceability read containment as a graph. The
231
+ // edge type is registered natively in memo-tools' relationship registry.
263
232
 
264
233
 
265
234
  connection def BindsToInterface :> MemoRelationship {
@@ -76,8 +76,6 @@ package memo_core_relationships_workspace_membership {
76
76
  part membershipMotivates : WorkspaceMembershipEntry { attribute :>> relation = "motivates"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
77
77
  // A workflow follows the use case it realizes.
78
78
  part membershipRealizesUseCase : WorkspaceMembershipEntry { attribute :>> relation = "realizesUseCase"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
79
- // Neither: a transformation joins two actions.
80
- part membershipTransforms : WorkspaceMembershipEntry { attribute :>> relation = "transforms"; attribute :>> direction = WorkspaceMembershipKind::neither; }
81
79
  // A module follows the deployment unit it is built into.
82
80
  part membershipBuildsInto : WorkspaceMembershipEntry { attribute :>> relation = "buildsInto"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
83
81
  // The hardware or software follows the logical component it realizes: the logical component is
@@ -7,6 +7,9 @@ package memo {
7
7
  public import memo_core_common::*;
8
8
  public import memo_core_relationships::*;
9
9
  public import memo_core_annotations::*;
10
+ public import memo_core_stdlib_quantities::*;
11
+ public import memo_core_stdlib_money::*;
12
+ public import memo_core_stdlib_analysis::*;
10
13
 
11
14
  public import memo_architecture_operational_context_actors::*;
12
15
  public import memo_architecture_operational_context_stakeholders::*;
@@ -69,6 +72,7 @@ package memo {
69
72
  public import memo_viewpoints_cybersecurity_views_cybersecurity_assessment_view::*;
70
73
  public import memo_viewpoints_clinical_clinical_viewpoint::*;
71
74
  public import memo_viewpoints_clinical_views_clinical_evidence_view::*;
75
+ public import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
72
76
  public import memo_viewpoints_usability_usability_viewpoint::*;
73
77
  public import memo_viewpoints_usability_views_usability_engineering_view::*;
74
78
  public import memo_viewpoints_ui_layout_ui_layout_viewpoint::*;
@@ -304,6 +308,7 @@ package memo_namespace_rules {
304
308
  package memo_namespace_viewpoints {
305
309
  alias catalog for memo_namespace_viewpoints_catalog;
306
310
  alias clinical for memo_namespace_viewpoints_clinical;
311
+ alias clinical_workflow for memo_namespace_viewpoints_clinical_workflow;
307
312
  alias context for memo_namespace_viewpoints_context;
308
313
  alias cybersecurity for memo_namespace_viewpoints_cybersecurity;
309
314
  alias definitions for memo_namespace_viewpoints_definitions;
@@ -532,6 +537,10 @@ package memo_namespace_viewpoints_clinical {
532
537
  package views { alias clinical_evidence_view for memo_namespace_viewpoints_clinical_clinical_evidence_view; }
533
538
  }
534
539
 
540
+ package memo_namespace_viewpoints_clinical_workflow {
541
+ public import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
542
+ }
543
+
535
544
  package memo_namespace_viewpoints_context {
536
545
  public import memo_viewpoints_context_context_viewpoint::*;
537
546
  package views { alias system_context_view for memo_namespace_viewpoints_context_system_context_view; }
@@ -4,7 +4,6 @@ package memo_methodology_archetypes {
4
4
  private import memo_methodology_core::*;
5
5
 
6
6
  private import memo_core_common::*;
7
- private import memo_core_common::MemoIdentity;
8
7
  part minimal : Archetype {
9
8
  @MemoIdentity { :>> providedId = "ARCH-MINIMAL"; }
10
9
  attribute :>> label = "Minimal";
@@ -81,21 +81,21 @@ package memo_methodology_core {
81
81
  //
82
82
  // The standards, artifact kinds and viewpoints a methodology selects
83
83
  // are TYPED: a standard is a RegulatoryStandard, an artifact kind is an
84
- // ArtifactKind literal, a viewpoint is a MemoViewpoint. They were
85
- // strings ("ISO 14155", "RiskManagementPlan", "VP-CTX"), and three
86
- // standards and an artifact kind in the GPCA methodology named nothing
87
- // the ontology declares: a string that matches nothing selects nothing,
88
- // and nothing said so. Now the compiler does.
84
+ // ArtifactKind literal, a viewpoint is a MemoViewpoint. A string that
85
+ // matches nothing selects nothing and nothing says so; a typed
86
+ // reference the compiler checks.
89
87
  ref includedStandard : RegulatoryStandard[0..*];
90
88
  attribute includedArtifactKind : ArtifactKind[0..*];
91
89
  ref includedViewpoint : MemoViewpoint[0..*];
92
90
  part rulePolicy : RulePolicy[0..*];
93
91
  }
94
92
 
95
- // Which viewpoints a role works with (plan O12). A viewpoint names the stakeholders it is written for,
96
- // and that is what a role sees by default; a methodology may say otherwise for a role, and then THIS is
97
- // what the role sees, an override and not an addition. A method that names a base starts from its
98
- // role views, and a later one for the same stakeholder replaces the earlier.
93
+ // Which viewpoints a role works with. A viewpoint names the stakeholders it
94
+ // is written for, and that is what a role sees by default; a methodology
95
+ // may say otherwise for a role, and then THIS is what the role sees, an
96
+ // override and not an addition. A method that names a base starts from its
97
+ // role views, and a later one for the same stakeholder replaces the
98
+ // earlier.
99
99
  //
100
100
  // part rvSafety : RoleView { ref :>> forStakeholder = safetyEngineer; ref :>> shownViewpoint = (vpRiskChain, vpEvidenceTraceability); }
101
101
  part def RoleView :> MemoPart {
@@ -131,9 +131,9 @@ package memo_methodology_core {
131
131
  part rulePolicy : RulePolicy[0..*];
132
132
  }
133
133
 
134
- // DEPRECATED in 0.14.0, deleted in 0.15.0: the former spelling of
135
- // ModelMethodBinding, kept so a model written with it still binds. MEMO
136
- // reads `projectName` when `modelName` is absent and warns on either.
134
+ // The deprecated spelling of ModelMethodBinding, kept so a model written
135
+ // with it still binds. MEMO reads `projectName` when `modelName` is absent
136
+ // and warns on either.
137
137
  part def ProjectMethodBinding :> ModelMethodBinding {
138
138
  attribute projectName : String;
139
139
  }