@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/automation-flow-coordinate/references/shared/flow-type-resolver/taxonomy.json

@@ -1,320 +0,0 @@
-{
-  "$comment": "SINGLE SOURCE OF TRUTH for Salesforce flow-type resolution. A feature of automation-flow-coordinate: consumed by the flow-type-resolver reference (flow-type-resolver.md, next to this file) and by coordinate's recipes/resolve-type/resolve-type.md, recipes/author/author.md (Phase 2), shared/decision-tree.md (thin pointer) and elements/start/start.md. A flow type is a (processType x triggerType [x recordTriggerType, runInMode]) tuple; `specCategory` is the coarse label used in summaries/reports. The AUTHORITATIVE supported set is `supportedTuples` (a full enumeration of the (processType x triggerType x recordTriggerType) combinations Project Codey supports); `categories` are the coarse resolver view over it. `supportedTuples` is validated against the live org by eval/verify_supported_types.py (org-check only: every tuple's processType must be in the org's list-process-types and every triggerType in list-trigger-types for that processType; no-trigger is valid by absence). Covers the four audience/engagement trigger types (AutomationEvent, List, CampaignMember, RecordQuery), plus IndivRelatedRecord (Engagement/Journey), FormSubmissionEvent (a Marketing form submission; Flow Builder lists it under the Automation Event picker but persists it as its own trigger type), Segment, BroadcastNoTrigger and OnDemandNoTrigger (marketing flows), DataCloudDataChange (org-gated: a single Data Cloud DMO record change, provisioned only on a Data Cloud org) and EvaluationFlow, that this org's automation-flow-coordinate skill supports. Org-gated types (Data Cloud triggers) are modeled first-class in the top-level `orgGating` block: each is a named feature, and a `supportedTuples` entry references it by id via `orgGated: <featureId>` so eval/verify_supported_types.py and the resolver can detect provisioning from the org read endpoints and skip it as informational (surfacing a clean 'org not provisioned' outcome) on an org that lacks the feature, rather than failing.",
-  "enums": {
-    "processType": ["Flow", "AutoLaunchedFlow", "Orchestrator", "ApprovalWorkflow", "EvaluationFlow"],
-    "triggerType": ["None", "RecordAfterSave", "RecordBeforeSave", "RecordBeforeDelete", "Scheduled", "PlatformEvent", "Segment", "List", "CampaignMember", "RecordQuery", "AutomationEvent", "FormSubmissionEvent", "IndivRelatedRecord", "DataCloudDataChange", "BroadcastNoTrigger", "OnDemandNoTrigger"],
-    "recordTriggerType": ["Create", "Update", "CreateAndUpdate", "Delete"],
-    "runInMode": ["DefaultMode", "SystemModeWithSharing", "SystemModeWithoutSharing", "UserMode"]
-  },
-  "axes": {
-    "$comment": "The characteristics of *what is being automated* that drive the process family. Combination is weighted / dominant-signal (NOT strict conjunction): lean toward Process when clearly multi-stage + long-running, even if one axis is ambiguous. Secondary factors (complexity, cognitive overload, manageability) are tie-breakers that promote a borderline Task->Process.",
-    "processVsTask": "Is it a single unit of work (Task) or a coordinated multi-stage business process (Process)?",
-    "runningTime": "Does it complete in one session/transaction (Short) or span time, wait for humans/events, and resume (Long)?",
-    "collaboration": "Does one actor do it (Single) or does it coordinate multiple users/teams/approvers across stages (Collaboration)?",
-    "invocation": "How does it START? Automatically on a record change (record-change), on a time schedule (scheduled), on a platform event (platform-event), on an email-engagement event such as open/click/bounce/response (automation-event), when someone submits a Marketing form (form-submission), or for a marketing/audience source — a Data Cloud segment (segment), an Actionable List (list), a Campaign's members (campaign-member), or all records of an object matching a filter (record-query) — VS. explicitly kicked off with no automatic trigger: launched by a person who steps through it (user-interactive) or called headlessly from Apex/API/a subflow/a button (on-demand). This is the axis that separates the Autolaunched families from their Record-Triggered / Scheduled / etc. counterparts: a record merely being *mentioned* as context is not a record trigger — only automatic firing on save is."
-  },
-  "fallbackCategory": "Other",
-  "characteristicValues": {
-    "$comment": "Closed legal-value sets for each characteristics axis (the `axes` above are the human descriptions; these are the enumerable values a category may declare). Consumers reference these instead of hard-coding literals, and loadTaxonomy() validates every category's characteristics against them.",
-    "processVsTask": ["task", "process"],
-    "runningTime": ["short", "long"],
-    "collaboration": ["single", "collaboration"],
-    "invocation": ["user-interactive", "on-demand", "record-change", "scheduled", "platform-event", "automation-event", "form-submission", "segment", "list", "campaign-member", "record-query", "data-cloud-data-change"]
-  },
-  "orgGating": {
-    "$comment": "First-class org-gating model. Some `supportedTuples` need a feature or provisioning the base org may lack; each such need is defined here ONCE as a named feature, and a tuple references it by id via `orgGated: <featureId>` (previously a bare tactical string, applied to DataCloudDataChange only). Consumers — eval/verify_supported_types.py and the flow-type-resolver reasoning — look the feature up to decide how to DETECT provisioning and what to tell the user when it is absent, instead of special-casing an individual trigger. `detectBy` names the org read-endpoint signal that reveals provisioning: `triggerType` (the gated trigger appears in list-trigger-types only when the feature is provisioned) or `processType` (the gated process type appears in list-process-types only when the feature is provisioned). `requires` is the human precondition; `minApiVersion`, where set, is the floor for the feature's metadata. `notProvisioned` is the clean, user-facing outcome the resolver surfaces (and the validator's skip note carries) when the org lacks the feature. Non-gated tuples (those without `orgGated`) are unaffected. This model generalizes: DataGraphDataChange, when its tuples are added, references the `data-cloud` feature (same Data Cloud provisioning, detectBy triggerType), and any future org-gated process type gets a `detectBy: processType` feature.",
-    "features": {
-      "data-cloud": {
-        "label": "Data Cloud",
-        "requires": "a Data Cloud-provisioned org",
-        "minApiVersion": "59.0",
-        "detectBy": "triggerType",
-        "notProvisioned": "the org is not provisioned for Data Cloud (API version 59.0+); stop and tell the user rather than falling back to a core record trigger"
-      }
-    }
-  },
-  "supportedTuples": {
-    "$comment": "AUTHORITATIVE supported set: the full enumeration of (processType x triggerType x recordTriggerType) combinations Project Codey supports, curated to the subset the automation-flow-coordinate skill can author (narrower than the org's full capability). A no-trigger entry omits `triggerType` (it is valid by ABSENCE, not by a `None` trigger value in the org's list-trigger-types). `recordTriggerType` is enumerated per the skill's start-element pairing table; the org's read endpoints do not gate it (getFlowCapabilities returns 200 even for an invalid recordTriggerType), so it is advisory and enforced only at save-time. `runInMode`, where set, is validated against getFlowCapabilities.runInModes. Every processType/triggerType/recordTriggerType/runInMode value here MUST appear in the corresponding `enums` list; validated org-side by eval/verify_supported_types.py. An entry may also carry an advisory `uiLabel` — the finer Flow Builder picker name (e.g. 'Before Save'/'After Save'/'Before Delete', which all map to specCategory `RecordTriggered`); it is display metadata only, NOT an org-validated value, and the validator ignores it. An entry may also carry `orgGated` — the id of a feature defined in the top-level `orgGating.features` block (e.g. \"data-cloud\") — to mark a type that exists only on an org provisioned for that feature. eval/verify_supported_types.py resolves the feature and, per its `detectBy`, treats the tuple as skipped-informational when the org lacks the feature (its triggerType absent from list-trigger-types, or its processType absent from list-process-types) and validates it normally when the org exposes it; an `orgGated` value naming no defined feature is a config violation. See `orgGating` for the model.",
-    "entries": [
-      { "specCategory": "Screen", "processType": "Flow" },
-      { "specCategory": "Autolaunched", "processType": "AutoLaunchedFlow" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordBeforeSave", "recordTriggerType": "Create", "uiLabel": "Before Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordBeforeSave", "recordTriggerType": "Update", "uiLabel": "Before Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordBeforeSave", "recordTriggerType": "CreateAndUpdate", "uiLabel": "Before Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordAfterSave", "recordTriggerType": "Create", "uiLabel": "After Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordAfterSave", "recordTriggerType": "Update", "uiLabel": "After Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordAfterSave", "recordTriggerType": "CreateAndUpdate", "uiLabel": "After Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordAfterSave", "recordTriggerType": "Delete", "uiLabel": "After Save" },
-      { "specCategory": "RecordTriggered", "processType": "AutoLaunchedFlow", "triggerType": "RecordBeforeDelete", "recordTriggerType": "Delete", "uiLabel": "Before Delete" },
-      { "specCategory": "Scheduled", "processType": "AutoLaunchedFlow", "triggerType": "Scheduled" },
-      { "specCategory": "PlatformEvent", "processType": "AutoLaunchedFlow", "triggerType": "PlatformEvent" },
-      { "specCategory": "AutomationEvent", "processType": "AutoLaunchedFlow", "triggerType": "AutomationEvent" },
-      { "specCategory": "FormSubmissionEvent", "processType": "AutoLaunchedFlow", "triggerType": "FormSubmissionEvent", "uiLabel": "Automation Event > Form Submission" },
-      { "specCategory": "Segment", "processType": "AutoLaunchedFlow", "triggerType": "Segment" },
-      { "specCategory": "Broadcast", "processType": "AutoLaunchedFlow", "triggerType": "BroadcastNoTrigger" },
-      { "specCategory": "OnDemand", "processType": "AutoLaunchedFlow", "triggerType": "OnDemandNoTrigger" },
-      { "specCategory": "List", "processType": "AutoLaunchedFlow", "triggerType": "List" },
-      { "specCategory": "CampaignMember", "processType": "AutoLaunchedFlow", "triggerType": "CampaignMember" },
-      { "specCategory": "RecordQuery", "processType": "AutoLaunchedFlow", "triggerType": "RecordQuery" },
-      { "specCategory": "IndivRelatedRecord", "processType": "AutoLaunchedFlow", "triggerType": "IndivRelatedRecord", "recordTriggerType": "Create" },
-      { "specCategory": "IndivRelatedRecord", "processType": "AutoLaunchedFlow", "triggerType": "IndivRelatedRecord", "recordTriggerType": "Update" },
-      { "specCategory": "IndivRelatedRecord", "processType": "AutoLaunchedFlow", "triggerType": "IndivRelatedRecord", "recordTriggerType": "CreateAndUpdate" },
-      { "specCategory": "DataCloudDataChange", "processType": "AutoLaunchedFlow", "triggerType": "DataCloudDataChange", "recordTriggerType": "Create", "orgGated": "data-cloud" },
-      { "specCategory": "DataCloudDataChange", "processType": "AutoLaunchedFlow", "triggerType": "DataCloudDataChange", "recordTriggerType": "Update", "orgGated": "data-cloud" },
-      { "specCategory": "DataCloudDataChange", "processType": "AutoLaunchedFlow", "triggerType": "DataCloudDataChange", "recordTriggerType": "CreateAndUpdate", "orgGated": "data-cloud" },
-      { "specCategory": "RecordTriggeredOrchestration", "processType": "Orchestrator", "triggerType": "RecordAfterSave", "recordTriggerType": "Create", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "RecordTriggeredOrchestration", "processType": "Orchestrator", "triggerType": "RecordAfterSave", "recordTriggerType": "Update", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "RecordTriggeredOrchestration", "processType": "Orchestrator", "triggerType": "RecordAfterSave", "recordTriggerType": "CreateAndUpdate", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "AutolaunchedOrchestration", "processType": "Orchestrator", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "RecordTriggeredApprovalOrchestration", "processType": "ApprovalWorkflow", "triggerType": "RecordAfterSave", "recordTriggerType": "Create", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "RecordTriggeredApprovalOrchestration", "processType": "ApprovalWorkflow", "triggerType": "RecordAfterSave", "recordTriggerType": "Update", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "RecordTriggeredApprovalOrchestration", "processType": "ApprovalWorkflow", "triggerType": "RecordAfterSave", "recordTriggerType": "CreateAndUpdate", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "AutolaunchedApprovalOrchestration", "processType": "ApprovalWorkflow", "runInMode": "SystemModeWithoutSharing" },
-      { "specCategory": "EvaluationFlow", "processType": "EvaluationFlow" }
-    ]
-  },
-  "unsupportedProcessTypes": {
-    "$comment": "Out-of-scope process types the resolver does NOT author but must recognize in order to hand off. INTENTIONALLY NOT part of `enums.processType` or `supportedTuples` — the org-validator (eval/verify_supported_types.py) must never iterate these (it would reject them as unsupported). This block is the single home for the process-type glossary formerly duplicated in automation-flow-coordinate's shared/flow-properties/flow-properties.md. `label` = Flow Builder picker name; `processType` = metadata API value; `note` = why out of scope plus any distinguishing build fact. Feature families that are not a single processType (e.g. CPQ) stay as SKILL.md prose, not entries here.",
-    "entries": [
-      { "label": "Field Service Mobile", "processType": "FieldServiceMobile", "note": "Offline mobile scenarios. Out of scope — hand off." },
-      { "label": "Field Service Web", "processType": "FieldServiceWeb", "note": "Field Service (web). Out of scope — hand off." },
-      { "label": "Data Capture Flow", "processType": "DataCaptureFlow", "note": "Offline data collection; can be LLM-targetable (see automation-flow-coordinate shared/flow-properties/flow-properties.md). Out of scope — hand off." },
-      { "label": "Unified Scheduling Flow", "processType": "UnifiedSchedulingFlow", "note": "Unified scheduling scenarios; supports the Screen Progress Indicator (see flow-properties.md). Out of scope — hand off." }
-    ]
-  },
-  "categories": [
-    {
-      "specCategory": "Screen",
-      "label": "Screen Flow",
-      "tuple": { "processType": "Flow" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "user-interactive" },
-      "aliases": ["Screen", "ScreenFlow", "Flow"],
-      "keywords": ["form", "wizard", "screen", "guide the user", "user enters", "user selects", "step-by-step for a user", "collect input"]
-    },
-    {
-      "specCategory": "Autolaunched",
-      "label": "Autolaunched Flow",
-      "tuple": { "processType": "AutoLaunchedFlow" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "on-demand" },
-      "aliases": ["Autolaunched", "AutoLaunchedFlow"],
-      "keywords": ["called from apex", "called from another flow", "subflow", "on demand", "no trigger", "headless", "library flow"],
-      "$note": "A marketing send (email, SMS, journey) that an app or the API starts for one person, or a request that names the On-Demand Flow type, is OnDemandNoTrigger, not this no-trigger type: a no-trigger flow's action catalog does not offer the E360 send actions (sendEmailMessage, sendSmsMessage, sendToJourney). The send action decides, not the launch channel: an email or text sent with consent from a communication subscription is a marketing send (sendEmailMessage / sendSmsMessage); emailAlert and emailSimple take no subscription. A core emailSimple, a subflow or an Apex/REST utility flow stays here, and so does a flow described only as running on demand (called from Apex, a button or another flow) with no marketing send."
-    },
-    {
-      "specCategory": "RecordTriggered",
-      "label": "Record-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "RecordAfterSave" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "record-change" },
-      "aliases": ["RecordTriggered", "RecordTriggeredFlow"],
-      "keywords": ["when a record is created", "when a record is updated", "when a record is deleted", "on save", "for each record that reaches", "whenever X happens"]
-    },
-    {
-      "specCategory": "Scheduled",
-      "label": "Scheduled Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "Scheduled" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "scheduled" },
-      "aliases": ["Scheduled", "ScheduledFlow"],
-      "keywords": ["on a schedule", "every day", "nightly", "cron", "at 9am", "weekly batch"]
-    },
-    {
-      "specCategory": "PlatformEvent",
-      "label": "Platform Event-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "PlatformEvent" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "platform-event" },
-      "aliases": ["PlatformEvent", "PlatformEventFlow"],
-      "keywords": ["platform event", "subscribe to event", "when an event is published"]
-    },
-    {
-      "specCategory": "AutomationEvent",
-      "label": "Automation Event-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "AutomationEvent" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "automation-event" },
-      "aliases": ["AutomationEvent", "AutomationEventFlow"],
-      "keywords": ["email opened", "link clicked", "email bounced", "email response", "email-engagement event", "engagement signal", "engagement signals", "fires when an email is opened/clicked/bounced/responded to"]
-    },
-    {
-      "specCategory": "FormSubmissionEvent",
-      "label": "Form-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "FormSubmissionEvent" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "form-submission" },
-      "aliases": ["FormSubmissionEvent", "FormSubmission", "Form Submission", "Form Submission Event", "Form-Triggered Flow", "FormTriggered", "Form Submission-Triggered Flow"],
-      "keywords": ["form submitted", "form submission", "when a form is submitted", "on form submit", "when someone submits our form", "fills out our form", "registration form submitted", "contact us form", "web form", "marketing form"],
-      "$note": "A Marketing form (a Form Builder form stored as Managed Content, type sfdc_cms__form) is submitted; the flow runs headless on each submission and reads the submitted fields via $Form. Flow Builder lists Form Submission under the Automation Event picker, but selecting it persists the flow as triggerType FormSubmissionEvent, so FormSubmissionEvent is the canonical saved shape, NOT AutomationEvent. HARD PROHIBITION: never author a form-submission flow as triggerType AutomationEvent with eventName/eventType trgrOnFormSubmission (the platform rejects it; see badPairs). Distinct from a Screen flow, which IS a form a user steps through interactively. Per-trigger build detail lives in automation-flow-coordinate's elements/start/form-submission-triggered.md."
-    },
-    {
-      "specCategory": "Segment",
-      "label": "Segment-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "Segment" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "segment" },
-      "aliases": ["Segment"],
-      "keywords": ["marketing segment", "audience", "drip", "nurture", "re-engagement", "campaign outreach", "segment-triggered", "when a segment is published"],
-      "$note": "A broadcast that fans out a dynamic segment now is BroadcastNoTrigger, not Segment. Segment is the scheduled or on-activate audience trigger and keeps the Individual-only eligibility gate."
-    },
-    {
-      "specCategory": "Broadcast",
-      "label": "Broadcast Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "BroadcastNoTrigger" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "on-demand" },
-      "aliases": ["Broadcast", "BroadcastNoTrigger", "BroadcastFlow"],
-      "keywords": ["broadcast", "broadcast flow", "fan out a dynamic segment", "fan-out", "cdpJitSegment", "run a segment now"],
-      "$note": "Start fan-out, not a canvas action. actionType cdpJitSegment; actionName and nameSegment are the segment API name. isAsync false is Run Type Sync. No start.object and no schedule. Per-member fields are $Input.<segmentOnApiName>.<field>. The segment DMO may be Account or Unified Individual. Build detail is in elements/start/start.md."
-    },
-    {
-      "specCategory": "OnDemand",
-      "label": "On-Demand Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "OnDemandNoTrigger" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "on-demand" },
-      "aliases": ["OnDemand", "OnDemandNoTrigger", "OnDemandFlow"],
-      "keywords": ["On-Demand Flow (the flow type)", "on-demand marketing flow", "on demand marketing flow", "marketing send triggered by the app for a person", "api-triggered marketing send"],
-      "$note": "A marketing flow an app or integration starts through the API for one person. Top-level dataSpace required. No start.object, filters or schedule. A send's recipient comes from the reserved request inputs IndividualId / EmailAddress / TelephoneNumber, not an action parameter. Optional dataGraph (primary DMO Unified Individual or Individual) exposes $SelectedIndividual. Output variables are not returned in the launch response. Can't be a subflow. An email or text sent with consent from a communication subscription is a marketing send (sendEmailMessage / sendSmsMessage), never emailAlert or emailSimple. \"On demand\" alone (runs when called from Apex, a button or another flow, with no marketing send) is Autolaunched, not this type. Build detail is in elements/start/start.md."
-    },
-    {
-      "specCategory": "List",
-      "label": "List-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "List" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "list" },
-      "aliases": ["List", "ListTriggered", "ActionableList"],
-      "keywords": ["actionable list", "list view", "run for each record in a list", "list-triggered audience"]
-    },
-    {
-      "specCategory": "CampaignMember",
-      "label": "Campaign Member-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "CampaignMember" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "campaign-member" },
-      "aliases": ["CampaignMember", "Campaign"],
-      "keywords": ["campaign member", "run campaign", "campaign audience", "members of a campaign"]
-    },
-    {
-      "specCategory": "RecordQuery",
-      "label": "RecordQuery-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "RecordQuery" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "record-query" },
-      "aliases": ["RecordQuery"],
-      "keywords": ["all records of an object matching a filter", "audience of records", "batch of records matching criteria", "record-query triggered audience"]
-    },
-    {
-      "specCategory": "RecordTriggeredOrchestration",
-      "label": "Record-Triggered Orchestration",
-      "tuple": { "processType": "Orchestrator", "triggerType": "RecordAfterSave", "runInMode": "SystemModeWithoutSharing" },
-      "characteristics": { "processVsTask": "process", "runningTime": "long", "collaboration": "collaboration", "invocation": "record-change" },
-      "aliases": ["RecordTriggeredOrchestration"],
-      "keywords": ["multi-stage process starting on a record change", "orchestrate work when a record is created/updated", "route the work across stages on save"]
-    },
-    {
-      "specCategory": "AutolaunchedOrchestration",
-      "label": "Autolaunched Orchestration",
-      "tuple": { "processType": "Orchestrator", "runInMode": "SystemModeWithoutSharing" },
-      "characteristics": { "processVsTask": "process", "runningTime": "long", "collaboration": "collaboration", "invocation": "on-demand" },
-      "aliases": ["AutolaunchedOrchestration", "Orchestrator", "OrchestrationFlow"],
-      "keywords": ["orchestrate multi-stage work", "stages", "hand off between teams", "assign to teams", "track the work that needs to be done", "coordinate a process across people", "interactive and background steps", "a user can kick off / start / initiate the process", "started from a button or on demand (NOT automatically on record save)", "launch the coordinated process when someone chooses to"]
-    },
-    {
-      "specCategory": "RecordTriggeredApprovalOrchestration",
-      "label": "Record-Triggered Approval Orchestration",
-      "tuple": { "processType": "ApprovalWorkflow", "triggerType": "RecordAfterSave", "runInMode": "SystemModeWithoutSharing" },
-      "characteristics": { "processVsTask": "process", "runningTime": "long", "collaboration": "collaboration", "invocation": "record-change" },
-      "aliases": ["RecordTriggeredApprovalOrchestration"],
-      "keywords": ["approval that starts when a record is created/updated", "route for sign-off on record change"]
-    },
-    {
-      "specCategory": "AutolaunchedApprovalOrchestration",
-      "label": "Autolaunched Approval Orchestration",
-      "tuple": { "processType": "ApprovalWorkflow", "runInMode": "SystemModeWithoutSharing" },
-      "characteristics": { "processVsTask": "process", "runningTime": "long", "collaboration": "collaboration", "invocation": "on-demand" },
-      "aliases": ["AutolaunchedApprovalOrchestration", "ApprovalWorkflow"],
-      "keywords": ["approval", "approve or reject", "submit for approval", "sign-off", "authorize", "recall", "approval request", "approval work item", "a user submits / sends the record for approval", "kicked off when someone submits it (NOT automatically on record save)"]
-    },
-    {
-      "specCategory": "IndivRelatedRecord",
-      "label": "Engagement / Journey-Triggered Flow (Individual Related Record)",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "IndivRelatedRecord" },
-      "characteristics": { "processVsTask": "task", "runningTime": "long", "collaboration": "single", "invocation": "record-change" },
-      "aliases": ["IndivRelatedRecord", "IndividualRelatedRecord", "Individual Related Record-Triggered Flow", "Individual Related Record", "Engagement", "Journey", "CRM Triggered Flow", "CRM Triggered", "CRM Trigger"],
-      "keywords": ["pauses mid-flow until an engagement event", "wait until event", "email open then continue", "wait for the customer to click", "journey builder contact event", "run then wait for engagement", "SMS response then resume", "individual-related record", "individual related record-triggered flow", "crm triggered flow"],
-      "$note": "Also called a CRM Triggered Flow ('CRM Triggered', 'CRM Trigger'). Flow Builder lists it under Automation Event-Triggered Flow as 'Prospect, Lead, Contact or Related Record Change'. People also say it for a core Record-Triggered Flow, so the name alone does not decide. A request that names a CRM Triggered Flow AND says 'marketing' resolves here with no question, even when the rest of it uses record-change wording ('every time a Contact is updated'): that wording sets the Start object and recordTriggerType, not the trigger type. Without 'marketing', lean here but set mustAsk and ask: a marketing Automation Event flow (Prospect, Lead, Contact or Related Record Change), or a Record-Triggered Flow (RecordAfterSave, which rejects the marketing sendEmailMessage action with ACTIONCALL_NOT_SUPPORTED_FOR_PROCESSTYPE, so an email there uses the core Send Email action). Never the Data Cloud-triggered DataCloudDataChange (a Data Cloud DMO change). It needs no mid-flow wait to be this type. Per-trigger build detail (builderType JourneyBuilder, triggering record as $Input, required dataSpace) lives in automation-flow-coordinate's elements/start/start.md, Engagement / Journey-Triggered section."
-    },
-    {
-      "specCategory": "DataCloudDataChange",
-      "label": "Data Cloud-Triggered Flow",
-      "tuple": { "processType": "AutoLaunchedFlow", "triggerType": "DataCloudDataChange" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "data-cloud-data-change" },
-      "aliases": ["DataCloudDataChange", "DataCloudTriggered", "DataCloud"],
-      "keywords": ["when a data cloud dmo record changes", "data model object created or updated", "ssot__ record change", "__dlm record trigger", "data cloud record-triggered flow"],
-      "$note": "Org-gated: requires a Data Cloud-provisioned org (API version 59.0+). The single-DMO record-change trigger — fires on one `ssot__*__dlm` DMO create/update, exposes the changed DMO as read-only `$Record`; distinct from the multi-object `DataGraphDataChange`, from core-SObject record triggers, and from `AutomationEvent`. Per-trigger build detail lives in automation-flow-coordinate's elements/start/data-cloud-data-change-triggered.md."
-    },
-    {
-      "specCategory": "EvaluationFlow",
-      "label": "Evaluation Flow",
-      "tuple": { "processType": "EvaluationFlow" },
-      "characteristics": { "processVsTask": "task", "runningTime": "short", "collaboration": "single", "invocation": "on-demand" },
-      "aliases": ["EvaluationFlow"],
-      "keywords": ["evaluation flow", "orchestration entry criteria flow", "orchestration exit criteria flow", "flow that decides whether an orchestration step can start or a step or stage can finish"],
-      "$note": "The determination flow behind an orchestration's entry/exit criteria: a restricted, read-only autolaunched flow (no record writes, actions, Apex, waits, or screens; subflows must also be EvaluationFlows) that returns the Boolean output `isOrchestrationConditionMet`. Normally co-generated or referenced from an Orchestrator / ApprovalWorkflow via elements/entry-exit-criteria/entry-exit-criteria.md, which carries the hand-off contract. Resolve here directly only on an explicit Evaluation Flow request; do not over-route generic automation to it. Next Best Action does NOT use EvaluationFlow — NBA recommendation logic is a RecommendationStrategy flow."
-    },
-    {
-      "specCategory": "Other",
-      "label": "Other",
-      "tuple": {},
-      "characteristics": {},
-      "aliases": ["Other"],
-      "keywords": []
-    }
-  ],
-  "badPairs": [
-    {
-      "implies": "Before-save flow that sends email, makes a callout, or updates a related record",
-      "why": "Before-save cannot perform those operations and only mutates the triggering record in-place",
-      "redesign": "Use RecordAfterSave"
-    },
-    {
-      "implies": "Screen element inside an AutoLaunchedFlow or the background steps of an Orchestration",
-      "why": "Screen elements are not supported in headless contexts",
-      "redesign": "Net-new / GENERATE only: use processType Flow for a Screen Flow; model the interactive work as an interactive Orchestration stage; or split the work so a headless flow (AutoLaunchedFlow, or a platform event-triggered flow) does the background steps and a SEPARATE Screen Flow — launched by a user, not by the event — does the interactive part (see anti-patterns.md). In EVOLVE — editing a supplied flow — this pair is a process-type change: decline per recipes/author/author.md Phase 0; do not propose a separate flow."
-    },
-    {
-      "implies": "Wait/Pause element in RecordBeforeSave",
-      "why": "Wait elements are not allowed in before-save context",
-      "redesign": "Use RecordAfterSave, or move the wait into a subflow"
-    },
-    {
-      "implies": "Orchestrator or ApprovalWorkflow using RecordBeforeSave / RecordBeforeDelete",
-      "why": "Orchestrations run asynchronously across stages; they trigger only after the record is committed",
-      "redesign": "Use RecordAfterSave (record-triggered) or None (autolaunched)"
-    },
-    {
-      "implies": "Marketing campaign targeting an audience/segment but using Scheduled or RecordAfterSave",
-      "why": "Those triggers have no concept of segment/list/campaign membership, audience exclusion, or marketing frequency caps",
-      "redesign": "Use triggerType Segment, List, CampaignMember, or RecordQuery — whichever matches the audience source the user described. A broadcast that fans out a dynamic segment now is BroadcastNoTrigger, not Segment."
-    },
-    {
-      "implies": "A 'fire when the email is opened/clicked/bounced/responded-to' flow built as a Segment/record flow + a Wait Until Event element — or vice-versa",
-      "why": "IndivRelatedRecord (or Segment) + WaitUntilEvent runs the flow first and PAUSES for the event; AutomationEvent FIRES the whole flow when the event occurs. They are not interchangeable.",
-      "redesign": "Fire-on-event -> triggerType AutomationEvent. Run-then-wait -> Segment/record trigger + a WaitUntilEvent element mid-flow."
-    },
-    {
-      "implies": "A form-submission flow built as triggerType AutomationEvent with eventName/eventType trgrOnFormSubmission (the Form Submission row that event discovery returns when scoped to the Automation Event trigger)",
-      "why": "PROHIBITED. Flow Builder lists Form Submission under the Automation Event picker, but selecting it saves the flow as triggerType FormSubmissionEvent. The platform rejects AutomationEvent + trgrOnFormSubmission: the event name is invalid (rewritten to nullNotFound on save), the flow saves as InvalidDraft, and $Form references no longer resolve. Never emit it, even when the user says 'Automation Event' or discovery returns trgrOnFormSubmission.",
-      "redesign": "Use triggerType FormSubmissionEvent with start.form = the form's content FQN and read the submitted fields via $Form.<field> (see elements/start/form-submission-triggered.md)."
-    },
-    {
-      "implies": "A 'when someone submits our form' flow built as a Screen flow (processType Flow), or a form a user fills in step by step built as FormSubmissionEvent",
-      "why": "A submitted Marketing form fires a headless flow once per submission, with the answers in $Form; a Screen flow IS the form, stepped through interactively by a user. The word 'form' alone does not decide it.",
-      "redesign": "Submitted form (the flow reacts after someone submits it) -> triggerType FormSubmissionEvent. A form the user fills in or steps through inside the flow -> processType Flow (Screen)."
-    },
-    {
-      "implies": "A Data Cloud DMO (a `__dlm` object) record-change flow built as a core RecordAfterSave/RecordBeforeSave — or a core SObject trigger built as DataCloudDataChange",
-      "why": "DataCloudDataChange fires on a Data Cloud DMO record change and exposes the DMO as a read-only $Record; core record triggers fire on a CRM SObject. They are not interchangeable, and a DMO is never a writable DML target.",
-      "redesign": "A `__dlm` target -> triggerType DataCloudDataChange (single DMO) or DataGraphDataChange (data graph). A core SObject -> RecordAfterSave / RecordBeforeSave / RecordBeforeDelete."
-    },
-    {
-      "implies": "A broadcast flow, or a flow that fans out a dynamic segment now, built as triggerType Segment",
-      "why": "Segment is a scheduled or on-activate audience trigger and rejects non-Individual segments. BroadcastNoTrigger fans the segment out from the start, including an Account segment, with no schedule.",
-      "redesign": "Use triggerType BroadcastNoTrigger. Put the segment on start.fanOutAction (actionType cdpJitSegment, actionName = the segment API name). Do not apply the Segment eligibility gate."
-    },
-    {
-      "implies": "An On-Demand Flow, or a marketing send that an app or the API starts for one person, built as a no-trigger autolaunched flow",
-      "why": "A no-trigger AutoLaunchedFlow rejects marketing send actions (You can't use the Send SMS Message action type in flows with the Autolaunched Flow process type).",
-      "redesign": "Use triggerType OnDemandNoTrigger with a top-level dataSpace (resolved as in elements/start/audience-common.md, Set the data space). Take the recipient from the reserved request inputs; do not add a recipient parameter."
-    }
-  ]
-}