@memoarchitect/ontology 0.13.2 → 0.15.0

package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml

@@ -97,43 +97,36 @@ package memo_viewpoints_stakeholders_concerns {
 
     part def Availability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-1"; }
-        attribute :>> name = "Availability";
         ref :>> addressesConcerns = (safetyConcern, reliabilityConcern, clinicalConcern);
         attribute :>> measure = "Proportion of scheduled procedure time the function is delivered, and time to recover after a fault.";
     }
     part def Performance :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-2"; }
-        attribute :>> name = "Performance";
         ref :>> addressesConcerns = (performanceConcern, clinicalConcern);
         attribute :>> measure = "Latency and throughput under the arrival pattern the procedure produces.";
     }
     part def Security :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-3"; }
-        attribute :>> name = "Security";
         ref :>> addressesConcerns = (cybersecurityConcern, privacyConcern, safetyConcern);
         attribute :>> measure = "Resistance to a stated threat, and time to detect and recover from a compromise.";
     }
     part def Modifiability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-4"; }
-        attribute :>> name = "Modifiability";
         ref :>> addressesConcerns = (regulatoryConcern);
         attribute :>> measure = "Cost and blast radius of a stated change, including the re-verification it forces.";
     }
     part def Testability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-5"; }
-        attribute :>> name = "Testability";
         ref :>> addressesConcerns = (regulatoryConcern, safetyConcern);
         attribute :>> measure = "Probability that a fault present is revealed by the next test, and the effort to observe it.";
     }
     part def Usability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-6"; }
-        attribute :>> name = "Usability";
         ref :>> addressesConcerns = (usabilityConcern, safetyConcern, clinicalConcern);
         attribute :>> measure = "Task success and use-error rate for the intended user under use conditions (IEC 62366-1).";
     }
     part def Interoperability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-7"; }
-        attribute :>> name = "Interoperability";
         ref :>> addressesConcerns = (interoperabilityConcern, clinicalConcern);
         attribute :>> measure = "Proportion of exchanges with a named partner system that are correctly understood.";
     }
@@ -146,48 +139,37 @@ package memo_viewpoints_stakeholders_concerns {
     abstract part def MemoStakeholder :> MemoPart;
 
     part def SystemArchitect :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-1"; }
-        attribute :>> name = "System Architect";
+        @MemoIdentity { :>> providedId = "STK-1"; :>> label = "System Architect"; }
     }
     part def SoftwareArchitect :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-2"; }
-        attribute :>> name = "Software Architect";
+        @MemoIdentity { :>> providedId = "STK-2"; :>> label = "Software Architect"; }
     }
     part def HardwareEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-3"; }
-        attribute :>> name = "Hardware Engineer";
+        @MemoIdentity { :>> providedId = "STK-3"; :>> label = "Hardware Engineer"; }
     }
     part def SafetyEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-4"; }
-        attribute :>> name = "Safety Engineer";
+        @MemoIdentity { :>> providedId = "STK-4"; :>> label = "Safety Engineer"; }
     }
     part def VerificationEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-5"; }
-        attribute :>> name = "Verification Engineer";
+        @MemoIdentity { :>> providedId = "STK-5"; :>> label = "Verification Engineer"; }
     }
     part def RegulatoryEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-6"; }
-        attribute :>> name = "Regulatory Engineer";
+        @MemoIdentity { :>> providedId = "STK-6"; :>> label = "Regulatory Engineer"; }
     }
     part def ProjectLead :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-7"; }
-        attribute :>> name = "Project Lead";
+        @MemoIdentity { :>> providedId = "STK-7"; :>> label = "Project Lead"; }
     }
     part def SecurityEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-8"; }
-        attribute :>> name = "Security Engineer";
+        @MemoIdentity { :>> providedId = "STK-8"; :>> label = "Security Engineer"; }
     }
     part def PrivacyEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-9"; }
-        attribute :>> name = "Privacy Engineer";
+        @MemoIdentity { :>> providedId = "STK-9"; :>> label = "Privacy Engineer"; }
     }
     part def ClinicalEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-10"; }
