@memoarchitect/ontology 0.8.24 → 0.11.0

package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml

@@ -29,6 +29,8 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_main_screen_l
     private import memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
     private import memo_examples_ui_screen_regions_traces::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     // The geometry view: the capture as backdrop, elements drawn at their
     // authored bounds. Images for a layout view live in
     // `model/assets/<viewName>/`, so this view's backdrop is under
@@ -50,7 +52,7 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_main_screen_l
         expose memo_examples_ui_screen_regions_artifacts_reviews_rationales::*;
         expose memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
         expose memo_examples_ui_screen_regions_traces::*;
-        attribute :>> id = "UIE-001";
+        @MemoIdentity { :>> providedId = "UIE-001"; }
         ref :>> viewpointDefinition = uiLayoutViewpoint;
     }
 }

package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml

@@ -29,6 +29,8 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_settings_scre
     private import memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
     private import memo_examples_ui_screen_regions_traces::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     // The settings screen reached by NavigatesTo, rendered on its own capture.
     // One layout view per captured screen, and the view's name is the folder
     // its images live in — `model/assets/settingsScreenLayout/`.
@@ -45,7 +47,7 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_settings_scre
         expose memo_examples_ui_screen_regions_artifacts_reviews_rationales::*;
         expose memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
         expose memo_examples_ui_screen_regions_traces::*;
-        attribute :>> id = "UIE-008";
+        @MemoIdentity { :>> providedId = "UIE-008"; }
         ref :>> viewpointDefinition = uiLayoutViewpoint;
     }
 }

package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml

@@ -29,6 +29,8 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_ui_region_tra
     private import memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
     private import memo_examples_ui_screen_regions_traces::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     // The same content as a graph, for reviewers who want to read the trace
     // chain rather than look at the screen.
     view uiRegionTrace : MemoDiagramView {
@@ -44,7 +46,7 @@ package memo_examples_ui_screen_regions_viewpoints_ui_layout_views_ui_region_tra
         expose memo_examples_ui_screen_regions_artifacts_reviews_rationales::*;
         expose memo_examples_ui_screen_regions_artifacts_reviews_notes::*;
         expose memo_examples_ui_screen_regions_traces::*;
-        attribute :>> id = "UIV-001";
+        @MemoIdentity { :>> providedId = "UIV-001"; }
         attribute depth = 3;
         attribute :>> viewKind = DiagramViewKind::general;
         attribute :>> diagramType = "bdd";

package/extensions/aadl/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-aadl'
-version: 0.8.24
+version: 0.11.0
 description: AADL (SAE AS5506) correspondence profile and runtime component families
 license: MIT
 tags:

package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml

@@ -19,42 +19,44 @@ package memo_extension_aadl_correspondence {
 
     private import memo_architecture_operational_context_stakeholders::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     // ── Component categories ────────────────────────────────────────────
     part aadlCorrProcess : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-001";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-001"; }
         attribute :>> name = "ProcessCorrespondence";
         attribute :>> ruleExpression = "memo_extension_aadl_runtime::AadlProcess <-> AADL component category `process`";
         attribute :>> description = "A MEMO SoftwareComponent with runtimeKind = process, carrying addressSpaceIsolated.";
     }
     part aadlCorrThread : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-002";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-002"; }
         attribute :>> name = "ThreadCorrespondence";
         attribute :>> ruleExpression = "memo_extension_aadl_runtime::AadlThread <-> AADL component category `thread`";
         attribute :>> description = "Schedulable unit inside one process; owningProcessName names the containing process.";
     }
     part aadlCorrVirtualProcessor : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-003";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-003"; }
         attribute :>> name = "VirtualProcessorCorrespondence";
         attribute :>> ruleExpression = "memo_extension_aadl_runtime::AadlVirtualProcessor <-> AADL component category `virtual processor`";
         attribute :>> description = "An ARINC 653 partition. partitionBudget is the guaranteed time and memory; isolationMechanism is what enforces it.";
     }
     part aadlCorrProcessor : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-004";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-004"; }
         attribute :>> name = "ProcessorCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_physical::ProcessingNode <-> AADL component category `processor`";
     }
     part aadlCorrMemory : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-005";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-005"; }
         attribute :>> name = "MemoryCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_physical::MemoryDevice <-> AADL component category `memory`";
     }
     part aadlCorrBus : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-006";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-006"; }
         attribute :>> name = "BusCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_implementation_hardware_electrical::NetworkMedium <-> AADL component category `bus`";
     }
     part aadlCorrSystem : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-007";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-007"; }
         attribute :>> name = "SystemCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_logical_structure::System <-> AADL component category `system`";
         attribute :>> description = "AADL's system is the composition unit, which is MEMO's logical System rather than any runtime element.";
