@memoarchitect/ontology 0.8.22 → 0.10.9

package/src/core/common/memo_common.sysml

@@ -34,6 +34,56 @@ package memo_core_common {
     private import memo_core_terminology::*;
     private import memo_core_enumerations::*;
 
+    // The metaclass-agnostic carrier for MEMO's identity fields.
+    //
+    // A `metadata def` annotates an element of ANY metaclass — restriction is
+    // opt-in through `annotatedElement`, and this one declares none. That is
+    // what the per-metaclass base definitions below cannot do: KerML will not
+    // let an action, port, item, requirement or connection inherit from a part
+    // def, which is why the identification core is currently declared ten
+    // times. Metadata has no such limit, so one declaration replaces ten.
+    //
+    // An element has five identities and they are not interchangeable:
+    //
+    //   1. code reference   `sfnAcquireMap`        native declaredName
+    //   2. display label    "Acquire EA Map"       `label`, below
+    //   3. number id        `SFN-1`                assigned, never authored
+    //   4. provided id      `SPEC-4471`            `providedId`, below
+    //   5. technical uuid   `e2f75cf6-…`           `uuid`, below
+    //
+    // 1 is native and needs no field here. 3 is generated by the compiler and
+    // recorded in `memo.identity.yaml`: it is monotonic, gaps are kept, and a
+    // retired number is never reused, so nothing authors it by hand.
+    //
+    // `label` is NOT a duplicate of the native name, which is the reading that
+    // nearly deleted it: the native name is a lowerCamelCase identifier and
+    // must be unique in its namespace, while a label is free text that
+    // legitimately repeats — measured 2026-08-18, 1278 labels across the
+    // ontology and examples share only 1216 distinct values, because seven
+    // different ports are all correctly labelled "TLM_MODE_IN". A label
+    // therefore cannot live in a name slot, native or otherwise.
+    //
+    // `providedId` is the identifier an EXTERNAL system knows the element by,
+    // and it exists because that system's scheme is not MEMO's: a customer
+    // numbering software requirements `SPEC-4471` cannot be made to use `SWR-`,
+    // and overwriting the generated number to please them would break the
+    // guarantee that numbers are never reassigned.
+    //
+    // `uuid` is machine identity. Authored values win over the registry, which
+    // wins over derivation — so an element whose file must move can pin its own
+    // uuid, which is what the attribute always advertised.
+    //
+    // Deliberately absent: `name` and `description` (native name and `doc`),
+    // `rationale` (standard `@Rationale`), and `id` — superseded by the
+    // generated number id and by `providedId`.
+    metadata def MemoIdentity {
+        attribute label : String[0..1];
+        attribute providedId : String[0..1];
+        attribute uuid : String[0..1];
+        attribute shortDescription : String[0..1];
+        attribute sourceReference : String[0..1];
+    }
+
     // ─── Single abstract part root ──────────────────────────────────
     // Every structural MEMO concept specializes MemoPart. Identity and
     // traceability are attributes of this one root — MEMO has no separate
@@ -48,8 +98,6 @@ package memo_core_common {
     // cross-cutting concern, and editorial status.
     abstract part def MemoPart {
         // identity
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
         // Two description registers on every MEMO element, because views have
         // two densities. `shortDescription` is the one-line form a table cell,
@@ -58,11 +106,8 @@ package memo_core_common {
         // renders. A view picks the register that fits — it never truncates
         // the long one, because a silently clipped sentence in a DHF table is
         // a defect, not a layout choice.
-        attribute shortDescription : String;
         attribute description : String;
         // traceability
-        attribute rationale : String;
-        attribute sourceReference : String;
         // editorial status and lifecycle
         attribute status : ElementStatusKind;
         attribute lifecycleState : LifecycleStateKind;
@@ -78,7 +123,6 @@ package memo_core_common {
     //     MemoPart so all existing content inherits the dimensions. ───
     part def RequirementDriver specializes MemoPart;
     abstract part def VerifiableElement specializes MemoPart;
-    abstract part def ArchitectureElement specializes MemoPart;
     part def InterfaceElement specializes MemoPart;
     enum def EvidenceKind { enum testArtifact; enum evidence; enum formativeEvaluation; enum usabilityValidation; enum securityClaim; }
     part def MemoEvidence specializes MemoPart {
@@ -108,10 +152,15 @@ package memo_core_common {
     // description registers every MemoPart now carries: a title and its place
     // in a document. The former `shortDescription`/`longDescription` pair is
     // gone — short is inherited, and `description` IS the long form.
-    part def DocumentedElement specializes MemoPart {
-        attribute title : String;
-        attribute documentUsage : String[*];
-        attribute sectionIdentifier : String;
+    // Top-level goal a system or operation exists to fulfil, with its success
+    // criteria and context. Domain layers specialize it; the medical-device
+    // intended use (memo_architecture_operational_structure::IntendedUse) is a
+    // MemoMission. Specializes MemoPart directly — name/description/rationale
+    // already live there, so no DocumentedElement layer is needed.
+    abstract part def MemoMission specializes MemoPart {
+        attribute missionKind : String;
+        attribute successCriteria : String;
+        attribute operationalContext : String;
     }
 
     // ─── Construct-specific foundations (non-part metaclasses) ───────
@@ -119,25 +168,15 @@ package memo_core_common {
     // Behavioral foundation: operational activities, tasks, system actions,
     // and interaction steps specialize MemoAction.
     action def MemoAction {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
     }
 
     // Boundary feature foundation for typed ports.
     port def MemoPort {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
     }
 
@@ -145,13 +184,8 @@ package memo_core_common {
     abstract interface def MemoInterface {
         end source;
         end target;
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
     }
 
     // Single item foundation. Standards, hazards, stored software data, and
@@ -159,13 +193,8 @@ package memo_core_common {
     // exchanged is expressed by its use in a port or flow, not by a second
     // ontology root.
     abstract item def MemoItem {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
         // What the item CARRIES, as distinct from what it is called. Removed
         // by `595bfac` while modelling native wrappers; nothing replaced them,
@@ -186,26 +215,16 @@ package memo_core_common {
     // references; identity is carried here so use cases do not maintain a
     // partial hand-written copy of the MEMO identification core.
     abstract use case def MemoUseCase {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
     }
 
     // General constraint foundation. Executable consistency rules and
     // reusable quantitative constraints are both native constraint defs.
     abstract constraint def MemoConstraint {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
     }
 
@@ -216,13 +235,8 @@ package memo_core_common {
     // say "a need or a requirement" with one type name — before it, every end
     // that had to accept both was left untyped.
     abstract requirement def MemoRequirementElement {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
         attribute statement : String;
     }
@@ -241,13 +255,8 @@ package memo_core_common {
     // the part-based MemoPart — so, like MemoAction, it re-declares the small
     // identification core rather than inheriting it.
     verification def MemoVerificationCase {
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
     }
 
@@ -260,13 +269,8 @@ package memo_core_common {
 
     state def MemoState {
         attribute stateKind : StateKind;
-        attribute id : String;
-        attribute uuid : String;
         attribute name : String;
-        attribute shortDescription : String;
         attribute description : String;
-        attribute rationale : String;
-        attribute sourceReference : String;
         attribute status : ElementStatusKind;
         attribute modeKind : String;
         attribute entryCondition : String;

package/src/core/enumerations/memo_enumerations.sysml

@@ -142,7 +142,7 @@ package memo_core_enumerations {
         enum maintenance;
         enum obsolete;
     }
-    enum def VerificationMethodKind {
+    enum def MemoVerificationMethodKind {
         enum inspection;
         enum analytical;
         enum demonstration;

package/src/core/relationships/memo_relationships.sysml

@@ -7,6 +7,7 @@ package memo_core_relationships {
     private import memo_core_common::*;
     private import memo_core_enumerations::*;
 
+    private import Allocations::Allocation;
     // All MEMO relations are native SysML v2 `connection def`s (each is a
     // Connection/Association), specializing the MemoRelationship base. The
     // relationship name is the verb; the RelationshipRegistry derives the
@@ -79,12 +80,12 @@ package memo_core_relationships {
     // SystemFunction a part def with its behaviour stapled on through a
     // separate action def, and what makes `allocate <function> to <actor>` —
     // ARCADIA's own System Analysis mechanism — illegal, since Actor is a
-    // MemoPart but not an ArchitectureElement.
+    // MemoPart but not a narrower part subtype.
     //
     // Several of the relaxed ends were ALREADY being violated by real content
-    // before they were relaxed: `composes` links parts to WorkflowStep and
-    // OperationalActivity (action defs) and to SoftwarePort/PhysicalPort;
-    // `precedes` links OperationalActivity to OperationalActivity; `allocatedTo`
+    // before they were relaxed: `composes` links parts to OperativeAction
+    // (an action def) and to SoftwarePort/PhysicalPort;
+    // `precedes` links OperativeAction to OperativeAction; `allocatedTo`
     // has ActionUsage sources; `bindsToInterface` targets an `interface def`,
     // which an InterfaceElement-typed end cannot hold. The types were not
     // buying the strictness they appeared to buy.
@@ -107,17 +108,6 @@ package memo_core_relationships {
     // only when no specific relation carries the meaning, and say why in the
     // inherited `rationale` — an untyped link with no stated reason is an
     // audit gap, not a model fact.
-    connection def MemoLink :> MemoRelationship {
-        doc /* Generic association between any two model elements. */
-        end linkSource :>> source;
-        end linkTarget :>> target;
-    }
-    abstract connection memoLinkLinks : MemoLink[*];
-    metadata def <memoLink> MemoLinkMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = memoLinkLinks meta SysML::Usage;
-    }
 
     connection def DerivesFrom :> MemoRelationship {
         // Drivers span metaclasses — a need is a requirement def, a hazard an
@@ -160,7 +150,7 @@ package memo_core_relationships {
 
     connection def ThreatenedBy :> MemoRelationship {
         attribute threatRole : String;
-        end protectedAsset : ArchitectureElement :>> source;
+        end protectedAsset : MemoPart :>> source;
         end realizedThreat : RequirementDriver :>> target;
     }
     abstract connection threatenedByLinks : ThreatenedBy[*];
@@ -206,57 +196,40 @@ package memo_core_relationships {
 
     // Enables unifies the former EnablesWorkflow / EnablesActivity synonyms
     // (an enabling system/function enables a workflow/activity).
-    connection def Enables :> MemoRelationship {
-        end enabling :>> source;
-        end enabled : MemoAction :>> target;
-    }
-    abstract connection enablesLinks : Enables[*];
-    metadata def <enables> EnablesMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = enablesLinks meta SysML::Usage;
-    }
+    // `Enables` is native `dependency` (2026-08-18): write
+    // `dependency from <enabling> to <enabled>;`. Same call as `Supports`,
+    // which was deleted as a duplicate of both `dependency` and `Enables`.
 
-    connection def HostedBy :> MemoRelationship {
-        end processingNode : ArchitectureElement :>> source;
-        end hostAssembly : ArchitectureElement :>> target;
+        // A processing node hosted by an assembly is allocated to it. The end
+    // NAMES were already right; two of the three usages wrote them in reverse
+    // order, and the builder binds by position, so those two edges pointed the
+    // wrong way. See the reversed-end-name lint in memo-tools.
+    allocation def HostedBy :> MemoRelationship, Allocations::Allocation {
+        end processingNode : MemoPart :>> source;
+        end hostAssembly : MemoPart :>> target;
     }
     abstract connection hostedByLinks : HostedBy[*];
     metadata def <hostedBy> HostedByMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
+        :> annotatedElement : SysML::AllocationDefinition;
+        :> annotatedElement : SysML::AllocationUsage;
         :>> baseType = hostedByLinks meta SysML::Usage;
     }
 
 
 
 
-    // Composes is the single whole/part decomposition relation. It unifies the
-    // former ComposesLogical / AssemblyComprises / Contains{Component,Element} /
-    // {Workflow,Task,Activity,Scenario}Comprises* / FlowComprisesSpec /
-    // Collection membership is carried by the end instance.
-    // types, so the ends are generic MemoPart.
-    connection def Composes :> MemoRelationship {
-        end parent :>> source;
-        end child :>> target;
-    }
-    abstract connection composesLinks : Composes[*];
-    metadata def <composes> ComposesMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = composesLinks meta SysML::Usage;
-    }
+    // `Composes` is deleted (R10-S7). Containment is NESTING — the child is
+    // declared inside the parent — which is how SysML v2 models composition:
+    // composite feature ownership, not a link. The relation specialized
+    // `Connections::BinaryConnection`, "a link between two things WITHIN some
+    // containing structure", so it was the wrong category for the containment
+    // itself, and the corpus has no composition connection to specialize.
+    //
+    // Nothing is lost: the builder synthesizes a `composes` edge from every
+    // nested part and item, so rules, the DSM and traceability read exactly the
+    // graph they read before. The edge type is registered natively in
+    // memo-tools' relationship registry.
 
-    connection def AnalyzedBy :> MemoRelationship {
-        end element : ArchitectureElement :>> source;
-        end analysisArtifact : AnalysisArtifact :>> target;
-    }
-    abstract connection analyzedByLinks : AnalyzedBy[*];
-    metadata def <analyzedBy> AnalyzedByMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = analyzedByLinks meta SysML::Usage;
-    }
 
     connection def BindsToInterface :> MemoRelationship {
         end portElement :>> source;

package/src/methodology/archetypes/memo_archetypes.sysml

@@ -3,8 +3,10 @@ package memo_methodology_archetypes {
 
     private import memo_methodology_core::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part minimal : Archetype {
-        attribute :>> id = "ARCH-MINIMAL";
+        @MemoIdentity { :>> providedId = "ARCH-MINIMAL"; }
         attribute :>> name = "Minimal";
         attribute :>> label = "Minimal";
         attribute :>> description = "Core ontology only — requirements, hazards, basic architecture (~53 kinds)";
@@ -15,7 +17,7 @@ package memo_methodology_archetypes {
     }
 
     part standardArchetype : Archetype {
-        attribute :>> id = "ARCH-STANDARD";
+        @MemoIdentity { :>> providedId = "ARCH-STANDARD"; }
         attribute :>> name = "Standard";
         attribute :>> label = "Standard";
         attribute :>> description = "Core + risk + software + DHF — covers most Class II devices (~120 kinds)";
@@ -26,7 +28,7 @@ package memo_methodology_archetypes {
     }
 
     part full : Archetype {
-        attribute :>> id = "ARCH-FULL";
+        @MemoIdentity { :>> providedId = "ARCH-FULL"; }
         attribute :>> name = "Full";
         attribute :>> label = "Full";
         attribute :>> description = "All architecture layers, standards, and extensions (~200+ kinds)";
@@ -37,7 +39,7 @@ package memo_methodology_archetypes {
     }
 
     part samd : Archetype {
-        attribute :>> id = "ARCH-SAMD";
+        @MemoIdentity { :>> providedId = "ARCH-SAMD"; }
         attribute :>> name = "SaMD";
         attribute :>> label = "Software as Medical Device (SaMD)";
         attribute :>> description = "Clinical decision support, diagnostic algorithm, AI/ML tool, mobile medical app";
@@ -48,7 +50,7 @@ package memo_methodology_archetypes {
     }
 
     part connected : Archetype {
-        attribute :>> id = "ARCH-CONNECTED";
+        @MemoIdentity { :>> providedId = "ARCH-CONNECTED"; }
         attribute :>> name = "Connected";
         attribute :>> label = "Connected / IoT Device";
         attribute :>> description = "Remote monitoring, wearable, smart device with cloud connectivity and cybersecurity requirements";
@@ -59,7 +61,7 @@ package memo_methodology_archetypes {
     }
 
     part monitoring : Archetype {
-        attribute :>> id = "ARCH-MONITORING";
+        @MemoIdentity { :>> providedId = "ARCH-MONITORING"; }
         attribute :>> name = "Monitoring";
         attribute :>> label = "Monitoring / Diagnostic Device";
         attribute :>> description = "Patient monitor, ECG, SpO2, vital signs, bedside diagnostic equipment";
@@ -70,7 +72,7 @@ package memo_methodology_archetypes {
     }
 
     part infusion_pump : Archetype {
-        attribute :>> id = "ARCH-INFUSION";
+        @MemoIdentity { :>> providedId = "ARCH-INFUSION"; }
         attribute :>> name = "InfusionPump";
         attribute :>> label = "Infusion / Drug Delivery Device";
         attribute :>> description = "Infusion pump, syringe driver, implantable drug delivery, dosing device";
@@ -81,7 +83,7 @@ package memo_methodology_archetypes {
     }
 
     part blank : Archetype {
-        attribute :>> id = "ARCH-BLANK";
+        @MemoIdentity { :>> providedId = "ARCH-BLANK"; }
         attribute :>> name = "Blank";
         attribute :>> label = "Blank Project";
         attribute :>> description = "Start from scratch with a minimal SysML shell";

package/src/methodology/core/memo_core.sysml

@@ -113,14 +113,4 @@ package memo_methodology_core {
     // ── Relations owned by this package ─────────────────────────────
     // Moved out of memo_core_relationships: their ends are typed against
     // types declared here, and core must not depend on a domain package.
-    connection def ResolvesToMethodology :> MemoRelationship {
-        end boundModelElement : MemoPart :>> source;
-        end resolvedMethodology : MethodologyDefinition :>> target;
-    }
-    abstract connection resolvesToMethodologyLinks : ResolvesToMethodology[*];
-    metadata def <resolvesToMethodology> ResolvesToMethodologyMetadata :> SemanticMetadata {
-        :> annotatedElement : SysML::ConnectionDefinition;
-        :> annotatedElement : SysML::ConnectionUsage;
-        :>> baseType = resolvesToMethodologyLinks meta SysML::Usage;
-    }
 }

package/src/methodology/profiles/memo_profiles.sysml

@@ -9,8 +9,10 @@ package memo_methodology_profiles {
     private import memo_core_enumerations::*;
     private import memo_core_methodology_scope::*;
 
+    private import memo_core_common::*;
+    private import memo_core_common::MemoIdentity;
     part mdCoreLibrary : MethodologyLibrary {
-        attribute :>> id = "METHLIB-001";
+        @MemoIdentity { :>> providedId = "METHLIB-001"; }
         attribute :>> name = "MedicalDeviceMethodologyLibrary";
         attribute :>> version = "0.1";
         attribute :>> domain = "medical device modeling";
@@ -31,7 +33,7 @@ package memo_methodology_profiles {
     // that into `allAvailable` preserves the effective result and removes the
     // second scope authority.
     part mdDefaultDefinition : MethodologyDefinition {
-        attribute :>> id = "METH-MD-DEFAULT";
+        @MemoIdentity { :>> providedId = "METH-MD-DEFAULT"; }
         attribute :>> name = "MedicalDeviceDefault";
         attribute :>> version = "0.6.5";
         attribute :>> domain = "medical device modeling";
@@ -40,7 +42,7 @@ package memo_methodology_profiles {
     }
 
     part useRiskAndResidualRule : ElementUsageRule {
-        attribute :>> id = "RULE-001";
+        @MemoIdentity { :>> providedId = "RULE-001"; }
         attribute :>> name = "UseRiskAndResidualRisk";
         attribute :>> elementTypeName = "Risk,ResidualRisk,RiskMatrix";
         attribute :>> strength = RuleStrengthKind::recommended;
@@ -48,7 +50,7 @@ package memo_methodology_profiles {
     }
 
     part requireVerifiedByRule : RelationUsageRule {
-        attribute :>> id = "RULE-002";
+        @MemoIdentity { :>> providedId = "RULE-002"; }
         attribute :>> name = "VerifiedBysRequired";
         attribute :>> relationTypeName = "verify";
         attribute :>> strength = RuleStrengthKind::required;
@@ -56,7 +58,7 @@ package memo_methodology_profiles {
     }
 
     part lightRiskPattern : ModelingPattern {
-        attribute :>> id = "PAT-001";
+        @MemoIdentity { :>> providedId = "PAT-001"; }
         attribute :>> name = "LightRiskBeforeAfterPattern";
         attribute :>> intent = "Model hazard chain, before/after mitigation risk, controls, and residual evaluation in a lightweight way.";
         attribute :>> stage = WorkflowStageKind::risk;
@@ -64,7 +66,7 @@ package memo_methodology_profiles {
     }
 
     part lightTracePattern : ModelingPattern {
-        attribute :>> id = "PAT-002";
+        @MemoIdentity { :>> providedId = "PAT-002"; }
         attribute :>> name = "CoreTracePattern";
         attribute :>> intent = "Need or risk to requirement, requirement to architecture, requirement/control to verification.";
         attribute :>> stage = WorkflowStageKind::requirements;
@@ -72,7 +74,7 @@ package memo_methodology_profiles {
     }
 
     action stepRequirements : MethodologyWorkflowStep {
-        attribute :>> id = "STEP-001";
+        @MemoIdentity { :>> providedId = "STEP-001"; }
         attribute :>> name = "CaptureRequirements";
         attribute :>> stage = WorkflowStageKind::requirements;
         attribute :>> objectiveDescription = "Capture stakeholder needs and derive requirements.";
@@ -81,7 +83,7 @@ package memo_methodology_profiles {
     }
 
     action stepArchitecture : MethodologyWorkflowStep {
-        attribute :>> id = "STEP-002";
+        @MemoIdentity { :>> providedId = "STEP-002"; }
         attribute :>> name = "DefineArchitecture";
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> objectiveDescription = "Define key software and hardware architecture elements and interfaces.";
@@ -90,7 +92,7 @@ package memo_methodology_profiles {
     }
 
     action stepRisk : MethodologyWorkflowStep {
-        attribute :>> id = "STEP-003";
+        @MemoIdentity { :>> providedId = "STEP-003"; }
         attribute :>> name = "PerformRiskAnalysis";
         attribute :>> stage = WorkflowStageKind::risk;
         attribute :>> objectiveDescription = "Create core risk chain and controls.";
@@ -99,7 +101,7 @@ package memo_methodology_profiles {
     }
 
     action stepVerification : MethodologyWorkflowStep {
-        attribute :>> id = "STEP-004";
+        @MemoIdentity { :>> providedId = "STEP-004"; }
         attribute :>> name = "PlanVerification";
         attribute :>> stage = WorkflowStageKind::verificationStage;
         attribute :>> objectiveDescription = "Define verification and evidence expectations.";
@@ -111,7 +113,7 @@ package memo_methodology_profiles {
     first stepRisk then stepVerification;
 
     part gateLightComplete : QualityGate {
-        attribute :>> id = "GATE-001";
+        @MemoIdentity { :>> providedId = "GATE-001"; }
         attribute :>> name = "LightMethodReady";
         attribute :>> gateStage = WorkflowStageKind::verificationStage;
         attribute :>> passCriteria = "Core traceability, risk, verification, and RMF view support are present.";
@@ -123,7 +125,7 @@ package memo_methodology_profiles {
     // references its methodology with a typed SysML reference.
 
     part rmpDoc : DhfDocumentBinding {
-        attribute :>> id = "DHF-001";
+        @MemoIdentity { :>> providedId = "DHF-001"; }
         attribute :>> name = "RiskManagementPlan";
         attribute :>> documentTitle = "Risk Management Plan";
         attribute :>> groupLabel = "Risk Management";
@@ -135,7 +137,7 @@ package memo_methodology_profiles {
     }
 
     part harDoc : DhfDocumentBinding {
-        attribute :>> id = "DHF-002";
+        @MemoIdentity { :>> providedId = "DHF-002"; }
         attribute :>> name = "HazardAnalysisReport";
         attribute :>> documentTitle = "Hazard Analysis Report";
         attribute :>> groupLabel = "Risk Management";
@@ -147,7 +149,7 @@ package memo_methodology_profiles {
     }
 
     part sadDoc : DhfDocumentBinding {
-        attribute :>> id = "DHF-003";
+        @MemoIdentity { :>> providedId = "DHF-003"; }
         attribute :>> name = "SoftwareArchitectureDescription";
         attribute :>> documentTitle = "Software Architecture Description";
         attribute :>> groupLabel = "Software";
@@ -159,7 +161,7 @@ package memo_methodology_profiles {
     }
 
     part threatModelDoc : DhfDocumentBinding {
-        attribute :>> id = "DHF-004";
+        @MemoIdentity { :>> providedId = "DHF-004"; }
         attribute :>> name = "CybersecurityThreatModel";
         attribute :>> documentTitle = "Threat Model";
         attribute :>> groupLabel = "Cybersecurity";
@@ -171,7 +173,7 @@ package memo_methodology_profiles {
     }
 
     part vvPlanDoc : DhfDocumentBinding {
-        attribute :>> id = "DHF-005";
+        @MemoIdentity { :>> providedId = "DHF-005"; }
         attribute :>> name = "VerificationValidationPlan";
         attribute :>> documentTitle = "V&V Plan";
         attribute :>> groupLabel = "Verification & Validation";

package/src/methodology/workflow/memo_workflow.sysml

@@ -5,11 +5,11 @@ package memo_methodology_workflow {
     private import memo_core_enumerations::*;
 
     // Named for its axis: this is a step in a METHODOLOGY workflow (a lifecycle
-    // stage with entry/exit criteria), distinct from
-    // memo_architecture_operational_workflows::WorkflowStep, which is a step in
-    // an OPERATIONAL workflow performed by users. The two carry different
-    // attributes and must not share a short name — an overloaded name resolves
-    // by load order and silently validates a usage against the wrong type.
+    // stage with entry/exit criteria), distinct from an OPERATIONAL workflow's
+    // steps, which are OperativeActions performed by users or the system. The
+    // two carry different attributes and must not share a short name — an
+    // overloaded name resolves by load order and silently validates a usage
+    // against the wrong type.
     action def MethodologyWorkflowStep :> MemoAction {
         attribute stage : WorkflowStageKind;
         attribute objectiveDescription : String;