@memoarchitect/ontology 0.6.4 → 0.7.0

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/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::*;
-}

package/examples/temperature-alarm/model/temperature_alarm.sysml

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

package/ontology/memo.rendering.yaml

@@ -1,84 +0,0 @@
-# @memoarchitect/ontology rendering configuration
-# Architecture layer colors — v12 Visual Map palette
-
-layers:
-  - id: operational
-    label: Operational
-    color: "#C0392B"
-
-  - id: behavioral
-    label: Behavioral
-    color: "#E74C3C"
-
-  - id: functional
-    label: Functional
-    color: "#E67E22"
-
-  - id: logical
-    label: Logical
-    color: "#7B68EE"
-
-  - id: software
-    label: Software
-    color: "#F39C12"
-
-  - id: software-extension
-    label: Software Extension (ROS)
-    color: "#D4AC0D"
-
-  - id: hardware
-    label: Hardware
-    color: "#95A5A6"
-
-  - id: safety
-    label: Safety
-    color: "#E74C3C"
-
-  - id: security
-    label: Security
-    color: "#2C3E50"
-
-  - id: privacy
-    label: Privacy
-    color: "#8E44AD"
-
-  - id: verification
-    label: Verification
-    color: "#2ECC71"
-
-# Model Explorer taxonomy. This is ontology metadata: Architect receives these
-# values from memo-tools and does not infer MEMO's V-model from source paths.
-explorer:
-  classifications:
-    - { source: activities, domain: architecture, group: operational }
-    - { source: context, domain: architecture, group: operational }
-    # Context has concrete namespaces such as actors and use_context; retain
-    # them when the Explorer receives ontology-derived kinds directly.
-    - { source: actors, domain: architecture, group: operational }
-    - { source: use_context, domain: architecture, group: operational }
-    - { source: workflows, domain: architecture, group: operational }
-    - { source: scenarios, domain: architecture, group: operational }
-    - { source: use_cases, domain: architecture, group: operational }
-    - { source: interaction, domain: architecture, group: operational }
-    - { source: operational, domain: architecture, group: operational }
-    - { source: functions, domain: architecture, group: functional }
-    - { source: behavior, domain: architecture, group: functional }
-    - { source: constraints, domain: architecture, group: functional }
-    - { source: logical_structure, domain: architecture, group: logical }
-    - { source: interfaces, domain: architecture, group: logical }
-    - { source: hardware_structure, domain: architecture, group: implementation }
-    # HardwareAssembly is declared in architecture/implementation/hardware.
-    - { source: implementation, domain: architecture, group: implementation }
-    - { source: software_structure, domain: architecture, group: implementation }
-    - { source: software_runtime, domain: architecture, group: implementation }
-    - { source: physical, domain: architecture, group: realization }
-    - { source: deployment, domain: architecture, group: realization }
-    - { source: needs, domain: assurance, group: requirements }
-    - { source: requirements, domain: assurance, group: requirements }
-    - { source: safety, domain: assurance, group: safety-risk }
-    - { source: safety_analysis, domain: assurance, group: safety-risk }
-    - { source: cybersecurity, domain: assurance, group: cybersecurity }
-    - { source: human_factors, domain: assurance, group: human-factors }
-    - { source: verification, domain: assurance, group: verification-validation }
-    - { source: core, domain: assurance, group: evidence }
-    - { source: methodology, domain: methodology, group: methodology }

package/src/compliance/artifacts/memo_artifacts.sysml

@@ -1,12 +0,0 @@
-package memo_compliance_artifacts {
-    private import ScalarValues::*;
-
-    private import memo_core_common::*;
-    private import memo_core_enumerations::*;
-    item def ControlledArtifact specializes MemoPart {
-        attribute version : String;
-        attribute artifactKind : ArtifactKind;
-        attribute owner : String;
-        attribute approvalStatus : String;
-    }
-}

package/src/compliance/document_views/memo_document_views.sysml

@@ -1,7 +0,0 @@
-package memo_compliance_document_views {
-    private import ScalarValues::*;
-
-    public import memo_viewpoints_definitions::MemoDocumentView;
-    public import memo_viewpoints_cybersecurity_threat_model_view::MemoCybersecurityThreatModelView;
-    public import memo_viewpoints_cybersecurity_cybersecurity_assessment_view::MemoCybersecurityAssessmentView;
-}

package/src/compliance/iso14971/risk_management_file.sysml

@@ -1,16 +0,0 @@
-package memo_compliance_iso14971 {
-    private import ScalarValues::*;
-
-    private import memo_core_common::*;
-    private import memo_core_enumerations::*;
-
-    doc /* ISO 14971 Risk Management File — the top-level deliverable
-           that aggregates all risk management artifacts required by
-           ISO 14971:2019 clause 4.5. */
-    part def RiskManagementFile specializes MemoPart {
-        attribute standardReference : String;
-        attribute clause : String;
-        attribute edition : String;
-        attribute completenessStatus : String;
-    }
-}

package/src/compliance/postmarket/memo_postmarket.sysml

@@ -1,16 +0,0 @@
-package memo_compliance_postmarket {
-    private import ScalarValues::*;
-
-    private import memo_core_common::*;
-    private import memo_core_enumerations::*;
-    part def ClinicalEvaluation specializes MemoPart {
-        attribute evaluationStage : String;
-        attribute clinicalDataSource : String;
-        attribute conclusion : String;
-    }
-    part def PostMarketSurveillance specializes MemoPart {
-        attribute surveillanceKind : String;
-        attribute dataSource : String;
-        attribute reportingObligation : String;
-    }
-}