@memoarchitect/ontology 0.6.5 → 0.8.22

package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml

@@ -0,0 +1,28 @@
+package memo_viewpoints_ui_layout_ui_layout_viewpoint {
+    private import ScalarValues::*;
+
+    private import memo_viewpoints_definitions::*;
+    private import memo_core_enumerations::*;
+
+    part uiLayoutViewpoint : Viewpoint {
+        attribute :>> id = "VP-UIL";
+        attribute :>> name = "UILayoutViewpoint";
+        attribute :>> title = "UI Layout Viewpoint";
+        attribute :>> 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.";
+        attribute :>> purpose = "Review the interface as the user sees it, with every functional area backed by a design record.";
+        attribute :>> audience = (AudienceKind::usabilityEngineer, AudienceKind::softwareArchitect, AudienceKind::safetyEngineer);
+        attribute :>> stage = WorkflowStageKind::architecture;
+        attribute :>> abstractionLevel = "implementation";
+        attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::documentSection);
+        attribute :>> presentationKind = (PresentationKind::screenLayout);
+        attribute :>> concernKinds = (ConcernKind::usability, ConcernKind::safety);
+        attribute :>> includedLayers = ("implementation");
+        attribute :>> explorerLane = "architecture";
+        attribute :>> explorerOrder = 4;
+        attribute :>> allowedElementKinds = ("ScreenCapture", "UIElement", "UserInterface");
+        attribute :>> allowedRelationshipKinds = ("CapturesScreen", "NavigatesTo", "Composes", "satisfy", "ElementTriggersAction");
+        attribute :>> defaultViewKind = DiagramViewKind::geometry;
+        attribute :>> userExtensible = true;
+    }
+}

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

@@ -0,0 +1,23 @@
+// The first geometry-kind view in MEMO. ADR-1-19 (memo-architect) deferred the
+// geometry renderer because the ontology carried no geometric data and any 2D
+// placement would have been invented layout rather than model content. With
+// memo_architecture_implementation_ui_layout, placement is modelled: a region's
+// RegionBounds are authored facts, drawn over an authored capture. The
+// renderer now has something true to draw.
+package memo_viewpoints_ui_layout_views_screen_layout_view {
+    private import ScalarValues::*;
+
+    private import memo_viewpoints_definitions::*;
+    private import memo_core_enumerations::*;
+
+    view def MemoScreenLayoutView :> MemoDiagramView {
+        attribute :>> viewKind = DiagramViewKind::geometry;
+        attribute :>> 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.";
+        attribute :>> outputKind = (ViewOutputKind::diagram);
+        attribute :>> presentationKind = (PresentationKind::screenLayout);
+        attribute :>> layoutHint = "authored";
+        attribute :>> autoPopulate = true;
+        attribute :>> queryDescription = "One ScreenCapture, the screen UIElement it captures, and the UIElement tree composed beneath that screen.";
+    }
+}

package/src/viewpoints/usability/usability_viewpoint.sysml

