@documentation-robotics/cli 0.1.13 → 0.3.0

package/dist/schemas/bundled/product.json

@@ -1,76 +1,29 @@
 {
-  "specVersion": "0.9.0",
+  "specVersion": "0.11.0",
   "layer": {
     "id": "product",
     "number": 3,
     "name": "Product Layer",
-    "description": "Layer 3: Product Layer",
+    "description": "Frames the system from a product-management point of view: the personas it serves, the software capabilities it must possess, the features that deliver them, the user workflows that exercise them and the milestones that schedule delivery. It adapts the ArchiMate 3.2 strategy vocabulary rather than adopting it: a software capability is an ability of the software platform, not ArchiMate's Capability, which is the organization's ability and is modelled as business.businesscapability. Product elements describe what the software offers and to whom, never how it is built. Modelling rules: realization runs upward through product. Application and technology services realize software capabilities and features, views realize features, and navigation flows and flow steps realize user workflows and their steps; product elements in turn realize business behaviour, a software capability realizing the business function it carries out and a user workflow the business process the user performs. A feature realizes the software capabilities it exercises; software capabilities aggregate narrower capabilities, and capabilities and features may depend on their own kind. Features and user workflows serve the personas they are designed for; a persona describes a kind of person, so it references the stakeholder and business role it stands for rather than realizing or serving them. A user workflow composes its steps, steps flow to steps, and each step uses the features it exercises; a workflow reaches features and software capabilities only through its steps. Software capabilities support goals; software capabilities and features satisfy requirements; features deliver value and workflows deliver outcomes. Software capabilities and features are scheduled for milestones, and milestones precede milestones.",
     "inspired_by": {
       "standard": "ArchiMate 3.2 Strategy Extension + Product Management Practice",
       "version": "3.2",
       "url": "https://pubs.opengroup.org/architecture/archimate32-doc/"
     },
     "node_types": [
-      "product.capability",
+      "product.softwarecapability",
       "product.feature",
       "product.milestone",
       "product.persona",
-      "product.userworkflow"
+      "product.userworkflow",
+      "product.workflowstep"
     ]
   },
   "nodeSchemas": {
-    "capability": {
-      "$schema": "http://json-schema.org/draft-07/schema#",
-      "title": "Capability",
-      "description": "An ability the product possesses, independent of how it's implemented",
-      "allOf": [
-        {
-          "$ref": "urn:dr:spec:base:spec-node"
-        }
-      ],
-      "properties": {
-        "spec_node_id": {
-          "const": "product.capability"
-        },
-        "layer_id": {
-          "const": "product"
-        },
-        "type": {
-          "const": "capability"
-        },
-        "attributes": {
-          "type": "object",
-          "properties": {
-            "documentation": {
-              "type": "string",
-              "description": "Detailed description of the capability"
-            },
-            "status": {
-              "type": "string",
-              "enum": [
-                "proposed",
-                "planned",
-                "developing",
-                "delivered",
-                "deprecated"
-              ],
-              "description": "Lifecycle status of the capability"
-            },
-            "properties": {
-              "type": "object",
-              "description": "Cross-layer properties"
-            }
-          },
-          "required": ["status"],
-          "additionalProperties": false
-        }
-      },
-      "$id": "urn:dr:spec:node:product.capability"
-    },
     "feature": {
       "$schema": "http://json-schema.org/draft-07/schema#",
       "title": "Feature",
-      "description": "A user-visible unit of product functionality that delivers one or more capabilities",
+      "description": "A unit of product functionality that a persona can directly perceive and invoke, such as a screen, command, setting or behaviour. It is described in user terms and can be prioritised, sized and scheduled on its own, and it realises one or more software capabilities. Use SoftwareCapability instead when the element names an ability the software must have regardless of which user-visible functionality provides it, and is not itself prioritised or sized as a deliverable. Use UserWorkflow instead when the element is a goal-directed sequence of user actions that passes through one or more features rather than a single piece of functionality. Use WorkflowStep instead when the element is one ordered action or experience within a specific user journey that exercises a feature, rather than the functionality itself. Use Milestone instead when the element is a dated delivery target that groups features, rather than functionality the user interacts with.",
       "allOf": [
         {
           "$ref": "urn:dr:spec:base:spec-node"
@@ -123,12 +76,24 @@
           "additionalProperties": false
         }
       },
+      "x-dr-standard": "Product Management Practice: Feature (backlog/roadmap item). There is no direct ArchiMate 3.2 element; it is modelled as realising a Strategy Capability (§7.3.1).",
+      "x-dr-evidence": [
+        "a feature-flag definition (e.g. LaunchDarkly, Unleash or a features.yml key) that gates a user-visible behaviour such as 'bulk-export' or 'dark-mode'",
+        "a Gherkin .feature file whose 'Feature:' block describes user-facing functionality with acceptance scenarios",
+        "a release-notes, changelog or user-guide entry announcing user-visible functionality (e.g. 'New: export reports to CSV') that is traceable to a set of routes, views or endpoints"
+      ],
+      "x-dr-distinguish": {
+        "product.softwarecapability": "the element names an ability the software must have regardless of which user-visible functionality provides it, and is not itself prioritised or sized as a deliverable",
+        "product.userworkflow": "the element is a goal-directed sequence of user actions that passes through one or more features rather than a single piece of functionality",
+        "product.workflowstep": "the element is one ordered action or experience within a specific user journey that exercises a feature, rather than the functionality itself",
+        "product.milestone": "the element is a dated delivery target that groups features, rather than functionality the user interacts with"
+      },
       "$id": "urn:dr:spec:node:product.feature"
     },
     "milestone": {
       "$schema": "http://json-schema.org/draft-07/schema#",
       "title": "Milestone",
-      "description": "A time-bound delivery target grouping features or capabilities",
+      "description": "A named, time-bound delivery target, such as a release, version or roadmap phase, against which features and software capabilities are scheduled. It is defined by its target date or period and the scope assigned to it, not by any functionality of its own. Use Feature instead when the element is a user-visible unit of functionality being delivered, rather than the dated target or release it is delivered in. Use SoftwareCapability instead when the element names an ability the software has or should have, independent of when it is delivered, rather than a scheduled delivery point.",
       "allOf": [
         {
           "$ref": "urn:dr:spec:base:spec-node"
@@ -167,12 +132,22 @@
           "additionalProperties": false
         }
       },
+      "x-dr-standard": "ArchiMate 3.2 §12.2.4 Plateau (closest analogue; partly §12.2.3 Implementation Event). The Strategy Layer has no direct equivalent.",
+      "x-dr-evidence": [
+        "An issue-tracker milestone or fixVersion (e.g. a GitHub milestone, Jira release) with a due date and a set of linked feature issues.",
+        "A ROADMAP.md or planning document section headed by a version or quarter (e.g. 'v2.0 — Q3 2025') that lists the features targeted for it.",
+        "Feature-flag or configuration entries annotated with a target release (e.g. 'enabled_in: 3.1', 'since: v2.0'), or an 'Unreleased' or upcoming-version section in CHANGELOG.md."
+      ],
+      "x-dr-distinguish": {
+        "product.feature": "the element is a user-visible unit of functionality being delivered, rather than the dated target or release it is delivered in.",
+        "product.softwarecapability": "the element names an ability the software has or should have, independent of when it is delivered, rather than a scheduled delivery point."
+      },
       "$id": "urn:dr:spec:node:product.milestone"
     },
     "persona": {
       "$schema": "http://json-schema.org/draft-07/schema#",
       "title": "Persona",
-      "description": "A user archetype representing a class of users with shared goals, behaviors, and pain points",
+      "description": "A named, fictional archetype of a class of the product's actual or intended users, characterised by shared goals, behaviours, proficiency and pain points, against which features and workflows are designed. It describes who the user is, not what they do in the product or what access they are granted. Use UserWorkflow instead when the artefact describes a goal-directed journey the user takes through the product rather than the characteristics of the user taking it. Use WorkflowStep instead when the artefact is a single action or experience a user has at one point in a journey, even if phrased as 'the admin does X'.",
       "allOf": [
         {
           "$ref": "urn:dr:spec:base:spec-node"
@@ -210,12 +185,83 @@
           "additionalProperties": false
         }
       },
+      "x-dr-standard": "Product Management Practice: Persona (Cooper, goal-directed design); no direct ArchiMate 3.2 equivalent, nearest are Stakeholder (§6.2.1) and Business Role (§8.2.2)",
+      "x-dr-evidence": [
+        "persona documents in the repository (e.g. docs/personas/*.md or a product brief) naming an archetype with goals, frustrations and skill level",
+        "user stories or acceptance criteria in issues or BDD feature files phrased 'As a <named user type>, I want ...' that recur across many stories",
+        "a user-segment or user-type discriminator (e.g. onboarding question 'I am a developer / designer', analytics segment definitions, feature-flag targeting rules) that tailors UI or content per user class rather than granting permissions"
+      ],
+      "x-dr-distinguish": {
+        "product.userworkflow": "the artefact describes a goal-directed journey the user takes through the product rather than the characteristics of the user taking it",
+        "product.workflowstep": "the artefact is a single action or experience a user has at one point in a journey, even if phrased as 'the admin does X'"
+      },
       "$id": "urn:dr:spec:node:product.persona"
     },
+    "softwarecapability": {
+      "$schema": "http://json-schema.org/draft-07/schema#",
+      "title": "SoftwareCapability",
+      "description": "An ability of the software platform, stated as what the software can do (e.g. 'Save documents to files', 'Full-text search', 'Payment processing') rather than as a deliverable unit or a user journey. It is realized by one or more features, application services or technology services, and it realizes the business functions it carries out (saving documents to files realizes the business function of sharing data). Use BusinessCapability (business layer) instead when the ability belongs to the organization and would remain if different software, or none, provided it (e.g. 'Share data with partners'): a business capability is what the business can do, a software capability is what the platform can do. Use Feature instead when the element is a discrete, user-visible, prioritizable and sizable unit of functionality that ships (e.g. 'Apple Pay checkout button') rather than the enduring ability it contributes to (e.g. 'Payment processing'). Use UserWorkflow instead when the element describes an ordered sequence of user actions toward a goal rather than an ability the software has regardless of who uses it or in what order. Use WorkflowStep instead when the element is a single user action or experience at a position within a workflow rather than an ability that many steps may rely on. Use Milestone instead when the element is a dated delivery target that groups software capabilities or features rather than an ability itself.",
+      "allOf": [
+        {
+          "$ref": "urn:dr:spec:base:spec-node"
+        }
+      ],
+      "properties": {
+        "spec_node_id": {
+          "const": "product.softwarecapability"
+        },
+        "layer_id": {
+          "const": "product"
+        },
+        "type": {
+          "const": "softwarecapability"
+        },
+        "attributes": {
+          "type": "object",
+          "properties": {
+            "documentation": {
+              "type": "string",
+              "description": "Detailed description of the software capability"
+            },
+            "status": {
+              "type": "string",
+              "enum": [
+                "proposed",
+                "planned",
+                "developing",
+                "delivered",
+                "deprecated"
+              ],
+              "description": "Lifecycle status of the software capability"
+            },
+            "properties": {
+              "type": "object",
+              "description": "Cross-layer properties"
+            }
+          },
+          "required": ["status"],
+          "additionalProperties": false
+        }
+      },
+      "x-dr-standard": "Adapted from ArchiMate 3.2 §7.3.1 Capability (Strategy Layer) as a capability of the software platform rather than of the organization; the organization's capability is business.businesscapability",
+      "x-dr-evidence": [
+        "a product capability map, roadmap or README section headed 'Capabilities' listing abilities such as 'Search', 'Billing', 'Notifications' that are realized by several features",
+        "a top-level domain module, bounded context or service named for an ability of the platform (e.g. billing/, search/, export/) whose submodules implement several distinct user-facing features",
+        "a declared capability set in a manifest or handshake (e.g. a 'capabilities' object in a plugin manifest or protocol initialization response) enumerating abilities the system offers independent of specific UI entry points"
+      ],
+      "x-dr-distinguish": {
+        "business.businesscapability": "the ability belongs to the organization and would remain if different software, or none, provided it (e.g. 'Share data with partners'), rather than an ability of the software platform (e.g. 'Save documents to files')",
+        "product.feature": "the element is a discrete, user-visible, prioritizable and sizable unit of functionality that ships (e.g. 'Apple Pay checkout button') rather than the enduring ability it contributes to (e.g. 'Payment processing')",
+        "product.userworkflow": "the element describes an ordered sequence of user actions toward a goal rather than an ability the product possesses regardless of who uses it or in what order",
+        "product.workflowstep": "the element is a single user action or experience at a position within a workflow rather than an ability that many steps may rely on",
+        "product.milestone": "the element is a dated delivery target that groups software capabilities or features rather than an ability itself"
+      },
+      "$id": "urn:dr:spec:node:product.softwarecapability"
+    },
     "userworkflow": {
       "$schema": "http://json-schema.org/draft-07/schema#",
       "title": "UserWorkflow",
-      "description": "A sequence of user-facing steps through the product to accomplish a goal",
+      "description": "An ordered, end-to-end journey of user-facing steps that a persona performs through the product to reach one goal, described from the user's point of view and independent of screens, routes or code. It is composed of WorkflowSteps and spans the features those steps exercise. Use WorkflowStep instead when the element is a single action or experience at one position in a journey, not the whole sequence from trigger to goal. Use Feature instead when the element is a unit of functionality the user can switch on, buy or ship, rather than the ordered path a user takes to reach a goal. Use SoftwareCapability instead when the element names an ability the software has (e.g. 'password recovery') with no ordering of user actions.",
       "allOf": [
         {
           "$ref": "urn:dr:spec:base:spec-node"
@@ -252,75 +298,98 @@
           "additionalProperties": false
         }
       },
+      "x-dr-standard": "ArchiMate 3.2 §7.3.2 Value Stream (closest analogue), plus the product-management user journey / user story map",
+      "x-dr-evidence": [
+        "an end-to-end test spec (Playwright, Cypress, Selenium) named after a user goal, such as 'checkout.e2e.ts', that drives a user across several pages in order",
+        "an analytics funnel definition (Amplitude, Mixpanel, GA4 config) listing ordered events from a start event to a goal event",
+        "a Gherkin .feature file or docs/user-journeys page describing numbered Given/When/Then steps a named user type takes to accomplish a goal"
+      ],
+      "x-dr-distinguish": {
+        "product.workflowstep": "the element is a single action or experience at one position in a journey, not the whole sequence from trigger to goal",
+        "product.feature": "the element is a unit of functionality the user can switch on, buy or ship, rather than the ordered path a user takes to reach a goal",
+        "product.softwarecapability": "the element names an ability the software has (e.g. 'password recovery') with no ordering of user actions"
+      },
       "$id": "urn:dr:spec:node:product.userworkflow"
+    },
+    "workflowstep": {
+      "$schema": "http://json-schema.org/draft-07/schema#",
+      "title": "WorkflowStep",
+      "description": "An ordered, user-facing action within exactly one UserWorkflow, stating what the user does or experiences at that point in the journey and its observable result, described without reference to screens, routes, components or code. Each step names one position in one workflow; the same action in a different workflow is a different step. Use UserWorkflow instead when the element is the whole goal-directed journey made up of several steps, rather than one position within it. Use Feature instead when the element is a reusable unit of user-visible functionality that may be exercised by steps in many workflows, rather than a point in a particular journey. Use SoftwareCapability instead when the element describes an ability the software has regardless of any user sequence, with no ordering or user action attached.",
+      "allOf": [
+        {
+          "$ref": "urn:dr:spec:base:spec-node"
+        }
+      ],
+      "properties": {
+        "spec_node_id": {
+          "const": "product.workflowstep"
+        },
+        "layer_id": {
+          "const": "product"
+        },
+        "type": {
+          "const": "workflowstep"
+        },
+        "attributes": {
+          "type": "object",
+          "properties": {
+            "documentation": {
+              "type": "string",
+              "description": "Detailed description of the step"
+            },
+            "sequence": {
+              "type": "integer",
+              "minimum": 1,
+              "description": "Position of the step within its UserWorkflow (1-based)"
+            },
+            "action": {
+              "type": "string",
+              "description": "What the user does or experiences at this step, from the user's point of view (e.g. 'Requests a password reset link')"
+            },
+            "outcome": {
+              "type": "string",
+              "description": "Observable result of the step for the user (e.g. 'Receives an email containing a reset link')"
+            },
+            "optional": {
+              "type": "boolean",
+              "description": "Whether the workflow can complete without this step",
+              "default": false
+            },
+            "properties": {
+              "type": "object",
+              "description": "Cross-layer properties"
+            }
+          },
+          "required": ["sequence", "action"],
+          "additionalProperties": false
+        }
+      },
+      "x-dr-standard": "No direct ArchiMate 3.2 Strategy element; closest is a sub-process in ArchiMate 3.2 §8.3.1 Business Process decomposition, combined with the user-journey or story-map step of product-management practice",
+      "x-dr-evidence": [
+        "Numbered 'When'/'Then' lines inside a Gherkin Scenario or acceptance-criteria list that describe a user action and its visible result",
+        "test.step('...') or cy.step-style blocks inside an end-to-end test (Playwright, Cypress) named after a user action within a journey test",
+        "A user-journey, onboarding or story-map document (or wizard step config array) listing ordered steps with titles like 'Enter email' and 'Confirm code'"
+      ],
+      "x-dr-distinguish": {
+        "product.userworkflow": "the element is the whole goal-directed journey made up of several steps, rather than one position within it",
+        "product.feature": "the element is a reusable unit of user-visible functionality that may be exercised by steps in many workflows, rather than a point in a particular journey",
+        "product.softwarecapability": "the element describes an ability the software has regardless of any user sequence, with no ordering or user action attached"
+      },
+      "$id": "urn:dr:spec:node:product.workflowstep"
     }
   },
   "relationshipSchemas": {
-    "product.capability.aggregates.product.capability": {
-      "id": "product.capability.aggregates.product.capability",
-      "source_spec_node_id": "product.capability",
-      "source_layer": "product",
-      "destination_spec_node_id": "product.capability",
-      "destination_layer": "product",
-      "predicate": "aggregates",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.capability.fulfills.motivation.requirement": {
-      "id": "product.capability.fulfills.motivation.requirement",
-      "source_spec_node_id": "product.capability",
-      "source_layer": "product",
-      "destination_spec_node_id": "motivation.requirement",
-      "destination_layer": "motivation",
-      "predicate": "fulfills",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.capability.realizes.business.businessfunction": {
-      "id": "product.capability.realizes.business.businessfunction",
-      "source_spec_node_id": "product.capability",
-      "source_layer": "product",
-      "destination_spec_node_id": "business.businessfunction",
-      "destination_layer": "business",
-      "predicate": "realizes",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.capability.scheduled-for.product.milestone": {
-      "id": "product.capability.scheduled-for.product.milestone",
-      "source_spec_node_id": "product.capability",
-      "source_layer": "product",
-      "destination_spec_node_id": "product.milestone",
-      "destination_layer": "product",
-      "predicate": "scheduled-for",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.capability.supports.motivation.goal": {
-      "id": "product.capability.supports.motivation.goal",
-      "source_spec_node_id": "product.capability",
-      "source_layer": "product",
-      "destination_spec_node_id": "motivation.goal",
-      "destination_layer": "motivation",
-      "predicate": "supports",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.feature.delivers-value.motivation.value": {
-      "id": "product.feature.delivers-value.motivation.value",
+    "product.feature.delivers.motivation.value": {
+      "id": "product.feature.delivers.motivation.value",
       "source_spec_node_id": "product.feature",
       "source_layer": "product",
       "destination_spec_node_id": "motivation.value",
       "destination_layer": "motivation",
-      "predicate": "delivers-value",
+      "predicate": "delivers",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "Users of the feature gain the value; the value is the reason the feature is worth building."
     },
     "product.feature.depends-on.product.feature": {
       "id": "product.feature.depends-on.product.feature",
@@ -331,29 +400,20 @@
       "predicate": "depends-on",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The feature cannot work, or cannot ship, without the other feature, such as sharing a document depending on the document being savable."
     },
-    "product.feature.realizes.business.businessservice": {
-      "id": "product.feature.realizes.business.businessservice",
+    "product.feature.realizes.product.softwarecapability": {
+      "id": "product.feature.realizes.product.softwarecapability",
       "source_spec_node_id": "product.feature",
       "source_layer": "product",
-      "destination_spec_node_id": "business.businessservice",
-      "destination_layer": "business",
-      "predicate": "realizes",
-      "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
-    },
-    "product.feature.realizes.product.capability": {
-      "id": "product.feature.realizes.product.capability",
-      "source_spec_node_id": "product.feature",
-      "source_layer": "product",
-      "destination_spec_node_id": "product.capability",
+      "destination_spec_node_id": "product.softwarecapability",
       "destination_layer": "product",
       "predicate": "realizes",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The feature is one concrete, user-visible way the software exercises the capability, such as an export button realizing the ability to save documents to files."
     },
     "product.feature.satisfies.motivation.requirement": {
       "id": "product.feature.satisfies.motivation.requirement",
@@ -364,7 +424,8 @@
       "predicate": "satisfies",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The feature is how the product meets the requirement, so the requirement is fulfilled once the feature ships."
     },
     "product.feature.scheduled-for.product.milestone": {
       "id": "product.feature.scheduled-for.product.milestone",
@@ -375,7 +436,8 @@
       "predicate": "scheduled-for",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The feature is planned to ship in the milestone's release, version or roadmap phase."
     },
     "product.feature.serves.product.persona": {
       "id": "product.feature.serves.product.persona",
@@ -386,7 +448,8 @@
       "predicate": "serves",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The feature is designed for the persona: people like the persona use it to get their work done."
     },
     "product.milestone.precedes.product.milestone": {
       "id": "product.milestone.precedes.product.milestone",
@@ -397,51 +460,116 @@
       "predicate": "precedes",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The earlier milestone is delivered before the later one, which builds on its scope."
+    },
+    "product.persona.references.business.businessrole": {
+      "id": "product.persona.references.business.businessrole",
+      "source_spec_node_id": "product.persona",
+      "source_layer": "product",
+      "destination_spec_node_id": "business.businessrole",
+      "destination_layer": "business",
+      "predicate": "references",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The persona describes a kind of person who holds the business role; it points to the role rather than performing or serving it."
     },
-    "product.persona.realizes.motivation.stakeholder": {
-      "id": "product.persona.realizes.motivation.stakeholder",
+    "product.persona.references.motivation.stakeholder": {
+      "id": "product.persona.references.motivation.stakeholder",
       "source_spec_node_id": "product.persona",
       "source_layer": "product",
       "destination_spec_node_id": "motivation.stakeholder",
       "destination_layer": "motivation",
-      "predicate": "realizes",
+      "predicate": "references",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The persona is a design archetype for a group the stakeholder represents; it points to the stakeholder whose concerns its users share."
     },
-    "product.persona.serves.business.businessrole": {
-      "id": "product.persona.serves.business.businessrole",
-      "source_spec_node_id": "product.persona",
+    "product.softwarecapability.aggregates.product.softwarecapability": {
+      "id": "product.softwarecapability.aggregates.product.softwarecapability",
+      "source_spec_node_id": "product.softwarecapability",
       "source_layer": "product",
-      "destination_spec_node_id": "business.businessrole",
-      "destination_layer": "business",
-      "predicate": "serves",
+      "destination_spec_node_id": "product.softwarecapability",
+      "destination_layer": "product",
+      "predicate": "aggregates",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The narrower software capability is part of the wider one in the platform's capability map; it keeps its own identity and may be grouped under more than one parent."
     },
-    "product.userworkflow.aggregates.business.businessprocess": {
-      "id": "product.userworkflow.aggregates.business.businessprocess",
-      "source_spec_node_id": "product.userworkflow",
+    "product.softwarecapability.depends-on.product.softwarecapability": {
+      "id": "product.softwarecapability.depends-on.product.softwarecapability",
+      "source_spec_node_id": "product.softwarecapability",
       "source_layer": "product",
-      "destination_spec_node_id": "business.businessprocess",
+      "destination_spec_node_id": "product.softwarecapability",
+      "destination_layer": "product",
+      "predicate": "depends-on",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The software capability needs the other capability of the platform to work, such as full-text search depending on document indexing."
+    },
+    "product.softwarecapability.realizes.business.businessfunction": {
+      "id": "product.softwarecapability.realizes.business.businessfunction",
+      "source_spec_node_id": "product.softwarecapability",
+      "source_layer": "product",
+      "destination_spec_node_id": "business.businessfunction",
       "destination_layer": "business",
-      "predicate": "aggregates",
+      "predicate": "realizes",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The software capability is how the platform carries out the business function, such as saving documents to files realizing the business function of sharing data. This is the product layer's main link to the business layer."
+    },
+    "product.softwarecapability.satisfies.motivation.requirement": {
+      "id": "product.softwarecapability.satisfies.motivation.requirement",
+      "source_spec_node_id": "product.softwarecapability",
+      "source_layer": "product",
+      "destination_spec_node_id": "motivation.requirement",
+      "destination_layer": "motivation",
+      "predicate": "satisfies",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The software capability is how the platform meets the requirement."
+    },
+    "product.softwarecapability.scheduled-for.product.milestone": {
+      "id": "product.softwarecapability.scheduled-for.product.milestone",
+      "source_spec_node_id": "product.softwarecapability",
+      "source_layer": "product",
+      "destination_spec_node_id": "product.milestone",
+      "destination_layer": "product",
+      "predicate": "scheduled-for",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The software capability is planned to be in place by the milestone."
+    },
+    "product.softwarecapability.supports.motivation.goal": {
+      "id": "product.softwarecapability.supports.motivation.goal",
+      "source_spec_node_id": "product.softwarecapability",
+      "source_layer": "product",
+      "destination_spec_node_id": "motivation.goal",
+      "destination_layer": "motivation",
+      "predicate": "supports",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "Having the software capability helps the organization reach the goal."
     },
-    "product.userworkflow.composes.product.feature": {
-      "id": "product.userworkflow.composes.product.feature",
+    "product.userworkflow.composes.product.workflowstep": {
+      "id": "product.userworkflow.composes.product.workflowstep",
       "source_spec_node_id": "product.userworkflow",
       "source_layer": "product",
-      "destination_spec_node_id": "product.feature",
+      "destination_spec_node_id": "product.workflowstep",
       "destination_layer": "product",
       "predicate": "composes",
       "cardinality": "many-to-many",
-      "strength": "medium",
-      "required": false
+      "strength": "high",
+      "required": false,
+      "description": "The step is one position in the workflow's ordered journey and exists only as part of it."
     },
     "product.userworkflow.delivers.motivation.outcome": {
       "id": "product.userworkflow.delivers.motivation.outcome",
@@ -452,7 +580,20 @@
       "predicate": "delivers",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "Completing the journey produces the outcome the user or organization wants."
+    },
+    "product.userworkflow.realizes.business.businessprocess": {
+      "id": "product.userworkflow.realizes.business.businessprocess",
+      "source_spec_node_id": "product.userworkflow",
+      "source_layer": "product",
+      "destination_spec_node_id": "business.businessprocess",
+      "destination_layer": "business",
+      "predicate": "realizes",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "The workflow is the user's way of carrying out the business process through the product, so following the journey performs the process or its user-facing part."
     },
     "product.userworkflow.serves.product.persona": {
       "id": "product.userworkflow.serves.product.persona",
@@ -463,7 +604,32 @@
       "predicate": "serves",
       "cardinality": "many-to-many",
       "strength": "medium",
-      "required": false
+      "required": false,
+      "description": "The workflow is designed for the persona: it is the journey people like the persona follow to reach their goal."
+    },
+    "product.workflowstep.flows-to.product.workflowstep": {
+      "id": "product.workflowstep.flows-to.product.workflowstep",
+      "source_spec_node_id": "product.workflowstep",
+      "source_layer": "product",
+      "destination_spec_node_id": "product.workflowstep",
+      "destination_layer": "product",
+      "predicate": "flows-to",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "When the user finishes the step, the journey continues with the next step."
+    },
+    "product.workflowstep.uses.product.feature": {
+      "id": "product.workflowstep.uses.product.feature",
+      "source_spec_node_id": "product.workflowstep",
+      "source_layer": "product",
+      "destination_spec_node_id": "product.feature",
+      "destination_layer": "product",
+      "predicate": "uses",
+      "cardinality": "many-to-many",
+      "strength": "medium",
+      "required": false,
+      "description": "At this step the user exercises the feature; a workflow reaches features, and through them software capabilities, only through its steps."
     }
   }
 }