@@ -64,17 +66,17 @@ package memo_extension_aadl_correspondence {
     // something, and the binding is where latency, bandwidth, and fault
     // propagation accrue. MEMO has all three (plan C1). ────────────────────
     part aadlCorrProcessorBinding : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-010";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-010"; }
         attribute :>> name = "ActualProcessorBindingCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_deployment::DeploysTo <-> AADL property `Actual_Processor_Binding`";
     }
     part aadlCorrMemoryBinding : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-011";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-011"; }
         attribute :>> name = "ActualMemoryBindingCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_deployment::MemoryBinding <-> AADL property `Actual_Memory_Binding`";
     }
     part aadlCorrConnectionBinding : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-012";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-012"; }
         attribute :>> name = "ActualConnectionBindingCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_deployment::ConnectionBinding <-> AADL property `Actual_Connection_Binding`";
         attribute :>> description = "The bound element is the ComponentExchange, because the exchange is what owns the budget the medium spends.";
@@ -82,18 +84,18 @@ package memo_extension_aadl_correspondence {
 
     // ── Ports and flows ─────────────────────────────────────────────────
     part aadlCorrPortCategory : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-020";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-020"; }
         attribute :>> name = "PortCategoryCorrespondence";
         attribute :>> ruleExpression = "memo_core_enumerations::PortCategoryKind (data | 'event' | eventData) <-> AADL `data port` | `event port` | `event data port`";
         attribute :>> description = "Determines whether a missed deadline loses a sample or grows a queue — two failure modes with two mitigations.";
     }
     part aadlCorrFlowSpec : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-021";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-021"; }
         attribute :>> name = "FlowSpecificationCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_deployment::FlowSpecification (FlowSpecKind source | sink | path) <-> AADL `flow source` | `flow sink` | `flow path`";
     }
     part aadlCorrEndToEndFlow : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-022";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-022"; }
         attribute :>> name = "EndToEndFlowCorrespondence";
         attribute :>> ruleExpression = "memo_architecture_realization_deployment::EndToEndFlow <-> AADL `end to end flow`";
     }