@@ -9,7 +9,7 @@ package memo_viewpoints_usability_usability_viewpoint {
         attribute :>> name = "UsabilityViewpoint";
         attribute :>> title = "Usability Viewpoint";
         attribute :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements.";
-        attribute :>> longDescription = "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 :>> 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.";
         attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
         attribute :>> audience = (AudienceKind::usabilityEngineer, AudienceKind::safetyEngineer);
         attribute :>> stage = WorkflowStageKind::requirements;
@@ -18,6 +18,8 @@ package memo_viewpoints_usability_usability_viewpoint {
         attribute :>> presentationKind = (PresentationKind::narrativeSection);
         attribute :>> concernKinds = (ConcernKind::usability, ConcernKind::safety);
         attribute :>> includedLayers = ("context", "requirements");
+        attribute :>> explorerLane = "assurance";
+        attribute :>> explorerOrder = 4;
         attribute :>> allowedElementKinds = ("Actor", "UseContext", "UseError", "Requirement");
         attribute :>> userExtensible = true;
     }

package/src/viewpoints/usability/{usability_engineering_view → views/usability_engineering_view}/usability_engineering_view.sysml

@@ -1,11 +1,11 @@
-package memo_viewpoints_usability_usability_engineering_view {
+package memo_viewpoints_usability_views_usability_engineering_view {
     private import ScalarValues::*;
 
                 private import memo_viewpoints_definitions::*;
                 private import memo_core_enumerations::*;
 
                 view def MemoUsabilityEngineeringView :> MemoDocumentView {
-    attribute :>> viewKind = DocumentViewKind::Usability;
+    attribute :>> viewKind = DocumentViewKind::usability;
     attribute :>> generationRule = "Include actors, use contexts, use errors, and requirements tagged with the usability concern to support the Usability Engineering Report.";
     attribute :>> outputKind = (ViewOutputKind::documentSection);
     attribute :>> presentationKind = (PresentationKind::narrativeSection);

package/src/viewpoints/verification/verification_viewpoint.sysml

@@ -9,7 +9,7 @@ package memo_viewpoints_verification_verification_viewpoint {
         attribute :>> name = "VerificationViewpoint";
         attribute :>> title = "Verification & Validation Viewpoint";
         attribute :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements.";
-        attribute :>> longDescription = "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 :>> 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.";
         attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
         attribute :>> audience = (AudienceKind::verificationEngineer);
         attribute :>> stage = WorkflowStageKind::verificationStage;
@@ -18,7 +18,9 @@ package memo_viewpoints_verification_verification_viewpoint {
         attribute :>> presentationKind = (PresentationKind::traceMatrix);
         attribute :>> concernKinds = (ConcernKind::safety, ConcernKind::regulatory);
         attribute :>> includedLayers = ("requirements", "assurance");
-        attribute :>> allowedElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "Evidence", "TestArtifact");
+        attribute :>> explorerLane = "assurance";
+        attribute :>> explorerOrder = 5;
+        attribute :>> allowedElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "MemoEvidence");
         attribute :>> userExtensible = true;
     }
 }

package/src/viewpoints/verification/{verification_coverage_view → views/verification_coverage_view}/verification_coverage_view.sysml

@@ -1,4 +1,4 @@
-package memo_viewpoints_verification_verification_coverage_view {
+package memo_viewpoints_verification_views_verification_coverage_view {
     private import ScalarValues::*;
 
                 private import memo_viewpoints_definitions::*;
@@ -6,7 +6,7 @@ package memo_viewpoints_verification_verification_coverage_view {
     private import memo_viewpoints_verification_verification_viewpoint::*;
 
                 view verificationCoverageView : MemoDiagramView {
-                    expose memo_viewpoints_verification_verification_coverage_view::*;
+                    expose memo_viewpoints_verification_views_verification_coverage_view::*;
                     attribute depth = 2;
     attribute :>> id = "VIEW-VER-001";
     attribute :>> name = "VerificationCoverageView";
@@ -20,7 +20,7 @@ package memo_viewpoints_verification_verification_coverage_view {
     part :>> selectionQuery {
         attribute :>> id = "QRY-VER-001";
         attribute :>> name = "VerificationCoverageQuery";
-        attribute :>> includeElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "Evidence");
+        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/connected-device/memo.package.yaml

@@ -1,5 +1,11 @@
-name: "{{name}}"
-version: "0.1.0"
-type: device
-extends: "@memoarchitect/methodology-default"
-description: "MEMO connected device model"
+# 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}}'
+version: 0.1.0
+description: MEMO connected device model

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

@@ -0,0 +1,28 @@
+// 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::*;
+
+    part projectMethodBinding : ProjectMethodBinding {
+        attribute :>> id = "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;
+    }
+}

package/templates/connected-device/syside.toml

@@ -1,7 +1,7 @@
 #:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
 
 include = [
-    "src",
+    "model",
     "node_modules/@memoarchitect/ontology/src",
 ]
 

package/templates/default/memo.package.yaml

@@ -1,5 +1,11 @@
-name: "{{name}}"
-version: "0.1.0"
-type: device
-extends: "@memoarchitect/methodology-default"
-description: "MEMO architecture and assurance model"
+# 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}}'
+version: 0.1.0
+description: MEMO architecture and assurance model

package/templates/default/model/catalog/project.sysml

@@ -0,0 +1,28 @@
+// 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 project_catalog {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    private import project_architecture::*;
+    private import project_assurance::*;
+    private import project_artifacts::*;
+
+    part projectMethodBinding : ProjectMethodBinding {
+        attribute :>> id = "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;
+    }
+}

package/templates/default/syside.toml

@@ -1,7 +1,7 @@
 #:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
 
 include = [
-    "src",
+    "model",
     "node_modules/@memoarchitect/ontology/src",
 ]
 

package/templates/infusion-pump/memo.package.yaml

@@ -1,5 +1,11 @@
-name: "{{name}}"
-version: "0.1.0"
-type: device
-extends: "@memoarchitect/methodology-default"
-description: "MEMO infusion pump model"
+# 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}}'
+version: 0.1.0
+description: MEMO infusion pump model

package/templates/infusion-pump/model/catalog/project.sysml

@@ -0,0 +1,28 @@
+// 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 infusion_pump_catalog {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    private import infusion_pump_architecture::*;
+    private import infusion_pump_assurance::*;
+    private import infusion_pump_artifacts::*;
+
+    part projectMethodBinding : ProjectMethodBinding {
+        attribute :>> id = "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;
+    }
+}

package/templates/infusion-pump/syside.toml

@@ -1,7 +1,7 @@
 #:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
 
 include = [
-    "src",
+    "model",
     "node_modules/@memoarchitect/ontology/src",
 ]
 

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

@@ -1,5 +1,11 @@
-name: "{{name}}"
-version: "0.1.0"
-type: device
-extends: "@memoarchitect/methodology-default"
-description: "MEMO monitoring device model"
+# 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}}'
+version: 0.1.0
+description: MEMO monitoring device model

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

@@ -0,0 +1,28 @@
+// 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 monitoring_device_catalog {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    private import monitoring_device_architecture::*;
+    private import monitoring_device_assurance::*;
+    private import monitoring_device_artifacts::*;
+
+    part projectMethodBinding : ProjectMethodBinding {
+        attribute :>> id = "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;
+    }
+}

package/templates/monitoring-device/syside.toml

@@ -1,7 +1,7 @@
 #:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
 
 include = [
-    "src",
+    "model",
     "node_modules/@memoarchitect/ontology/src",
 ]
 

package/templates/samd/memo.package.yaml

@@ -1,5 +1,11 @@
-name: "{{name}}"
-version: "0.1.0"
-type: device
-extends: "@memoarchitect/methodology-default"
-description: "MEMO software as a medical device model"
+# 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}}'
+version: 0.1.0
+description: MEMO software as a medical device model

package/templates/samd/model/catalog/project.sysml

@@ -0,0 +1,28 @@
+// 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 samd_catalog {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    private import samd_architecture::*;
+    private import samd_assurance::*;
+    private import samd_artifacts::*;
+
+    part projectMethodBinding : ProjectMethodBinding {
+        attribute :>> id = "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;
+    }
+}

package/templates/samd/syside.toml

@@ -1,7 +1,7 @@
 #:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
 
 include = [
-    "src",
+    "model",
     "node_modules/@memoarchitect/ontology/src",
 ]
 

package/examples/connected-patient-monitor/model/connected_patient_monitor.sysml

@@ -1,3 +0,0 @@
-package memo_examples_connected_patient_monitor_parent {
-    public import memo_examples_connected_patient_monitor::*;
-}

package/examples/embedded-infusion-pump/model/embedded_infusion_pump.sysml

@@ -1,3 +0,0 @@
-package memo_examples_embedded_infusion_pump_parent {
-    public import memo_examples_embedded_infusion_pump::*;
-}

package/examples/extensions/README.md

@@ -1,16 +0,0 @@
-# Extension examples
-
-An extension is a regular SysML package selected by a MEMO methodology. MEMO
-does not define a separate extension metaclass. `MethodologyDefinition` and
-`ProjectMethodBinding` already accept packages through `includedModule`.
-
-- `template/` is the starting structure for an extension.
-- `clinical/` specializes `OperationalWorkflow` with clinical procedure data.
-
-Extensions specialize or reference base types. They do not redefine
-activities, workflows, architecture elements, relationships, or constraints
-already expressed by the base ontology.
-
-Extension packages remain outside `src/` and outside the `memo::` namespace.
-Projects import an extension package directly and include it in their selected
-methodology.

package/examples/extensions/clinical/memo.package.yaml

@@ -1,9 +0,0 @@
-name: "@memoarchitect/example-extension-clinical"
-version: "0.6.1"
-type: methodology
-extends: "@memoarchitect/methodology-default"
-sysmlDir: "./src"
-description: "Example methodology extension for clinical-procedure vocabulary"
-license: "MIT"
-tags: ["memo", "methodology", "extension", "clinical"]
-usage: ["extension", "clinical-procedures"]

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

@@ -1,14 +0,0 @@
-package memo_extension_clinical_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-
-    part clinicalExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-CLINICAL-001";
-        attribute :>> name = "ClinicalProcedureExtension";
-        attribute :>> version = "0.6.1";
-        attribute :>> domain = "clinical procedures";
-        attribute :>> description = "Adds optional clinical-procedure vocabulary to a MEMO project.";
-        attribute :>> baseMethodName = "MedicalDeviceLightDefault";
-        attribute :>> includedModule = "memo_extension_clinical";
-    }
-}

