@memoarchitect/ontology 0.6.5 → 0.7.0

package/examples/sysml-diagram-samples/model/catalog/project.sysml

@@ -0,0 +1,33 @@
+// Sysml Diagram Samples — project identity and method binding.
+//
+// The native entrypoint. The imports name what this project contains and the
+// binding names the methodology it is governed by. No YAML file participates.
+package memo_examples_sysml_diagram_samples_project {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    // The project's own content, imported so the catalog is one reachable
+    // closure from a single entrypoint.
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_action_flow_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_context_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_functional_flow_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_interconnection_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_operational_behaviour_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_requirements_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_standard_activity_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_state_transition_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_tree_view::*;
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_use_case_view::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-DIAGRAM-SAMPLES-001";
+        attribute :>> name = "SysmlDiagramSamplesProjectMethodBinding";
+        attribute :>> projectName = "Sysml Diagram Samples";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/viewpoint.sysml

@@ -0,0 +1,9 @@
+// unassigned viewpoint.
+//
+// This project does not define its own viewpoint here; it binds the reusable
+// MEMO viewpoint that frames these concerns. The views it governs sit beneath
+// `views/`.
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned {
+    // The reusable package declaring unassigned could not be resolved during
+    // conversion. Import it here so the views beneath this viewpoint resolve.
+}

package/examples/sysml-diagram-samples/model/{samples → catalog/viewpoints/unassigned/views}/action_flow_view.sysml

@@ -1,10 +1,12 @@
-package memo_examples_sysml_diagram_samples_model_samples_action_flow_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_action_flow_view {
     private import ScalarValues::*;
     private import memo_core_relationships::*;
 
     private import memo_architecture_logical_structure::*;
     private import memo_architecture_logical_interfaces::*;
+    private import memo_architecture_functional_functions::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_functional_functional_viewpoint::*;
     private import memo_core_enumerations::*;
 
     item def DataPacket specializes InterfaceItem {
@@ -17,15 +19,15 @@ package memo_examples_sysml_diagram_samples_model_samples_action_flow_view {
         attribute :>> itemKind = InterfaceItemKind::material;
     }
 
-    action def ReceiveInput { out received : DataPacket; }
-    action def ValidateInput { in received : DataPacket; out validated : EnergyToken; }
-    action def ProcessInput { in validated : EnergyToken; out result : MaterialBatch; }
-    action def RecordResult { in result : MaterialBatch; }
+    action def ReceiveInput specializes SystemAction { out item received : DataPacket; }
+    action def ValidateInput specializes SystemAction { in item received : DataPacket; out item validated : EnergyToken; }
+    action def ProcessInput specializes SystemAction { in item validated : EnergyToken; out item result : MaterialBatch; }
+    action def RecordResult specializes SystemAction { in item result : MaterialBatch; }
 
     part laneA : LogicalComponent { attribute :>> name = "Lane A"; }
     part laneB : LogicalComponent { attribute :>> name = "Lane B"; }
 
-    action sampleActionFlow {
+    action sampleActionFlow : SystemAction {
         action receive : ReceiveInput;
         action validate : ValidateInput;
         action process : ProcessInput {
@@ -60,11 +62,16 @@ package memo_examples_sysml_diagram_samples_model_samples_action_flow_view {
 
     // MemoLink sample — the universal relation, exercised where nothing else
     // reaches. laneB is a `part` (LogicalComponent :> ArchitectureElement) and
-    // ProcessInput is an `action def` (:> MemoAction). Those foundations share
-    // no supertype, so every typed relation in the ontology is unavailable
-    // here: legalRelationshipTypes returns MemoLink and nothing else.
+    // `sampleActionFlow.process` is an action usage (:> MemoAction). Those
+    // foundations share no supertype, so every typed relation in the ontology
+    // is unavailable here: legalRelationshipTypes returns MemoLink and nothing
+    // else.
+    //
+    // The target is the action *usage*, not the `ProcessInput` definition.
+    // Binding a value to a definition is not portable — SysIDE rejects it,
+    // because a value must be a feature and a definition is not.
     connection linkLaneBProcessesInput : MemoLink
-        connect linkSource ::> laneB to linkTarget ::> ProcessInput {
+        connect linkSource ::> laneB to linkTarget ::> sampleActionFlow.process {
         attribute :>> linkRationale =
             "Lane B is the swimlane that carries the ProcessInput behaviour. The association crosses the part/action metaclass boundary, so no typed relation can express it.";
     }
@@ -78,6 +85,7 @@ package memo_examples_sysml_diagram_samples_model_samples_action_flow_view {
         attribute :>> shortDescription = "Dummy actions, typed item flows, successions, and a composite action for renderer development.";
         attribute :>> viewKind = DiagramViewKind::actionflow;
         attribute :>> diagramType = "afd";
+        part :>> viewpointDefinition = functionalViewpoint;
     }
 
     connection : IncludedIn connect sourceElement ::> sampleActionFlow.receive to targetView ::> sampleActionFlowView;

package/examples/sysml-diagram-samples/model/{samples → catalog/viewpoints/unassigned/views}/context_view.sysml

@@ -1,7 +1,7 @@
 // System context sample (general view kind, `context` diagram type). The system
 // under consideration is one block; every other element is an external actor,
 // neighbouring system, or use context it interacts with across its boundary.
-package memo_examples_sysml_diagram_samples_model_samples_context_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_context_view {
     private import ScalarValues::*;
 
     private import memo_architecture_operational_context_actors::*;
@@ -9,6 +9,7 @@ package memo_examples_sysml_diagram_samples_model_samples_context_view {
     private import memo_architecture_operational_structure::*;
     private import memo_core_relationships::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_context_context_viewpoint::*;
     private import memo_core_enumerations::*;
 
     // The operational system of interest is intentionally represented as one
@@ -17,7 +18,7 @@ package memo_examples_sysml_diagram_samples_model_samples_context_view {
     part infusionSystem : OperationalEntity {
         attribute :>> name = "Infusion Pump System";
         attribute :>> entityKind = OperationalEntityKind::device;
-        attribute :>> contextRole = "systemOfInterest";
+        attribute :>> responsibility = "System of interest for this context view.";
     }
     part clinician : User { attribute :>> name = "Clinician"; }
     part patient : User { attribute :>> name = "Patient"; }
@@ -41,6 +42,7 @@ package memo_examples_sysml_diagram_samples_model_samples_context_view {
         attribute :>> shortDescription = "Operational system context: one black-box system boundary, its external people, peer systems, operating environment, and named boundary-crossing interactions.";
         attribute :>> viewKind = DiagramViewKind::general;
         attribute :>> diagramType = "context";
+        part :>> viewpointDefinition = contextViewpoint;
         part :>> selectionQuery {
             attribute :>> includeRelationshipKinds = ("InteractsWith", "ExchangesWith", "AppliesInContext");
         }

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

@@ -0,0 +1,47 @@
+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/{samples → catalog/viewpoints/unassigned/views}/functional_flow_view.sysml

@@ -1,10 +1,12 @@
-package memo_examples_sysml_diagram_samples_model_samples_functional_flow_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_functional_flow_view {
     private import ScalarValues::*;
 
     private import memo_architecture_logical_structure::*;
     private import memo_architecture_logical_interfaces::*;
+    private import memo_architecture_functional_functions::*;
     private import memo_core_relationships::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_functional_functional_viewpoint::*;
     private import memo_core_enumerations::*;
 
     // ─────────────────────────────────────────────────────────────────────────
@@ -37,13 +39,13 @@ package memo_examples_sysml_diagram_samples_model_samples_functional_flow_view {
     }
 
     // Functions with typed in/out pins
-    action def FxAcquire { out reading : FxSensorReading; }
-    action def FxCompute { in reading : FxSensorReading; out command : FxRateCommand; }
-    action def FxEnforce { in command : FxRateCommand; out safeCommand : FxRateCommand; }
-    action def FxDrive { in command : FxRateCommand; out energy : FxMotorEnergy; }
-    action def FxDeliverMedication { in energy : FxMotorEnergy; out fluid : FxMedicationFluid; }
-    action def FxMonitor { out signal : FxOcclusionSignal; }
-    action def FxDetect { in signal : FxOcclusionSignal; }
+    action def FxAcquire specializes SystemAction { out item reading : FxSensorReading; }
+    action def FxCompute specializes SystemAction { in item reading : FxSensorReading; out item command : FxRateCommand; }
+    action def FxEnforce specializes SystemAction { in item command : FxRateCommand; out item safeCommand : FxRateCommand; }
+    action def FxDrive specializes SystemAction { in item command : FxRateCommand; out item energy : FxMotorEnergy; }
+    action def FxDeliverMedication specializes SystemAction { in item energy : FxMotorEnergy; out item fluid : FxMedicationFluid; }
+    action def FxMonitor specializes SystemAction { out item signal : FxOcclusionSignal; }
+    action def FxDetect specializes SystemAction { in item signal : FxOcclusionSignal; }
 
     // Component hierarchy used by the Level control:
     // L1 system → L2 subsystems → L3 allocated components.
@@ -68,24 +70,24 @@ package memo_examples_sysml_diagram_samples_model_samples_functional_flow_view {
     connection : Composes connect parent ::> fxDeliverySubsystem to child ::> fxActuator;
     connection : Composes connect parent ::> fxSafetySubsystem to child ::> fxSafety;
 
-    action fxDeliveryFlow {
-        action fxAcquire : FxAcquire { attribute name = "Acquire Sensor Data"; }
-        action fxCompute : FxCompute { attribute name = "Compute Infusion Rate"; }
+    action fxDeliveryFlow : SystemAction {
+        action fxAcquire : FxAcquire { attribute :>> name = "Acquire Sensor Data"; }
+        action fxCompute : FxCompute { attribute :>> name = "Compute Infusion Rate"; }
 
         // Split: enforce/drive/deliver runs concurrently with occlusion monitoring
         fork fxForkDeliver;
-        action fxEnforce : FxEnforce { attribute name = "Enforce Dose Limits"; }
-        action fxDrive : FxDrive { attribute name = "Drive Pump Motor"; }
-        action fxMonitor : FxMonitor { attribute name = "Monitor Occlusion"; }
-        action fxDetect : FxDetect { attribute name = "Detect Occlusion"; }
+        action fxEnforce : FxEnforce { attribute :>> name = "Enforce Dose Limits"; }
+        action fxDrive : FxDrive { attribute :>> name = "Drive Pump Motor"; }
+        action fxMonitor : FxMonitor { attribute :>> name = "Monitor Occlusion"; }
+        action fxDetect : FxDetect { attribute :>> name = "Detect Occlusion"; }
         join fxJoinDeliver;
 
         // Composite function — valve sub-flow (drill-in)
         action fxDeliver : FxDeliverMedication {
-            attribute name = "Deliver Medication";
-            action fxOpenValve { attribute name = "Open Valve"; }
-            action fxHoldDose { attribute name = "Hold Metered Dose"; }
-            action fxCloseValve { attribute name = "Close Valve"; }
+            attribute :>> name = "Deliver Medication";
+            action fxOpenValve : SystemAction { attribute :>> name = "Open Valve"; }
+            action fxHoldDose : SystemAction { attribute :>> name = "Hold Metered Dose"; }
+            action fxCloseValve : SystemAction { attribute :>> name = "Close Valve"; }
 
             flow of FxMedicationFluid from fxDeliveryFlow.fxDeliver.fxHoldDose to fxCloseValve;
 
@@ -95,7 +97,7 @@ package memo_examples_sysml_diagram_samples_model_samples_functional_flow_view {
             first fxCloseValve then done;
         }
 
-        action fxLog { attribute name = "Log Delivery"; }
+        action fxLog : SystemAction { attribute :>> name = "Log Delivery"; }
 
         flow of FxSensorReading from fxAcquire.reading to fxCompute.reading;
         flow of FxRateCommand from fxEnforce.safeCommand to fxDrive.command;
@@ -137,6 +139,7 @@ package memo_examples_sysml_diagram_samples_model_samples_functional_flow_view {
         attribute :>> shortDescription = "Component behaviour: functions in swimlanes per realising component, typed data/energy/material flows, a fork/join for concurrent occlusion monitoring, and a composite 'Deliver Medication' valve sub-flow (double-click to drill in).";
         attribute :>> viewKind = DiagramViewKind::actionflow;
         attribute :>> diagramType = "ffd";
+        part :>> viewpointDefinition = functionalViewpoint;
     }
 
     connection : IncludedIn connect sourceElement ::> fxDeliveryFlow.fxAcquire to targetView ::> fxDeliveryView;

package/examples/sysml-diagram-samples/model/{samples → catalog/viewpoints/unassigned/views}/interconnection_view.sysml

@@ -1,12 +1,14 @@
-package memo_examples_sysml_diagram_samples_model_samples_interconnection_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_interconnection_view {
     private import ScalarValues::*;
     private import memo_architecture_operational_context_actors::*;
     private import memo_architecture_operational_context_use_context::*;
 
     private import memo_architecture_logical_interfaces::*;
     private import memo_architecture_logical_structure::*;
+    private import memo_core_common::*;
     private import memo_core_relationships::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_logical_logical_viewpoint::*;
     private import memo_core_enumerations::*;
 
     part coffeeMachine : LogicalComponent { attribute :>> name = "Coffee Machine"; }
@@ -17,19 +19,19 @@ package memo_examples_sysml_diagram_samples_model_samples_interconnection_view {
     part brewGroup : LogicalComponent { attribute :>> name = "Brew Group"; }
     part cup : LogicalComponent { attribute :>> name = "Cup"; }
 
-    port mainsWaterIn : DataPort { attribute :>> direction = DirectionKind::input; }
-    port beverageOut : DataPort { attribute :>> direction = DirectionKind::output; }
-    port supplyWaterOut : DataPort { attribute :>> direction = DirectionKind::output; }
-    port cupBeverageIn : DataPort { attribute :>> direction = DirectionKind::input; }
-    port serviceInterface : DataPort { attribute :>> direction = DirectionKind::bidirectional; }
-    port diagnostics : DataPort { attribute :>> direction = DirectionKind::output; }
-    port tankWaterOut : DataPort { attribute :>> direction = DirectionKind::output; }
-    port tankWaterIn : DataPort { attribute :>> direction = DirectionKind::input; }
-    port heaterWaterIn : DataPort { attribute :>> direction = DirectionKind::input; }
-    port heatedWaterOut : DataPort { attribute :>> direction = DirectionKind::output; }
-    port brewWaterIn : DataPort { attribute :>> direction = DirectionKind::input; }
-    port brewedCoffeeOut : DataPort { attribute :>> direction = DirectionKind::output; }
-    port heaterStatusOut : DataPort { attribute :>> direction = DirectionKind::output; }
+    in port mainsWaterIn : DataPort { in item payload : MemoExchangeItem; }
+    out port beverageOut : DataPort { out item payload : MemoExchangeItem; }
+    out port supplyWaterOut : DataPort { out item payload : MemoExchangeItem; }
+    in port cupBeverageIn : DataPort { in item payload : MemoExchangeItem; }
+    inout port serviceInterface : DataPort { inout item payload : MemoExchangeItem; }
+    out port diagnostics : DataPort { out item payload : MemoExchangeItem; }
+    out port tankWaterOut : DataPort { out item payload : MemoExchangeItem; }
+    in port tankWaterIn : DataPort { in item payload : MemoExchangeItem; }
+    in port heaterWaterIn : DataPort { in item payload : MemoExchangeItem; }
+    out port heatedWaterOut : DataPort { out item payload : MemoExchangeItem; }
+    in port brewWaterIn : DataPort { in item payload : MemoExchangeItem; }
+    out port brewedCoffeeOut : DataPort { out item payload : MemoExchangeItem; }
+    out port heaterStatusOut : DataPort { out item payload : MemoExchangeItem; }
 
     connection : Composes connect parent ::> coffeeMachine to child ::> waterTank;
     connection : Composes connect parent ::> coffeeMachine to child ::> heaterAssembly;
@@ -66,6 +68,7 @@ package memo_examples_sysml_diagram_samples_model_samples_interconnection_view {
         attribute :>> shortDescription = "Balanced internal architecture with readable boundary ports, nested service diagnostics, and external water and beverage interfaces.";
         attribute :>> viewKind = DiagramViewKind::interconnection;
         attribute :>> diagramType = "ibd";
+        part :>> viewpointDefinition = logicalArchitectureViewpoint;
         part :>> selectionQuery {
             attribute :>> includeRelationshipKinds = ("Composes", "ExchangesWith");
         }

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

@@ -0,0 +1,94 @@
+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/{samples → catalog/viewpoints/unassigned/views}/operational_behaviour_view.sysml

@@ -1,10 +1,12 @@
-package memo_examples_sysml_diagram_samples_model_samples_operational_behaviour_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_operational_behaviour_view {
     private import ScalarValues::*;
     private import memo_architecture_operational_context_actors::*;
     private import memo_core_relationships::*;
     private import memo_architecture_logical_interfaces::*;
     private import memo_architecture_operational_structure::*;
+    private import memo_architecture_operational_activities::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_operational_operational_viewpoint::*;
     private import memo_core_enumerations::*;
 
     // Operational activity across clinical roles. The fixture is intentionally
@@ -16,17 +18,17 @@ package memo_examples_sysml_diagram_samples_model_samples_operational_behaviour_
         attribute :>> itemKind = InterfaceItemKind::signal;
     }
 
-    action def OpPrescribeTherapy { out prescription : OpPrescription; }
-    action def OpVerifyPrescription { in prescription : OpPrescription; }
-    action def OpRequestBolus { out bolusRequest : OpBolusRequest; }
-    action def OpCheckLockout { in bolusRequest : OpBolusRequest; }
+    action def OpPrescribeTherapy specializes OperationalActivity { out item prescription : OpPrescription; }
+    action def OpVerifyPrescription specializes OperationalActivity { in item prescription : OpPrescription; }
+    action def OpRequestBolus specializes OperationalActivity { out item bolusRequest : OpBolusRequest; }
+    action def OpCheckLockout specializes OperationalActivity { in item bolusRequest : OpBolusRequest; }
 
     // Use the canonical MEMO operational system type—never a sample-local
     // placeholder—so ontology-driven Explorer grouping remains authoritative.
     part opCareSystem : OperationalEntity {
         attribute :>> name = "PCA Care System";
         attribute :>> entityKind = OperationalEntityKind::device;
-        attribute :>> contextRole = "systemOfInterest";
+        attribute :>> responsibility = "System of interest for this context view.";
     }
     part opClinicalTeam : User {
         attribute :>> actorKind = ActorKind::clinician; attribute :>> name = "Clinical Team"; }
@@ -48,22 +50,22 @@ package memo_examples_sysml_diagram_samples_model_samples_operational_behaviour_
     connection : Composes connect parent ::> opClinicalTeam to child ::> opRoleBiomed;
     connection : Composes connect parent ::> opPatientGroup to child ::> opRolePatient;
 
-    action opSetupFlow {
-        action opPrescribe : OpPrescribeTherapy { attribute name = "Prescribe Therapy"; }
-        action opVerify : OpVerifyPrescription { attribute name = "Verify Prescription"; }
+    action opSetupFlow : OperationalActivity {
+        action opPrescribe : OpPrescribeTherapy { attribute :>> name = "Prescribe Therapy"; }
+        action opVerify : OpVerifyPrescription { attribute :>> name = "Verify Prescription"; }
         fork opForkPrep;
-        action opPrime { attribute name = "Prime Pump & Load Reservoir"; }
-        action opSelfTest { attribute name = "Run Device Self-Test"; }
+        action opPrime : OperationalActivity { attribute :>> name = "Prime Pump & Load Reservoir"; }
+        action opSelfTest : OperationalActivity { attribute :>> name = "Run Device Self-Test"; }
         join opJoinPrep;
-        action opProgram { attribute name = "Program Pump Parameters"; }
-        action opConnect { attribute name = "Connect to Patient"; }
-        action opStart { attribute name = "Start Infusion"; }
-        action opAdminister {
-            attribute name = "Administer PCA Therapy";
-            action opRequestBolus : OpRequestBolus { attribute name = "Request Bolus"; }
-            action opCheckLockout : OpCheckLockout { attribute name = "Check Lockout"; }
-            action opDeliverDose { attribute name = "Deliver Dose"; }
-            action opLogEvent { attribute name = "Log Dose Event"; }
+        action opProgram : OperationalActivity { attribute :>> name = "Program Pump Parameters"; }
+        action opConnect : OperationalActivity { attribute :>> name = "Connect to Patient"; }
+        action opStart : OperationalActivity { attribute :>> name = "Start Infusion"; }
+        action opAdminister : OperationalActivity {
+            attribute :>> name = "Administer PCA Therapy";
+            action opRequestBolus : OpRequestBolus { attribute :>> name = "Request Bolus"; }
+            action opCheckLockout : OpCheckLockout { attribute :>> name = "Check Lockout"; }
+            action opDeliverDose : OperationalActivity { attribute :>> name = "Deliver Dose"; }
+            action opLogEvent : OperationalActivity { attribute :>> name = "Log Dose Event"; }
             flow of OpBolusRequest from opRequestBolus.bolusRequest to opCheckLockout.bolusRequest;
             first start then opRequestBolus;
             first opRequestBolus then opCheckLockout;
@@ -109,6 +111,7 @@ package memo_examples_sysml_diagram_samples_model_samples_operational_behaviour_
         attribute :>> shortDescription = "Operational activity across clinical roles with concurrent preparation and a composite therapy step.";
         attribute :>> viewKind = DiagramViewKind::actionflow;
         attribute :>> diagramType = "ofd";
+        part :>> viewpointDefinition = operationalViewpoint;
     }
 
     connection : IncludedIn connect sourceElement ::> opSetupFlow.opPrescribe to targetView ::> opSetupView;

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

@@ -0,0 +1,13 @@
+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/sysml-diagram-samples/model/{samples → catalog/viewpoints/unassigned/views}/requirements_view.sysml

@@ -1,13 +1,14 @@
 // Requirements sample (general view kind, `req` diagram type). Stakeholder needs
 // on the left derive into system requirements; `DerivesFrom` edges render as the
 // requirements-diagram trace lines.
-package memo_examples_sysml_diagram_samples_model_samples_requirements_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_requirements_view {
     private import ScalarValues::*;
 
     private import memo_assurance_requirements_needs::*;
     private import memo_assurance_requirements::*;
     private import memo_core_relationships::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_requirements_requirements_viewpoint::*;
     private import memo_core_enumerations::*;
 
     requirement needSafeTherapy : Need {
@@ -50,6 +51,7 @@ package memo_examples_sysml_diagram_samples_model_samples_requirements_view {
         attribute :>> shortDescription = "Stakeholder needs deriving into system requirements, wired by DerivesFrom trace edges.";
         attribute :>> viewKind = DiagramViewKind::general;
         attribute :>> diagramType = "req";
+        part :>> viewpointDefinition = requirementsViewpoint;
         part :>> selectionQuery {
             attribute :>> includeRelationshipKinds = ("DerivesFrom");
         }

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

@@ -0,0 +1,51 @@
+// Standard SysML v2 activity sample (actionflow view kind, `afd` diagram type).
+//
+// The view over `activity_example::CustomerProcess`, the standard-SysML activity
+// fixture in `model/sysml_v2_activity_example.sysml`. It exists because the
+// fixture's whole point is the node types `action_flow_view.sysml` does not
+// have — decision, merge, fork, join, accept, send, terminate, and guarded
+// successions. Without a view exposing it the fixture parses into the model and
+// is never drawn, which is indistinguishable from a renderer that cannot draw
+// decisions.
+//
+// Nothing here specializes a MEMO kind: the fixture is plain standard SysML,
+// and that is the property under test. The renderer classifies its nodes from
+// the metamodel (`activity-notation.ts`), not from an ontology kind.
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_standard_activity_view {
+    private import ScalarValues::*;
+
+    private import memo_core_relationships::*;
+    private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_functional_functional_viewpoint::*;
+    private import memo_core_enumerations::*;
+
+    private import activity_example::*;
+
+    view standardActivityView : MemoDiagramView {
+        expose CustomerProcess::**;
+        attribute depth = 2;
+        attribute :>> title = "Sample · Customer Purchase Process";
+        attribute :>> shortDescription = "Customer login, guarded validation, shopping loop, checkout, credit approval, and explicit completion outcomes.";
+        attribute :>> viewKind = DiagramViewKind::actionflow;
+        attribute :>> diagramType = "afd";
+        part :>> viewpointDefinition = functionalViewpoint;
+    }
+
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::customerLogsIn to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::validUserDecision to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::rejected to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::browseCatalog to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::viewBookStore to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::selectBookForPurchase to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::addToShoppingBasket to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::viewShoppingBasket to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::shoppingDecision to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::commitOrder to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::supplyCreditCardDetails to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::creditDecision to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::rejectCreditCard to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::closeOrder to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::confirmPurchase to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::itemsDelivered to targetView ::> standardActivityView;
+    connection : IncludedIn connect sourceElement ::> CustomerProcess::orderComplete to targetView ::> standardActivityView;
+}

package/examples/sysml-diagram-samples/model/{samples → catalog/viewpoints/unassigned/views}/state_transition_view.sysml

@@ -1,12 +1,13 @@
 // State transition sample (statetransition view kind, `stm` diagram type). A
 // behaviour machine owns its mode states; each Transition carries `sourceState`
 // / `targetState` naming the states it connects, and renders as a labelled edge.
-package memo_examples_sysml_diagram_samples_model_samples_state_transition_view {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_state_transition_view {
     private import ScalarValues::*;
 
     private import memo_architecture_functional_behavior::*;
     private import memo_core_relationships::*;
     private import memo_viewpoints_definitions::*;
+    private import memo_viewpoints_functional_functional_viewpoint::*;
     private import memo_core_enumerations::*;
 
     state pumpModes : StateMachine { attribute :>> name = "Pump Operating Modes"; }
@@ -84,6 +85,7 @@ package memo_examples_sysml_diagram_samples_model_samples_state_transition_view
         attribute :>> shortDescription = "A pump-mode state machine — Idle, Infusing, Paused, Alarm — where Infusing is a composite state nesting Priming, Delivering and Holding.";
         attribute :>> viewKind = DiagramViewKind::statetransition;
         attribute :>> diagramType = "stm";
+        part :>> viewpointDefinition = functionalViewpoint;
         part :>> selectionQuery {
             attribute :>> includeElementKinds = ("StateMachine", "ModeState", "Transition");
         }