@@ -101,45 +103,45 @@ package memo_extension_aadl_correspondence {
     // ── Properties. AADL's property sets are the technology-specific half of
     // the language; these are the ones MEMO already carries by another name.
     part aadlCorrPeriod : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-030";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-030"; }
         attribute :>> name = "PeriodCorrespondence";
         attribute :>> ruleExpression = "SoftwareComponent.periodMs <-> AADL `Timing_Properties::Period` (ms)";
     }
     part aadlCorrDeadline : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-031";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-031"; }
         attribute :>> name = "DeadlineCorrespondence";
         attribute :>> ruleExpression = "SoftwareComponent.deadlineMs <-> AADL `Timing_Properties::Deadline` (ms)";
     }
     part aadlCorrComputeExecutionTime : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-032";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-032"; }
         attribute :>> name = "ComputeExecutionTimeCorrespondence";
         attribute :>> ruleExpression = "SoftwareComponent.wcetMs <-> upper bound of AADL `Timing_Properties::Compute_Execution_Time` (ms)";
         attribute :>> description = "AADL records a range; MEMO records the worst case, which is the bound a schedulability argument uses.";
     }
     part aadlCorrPriority : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-033";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-033"; }
         attribute :>> name = "PriorityCorrespondence";
         attribute :>> ruleExpression = "SoftwareComponent.priority <-> AADL `Thread_Properties::Priority`";
     }
     part aadlCorrSchedulingProtocol : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-034";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-034"; }
         attribute :>> name = "SchedulingProtocolCorrespondence";
         attribute :>> ruleExpression = "SoftwareComponent.schedulingPolicy <-> AADL `Deployment_Properties::Scheduling_Protocol`";
     }
     part aadlCorrLatency : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-035";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-035"; }
         attribute :>> name = "LatencyCorrespondence";
         attribute :>> ruleExpression = "EndToEndFlow.latencyBudgetMs <-> AADL `Communication_Properties::Latency` upper bound (ms)";
     }
     part aadlCorrBandwidth : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-036";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-036"; }
         attribute :>> name = "BandwidthCorrespondence";
         attribute :>> ruleExpression = "ConnectionBinding.allocatedBandwidth <-> AADL `Communication_Properties::Bandwidth_Budget`";
     }
 
     // ── Where the correspondence stops ──────────────────────────────────
     part aadlCorrNoCounterpart : CorrespondenceRule {
-        attribute :>> id = "EXT-AADL-C-090";
+        @MemoIdentity { :>> providedId = "EXT-AADL-C-090"; }
         attribute :>> name = "NoCounterpartNote";
         attribute :>> ruleExpression = "no correspondence: AADL `subprogram`, `device`, `abstract`; MEMO's five assurance disciplines";
         attribute :>> description = "Recorded so the gap is a stated boundary of the profile rather than an omission a reader has to discover.";

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

@@ -4,8 +4,10 @@ package memo_extension_aadl_methodology {
     private import memo_methodology_profiles::*;
     private import memo_core_enumerations::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part aadlExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-AADL-001";
+        @MemoIdentity { :>> providedId = "EXT-AADL-001"; }
         attribute :>> name = "AadlCorrespondenceExtension";
         attribute :>> version = "0.7.0";
         attribute :>> domain = "AADL (SAE AS5506) software runtime";

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

@@ -4,8 +4,10 @@ package memo_extension_clinical_methodology {
     private import memo_methodology_profiles::*;
     private import memo_core_enumerations::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part clinicalExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-CLINICAL-001";
+        @MemoIdentity { :>> providedId = "EXT-CLINICAL-001"; }
         attribute :>> name = "ClinicalProcedureExtension";
         attribute :>> version = "0.6.5";
         attribute :>> domain = "clinical procedures";

package/extensions/cloud/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-cloud'
-version: 0.8.24
+version: 0.11.0
 description: Networked services and managed data stores
 license: MIT
 tags:

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

@@ -4,8 +4,10 @@ package memo_extension_cloud_methodology {
     private import memo_methodology_profiles::*;
     private import memo_core_enumerations::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part cloudExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-CLOUD-001";
+        @MemoIdentity { :>> providedId = "EXT-CLOUD-001"; }
         attribute :>> name = "CloudRuntimeExtension";
         attribute :>> version = "0.7.0";
         attribute :>> domain = "networked services and managed data stores";

package/extensions/container/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-container'
-version: 0.8.24
+version: 0.11.0
 description: OCI container images and container runtimes as deployment content
 license: MIT
 tags:

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

@@ -4,8 +4,10 @@ package memo_extension_container_methodology {
     private import memo_methodology_profiles::*;
     private import memo_core_enumerations::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part containerExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-CONTAINER-001";
+        @MemoIdentity { :>> providedId = "EXT-CONTAINER-001"; }
         attribute :>> name = "ContainerDeploymentExtension";
         attribute :>> version = "0.7.0";
         attribute :>> domain = "containerized deployment";

package/extensions/messaging/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-messaging'
-version: 0.8.24
+version: 0.11.0
 description: Publish/subscribe messaging — topics, brokers, and delivery semantics
 license: MIT
 tags:

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

@@ -4,8 +4,10 @@ package memo_extension_messaging_methodology {
     private import memo_methodology_profiles::*;
     private import memo_core_enumerations::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part messagingExtensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-MESSAGING-001";
+        @MemoIdentity { :>> providedId = "EXT-MESSAGING-001"; }
         attribute :>> name = "MessagingExtension";
         attribute :>> version = "0.7.0";
         attribute :>> domain = "publish/subscribe messaging";

package/extensions/ros/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-ros'
-version: 0.8.24
+version: 0.11.0
 description: ROS 2 nodes, messages, topic/service/action interfaces, QoS, and containerized deployment
 license: MIT
 tags:

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

@@ -4,12 +4,14 @@ package memo_extension_ros_methodology {
     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 {
-        attribute :>> id = "EXT-ROS-001";
+        @MemoIdentity { :>> providedId = "EXT-ROS-001"; }
         attribute :>> name = "Ros2Extension";
         attribute :>> version = "0.7.0";
         attribute :>> domain = "ROS 2 robotics middleware";

package/extensions/template/src/extension.sysml

@@ -21,8 +21,10 @@ package memo_extension_template {
     private import memo_methodology_core::*;
     private import memo_methodology_profiles::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part extensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-METH-001";
+        @MemoIdentity { :>> providedId = "EXT-METH-001"; }
         attribute :>> name = "ExtensionMethod";
         attribute :>> version = "0.1.0";
         attribute :>> domain = "project extension";

package/methodologies/default/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/methodology-default'
-version: 0.8.24
+version: 0.11.0
 description: "MEMO default medical-device methodology \u2014 selects viewpoints/views/DHF documents from @memoarchitect/ontology and adds rules, gates, patterns, profiles, and workflow."
 license: MIT
 tags:

package/methodologies/gpca/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/methodology-gpca'
-version: 0.8.24
+version: 0.11.0
 description: "GPCA infusion pump methodology \u2014 subtraction-based tailoring of @memoarchitect/methodology-default for the non-networked prototype variant. Excludes cybersecurity and SOUP."
 license: MIT
 tags:

package/ontology/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/ontology'
-version: 0.8.24
+version: 0.11.0
 description: "MEMO \u2014 the single canonical medical-device ontology: core semantics, the Arcadia-inspired architecture layers (context, requirements, behavior, structure, interfaces, risk, cybersecurity,\
   \ assurance, \u2026), compliance, viewpoints, views, and invariant rules. One namespace (memo::), one src/ tree."
 license: MIT

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@memoarchitect/ontology",
-  "version": "0.8.24",
+  "version": "0.11.0",
   "packageManager": "pnpm@9.15.0",
-  "description": "MEMO \u2014 Medical Engineering Modelling Ontology. Pure SysML v2 medical-device ontology with native constraints, portable to any conformant SysML v2 tool (SysIDE, SysON, sysand).",
+  "description": "MEMO — Medical Engineering Modelling Ontology. Pure SysML v2 medical-device ontology with native constraints, portable to any conformant SysML v2 tool (SysIDE, SysON, sysand).",
   "scripts": {
     "build": "bash scripts/build-kpar.sh",
     "check": "bash scripts/build-kpar.sh && npm run lint",

package/profile/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/medical-modeling-profile'
-version: 0.8.24
+version: 0.11.0
 description: Closure rules and viewpoints for medical device modeling
 license: MIT
 tags:

package/src/architecture/functional/behavior/memo_behavior.sysml

@@ -89,6 +89,6 @@ package memo_architecture_functional_behavior {
         attribute minMs : String;
         attribute maxMs : String;
         ref referenceElement : MemoPart[1];
-        attribute verificationMethod : VerificationMethodKind;
+        attribute verificationMethod : MemoVerificationMethodKind;
     }
 }

package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml

@@ -13,7 +13,17 @@ package memo_architecture_implementation_hardware_common {
     private import memo_core_enumerations::*;
     private import memo_core_relationships::*;
 
-    part def PhysicalAssembly specializes MemoPart {
+    // The shared root of the physical family.
+    //
+    // `PhysicalAssembly` and `PhysicalComponent` each specialized `MemoPart`
+    // directly, so the family had two roots and no single type that means
+    // "a physical thing". A containment rule has to name one type, and
+    // `conformsTo(MemoPart)` is far too wide — it admits a requirement or a
+    // hazard. This is that type, and it carries nothing of its own: the split
+    // between an assembly and a component is what the two subtypes are for.
+    abstract part def PhysicalElement specializes MemoPart { }
+
+    part def PhysicalAssembly specializes PhysicalElement {
         attribute responsibility : String;
         attribute safetyRole : String;
         attribute partNumber : String;
@@ -25,7 +35,7 @@ package memo_architecture_implementation_hardware_common {
     // Retained name from 0.4; an electronics-centred assembly.
     part def HardwareAssembly specializes PhysicalAssembly;
 
-    part def PhysicalComponent specializes MemoPart {
+    part def PhysicalComponent specializes PhysicalElement {
         attribute partNumber : String;
         attribute materialSummary : String;
         // ISO 10993-1 contact characterization; required when true.

package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml

@@ -78,15 +78,4 @@ package memo_architecture_implementation_software_runtime {
         // a component belongs to without claiming to describe it.
     }
 
-    connection def ComponentConnects :> MemoRelationship {
-        attribute protocolSummary : String;
-        end sourceComponent : SoftwareComponent :>> source;
-        end targetComponent : SoftwareComponent :>> target;
-    }
-    abstract connection componentConnectsLinks : ComponentConnects[*];
-    metadata def <componentConnects> ComponentConnectsMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = componentConnectsLinks meta SysML::Usage;
-    }
 }

package/src/architecture/implementation/ui/memo_ui.sysml

@@ -280,18 +280,6 @@ package memo_architecture_implementation_ui {
         attribute exitPoint : String;
     }
 
-    connection def DataBinding :> MemoRelationship {
-        attribute bindingExpression : String;
-        attribute refreshPolicy : String;
-        end boundElement : InteractionElement :>> source;
-        end dataSource : MemoItem :>> target;
-    }
-    abstract connection dataBindingLinks : DataBinding[*];
-    metadata def <dataBinding> DataBindingMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = dataBindingLinks meta SysML::Usage;
-    }
     // `PresentsState` had zero usages anywhere in the tree (R10-S6). Its
     // audited native form, `exhibit state`, does not actually fit: `UIState`
     // is a `part def` with plain string attributes, not a `state def`, and
@@ -320,17 +308,6 @@ package memo_architecture_implementation_ui {
     // Conflating the two was the mistake that made "clicking takes you to a
     // child view" look like spatial nesting; it is a separate frame reached
     // from here, and only this relation says so.
-    connection def NavigatesTo :> MemoRelationship {
-        attribute triggerGesture : String;
-        end sourceElement : UIElement :>> source;
-        end targetScreen : UIElement :>> target;
-    }
-    abstract connection navigatesToLinks : NavigatesTo[*];
-    metadata def <navigatesTo> NavigatesToMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = navigatesToLinks meta SysML::Usage;
-    }
 
     // ── §18 traceability ─────────────────────────────────────────
     connection def ElementTriggersAction :> MemoRelationship {

package/src/architecture/logical/interfaces/memo_interfaces.sysml

@@ -15,7 +15,9 @@ package memo_architecture_logical_interfaces {
     // DigitalInterface / SPIInterface / RestInterface … hierarchy: those were
     // 20+ classes that differed only in the value of `protocol`.
 
-    interface def Interface specializes MemoInterface {
+    // Specializes the standard library interface as well as MEMO's base,
+    // rather than shadowing it — see the note on UseCase.
+    interface def Interface specializes MemoInterface, Interfaces::Interface {
         attribute interfaceKind : InterfaceKind;   // semantic + signaling family
         attribute direction : DirectionKind;
         attribute protocol : String;               // "SPI", "CAN", "Ethernet", "REST", "4-20mA"

package/src/architecture/operational/context/use_context/memo_use_context.sysml

@@ -66,17 +66,9 @@ package memo_architecture_operational_context_use_context {
         :>> baseType = interactsInContextLinks meta SysML::Usage;
     }
 
-    connection def InteractsWith :> MemoRelationship {
-        end contextParticipant : OperationalParticipant :>> source;
-        // Untyped so operational activities (action def) can be targets as well as parts.
-        end target;
-    }
-    abstract connection interactsWithLinks : InteractsWith[*];
-    metadata def <interactsWith> InteractsWithMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = interactsWithLinks meta SysML::Usage;
-    }
+    // `InteractsWith` is native `connect` (2026-08-18): write
+    // `connection connect <participant> to <target>;`. It carried no
+    // attributes, and the operational-context package already scopes the ends.
     // `ConnectsPhysically` is native `connect` (R10-S6): write
     // `connection connect source ::> <a> to target ::> <b>;` — the ordinary
     // untyped binary connection — instead of a connection def for it.

package/src/architecture/operational/scenarios/memo_scenarios.sysml

@@ -42,27 +42,16 @@ package memo_architecture_operational_scenarios {
         attribute assumptionSummary : String;
         attribute guaranteeSummary : String;
         attribute securityObjective : String;
-        attribute abuseCaseReference : String;
+        ref abuseCase : OperativeScenario[0..1];
         attribute defaultCategory : ThreatCategoryKind[0..1];
         // verification scenario
         attribute verificationEnvironment : String;
         attribute stimulusSummary : String;
         // hazard-related use scenario (IEC 62366-1 3.9)
-        attribute hazardReference : String;
         attribute selectionRationale : String;
     }
 
     // A workflow is composed of one or more scenarios (nominal + alternate
     // paths). ScenarioOccurrence/Executes were removed: an actual execution is
     // a native SysML *usage* of the scenario, not a separate def + relation.
-    connection def HasScenario :> MemoRelationship {
-        end owningWorkflow : OperationalWorkflow :>> source;
-        end pathScenario : OperativeScenario :>> target;
-    }
-    abstract connection hasScenarioLinks : HasScenario[*];
-    metadata def <hasScenario> HasScenarioMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = hasScenarioLinks meta SysML::Usage;
-    }
 }

package/src/architecture/operational/use_cases/memo_use_cases.sysml

@@ -19,7 +19,13 @@ package memo_architecture_operational_use_cases {
         enum development;
     }
 
-    use case def UseCase :> MemoUseCase {
+    // Specializes the STANDARD library use case as well as MEMO's base. Before
+    // this it specialized only `MemoUseCase` and so shadowed `UseCases::UseCase`
+    // — same name, same metaclass, none of the semantics — which is why the
+    // subject/actor features below had to be re-declared by hand instead of
+    // being inherited. The wrapper survives only to carry the display label and
+    // lifecycle status; identity comes from `@MemoIdentity`.
+    use case def UseCase :> MemoUseCase, UseCases::UseCase {
         // Text of this use case's goal; this is not a separate Goal element.
         attribute goalStatement : String;
         attribute trigger : String;
@@ -62,14 +68,4 @@ package memo_architecture_operational_use_cases {
     // `include` (R10-S6); write that instead of a connection here. `extends`
     // has 0 hits in the corpus for a use-case `extend` production, so it stays
     // a MEMO construct: a cross-cutting relationship that is always presented.
-    connection def Extends :> MemoRelationship {
-        end extendingUseCase : UseCase :>> source;
-        end extendedUseCase : UseCase :>> target;
-    }
-    abstract connection extendsLinks : Extends[*];
-    metadata def <extends> ExtendsMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = extendsLinks meta SysML::Usage;
-    }
 }

package/src/architecture/operational/workflows/memo_workflows.sysml

@@ -91,26 +91,6 @@ package memo_architecture_operational_workflows {
     // SupportKind discriminator is gone: what used to be three enum values
     // that each implied a different target type are now two typed refs plus
     // this one plain relation.
-    connection def Supports :> MemoRelationship {
-        end supporter :>> source;
-        end supported : MemoAction :>> target;
-    }
-    abstract connection supportsLinks : Supports[*];
-    metadata def <supports> SupportsMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = supportsLinks meta SysML::Usage;
-    }
-    connection def RequiresResource :> MemoRelationship {
-        end workflow : OperationalWorkflow :>> source;
-        end resource : WorkflowResource :>> target;
-    }
-    abstract connection requiresResourceLinks : RequiresResource[*];
-    metadata def <requiresResource> RequiresResourceMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = requiresResourceLinks meta SysML::Usage;
-    }
 
     // ── Workflow transformation (as-is → to-be) ──────────────────
     // Transforms unifies TransformsStep / TransformsWorkflow / ReplacesWorkflow