package/examples/extensions/template/memo.package.yaml

@@ -1,9 +0,0 @@
-name: "{{name}}"
-version: "0.1.0"
-type: methodology
-extends: "@memoarchitect/methodology-default"
-sysmlDir: "./src"
-description: "MEMO methodology extension"
-license: "MIT"
-tags: ["memo", "methodology", "extension"]
-usage: ["extension"]

package/examples/extensions/template/src/extension.sysml

@@ -1,15 +0,0 @@
-// Replace the package name and included module with extension-specific names.
-package memo_extension_template {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-
-    part extensionMethod : MethodologyDefinition {
-        attribute :>> id = "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.";
-        attribute :>> baseMethodName = "MedicalDeviceLightDefault";
-        attribute :>> includedModule = "replace_with_extension_package";
-    }
-}

package/examples/functional-logical-physical/model/functional_logical_physical.sysml

@@ -1,3 +0,0 @@
-package memo_examples_functional_logical_physical_parent {
-    public import memo_examples_functional_logical_physical::*;
-}

package/examples/gpca-pump/memo.config.yaml

@@ -1,9 +0,0 @@
-# GPCA Infusion Pump — submission-grade reference model
-# Based on University of Minnesota CriSys GPCA project
-projectName: gpca-pump
-projectType: device
-
-# Phase H: project pins the GPCA-specific methodology.
-# @memoarchitect/methodology-gpca extends @memoarchitect/methodology-default and subtracts
-# cybersecurity and SOUP for the non-networked prototype variant.
-methodology: "@memoarchitect/methodology-gpca@^0.6.1"