-        attribute :>> name = "Clinical Engineer";
+        @MemoIdentity { :>> providedId = "STK-10"; :>> label = "Clinical Engineer"; }
     }
     part def UsabilityEngineer :> MemoStakeholder {
-        @MemoIdentity { :>> providedId = "STK-11"; }
-        attribute :>> name = "Usability Engineer";
+        @MemoIdentity { :>> providedId = "STK-11"; :>> label = "Usability Engineer"; }
     }
 
     // ─── The catalog, as usages ─────────────────────────────────────────

package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml

@@ -8,10 +8,9 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
     private import memo_core_common::*;
     private import memo_core_common::MemoIdentity;
     viewpoint uiLayoutViewpoint : MemoViewpoint {
-        @MemoIdentity { :>> providedId = "VP-UIL"; }
-        attribute :>> name = "UILayoutViewpoint";
+        @MemoIdentity { :>> providedId = "VP-UIL"; :>> label = "UILayoutViewpoint"; }
         @MemoIdentity { :>> shortDescription = "Shows screen captures with the UI element tree laid out over them."; }
-        attribute :>> description = "Frames the user interface spatially: a captured rendering of a screen, and the UIElement tree laid out over it by each element's bounds. Supports IEC 62366-1 use-related design review and the UI description in the software design specification, by making 'which control is this, and what does it do' answerable from the picture. There is one tree, not two — the elements carrying the geometry are the same elements carrying the requirements, functions, use errors, and risk controls.";
+        doc /* Frames the user interface spatially: a captured rendering of a screen, and the UIElement tree laid out over it by each element's bounds. Supports IEC 62366-1 use-related design review and the UI description in the software design specification, by making 'which control is this, and what does it do' answerable from the picture. There is one tree, not two — the elements carrying the geometry are the same elements carrying the requirements, functions, use errors, and risk controls. */
         attribute :>> purpose = "Review the interface as the user sees it, with every functional area backed by a design record.";
         ref :>> stakeholders = (usabilityEngineer, softwareArchitect, safetyEngineer);
         attribute :>> stage = WorkflowStageKind::architecture;

package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml

@@ -15,7 +15,7 @@ package memo_viewpoints_ui_layout_views_screen_layout_view {
     view def MemoScreenLayoutView :> MemoDiagramView {
         attribute :>> viewKind = DiagramViewKind::geometry;
         @MemoIdentity { :>> shortDescription = "Screen capture overlaid with its UI element tree."; }
-        attribute :>> description = "Renders one ScreenCapture as the backdrop and each UIElement composed under the captured screen as a boundary box at its authored bounds, coloured by boundaryColor. Bounds are relative to the parent element, so the renderer accumulates transforms down the Composes tree. Selecting an element isolates it: siblings recede rather than compete. Following an element's NavigatesTo edge swaps the backdrop to the target screen's capture, so the view walks the interface the way the user does.";
+        doc /* Renders one ScreenCapture as the backdrop and each UIElement composed under the captured screen as a boundary box at its authored bounds, coloured by boundaryColor. Bounds are relative to the parent element, so the renderer accumulates transforms down the Composes tree. Selecting an element isolates it: siblings recede rather than compete. Following an element's NavigatesTo edge swaps the backdrop to the target screen's capture, so the view walks the interface the way the user does. */
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::screenLayout);
         attribute :>> layoutHint = "authored";

package/src/viewpoints/usability/usability_viewpoint.sysml

@@ -8,10 +8,9 @@ package memo_viewpoints_usability_usability_viewpoint {
     private import memo_core_common::*;
     private import memo_core_common::MemoIdentity;
     viewpoint usabilityViewpoint : MemoViewpoint {
-        @MemoIdentity { :>> providedId = "VP-USE"; }
-        attribute :>> name = "UsabilityViewpoint";
+        @MemoIdentity { :>> providedId = "VP-USE"; :>> label = "UsabilityViewpoint"; }
         @MemoIdentity { :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements."; }
-        attribute :>> description = "Default viewpoint derived from the context and requirements layers for IEC 62366-1 usability engineering — actors, use contexts, identified use errors, and requirements tagged with the usability concern. Reuses existing context-layer elements (Actor, UseContext, UseError) rather than a separate usability layer.";
+        doc /* Default viewpoint derived from the context and requirements layers for IEC 62366-1 usability engineering — actors, use contexts, identified use errors, and requirements tagged with the usability concern. Reuses existing context-layer elements (Actor, UseContext, UseError) rather than a separate usability layer. */
         attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
         ref :>> stakeholders = (usabilityEngineer, safetyEngineer);
         attribute :>> stage = WorkflowStageKind::requirements;

package/src/viewpoints/verification/verification_viewpoint.sysml

@@ -8,10 +8,9 @@ package memo_viewpoints_verification_verification_viewpoint {
     private import memo_core_common::*;
     private import memo_core_common::MemoIdentity;
     viewpoint verificationViewpoint : MemoViewpoint {
-        @MemoIdentity { :>> providedId = "VP-VER"; }
-        attribute :>> name = "VerificationViewpoint";
+        @MemoIdentity { :>> providedId = "VP-VER"; :>> label = "VerificationViewpoint"; }
         @MemoIdentity { :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements."; }
-        attribute :>> description = "Default viewpoint derived from the requirements and assurance layers for V&V coverage — which requirements are verified/validated, by which case, and what evidence was produced, supporting ISO 13485 §7.3.6/§7.3.7 and IEC 62304 §5.7/§5.8.";
+        doc /* Default viewpoint derived from the requirements and assurance layers for V&V coverage — which requirements are verified/validated, by which case, and what evidence was produced, supporting ISO 13485 §7.3.6/§7.3.7 and IEC 62304 §5.7/§5.8. */
         attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
         ref :>> stakeholders = (verificationEngineer);
         attribute :>> stage = WorkflowStageKind::verificationStage;

package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml

@@ -10,8 +10,7 @@ package memo_viewpoints_verification_views_verification_coverage_view {
                 view verificationCoverageView : MemoDiagramView {
                     expose memo_viewpoints_verification_views_verification_coverage_view::*;
                     attribute depth = 2;
-    @MemoIdentity { :>> providedId = "VIEW-VER-001"; }
-    attribute :>> name = "VerificationCoverageView";
+    @MemoIdentity { :>> providedId = "VIEW-VER-001"; :>> label = "VerificationCoverageView"; }
     @MemoIdentity { :>> shortDescription = "Requirements with their verification cases, validation cases, and evidence."; }
     attribute :>> outputKind = (ViewOutputKind::matrix);
     attribute :>> presentationKind = (PresentationKind::traceMatrix);
@@ -19,8 +18,7 @@ package memo_viewpoints_verification_views_verification_coverage_view {
     attribute :>> autoPopulate = true;
     attribute :>> queryDescription = "Include requirements and their linked verification/validation cases and evidence.";
     part :>> selectionQuery {
-        @MemoIdentity { :>> providedId = "QRY-VER-001"; }
-        attribute :>> name = "VerificationCoverageQuery";
+        @MemoIdentity { :>> providedId = "QRY-VER-001"; :>> label = "VerificationCoverageQuery"; }
         attribute :>> includeElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "MemoEvidence");
         attribute :>> includeLayers = ("requirements", "assurance");
         attribute :>> rationaleText = "Auto-populate V&V coverage from the requirements and assurance layers.";

package/templates/default/memo.package.yaml

@@ -7,7 +7,12 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
-entrypoint: model/catalog/project.sysml
+entrypoint: model/methodology/project.sysml
 include: [model]
 version: 0.1.0
 description: MEMO architecture and assurance model
+# The SysML compiler every MEMO command uses (internal, syside or opensysml), and
+# the packager `memo pack` uses (internal or sysand).
+# Required; MEMO chooses none for a project that does not.
+toolchain:
+  packager: internal

package/templates/default/model/catalog/architecture/system.sysml

@@ -1,7 +1,11 @@
 package project_architecture {
-    private import memo::*;
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
+    private import memo_architecture_logical_structure::*;
 
-    part system : MemoPart {
-        attribute redefines name = "{{name}}";
+    // The product, as a System: the kind a workspace is made from, and a kind the explorer files
+    // under Architecture. (A bare `MemoPart` is the abstract base and files under evidence.)
+    part def ProductSystem specializes System {
+        @MemoIdentity { :>> label = "{{name}}"; }
     }
 }

package/templates/default/model/{catalog → methodology}/project.sysml

@@ -17,10 +17,9 @@ package project_catalog {
 
     private import memo_core_common::*;
     private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
+    part projectMethodBinding : ModelMethodBinding {
+        @MemoIdentity { :>> providedId = "PMB-001"; :>> label = "{{name}}ModelMethodBinding"; }
+        attribute :>> modelName = "{{name}}";
         ref :>> selectedMethodology = mdDefaultDefinition;
         // The project adds no modules of its own yet. Under `explicit` an
         // empty additive list means exactly that — no additions — rather than

package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/views/context_view.viewlayout

@@ -1,47 +0,0 @@
-format: memo.viewlayout/v1
-viewSource: model/catalog/viewpoints/unassigned/views/context_view.sysml
-layouts:
-  diag-sample-sampleContextView:
-    nodes:
-      __context_boundary__:
-        x: 327.4
-        y: 109
-        ports: {}
-      infusionSystem:
-        x: 92
-        y: 74
-        ports: {}
-      biomedTech:
-        x: 40
-        y: 40
-        ports: {}
-      clinician:
-        x: 53.400000000000006
-        y: 146
-        ports: {}
-      patient:
-        x: 53.400000000000006
-        y: 252
-        ports: {}
-      homeContext:
-        x: 440
-        y: 600
-        ports: {}
-      pharmacySystem:
-        x: 855.4
-        y: 199
-        ports: {}
-    edges:
-      rel-8: {}
-      rel-9: {}
-      rel-10: {}
-      rel-11: {}
-      rel-12: {}
-    annotations: {}
-    canvas:
-      autoLayout: false
-      zoom: 0.7154088050314465
-      pan:
-        x: 50.15487421383642
-        y: -9.616352201257882
-      coordinateSpace: context-child-v1

package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/views/interconnection_view.viewlayout

@@ -1,94 +0,0 @@
-format: memo.viewlayout/v1
-viewSource: model/catalog/viewpoints/unassigned/views/interconnection_view.sysml
-layouts:
-  diag-sample-sampleInterconnectionView:
-    nodes:
-      coffeeMachine:
-        x: 301.2
-        y: 0
-        ports:
-          mainsWaterIn:
-            x: -12
-            y: 95
-            side: left
-          beverageOut:
-            x: 536
-            y: 375
-            side: right
-          serviceInterface:
-            x: 536
-            y: 217
-            side: right
-          diagnostics:
-            x: 536
-            y: 247
-            side: right
-        width: 768
-        height: 422
-      waterTank:
-        x: 118.75
-        y: 48
-        ports:
-          tankWaterOut:
-            x: 299.5
-            y: 47
-            side: right
-          tankWaterIn:
-            x: -12
-            y: 47
-            side: left
-      heaterAssembly:
-        x: 78.80000000000001
-        y: 220
-        ports:
-          heaterWaterIn:
-            x: -12
-            y: 47
-            side: left
-          heatedWaterOut:
-            x: 352
-            y: 47
-            side: right
-      brewGroup:
-        x: 134
-        y: 328
-        ports:
-          brewWaterIn:
-            x: -12
-            y: 47
-            side: left
-          brewedCoffeeOut:
-            x: 268
-            y: 47
-            side: right
-      waterSupply:
-        x: 0
-        y: 170
-        ports:
-          supplyWaterOut:
-            x: 198.8
-            y: 47
-            side: right
-      cup:
-        x: 1000
-        y: 320
-        ports:
-          cupBeverageIn:
-            x: -12
-            y: 50
-            side: left
-    edges:
-      rel-66: {}
-      rel-67: {}
-      rel-68: {}
-      rel-69: {}
-      rel-70: {}
-      rel-71: {}
-    annotations: {}
-    canvas:
-      autoLayout: false
-      zoom: 0.83251321227496
-      pan:
-        x: -129.43112026011397
-        y: -3.900376690780462
-      coordinateSpace: context-child-v1

package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/views/operational_behaviour_view.viewlayout

@@ -1,13 +0,0 @@
-format: memo.viewlayout/v1
-viewSource: model/catalog/viewpoints/unassigned/views/operational_behaviour_view.sysml
-layouts:
-  diag-sample-opSetupView:
-    nodes: {}
-    edges: {}
-    canvas:
-      autoLayout: true
-      zoom: 0.3666153460391409
-      pan:
-        x: 359.78478424853927
-        y: 41.19938625300375
-      coordinateSpace: context-child-v1

package/examples/ui-screen-regions/model/catalog/relationships.sysml

@@ -1,8 +0,0 @@
-package memo_examples_ui_screen_regions_relationships {
-    private import memo_artifacts_configuration_management::*;
-    private import memo_assurance_safety_risk::*;
-    private import memo_examples_ui_screen_regions_architecture_implementation_ui::*;
-    private import memo_examples_ui_screen_regions_assurance_requirements::*;
-    connection rel_tracesRisk_uiElement12_reqDrugIdentityDisplay : TracesRisk connect sourceRiskElement ::> elMainScreen::uiElement12 to targetRiskElement ::> reqDrugIdentityDisplay;
-    connection rel_changes_uiElement12_reqDrugIdentityDisplay : Changes connect changeRequest ::> elMainScreen::uiElement12 to changedElement ::> reqDrugIdentityDisplay;
-}

package/extensions/aadl/src/methodology/aadl_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_aadl_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part aadlExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-AADL-001"; }
-        attribute :>> name = "AadlCorrespondenceExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "AADL (SAE AS5506) software runtime";
-        attribute :>> description = "Adds the AADL correspondence profile and the process / thread / virtual-processor runtime families.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_aadl";
-    }
-}

package/extensions/clinical/src/methodology/clinical_methodology.sysml

@@ -1,24 +0,0 @@
-package memo_extension_clinical_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part clinicalExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-CLINICAL-001"; }
-        attribute :>> name = "ClinicalProcedureExtension";
-        attribute :>> version = "0.6.5";
-        attribute :>> domain = "clinical procedures";
-        attribute :>> description = "Adds optional clinical-procedure vocabulary to a MEMO project.";
-        // The base is a typed SysML reference, not a name to keep in sync with
-        // another file. `baseMethodName` was the pre-flip spelling and no
-        // longer resolves.
-        ref :>> baseMethodology = mdDefaultDefinition;
-        // An extension adds its own module to whatever its base selected;
-        // saying so explicitly is required now that an empty list means empty.
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_clinical";
-    }
-}

package/extensions/cloud/src/methodology/cloud_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_cloud_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part cloudExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-CLOUD-001"; }
-        attribute :>> name = "CloudRuntimeExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "networked services and managed data stores";
-        attribute :>> description = "Adds service and data-store runtime families with their contracts, discovery, and retention.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_cloud";
-    }
-}

package/extensions/container/src/methodology/container_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_container_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part containerExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-CONTAINER-001"; }
-        attribute :>> name = "ContainerDeploymentExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "containerized deployment";
-        attribute :>> description = "Adds OCI container images and container runtimes as deployment content.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_container";
-    }
-}

package/extensions/messaging/src/methodology/messaging_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_messaging_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part messagingExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-MESSAGING-001"; }
-        attribute :>> name = "MessagingExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "publish/subscribe messaging";
-        attribute :>> description = "Adds message items, publisher/subscriber ports, topic interfaces, brokers, and delivery semantics.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_messaging";
-    }
-}

package/extensions/ros/src/methodology/ros_methodology.sysml

@@ -1,27 +0,0 @@
-package memo_extension_ros_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    // An extension that builds on other extensions names them all here.
-    // `baseMethodology` is [0..1] — single inheritance, deliberate — but
-    // `includedModule` is [0..*], so this is how a dependency between
-    // extensions is expressed. There is no chaining and no second base.
-    part rosExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-ROS-001"; }
-        attribute :>> name = "Ros2Extension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "ROS 2 robotics middleware";
-        attribute :>> description = "Adds ROS 2 nodes, messages, directional ports, topic/service/action interfaces, QoS, and containerized deployment.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = (
-            "memo_extension_messaging",
-            "memo_extension_container",
-            "memo_extension_ros"
-        );
-    }
-}

package/extensions/template/src/extension.sysml

@@ -1,39 +0,0 @@
-// Skeleton for a new MEMO extension. Copy the directory, rename the packages,
-// and replace the prefix.
-//
-// Two conventions this file follows and every extension must (extensions/README.md):
-//
-//   1. Every definition an extension declares is prefixed with the PascalCase
-//      form of the extension's directory name — `template/` gives `Template`.
-//      Extension names share one flat namespace with the base and with each
-//      other, so the prefix is what keeps two independent extensions from both
-//      declaring `Node`.
-//   2. A relation an extension declares specializes a base relation. It never
-//      roots independently.
-//
-// This package used to bind `baseMethodName = "MedicalDeviceLightDefault"` — a
-// pre-flip spelling that resolves to nothing. It went unnoticed for as long as
-// extensions lived under `examples/`, where the build did not check them; the
-// build checks `extensions/` now, and reported it on the first run.
-package memo_extension_template {
-    private import ScalarValues::*;
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part extensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-METH-001"; }
-        attribute :>> name = "ExtensionMethod";
-        attribute :>> version = "0.1.0";
-        attribute :>> domain = "project extension";
-        attribute :>> description = "Adds a project or domain package to the selected MEMO methodology.";
-        // The base is a typed SysML reference, not a name held in sync by hand.
-        ref :>> baseMethodology = mdDefaultDefinition;
-        // An extension adds its own module to whatever its base selected;
-        // saying so explicitly is required now that an empty list means empty.
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "replace_with_extension_package";
-    }
-}

