@memoarchitect/ontology 0.6.4 → 0.7.0

package/examples/gpca-pump/model/{views → catalog/viewpoints/requirements/views}/requirements_requirements_trace_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_requirements_requirements_trace_view {
+package memo_examples_gpca_pump_viewpoints_requirements_views_requirements_requirements_trace_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -14,7 +14,7 @@ package memo_examples_gpca_pump_model_views_requirements_requirements_trace_view
     private import memo_core_enumerations::*;
 
     view gpcaRequirementsTraceView : MemoDiagramView {
-        expose memo_examples_gpca_pump_model_views_requirements_requirements_trace_view::*;
+        expose memo_examples_gpca_pump_viewpoints_requirements_views_requirements_requirements_trace_view::*;
         attribute depth = 2;
         attribute :>> id = "VIEW-REQ-101";
         attribute :>> name = "GPCA_RequirementsTraceabilityView";

package/examples/gpca-pump/model/catalog/viewpoints/risk/viewpoint.sysml

@@ -0,0 +1,8 @@
+// risk 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_gpca_pump_viewpoints_risk {
+    public import memo_viewpoints_risk_risk_viewpoint::*;
+}

package/examples/gpca-pump/model/{views → catalog/viewpoints/risk/views}/document_hazard_analysis_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_document_hazard_analysis_view {
+package memo_examples_gpca_pump_viewpoints_risk_views_document_hazard_analysis_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -6,12 +6,12 @@ package memo_examples_gpca_pump_model_views_document_hazard_analysis_view {
     private import memo_core_enumerations::*;
 
     view hazardAnalysisView : MemoDocumentView {
-        expose memo_examples_gpca_pump_model_views_document_hazard_analysis_view::*;
+        expose memo_examples_gpca_pump_viewpoints_risk_views_document_hazard_analysis_view::*;
         attribute :>> id = "DOC-009";
         attribute :>> name = "HazardAnalysisReportView";
         attribute :>> title = "GPCA Hazard Analysis Report View";
         attribute :>> shortDescription = "Hazard analysis report aligned to the UMN CriSys GPCA hazard tables.";
-        attribute :>> longDescription = "Aggregates the five hazard chains, the FMEA worksheet, and the overdose fault tree with their controls and verification pointers.";
+        attribute :>> description = "Aggregates the five hazard chains, the FMEA worksheet, and the overdose fault tree with their controls and verification pointers.";
         attribute :>> version = "0.1";
         attribute :>> lifecycleState = LifecycleStateKind::development;
         attribute :>> viewKind = DocumentViewKind::RMF;

package/examples/gpca-pump/model/{views → catalog/viewpoints/risk/views}/document_rmf_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_document_rmf_view {
+package memo_examples_gpca_pump_viewpoints_risk_views_document_rmf_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -6,12 +6,12 @@ package memo_examples_gpca_pump_model_views_document_rmf_view {
     private import memo_core_enumerations::*;
 
     view rmfView : MemoDocumentView {
-        expose memo_examples_gpca_pump_model_views_document_rmf_view::*;
+        expose memo_examples_gpca_pump_viewpoints_risk_views_document_rmf_view::*;
         attribute :>> id = "DOC-001";
         attribute :>> name = "RiskManagementFileView";
         attribute :>> title = "GPCA Risk Management File View";
         attribute :>> shortDescription = "Document-backed risk view for GPCA.";
-        attribute :>> longDescription = "Aggregates the risk chain, controls, verification, residual risk, and cybersecurity links needed for the GPCA risk management file.";
+        attribute :>> description = "Aggregates the risk chain, controls, verification, residual risk, and cybersecurity links needed for the GPCA risk management file.";
         attribute :>> version = "0.2";
         attribute :>> lifecycleState = LifecycleStateKind::development;
         attribute :>> viewKind = DocumentViewKind::RMF;

package/examples/gpca-pump/model/{views → catalog/viewpoints/risk/views}/risk_fmea_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_risk_fmea_view {
+package memo_examples_gpca_pump_viewpoints_risk_views_risk_fmea_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -14,7 +14,7 @@ package memo_examples_gpca_pump_model_views_risk_fmea_view {
     private import memo_core_enumerations::*;
 
     view gpcaFmeaView : MemoDiagramView {
-        expose memo_examples_gpca_pump_model_views_risk_fmea_view::*;
+        expose memo_examples_gpca_pump_viewpoints_risk_views_risk_fmea_view::*;
         attribute depth = 2;
         attribute :>> id = "VIEW-RISK-102";
         attribute :>> name = "GPCA_FmeaView";

package/examples/gpca-pump/model/{views → catalog/viewpoints/risk/views}/risk_risk_chain_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_risk_risk_chain_view {
+package memo_examples_gpca_pump_viewpoints_risk_views_risk_risk_chain_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -14,13 +14,13 @@ package memo_examples_gpca_pump_model_views_risk_risk_chain_view {
     private import memo_core_enumerations::*;
 
     view gpcaRiskChainView : MemoDiagramView {
-        expose memo_examples_gpca_pump_model_views_risk_risk_chain_view::*;
+        expose memo_examples_gpca_pump_viewpoints_risk_views_risk_risk_chain_view::*;
         attribute depth = 2;
         attribute :>> id = "VIEW-RISK-101";
         attribute :>> name = "GPCA_RiskChainView";
         attribute :>> title = "GPCA Risk Mitigation Chain View";
         attribute :>> shortDescription = "All seven hazard causal trees from categorized cause through harm with controls and residual risk.";
-        attribute :>> longDescription = "Opioid over-infusion, under-infusion, air embolism, misprogramming, free-flow, reverse-delivery, and VTBI over-infusion causal trees (GIIP cause-source structure): categorized causes converging on each hazard, sequences of events, hazardous situations, harms, risk estimates, controls, and residual evaluations.";
+        attribute :>> description = "Opioid over-infusion, under-infusion, air embolism, misprogramming, free-flow, reverse-delivery, and VTBI over-infusion causal trees (GIIP cause-source structure): categorized causes converging on each hazard, sequences of events, hazardous situations, harms, risk estimates, controls, and residual evaluations.";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::blockDiagram);
         attribute :>> viewKind = DiagramViewKind::general;

package/examples/gpca-pump/model/catalog/viewpoints/software/viewpoint.sysml

@@ -0,0 +1,8 @@
+// software 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_gpca_pump_viewpoints_software {
+    public import memo_viewpoints_software_software_viewpoint::*;
+}

package/examples/gpca-pump/model/{views → catalog/viewpoints/software/views}/document_sdd_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_document_sdd_view {
+package memo_examples_gpca_pump_viewpoints_software_views_document_sdd_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -6,12 +6,12 @@ package memo_examples_gpca_pump_model_views_document_sdd_view {
     private import memo_core_enumerations::*;
 
     view sddView : MemoDocumentView {
-        expose memo_examples_gpca_pump_model_views_document_sdd_view::*;
+        expose memo_examples_gpca_pump_viewpoints_software_views_document_sdd_view::*;
         attribute :>> id = "DOC-004";
         attribute :>> name = "SoftwareDesignDescriptionView";
         attribute :>> title = "GPCA Software Design Description View";
         attribute :>> shortDescription = "IEC 62304 software design description for the GPCA software system.";
-        attribute :>> longDescription = "Aggregates the software system, its six components with safety classes and scheduling attributes, mode machine and transitions, interfaces, and function allocations for the SDD.";
+        attribute :>> description = "Aggregates the software system, its six components with safety classes and scheduling attributes, mode machine and transitions, interfaces, and function allocations for the SDD.";
         attribute :>> version = "0.1";
         attribute :>> lifecycleState = LifecycleStateKind::development;
         attribute :>> viewKind = DocumentViewKind::SDD;

package/examples/gpca-pump/model/{views → catalog/viewpoints/software/views}/software_software_architecture_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_software_software_architecture_view {
+package memo_examples_gpca_pump_viewpoints_software_views_software_software_architecture_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -14,13 +14,13 @@ package memo_examples_gpca_pump_model_views_software_software_architecture_view
     private import memo_core_enumerations::*;
 
     view gpcaSoftwareArchitectureView : MemoDiagramView {
-        expose memo_examples_gpca_pump_model_views_software_software_architecture_view::*;
+        expose memo_examples_gpca_pump_viewpoints_software_views_software_software_architecture_view::*;
         attribute depth = 2;
         attribute :>> id = "VIEW-SW-101";
         attribute :>> name = "GPCA_SoftwareArchitectureView";
         attribute :>> title = "GPCA Software Architecture View";
         attribute :>> shortDescription = "The eight AADL GPCA_SW.Impl subcomponents, top-level ports, and the full inter-component connection topology.";
-        attribute :>> longDescription = "Top_Level_Mode, System_Status, Alarm, Config, Infusion_Manager, System_Monitor, Logging, and OutputBus inside the GPCA_Software system, wired per GPCA_SW.Impl with the seven top-level ports (OP_CMD_IN, PRES_IN, PATIENT_IN, SENSOR_IN, CONST_IN, DB_IN, GPCA_SW_OUT). Connections are synchronous with AADL immediate port semantics.";
+        attribute :>> description = "Top_Level_Mode, System_Status, Alarm, Config, Infusion_Manager, System_Monitor, Logging, and OutputBus inside the GPCA_Software system, wired per GPCA_SW.Impl with the seven top-level ports (OP_CMD_IN, PRES_IN, PATIENT_IN, SENSOR_IN, CONST_IN, DB_IN, GPCA_SW_OUT). Connections are synchronous with AADL immediate port semantics.";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::internalDiagram);
         attribute :>> viewKind = DiagramViewKind::interconnection;

package/examples/gpca-pump/model/catalog/viewpoints/usability/viewpoint.sysml

@@ -0,0 +1,8 @@
+// usability 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_gpca_pump_viewpoints_usability {
+    public import memo_viewpoints_usability_usability_viewpoint::*;
+}

package/examples/gpca-pump/model/{views → catalog/viewpoints/usability/views}/document_usability_view.sysml

@@ -1,18 +1,18 @@
-package memo_examples_gpca_pump_model_views_document_usability_view {
+package memo_examples_gpca_pump_viewpoints_usability_views_document_usability_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
-    private import memo_viewpoints_usability_usability_engineering_view::*;
+    private import memo_viewpoints_usability_views_usability_engineering_view::*;
     private import memo_viewpoints_usability_usability_viewpoint::*;
     private import memo_core_enumerations::*;
 
     view usabilityView : MemoUsabilityEngineeringView {
-        expose memo_examples_gpca_pump_model_views_document_usability_view::*;
+        expose memo_examples_gpca_pump_viewpoints_usability_views_document_usability_view::*;
         attribute :>> id = "DOC-008";
         attribute :>> name = "UsabilityEngineeringFileView";
         attribute :>> title = "GPCA Usability Engineering File View";
         attribute :>> shortDescription = "IEC 62366-1 usability engineering file content for GPCA.";
-        attribute :>> longDescription = "Aggregates intended use, use contexts, actors, foreseeable use errors, related risk chains, usability requirements, and the summative usability validation case.";
+        attribute :>> description = "Aggregates intended use, use contexts, actors, foreseeable use errors, related risk chains, usability requirements, and the summative usability validation case.";
         attribute :>> version = "0.1";
         attribute :>> lifecycleState = LifecycleStateKind::development;
         attribute :>> marketScope = "generic";

package/examples/gpca-pump/model/catalog/viewpoints/verification/viewpoint.sysml

@@ -0,0 +1,8 @@
+// verification 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_gpca_pump_viewpoints_verification {
+    public import memo_viewpoints_verification_verification_viewpoint::*;
+}

package/examples/gpca-pump/model/{views → catalog/viewpoints/verification/views}/document_vv_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_document_vv_view {
+package memo_examples_gpca_pump_viewpoints_verification_views_document_vv_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -6,12 +6,12 @@ package memo_examples_gpca_pump_model_views_document_vv_view {
     private import memo_core_enumerations::*;
 
     view vvView : MemoDocumentView {
-        expose memo_examples_gpca_pump_model_views_document_vv_view::*;
+        expose memo_examples_gpca_pump_viewpoints_verification_views_document_vv_view::*;
         attribute :>> id = "DOC-006";
         attribute :>> name = "VerificationValidationView";
         attribute :>> title = "GPCA Verification and Validation View";
         attribute :>> shortDescription = "V&V plan and coverage for requirements and risk controls.";
-        attribute :>> longDescription = "Aggregates verification cases, validation cases, test artifacts, and evidence with their coverage of requirements, risk controls, behavior properties, and timing constraints.";
+        attribute :>> description = "Aggregates verification cases, validation cases, test artifacts, and evidence with their coverage of requirements, risk controls, behavior properties, and timing constraints.";
         attribute :>> version = "0.1";
         attribute :>> lifecycleState = LifecycleStateKind::development;
         attribute :>> viewKind = DocumentViewKind::VV;

package/examples/gpca-pump/model/{views → catalog/viewpoints/verification/views}/verification_verification_coverage_view.sysml

@@ -1,4 +1,4 @@
-package memo_examples_gpca_pump_model_views_verification_verification_coverage_view {
+package memo_examples_gpca_pump_viewpoints_verification_views_verification_verification_coverage_view {
     private import ScalarValues::*;
 
     private import memo_viewpoints_definitions::*;
@@ -14,7 +14,7 @@ package memo_examples_gpca_pump_model_views_verification_verification_coverage_v
     private import memo_core_enumerations::*;
 
     view gpcaVerificationCoverageView : MemoDiagramView {
-        expose memo_examples_gpca_pump_model_views_verification_verification_coverage_view::*;
+        expose memo_examples_gpca_pump_viewpoints_verification_views_verification_verification_coverage_view::*;
         attribute depth = 2;
         attribute :>> id = "VIEW-VER-101";
         attribute :>> name = "GPCA_VerificationCoverageView";

package/examples/ivd-laboratory-system/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Ivd Laboratory System — 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_ivd_laboratory_system_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_ivd_laboratory_system_viewpoints_unassigned::*;
+    private import memo_examples_ivd_laboratory_system_viewpoints_unassigned_views_ivd_laboratory_system_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-LABORATORY-SYSTEM-001";
+        attribute :>> name = "IvdLaboratorySystemProjectMethodBinding";
+        attribute :>> projectName = "Ivd Laboratory System";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/ivd-laboratory-system/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_ivd_laboratory_system_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/ivd-laboratory-system/model/{viewpoints → catalog/viewpoints/unassigned/views}/ivd_laboratory_system_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_ivd_laboratory_system_viewpoints {
+package memo_examples_ivd_laboratory_system_viewpoints_unassigned_views_ivd_laboratory_system_overview {
     private import memo_examples_ivd_laboratory_system::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

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

@@ -5,6 +5,7 @@ package memo_examples_manual_surgical_instrument {
     private import ScalarValues::*;
 
     private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
     private import memo_architecture_operational_activities::*;
     private import memo_architecture_implementation_hardware_structure::*;
 

package/examples/manual-surgical-instrument/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Manual Surgical Instrument — 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_manual_surgical_instrument_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_manual_surgical_instrument_viewpoints_unassigned::*;
+    private import memo_examples_manual_surgical_instrument_viewpoints_unassigned_views_manual_surgical_instrument_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-SURGICAL-INSTRUMENT-001";
+        attribute :>> name = "ManualSurgicalInstrumentProjectMethodBinding";
+        attribute :>> projectName = "Manual Surgical Instrument";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/manual-surgical-instrument/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_manual_surgical_instrument_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/manual-surgical-instrument/model/{viewpoints → catalog/viewpoints/unassigned/views}/manual_surgical_instrument_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_manual_surgical_instrument_viewpoints {
+package memo_examples_manual_surgical_instrument_viewpoints_unassigned_views_manual_surgical_instrument_overview {
     private import memo_examples_manual_surgical_instrument::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

package/examples/multidimensional-layers/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Multidimensional Layers — 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_multidimensional_layers_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_multidimensional_layers_viewpoints_unassigned::*;
+    private import memo_examples_multidimensional_layers_viewpoints_unassigned_views_multidimensional_layers_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-MULTIDIMENSIONAL-LAYERS-001";
+        attribute :>> name = "MultidimensionalLayersProjectMethodBinding";
+        attribute :>> projectName = "Multidimensional Layers";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/multidimensional-layers/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_multidimensional_layers_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/multidimensional-layers/model/{viewpoints → catalog/viewpoints/unassigned/views}/multidimensional_layers_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_multidimensional_layers_viewpoints {
+package memo_examples_multidimensional_layers_viewpoints_unassigned_views_multidimensional_layers_overview {
     private import memo_examples_multidimensional_layers::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

package/examples/nested-architecture-dsm/README.md

@@ -0,0 +1,49 @@
+# Nested Architecture DSM
+
+A small infusion-pump model whose only purpose is to exercise the two matrix
+analyses — the Design Structure Matrix and the Traceability Matrix — with a
+hierarchy deep enough that expanding and collapsing changes what you see.
+
+## What is in it
+
+| Axis material | Elements | Nesting |
+| --- | --- | --- |
+| Logical structure | 1 system, 5 subsystems, 12 components | 4 levels (`System → Subsystem → Subsystem → LogicalComponent`) |
+| Functional architecture | 18 system functions | 3 levels, four capability trees |
+| Requirements | 7 requirements | flat |
+
+Nesting is declared with `Composes`, so both matrices build their trees from
+the model rather than from a naming convention.
+
+## What it is set up to show
+
+- **Roll-up.** `SafetyMonitorSubsystem` sits one level deeper than its peers, so
+  a collapsed `ControlSubsystem` row genuinely sums its descendants instead of
+  standing in for a single child.
+- **Feedback.** `DriveActuator` and `MeasureDeliveredVolume` exchange in both
+  directions, so a partitioned DSM still shows one real feedback mark rather
+  than an empty lower triangle.
+- **Cross-tree dependency.** `EnforceDoseLimits → DriveActuator` and
+  `SelectPowerSource → DriveActuator` cross capability trees, which is what a
+  collapsed matrix rolls into a single number between two capabilities.
+- **Asymmetric axes.** Functions on the rows and blocks on the columns, joined
+  by `AllocatedTo` — including `MeterFluid → FluidPathSubsystem`, an allocation
+  made at subsystem level rather than to one component.
+- **A traceability gap.** `StatusVisibility` is satisfied by nothing, so
+  coverage reads under 100% and there is an empty row to author a link into.
+
+## Suggested run
+
+```bash
+memo-architect --example nested-architecture-dsm
+```
+
+In **DSM**: set rows and columns to `SystemFunction`, dependency to
+`exchangesWith`, and switch ordering between *Name* and *Partition* — the
+feedback count drops and one mark stays below the diagonal. Then set columns to
+the logical kinds and dependency to `allocatedTo` for the allocation view.
+
+In **Traceability**: rows `Requirement`, columns `SystemFunction`, trace via
+`satisfiedBy`. Turn on **Edit links** and click the empty `StatusVisibility` row
+to author the missing trace; it is written back to
+`model/catalog/traces.sysml`.

package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml

@@ -0,0 +1,174 @@
+// Functional architecture — the row axis of the DSM.
+//
+// Four capability trees, each decomposed with Composes, plus the functional
+// exchanges between the leaves. The exchanges are deliberately not a clean
+// pipeline: DriveActuator and MeasureDeliveredVolume feed each other, so a
+// partitioned DSM still shows one genuine feedback mark instead of an empty
+// lower triangle.
+package memo_examples_nested_architecture_dsm_architecture_functional_functions {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
+    private import memo_architecture_functional_functions::*;
+
+    // ── Deliver therapy ──────────────────────────────────────────
+    part fnDeliverTherapy : SystemFunction {
+        attribute :>> id = "NDS-FN-001"; attribute :>> name = "DeliverTherapy";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "fluid delivered to the patient line at the prescribed rate";
+    }
+    part fnMeterFluid : SystemFunction {
+        attribute :>> id = "NDS-FN-002"; attribute :>> name = "MeterFluid";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "measured volume displaced per control period";
+    }
+    part fnDriveActuator : SystemFunction {
+        attribute :>> id = "NDS-FN-003"; attribute :>> name = "DriveActuator";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "rate command from the dose control loop";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnMeasureDelivered : SystemFunction {
+        attribute :>> id = "NDS-FN-004"; attribute :>> name = "MeasureDeliveredVolume";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "cumulative delivered volume";
+    }
+    part fnControlDose : SystemFunction {
+        attribute :>> id = "NDS-FN-005"; attribute :>> name = "ControlDose";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnComputeRate : SystemFunction {
+        attribute :>> id = "NDS-FN-006"; attribute :>> name = "ComputeInfusionRate";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "rate command, saturated at the prescribed ceiling";
+    }
+    part fnValidatePrescription : SystemFunction {
+        attribute :>> id = "NDS-FN-007"; attribute :>> name = "ValidatePrescription";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::clinical;
+        attribute :>> outputSummary = "accepted or rejected prescription, with the reason";
+    }
+    connection : Composes connect parent ::> fnDeliverTherapy to child ::> fnMeterFluid;
+    connection : Composes connect parent ::> fnDeliverTherapy to child ::> fnControlDose;
+    connection : Composes connect parent ::> fnMeterFluid to child ::> fnDriveActuator;
+    connection : Composes connect parent ::> fnMeterFluid to child ::> fnMeasureDelivered;
+    connection : Composes connect parent ::> fnControlDose to child ::> fnComputeRate;
+    connection : Composes connect parent ::> fnControlDose to child ::> fnValidatePrescription;
+
+    // ── Ensure safety ────────────────────────────────────────────
+    part fnEnsureSafety : SystemFunction {
+        attribute :>> id = "NDS-FN-008"; attribute :>> name = "EnsureSafety";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnDetectOcclusion : SystemFunction {
+        attribute :>> id = "NDS-FN-009"; attribute :>> name = "DetectOcclusion";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "line pressure above the occlusion threshold";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnDetectAirInLine : SystemFunction {
+        attribute :>> id = "NDS-FN-010"; attribute :>> name = "DetectAirInLine";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "air bolus detected in the patient line";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnEnforceDoseLimits : SystemFunction {
+        attribute :>> id = "NDS-FN-011"; attribute :>> name = "EnforceDoseLimits";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "delivery stopped when the commanded dose leaves the accepted envelope";
+    }
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnDetectOcclusion;
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnDetectAirInLine;
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnEnforceDoseLimits;
+
+    // ── Inform the user ──────────────────────────────────────────
+    part fnInformUser : SystemFunction {
+        attribute :>> id = "NDS-FN-012"; attribute :>> name = "InformUser";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+    }
+    part fnRenderStatus : SystemFunction {
+        attribute :>> id = "NDS-FN-013"; attribute :>> name = "RenderTherapyStatus";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+        attribute :>> outputSummary = "rate, volume delivered and time remaining";
+    }
+    part fnAnnunciateAlarm : SystemFunction {
+        attribute :>> id = "NDS-FN-014"; attribute :>> name = "AnnunciateAlarm";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "any active alarm condition";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnAcceptInput : SystemFunction {
+        attribute :>> id = "NDS-FN-015"; attribute :>> name = "AcceptClinicianInput";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+        attribute :>> outputSummary = "confirmed prescription changes";
+    }
+    connection : Composes connect parent ::> fnInformUser to child ::> fnRenderStatus;
+    connection : Composes connect parent ::> fnInformUser to child ::> fnAnnunciateAlarm;
+    connection : Composes connect parent ::> fnInformUser to child ::> fnAcceptInput;
+
+    // ── Manage power ─────────────────────────────────────────────
+    part fnManagePower : SystemFunction {
+        attribute :>> id = "NDS-FN-016"; attribute :>> name = "ManagePower";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::reliability;
+    }
+    part fnMonitorBattery : SystemFunction {
+        attribute :>> id = "NDS-FN-017"; attribute :>> name = "MonitorBatteryState";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::reliability;
+        attribute :>> outputSummary = "state of charge and remaining run time";
+    }
+    part fnSelectPowerSource : SystemFunction {
+        attribute :>> id = "NDS-FN-018"; attribute :>> name = "SelectPowerSource";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> trigger = "mains loss or rail brownout";
+        attribute :>> concernKind = ConcernKind::reliability;
+    }
+    connection : Composes connect parent ::> fnManagePower to child ::> fnMonitorBattery;
+    connection : Composes connect parent ::> fnManagePower to child ::> fnSelectPowerSource;
+
+    // ── Functional exchange ──────────────────────────────────────
+    // Cross-tree marks are the interesting ones: they are what a collapsed DSM
+    // rolls up into a single number between two capabilities.
+    connection : ExchangesWith connect source ::> fnMeasureDelivered to target ::> fnComputeRate;
+    connection : ExchangesWith connect source ::> fnComputeRate to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnDriveActuator to target ::> fnMeasureDelivered;
+    connection : ExchangesWith connect source ::> fnValidatePrescription to target ::> fnComputeRate;
+    connection : ExchangesWith connect source ::> fnAcceptInput to target ::> fnValidatePrescription;
+    connection : ExchangesWith connect source ::> fnDetectOcclusion to target ::> fnEnforceDoseLimits;
+    connection : ExchangesWith connect source ::> fnDetectAirInLine to target ::> fnAnnunciateAlarm;
+    connection : ExchangesWith connect source ::> fnEnforceDoseLimits to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnMeasureDelivered to target ::> fnRenderStatus;
+    connection : ExchangesWith connect source ::> fnMonitorBattery to target ::> fnAnnunciateAlarm;
+    connection : ExchangesWith connect source ::> fnSelectPowerSource to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnDetectOcclusion to target ::> fnAnnunciateAlarm;
+}