package/examples/gpca-pump/methodology/gpca_scope.sysml

@@ -1,25 +0,0 @@
-package memo_examples_gpca_pump_methodology_gpca_scope {
-    private import ScalarValues::*;
-
-    private import memo_methodology_core::*;
-    private import memo_core_methodology_scope::*;
-    private import memo_core_enumerations::*;
-
-    part gpcaCoverageScope : MethodologyScope {
-        attribute :>> id = "SCOPE-GPCA-001";
-        attribute :>> name = "GPCACoverageScope";
-        attribute :>> scopeName = "coverage";
-
-        attribute :>> includedArchLayer = "context; requirements; functions; logical_structure; interfaces; software_structure; hardware_structure; behavior; risk; assurance; constraints";
-
-        attribute :>> includedStandard = "ISO 14971; IEC 62304; 21 CFR 820; ISO 13485; ISO 14155; IEC 62366; IEC 60601-1";
-
-        attribute :>> includedArtifactKind = "RiskManagementPlan";
-
-        attribute :>> includedViewpointType = "VP-CTX; VP-LOG; VP-RISK";
-
-        attribute :>> excludedKind = "CybersecurityAsset; AttackSurface; Threat; Vulnerability; ThreatScenario; CyberHazard; CyberRisk; CyberMitigation; SecurityRequirement; TrustBoundary; SecurityClaim; SoftwareModule[moduleKind=soup]";
-
-        attribute :>> description = "GPCA prototype methodology — subtracts cybersecurity layer (non-networked device) and SOUP modules (no SOUP in prototype). Derived from default methodology by exclusion.";
-    }
-}

package/examples/ivd-laboratory-system/model/ivd_laboratory_system.sysml

@@ -1,3 +0,0 @@
-package memo_examples_ivd_laboratory_system_parent {
-    public import memo_examples_ivd_laboratory_system::*;
-}

package/examples/manual-surgical-instrument/model/manual_surgical_instrument.sysml

@@ -1,3 +0,0 @@
-package memo_examples_manual_surgical_instrument_parent {
-    public import memo_examples_manual_surgical_instrument::*;
-}

package/examples/multidimensional-layers/model/multidimensional_layers.sysml

@@ -1,4 +0,0 @@
-// Public entry point for this example. Keep model content in catalog/ and views in viewpoints/.
-package memo_examples_multidimensional_layers_parent {
-    public import memo_examples_multidimensional_layers::*;
-}

package/examples/reusable-instrument/model/reusable_instrument.sysml

@@ -1,4 +0,0 @@
-// Public entry point for this example. Keep model content in catalog/ and views in viewpoints/.
-package memo_examples_reusable_instrument_parent {
-    public import memo_examples_reusable_instrument::*;
-}

package/examples/software-only-medical-device/model/software_only_medical_device.sysml

@@ -1,4 +0,0 @@
-// Public entry point for this example. Keep model content in catalog/ and views in viewpoints/.
-package memo_examples_software_only_medical_device_parent {
-    public import memo_examples_software_only_medical_device::*;
-}

package/examples/surgical-closure-workflow/model/surgical_closure_workflow.sysml

@@ -1,4 +0,0 @@
-// Public entry point for this example. Keep model content in catalog/ and views in viewpoints/.
-package memo_examples_surgical_closure_workflow_parent {
-    public import memo_examples_surgical_closure_workflow::*;
-}

package/examples/surgical-robot/model/surgical_robot.sysml

@@ -1,4 +0,0 @@
-// Public entry point for this example. Keep model content in catalog/ and views in viewpoints/.
-package memo_examples_surgical_robot_parent {
-    public import memo_examples_surgical_robot::*;
-}