package/templates/connected-device/memo.package.yaml

@@ -1,13 +0,0 @@
-# Application/distribution descriptor for this MEMO package.
-#
-# Identity and location only. It records what this package is called, what
-# version it is, and where its SysML source sits so a resolver can find it.
-# It does not select model content: the project's native SysML imports and its
-# ProjectMethodBinding decide what is in the model. Semantic fields
-# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
-# removed at the native semantic flip and are now rejected if present.
-name: '{{name}}'
-entrypoint: model/catalog/project.sysml
-include: [model]
-version: 0.1.0
-description: MEMO connected device model

package/templates/connected-device/model/catalog/architecture/system.sysml

@@ -1,5 +0,0 @@
-package connected_device_architecture {
-    private import memo::*;
-
-    part connectedDevice : PhysicalAssembly;
-}

package/templates/connected-device/model/catalog/artifacts/catalog.sysml

@@ -1,5 +0,0 @@
-package connected_device_artifacts {
-    private import memo::*;
-
-    // Add project artifact usages here.
-}

package/templates/connected-device/model/catalog/assurance/requirements.sysml

@@ -1,7 +0,0 @@
-package connected_device_assurance {
-    private import memo::*;
-
-    requirement connectivityRequirement : Requirement {
-        attribute redefines statement = "Define connectivity and cybersecurity boundaries";
-    }
-}

package/templates/connected-device/model/catalog/project.sysml

@@ -1,30 +0,0 @@
-// Project identity and method binding — the project's native entrypoint.
-//
-// The imports below name the reusable packages this project resolves, and the
-// binding names its methodology with a typed SysML reference. Nothing outside
-// SysML selects model content: delete every YAML file beside this one and the
-// model still means exactly what it means now.
-package connected_device_catalog {
-    private import ScalarValues::*;
-
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import connected_device_architecture::*;
-    private import connected_device_assurance::*;
-    private import connected_device_artifacts::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
-        ref :>> selectedMethodology = mdDefaultDefinition;
-        // The project adds no modules of its own yet. Under `explicit` an
-        // empty additive list means exactly that — no additions — rather than
-        // being read as "everything".
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-    }
-}