@salesforce/afv-skills 1.65.0 → 1.65.1

package/skills/fsc-digital-origination-bre-permissions-assign/SKILL.md

@@ -1,111 +0,0 @@
----
-name: fsc-digital-origination-bre-permissions-assign
-parent: "digital-origination-bre-setup"
-purpose: "Assign and verify the permission sets and Context Service access needed to build and run the lending decision-matrix BREs."
-description: "Assign and verify the permission-set access required to configure and run the Digital Lending decision-matrix Business Rules Engine setups (Disclosures and Consent, Document Upload, and STP applicant eligibility), and enable Context Service so decision-matrix evaluation works. Handles the Digital Lending, Rule Engine Designer, Product Catalog Management Designer/Viewer, and OmniStudio Admin/User access documented by the help articles. Reuses the approved PermSets SOR and standard assignment APIs, is idempotent on rerun, and never assigns access to inferred users or service accounts."
-metadata:
-  version: "1.0"
----
-
-# Digital Origination BRE permissions
-
-Prepare a specifically identified admin or runtime user for the lending decision-matrix Business Rules
-Engine setups, and enable Context Service so the matrices can be evaluated. This sibling manages access
-and one org-level enablement; it does not create matrices, records, or OmniScripts.
-
-## Inputs
-
-- Explicit target-org alias
-- Explicit target user ID or username
-- Role: design-time admin, runtime user, or both
-
-Never select all active users. Never target Automated Process, integration, guest, or service users.
-
-## Required access matrix
-
-The three help articles state the same permission surface. Resolve exact API names from the target org;
-labels can differ by release.
-
-| Role | Required product-supplied access |
-|---|---|
-| Set up Digital Lending | Digital Lending permission set |
-| Configure the Business Rules Engine (design time) | Rule Engine Designer AND Product Catalog Management Designer AND OmniStudio Admin |
-| Run the Business Rules Engine (runtime) | Product Catalog Management Viewer AND OmniStudio User |
-
-Do not manufacture a custom replacement for a missing product-supplied set. Report a missing
-entitlement or package artifact as a blocker.
-
-## Reusable operations
-
-Use the **Permission Sets** entity SOR (find it with `discover`, then `describe` it for these operations):
-
-- `get-permission-set-details` - Tooling read of a permission set and its `Permissions*` fields.
-- `assign-users` - create `PermissionSetAssignment` using AssigneeId and PermissionSetId.
-- `unassign-users` - rollback an assignment created by this run.
-- `edit-assignment-expiration` - update an explicitly requested expiration.
-
-For any permission-set-license required by the selected sets, query and create `PermissionSetLicenseAssign`
-through standard sObject REST. Assign a missing license before its permission set.
-
-## Context Service enablement
-
-Decision-matrix evaluation runs behind the Context Service feature family (`ContextResourceFamily`,
-org gate `IndustriesContext.orgHasIndustriesContextService`). When the gate is off, the matrix
-evaluation and OmniScript decision-matrix action element return HTTP 403 `FUNCTIONALITY_NOT_ENABLED`.
-
-Enable it headlessly via the Context Service Connect API — the `preferenceName` must be exactly
-`contextServiceEnabled` (not `ContextService`), and `uniqueIdentifier` is the 18-char Org Id:
-
-```text
-PUT /connect/contextservice/access/contextServiceEnabled/{orgId}  {"isEnabled":true}
-```
-
-If the family-level gate itself is not yet on, the PUT cannot reach the resource; in that case stop at
-the Setup checkpoint **Context Service Settings → enable Context Definitions**
-(`/lightning/setup/ContextServiceSettings/home`) and resume after the admin confirms. Verify a gate by
-calling its cheapest live endpoint (e.g. a decision-matrix read) rather than trusting the preference
-read-back, which can lag.
-
-Enabling an org preference is an org-wide change: report it explicitly and enable only after confirming
-the target org is the intended one.
-
-## Workflow
-
-1. Confirm org and target user. Query `User` and report username, profile, active state, and user type.
-2. Resolve each required set by its unique API `Name` first — the `Name` column is unique per org, the
-   `Label` is not. Query `PermissionSet` by `Name`, and fall back to `Label` only when the API name is
-   unknown. Capture Id, `Name`, `Label`, LicenseId, `NamespacePrefix`, and `IsOwnedByProfile`.
-3. If a `Label` query returns more than one candidate — common for the OmniStudio sets whose display
-   labels (`OmniStudio User`, `OmniStudio Admin`) collide with profile-owned or duplicate sets —
-   disambiguate deterministically **before** halting: keep only the product-supplied set
-   (`IsOwnedByProfile = false` with a non-null managed `NamespacePrefix`) and de-duplicate on `Name`.
-   Stop and ask **only** when two genuinely distinct product-supplied sets still survive that narrowing;
-   a profile-owned or namespace-duplicate label collision is NOT a reason to halt. Never guess between
-   two real product-supplied sets.
-4. Query any required `PermissionSetLicense` and existing `PermissionSetLicenseAssign`. Assign a
-   missing license before its permission set.
-5. Query existing `PermissionSetAssignment` records for the target user and candidate set IDs.
-6. Create only missing assignments. Treat `DUPLICATE_VALUE` as already assigned, then re-query.
-7. Re-read the assigned permission sets and assignments and verify each is attached to the intended
-   user.
-8. Confirm Context Service is enabled; if not, enable it as above and re-verify with a live endpoint.
-
-## Failure and rollback rules
-
-- Missing permission set or license: report the exact missing API/label and stop dependent BRE steps.
-- License-limit failure: do not remove another user's license; report the limit.
-- Assignment failure: preserve successful pre-existing assignments; remove only assignments created by
-  this run and only when the user requests rollback.
-- Never edit a standard managed permission set.
-
-## Output contract
-
-Return a table with target user, role, permission-set API name/ID, license ID if applicable, prior
-state, action, verified final state, and the Context Service enablement result. Separate blockers from
-optional runtime-user access.
-
-## Definition of done
-
-Every required design-time or runtime assignment for the explicitly selected role is present and
-verified in fresh queries, and Context Service reads enabled (or a Setup checkpoint is reported). No
-unrelated user or assignment was changed.

package/skills/fsc-digital-origination-bre-setup-coordinate/SKILL.md

@@ -1,250 +0,0 @@
----
-name: fsc-digital-origination-bre-setup-coordinate
-description: "End-to-end orchestrator for the Digital Origination (Digital Lending) Business Rules Engine setups that run on decision matrices: Disclosures and Consent, Document Upload, and Straight-Through Processing (applicant eligibility). Routes an unqualified \"set up the lending BREs\" request through nested sub-skills for permissions, the shared decision-matrix create/activate mechanics, and each of the three feature builds. Use this skill for the whole ordered journey, and use a sibling directly for a narrowed request such as \"create the disclosures and consent decision matrix\" or \"set up the STP eligibility matrix\"."
-metadata:
-  version: "1.0"
----
-
-# Digital Origination Business Rules Engine setup orchestrator
-
-Orchestrate the three decision-matrix-based Business Rules Engine setups for **Digital Origination**,
-whose underlying APIs and setup artifacts still use the **Digital Lending** name. This skill owns
-sequencing and state transfer between the sub-skills. It does not duplicate the implementation
-contracts maintained by its nested sub-skills.
-
-All three features share the same building block: a Business Rules Engine **decision matrix** (an
-admin-typed lookup of input columns to output columns), created and activated through the shared
-`decision-matrix-foundation` sibling, then populated with feature-specific columns and rows. This is a
-different Business Rules Engine surface from the source-object **decision tables** used by
-`digital-origination-pricing-setup`; do not conflate the two.
-
-## Mandatory prerequisites
-
-Before routing to any sibling, verify:
-
-1. Digital Origination Initial Setup is complete. If not, route to
-   `fsc-mandalorians/digital-origination-initial-setup` and stop.
-2. The target org alias and acting admin are explicit.
-3. The relevant feature is understood: **Disclosures and Consent**, **Document Upload**, and
-   **applicant-eligibility STP** are three independent Discovery Framework features. Set up only the
-   ones the admin requests.
-4. The admin has supplied or approved the concrete inputs — products, applicant types, credit-score
-   cutoffs, document types, and consent/disclosure text. Help-article examples are never customer
-   defaults.
-
-## Ordered journey
-
-```text
-Initial Setup (existing sibling)
- |
-1. BRE permissions
- |
-2. Feature build(s), each: decision-matrix-foundation (create + activate) then the feature sibling
-    - Disclosures and Consent
-    - Document Upload
-    - STP applicant eligibility
-```
-
-The three feature builds are independent — run whichever the admin asked for, in any order. Within a
-feature build, always create and activate the matrix shell through `decision-matrix-foundation` before
-the feature sibling loads columns/rows and supporting records. Run one sibling at a time. Do not
-continue after a sibling reports a blocking prerequisite or a manual checkpoint that has not been
-completed.
-
-### Step 1 - BRE permissions
-
-Delegate to nested skill `permissions` (emitted SOR
-`fsc-mandalorians/digital-origination-bre-setup-permissions`) with hints such as:
-
-- "assign the Digital Lending permission set"
-- "assign Rule Engine Designer and Product Catalog Management Designer"
-- "assign Product Catalog Management Viewer and OmniStudio User for runtime"
-- "enable Context Service for decision-matrix evaluation"
-
-Required handoff: target user IDs, resolved permission-set IDs/API names, and a fresh verification of
-every required assignment.
-
-### Step 2 - Decision-matrix foundation (per feature)
-
-Delegate to nested skill `decision-matrix-foundation` (emitted SOR
-`fsc-mandalorians/digital-origination-bre-setup-decision-matrix-foundation`) to create the named matrix (a
-`CalculationMatrix` sObject), add its columns (which auto-creates version 1), add its rows, and activate
-it. Pass the exact matrix name, the column contract, and the row values from the feature sibling.
-Required handoff: `CalculationMatrix` id, `CalculationMatrixVersion` id, and a fresh read confirming the
-version's active window (StartDateTime set, EndDateTime null).
-
-### Step 3 - Disclosures and Consent
-
-Delegate to nested skill `disclosures-consent` (emitted SOR
-`fsc-mandalorians/digital-origination-bre-setup-disclosures-consent`) with hints such as:
-
-- "set up disclosure and consent for a home loan product"
-- "create the data use purpose and authorization form"
-
-This sibling drives `decision-matrix-foundation` for a matrix keyed on Product Id / ApplicantType /
-Level with a Data Use Purpose output, and creates the supporting Product, Data Use Purpose, and
-Authorization Form records. Required handoff: matrix ID/version, Data Use Purpose ID, Authorization
-Form ID, and the activated matrix row linking them.
-
-### Step 4 - Document Upload
-
-Delegate to nested skill `document-upload` (emitted SOR
-`fsc-mandalorians/digital-origination-bre-setup-document-upload`) with hints such as:
-
-- "set up the document upload decision matrix for lending"
-- "create the lending document types"
-
-This sibling drives `decision-matrix-foundation` for a matrix keyed on productId / applicantType /
-level with a docTypeLabel output, and reuses the Document Type / Document Category entity SORs.
-Required handoff: matrix ID/version, Document Type API name(s), and the activated matrix row.
-
-### Step 5 - STP applicant eligibility
-
-Delegate to nested skill `stp-eligibility` (emitted SOR
-`fsc-mandalorians/digital-origination-bre-setup-stp-eligibility`) with hints such as:
-
-- "set up the IsSTPApplication decision matrix"
-- "automatically approve or reject a loan by credit score"
-
-This sibling drives `decision-matrix-foundation` for the `IsSTPApplication` matrix (CreditScore input,
-IsSTP output) and then **verifies and activates** the preconfigured `DigitalLendingDFIsSTPApplication`
-OmniScript that references the matrix. Required handoff: matrix ID/version, the live BRE lookup result,
-and the OmniScript verification/activation result.
-
-**OmniScript dependency (blocker, not a build).** The `DigitalLendingDFIsSTPApplication` OmniScript
-(type `DigitalLendingDF`, subType `IsSTPApplication`; variant `DigitalLendingDFIsSTPApplicationAAE`) is
-delivered by a Discovery Framework template, not created here. If it is absent, the STP sibling reports
-a blocker; obtain the Discovery Framework / Digital Lending sample-template deployment from its owner
-before completing STP. If it is present but inactive (template deploys land it `IsActive=false`), the
-sibling activates it. Disclosures and Document Upload do not depend on it.
-
-## Narrowed requests
-
-| User request | Route |
-|---|---|
-| Assign the BRE / lending permissions only | Nested `permissions` |
-| Create or activate a lending decision matrix shell | Nested `decision-matrix-foundation` |
-| Set up disclosure and consent | Nested `disclosures-consent` |
-| Set up document upload / lending document types | Nested `document-upload` |
-| Set up STP / applicant-eligibility approval | Nested `stp-eligibility` |
-
-For a narrowed request, validate that its upstream artifacts (permissions, matrix shell) exist. Do not
-silently run the entire journey when the user asks for one feature.
-
-## Shared invariants
-
-- Read before write; reuse a matching matrix, record, or permission-set by exact API name and verified
-  shape rather than creating a duplicate.
-- Never infer customer products, applicant types, credit-score cutoffs, document types, or disclosure
-  text. Help-article values are examples only.
-- Treat a bare activation 200 as in progress, not success. Require a fresh read of the
-  `CalculationMatrixVersion` showing an active window (StartDateTime set, EndDateTime null) before
-  advancing — and for a matrix that feeds runtime, additionally require a live BRE lookup
-  (`POST /connect/business-rules/decision-matrices/{name}`) that returns an output. A matrix can read
-  Active and still return "no output for the specified input" if `CalculationMatrix.Type` is null (the
-  derived version `MatrixType` then breaks the lookup) or its row `Name` hashes are wrong; see
-  `decision-matrix-foundation`.
-- A guided Setup checkpoint is a valid partial outcome only when the relevant headless write is absent
-  or unverified. State exactly what remains and resume after confirmation.
-- Each sibling must produce fresh read-back evidence before this orchestrator advances.
-
-## Definition of done
-
-The requested feature build is complete only when:
-
-1. The required permission-set assignments are verified for the acting user, and Context Service is
-   enabled for matrix evaluation.
-2. Each feature's decision matrix exists as a `CalculationMatrix`, carries the exact columns and rows
-   for that feature, and its version reads active (StartDateTime set, EndDateTime null) on a fresh read.
-3. Disclosures and Consent additionally has an active Data Use Purpose and an Authorization Form
-   (English locale, with an active default Authorization Form Text and a Data Use junction) linked
-   through the activated matrix row.
-4. Document Upload additionally has the intended Document Type label(s) in the activated matrix row. If
-   the `DocumentType` sObject is absent on the org, note it as a supporting-metadata gap (the matrix
-   still builds — `docTypeLabel` is a free Text column).
-5. STP additionally has the `IsSTPApplication` matrix returning a decision from a live BRE lookup, and
-   the `DigitalLendingDFIsSTPApplication` OmniScript verified to reference the matrix and Active — or a
-   blocker reported if that OmniScript is absent.
-6. Every manual checkpoint or unresolved gap is explicitly reported. A partial run is never reported
-   as complete.
-
-## Individual sibling reference
-
-| Sibling | Responsibility | Primary corpus reuse |
-|---|---|---|
-| `permissions` | Digital Lending / Rule Engine / PCM / OmniStudio permission sets and Context Service | `entity/authorization-experience/PermSets` + Context Service enable |
-| `decision-matrix-foundation` | Create, populate, and activate a decision matrix shell | `CalculationMatrix` sObject insert (with `Type="Standard"`) + BRE Taurus decisionmatrix Connect columns API (`post-decision-matrix-columns`) + direct `CalculationMatrixRow` inserts (MD5-hash `Name`) + decision-matrix builder `activate-dmversion` |
-| `disclosures-consent` | Consent matrix plus Data Use Purpose and Authorization Form records | `decision-matrix-foundation` + sObject REST (describe-first) |
-| `document-upload` | Document-type matrix plus lending document types | `decision-matrix-foundation` + `entity/fsc-darksaber/DocumentType` + `entity/fsc-mandalorians/DocumentCategory` |
-| `stp-eligibility` | IsSTPApplication matrix plus OmniScript verification | `decision-matrix-foundation` + OmniStudio read |
-
-These are nested source skills. Project Codey compiles each to a parent-qualified sibling SOR and adds
-formal `delegates_to` steps to this parent. Run the Path-B harness on this parent `SKILL.md`; the
-family is merged, ingested, and served together.
-
-<!-- skill-validate: ignore-start -->
-<!-- codey:operations start -->
-## Operations Reference
-
-Operations this skill uses — routing and dependency reference.
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `delegate-digital-origination-bre-setup-permissions` | delegate | — | → `fsc-mandalorians/digital-origination-bre-setup-permissions` | — |
-| `delegate-digital-origination-bre-setup-decision-matrix-foundation` | delegate | — | → `fsc-mandalorians/digital-origination-bre-setup-decision-matrix-foundation` | `delegate-digital-origination-bre-setup-permissions` |
-| `delegate-digital-origination-bre-setup-disclosures-consent` | delegate | — | → `fsc-mandalorians/digital-origination-bre-setup-disclosures-consent` | `delegate-digital-origination-bre-setup-permissions` |
-| `delegate-digital-origination-bre-setup-document-upload` | delegate | — | → `fsc-mandalorians/digital-origination-bre-setup-document-upload` | `delegate-digital-origination-bre-setup-permissions` |
-| `delegate-digital-origination-bre-setup-stp-eligibility` | delegate | — | → `fsc-mandalorians/digital-origination-bre-setup-stp-eligibility` | `delegate-digital-origination-bre-setup-permissions` |
-| `preflight-context-service-enabled` | verify | — | `/connect/context-definitions` | `delegate-digital-origination-bre-setup-permissions` |
-| `preflight-stp-omniscript-present` | verify | — | — | `delegate-digital-origination-bre-setup-permissions` |
-| `permissions-confirm-org-and-target-user` | read | — | `GET /services/data/v63.0/query` | — |
-| `permissions-resolve-permission-sets-by-name` | read | — | `GET /services/data/v63.0/query` | `permissions-confirm-org-and-target-user` |
-| `permissions-assign-required-license` | write | — | `POST /services/data/v63.0/sobjects/PermissionSetLicenseAssign` | `permissions-resolve-permission-sets-by-name` |
-| `permissions-assign-permission-sets` | write | — | `POST /services/data/v63.0/sobjects/PermissionSetAssignment` | `permissions-assign-required-license` |
-| `permissions-enable-context-service` | write | — | `PUT /services/data/v63.0/connect/contextservice/access/contextServiceEnabled/{orgId}` | `permissions-assign-permission-sets` |
-| `permissions-verify-context-service-live` | verify | — | `GET /services/data/v63.0/connect/context-definitions` | `permissions-enable-context-service` |
-| `permissions-verify-assignments` | verify | — | `GET /services/data/v63.0/query` | `permissions-verify-context-service-live` |
-| `decision-matrix-foundation-verify-context-service-gate` | verify | — | `GET /services/data/v63.0/connect/context-definitions` | — |
-| `decision-matrix-foundation-resolve-existing-calculation-matrix` | read | — | `GET /services/data/v63.0/query` | `decision-matrix-foundation-verify-context-service-gate` |
-| `decision-matrix-foundation-create-calculation-matrix` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrix` | `decision-matrix-foundation-resolve-existing-calculation-matrix` |
-| `decision-matrix-foundation-set-matrix-type-standard` | write | — | `PATCH /services/data/v63.0/sobjects/CalculationMatrix/{matrixId}` | `decision-matrix-foundation-create-calculation-matrix` |
-| `decision-matrix-foundation-add-decision-matrix-columns` | write | — | `POST /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/columns` | `decision-matrix-foundation-set-matrix-type-standard` |
-| `decision-matrix-foundation-resolve-auto-created-version` | verify | — | `GET /services/data/v63.0/query` | `decision-matrix-foundation-add-decision-matrix-columns` |
-| `decision-matrix-foundation-verify-decision-matrix-columns` | verify | — | `GET /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/columns` | `decision-matrix-foundation-resolve-auto-created-version` |
-| `decision-matrix-foundation-insert-calculation-matrix-rows` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrixRow` | `decision-matrix-foundation-verify-decision-matrix-columns` |
-| `decision-matrix-foundation-verify-calculation-matrix-rows` | verify | — | `GET /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/versions/{versionId}/rows` | `decision-matrix-foundation-insert-calculation-matrix-rows` |
-| `decision-matrix-foundation-activate-matrix-version` | write | — | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion` | `decision-matrix-foundation-verify-calculation-matrix-rows` |
-| `decision-matrix-foundation-verify-active-window` | verify | — | `GET /services/data/v63.0/query` | `decision-matrix-foundation-activate-matrix-version` |
-| `decision-matrix-foundation-verify-live-bre-lookup` | verify | — | `POST /services/data/v63.0/connect/business-rules/decision-matrices/{matrixName}` | `decision-matrix-foundation-verify-active-window` |
-| `decision-matrix-foundation-edit-rows-on-enabled-version` | write | — | `PATCH /services/data/v63.0/sobjects/CalculationMatrixVersion/{versionId}` | `decision-matrix-foundation-verify-live-bre-lookup` |
-| `disclosures-consent-resolve-or-create-lending-product` | write | — | `GET /services/data/v63.0/query` | — |
-| `disclosures-consent-resolve-or-create-data-use-purpose` | write | — | `GET /services/data/v63.0/query` | `disclosures-consent-resolve-or-create-lending-product` |
-| `disclosures-consent-create-authorization-form` | write | — | `POST /services/data/v63.0/sobjects/AuthorizationForm` | `disclosures-consent-resolve-or-create-data-use-purpose` |
-| `disclosures-consent-create-authorization-form-text` | write | — | `POST /services/data/v63.0/sobjects/AuthorizationFormText` | `disclosures-consent-create-authorization-form` |
-| `disclosures-consent-set-default-auth-form-text` | write | — | `PATCH /services/data/v63.0/sobjects/AuthorizationForm/{authorizationFormId}` | `disclosures-consent-create-authorization-form-text` |
-| `disclosures-consent-link-authorization-form-data-use` | write | — | `POST /services/data/v63.0/sobjects/AuthorizationFormDataUse` | `disclosures-consent-set-default-auth-form-text` |
-| `disclosures-consent-activate-data-use-purpose` | write | — | `PATCH /services/data/v63.0/sobjects/DataUsePurpose/{dataUsePurposeId}` | `disclosures-consent-link-authorization-form-data-use` |
-| `disclosures-consent-resolve-or-create-consent-matrix` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrix` | `disclosures-consent-activate-data-use-purpose` |
-| `disclosures-consent-add-consent-matrix-columns` | write | — | `POST /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/columns` | `disclosures-consent-resolve-or-create-consent-matrix` |
-| `disclosures-consent-insert-consent-matrix-row` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrixRow` | `disclosures-consent-add-consent-matrix-columns` |
-| `disclosures-consent-activate-consent-matrix-version` | write | — | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion` | `disclosures-consent-insert-consent-matrix-row` |
-| `disclosures-consent-verify-consent-matrix-live` | verify | — | `POST /services/data/v63.0/connect/business-rules/decision-matrices/{matrixName}` | `disclosures-consent-activate-consent-matrix-version` |
-| `document-upload-resolve-or-create-lending-product` | write | — | `GET /services/data/v63.0/query` | — |
-| `document-upload-resolve-or-create-document-type` | write | — | `GET /services/data/v63.0/query` | `document-upload-resolve-or-create-lending-product` |
-| `document-upload-resolve-or-create-document-category-and-junction` | write | — | `POST /services/data/v63.0/sobjects/DocumentCategoryDocumentType` | `document-upload-resolve-or-create-document-type` |
-| `document-upload-resolve-or-create-document-upload-matrix` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrix` | `document-upload-resolve-or-create-document-category-and-junction` |
-| `document-upload-add-document-upload-matrix-columns` | write | — | `POST /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/columns` | `document-upload-resolve-or-create-document-upload-matrix` |
-| `document-upload-insert-document-upload-matrix-rows` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrixRow` | `document-upload-add-document-upload-matrix-columns` |
-| `document-upload-activate-document-upload-matrix-version` | write | — | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion` | `document-upload-insert-document-upload-matrix-rows` |
-| `document-upload-verify-document-upload-matrix-live` | verify | — | `POST /services/data/v63.0/connect/business-rules/decision-matrices/{matrixName}` | `document-upload-activate-document-upload-matrix-version` |
-| `stp-eligibility-resolve-or-create-stp-matrix` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrix` | — |
-| `stp-eligibility-add-stp-matrix-columns` | write | — | `POST /services/data/v63.0/connect/omnistudio/decision-matrices/{matrixId}/columns` | `stp-eligibility-resolve-or-create-stp-matrix` |
-| `stp-eligibility-insert-stp-matrix-rows` | write | — | `POST /services/data/v63.0/sobjects/CalculationMatrixRow` | `stp-eligibility-add-stp-matrix-columns` |
-| `stp-eligibility-activate-stp-matrix-version` | write | — | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion` | `stp-eligibility-insert-stp-matrix-rows` |
-| `stp-eligibility-verify-stp-matrix-live` | verify | — | `POST /services/data/v63.0/connect/business-rules/decision-matrices/IsSTPApplication` | `stp-eligibility-activate-stp-matrix-version` |
-| `stp-eligibility-resolve-stp-omniscript` | read | — | `GET /services/data/v63.0/query` | `stp-eligibility-verify-stp-matrix-live` |
-| `stp-eligibility-verify-omniscript-references-matrix` | verify | — | `GET /services/data/v63.0/query` | `stp-eligibility-resolve-stp-omniscript` |
-| `stp-eligibility-activate-omniscript-if-inactive` | write | — | `PATCH /services/data/v63.0/sobjects/OmniProcess/{omniProcessId}` | `stp-eligibility-verify-omniscript-references-matrix` |
-| `stp-eligibility-verify-omniscript-active` | verify | — | `GET /services/data/v63.0/query` | `stp-eligibility-activate-omniscript-if-inactive` |
-<!-- codey:operations end -->
-<!-- skill-validate: ignore-end -->

package/skills/fsc-digital-origination-bre-stp-eligibility-configure/SKILL.md

@@ -1,122 +0,0 @@
----
-name: fsc-digital-origination-bre-stp-eligibility-configure
-parent: "digital-origination-bre-setup"
-purpose: "Set up the IsSTPApplication decision matrix that auto-approves or rejects a loan by credit score, and verify the OmniScript that consumes it."
-description: "Set up Straight-Through Processing for Digital Lending applicant eligibility: a Business Rules Engine decision matrix named IsSTPApplication that returns whether a loan application qualifies for automatic approval based on the applicant's credit score. Drives the shared decision-matrix-foundation sibling for the matrix, enforces the exact name the preconfigured DigitalLendingDFIsSTPApplication OmniScript expects, and verifies that OmniScript references the matrix. Treats the OmniScript as a delivered artifact it verifies, not one it creates."
-metadata:
-  version: "1.0"
----
-
-# Digital Origination STP applicant eligibility
-
-Automate loan approval by credit score. A decision matrix named `IsSTPApplication` returns whether an
-application qualifies for straight-through processing; the preconfigured `DigitalLendingDFIsSTPApplication`
-OmniScript reads that result to show the applicant a confirm-offer or submitted-offer page. This
-sibling owns the matrix and the verification that the OmniScript is wired to it. It does not create the
-OmniScript.
-
-The delivered OmniScript is `DigitalLendingDFIsSTPApplication` (type `DigitalLendingDF`, subType
-`IsSTPApplication`, language `English`; unique key `DigitalLendingDF_IsSTPApplication_English_1`), with an
-Angular/agent-console variant `DigitalLendingDFIsSTPApplicationAAE`. Inside it, the decision-matrix
-**action element is named exactly `IsSTPApplication`** — that element name, not the OmniScript name, is
-what the matrix name must match.
-
-Source: Salesforce Help "Applicant Eligibility Check by Using Business Rules Engine for Digital
-Lending" — the sub-topics "Approve or Reject a Loan Automatically" and "Verify the
-DigitalLendingDFIsSTPApplication OmniScript".
-
-## Required inputs
-
-- Target-org alias and acting admin.
-- The credit-score cutoff for automatic approval (the example approves at 740 and above, rejects 0–739).
-  The cutoff is a customer decision; the example value is not a default.
-
-## Decision matrix contract
-
-Drive nested `decision-matrix-foundation` to create and activate a decision matrix with the exact name
-`IsSTPApplication`:
-
-| Column header (apiName) | columnType | dataType |
-|---|---|---|
-| `CreditScore` | `Input` | `NumberRange` |
-| `IsSTP` | `Output` | `Boolean` |
-
-Row contract (example values — replace with the customer's cutoff):
-
-| CreditScore | IsSTP |
-|---|---|
-| `min 0, max 739` | `false` |
-| `min 740, max 9999` | `true` |
-
-Use the exact `CalculationMatrixColumn` enum tokens (`NumberRange`, `Boolean`) — not the English
-labels.
-
-**Runtime-critical (org-verified): the matrix needs `CalculationMatrix.Type="Standard"`, and its rows are
-direct `CalculationMatrixRow` inserts keyed by an MD5-hash `Name`.** The one thing that stops an
-`IsSTPApplication` matrix from evaluating is a null `Type` on the `CalculationMatrix` — its derived
-`MatrixType` then reads null and the BRE lookup throws "Unsupported Matrix type null", surfaced as
-*"there isn't any output for the specified input parameters."* Set `Type="Standard"` right after creating
-the matrix. Rows are inserted directly as `CalculationMatrixRow` sObjects (the Connect
-`post-decision-matrix-rows` write 500s on the verified org); each row's `Name` MUST be the engine's MD5
-hash of the input columns (for `CreditScore`, `md5("CreditScore" + boundary)`), and its `InputData`
-carries the **band-boundary value as a string** (`{"CreditScore":"0"}`, `{"CreditScore":"740"}` — not a
-`{"min","max"}` object). The `NumberRange` **bands are defined once on the column's `RangeValues`** (a
-comma-separated boundary list, e.g. `0,740,10000`) at column-creation time — it cannot be edited once the
-version is enabled or the matrix has more than one version. Rows can only be written while the version is
-a **draft** (`IsEnabled=false`). Pick a sensible top boundary (e.g. 10000). Delegate the whole
-Type+column+row+activate sequence to `decision-matrix-foundation`, which owns this ordering and the hash
-algorithm.
-
-**Name is a hard contract.** The matrix name MUST be exactly `IsSTPApplication`, because it must match
-the decision-matrix action element name inside the `DigitalLendingDFIsSTPApplication` OmniScript. A
-differently named matrix will not drive the applicant's confirm-offer / submitted-offer pages. Do not
-create a variant name.
-
-## OmniScript verification and activation
-
-The `DigitalLendingDFIsSTPApplication` OmniScript is **delivered by a Discovery Framework template, not
-created by this sibling.** Verify and activate it:
-
-1. Confirm the `DigitalLendingDFIsSTPApplication` OmniScript exists in the target org (App Launcher →
-   OmniStudio → OmniScripts, or a read of the `OmniProcess` by name / by
-   `type='DigitalLendingDF' AND subType='IsSTPApplication'`).
-2. Confirm it contains a decision-matrix **action element** named `IsSTPApplication` — the same name as
-   the matrix created above. This is a static read of `OmniProcessElement.PropertySetConfig`
-   (`"matrixName":"IsSTPApplication"`), which is present regardless of the OmniScript's active state.
-3. **Activate it if it is inactive.** Template deploys land the OmniScript `IsActive=false`, version 1.
-   Activate by setting `OmniProcess.IsActive=true` (the field is directly updateable) and read it back to
-   confirm `isActive:true` with `propertySetConfig` preserved. Only an active version is loadable at
-   runtime.
-
-**Blocker, not a build.** If the OmniScript is absent, stop and report a blocker: the
-`DigitalLendingDFIsSTPApplication` OmniScript must be deployed from the Discovery Framework / Digital
-Lending sample template, which is owned outside this skill (see `digital-origination-initial-setup` for
-enabling sample templates; materializing the OmniScripts requires deploying the template package).
-Report exactly what is missing and which artifact provides it; do not attempt to author the OmniScript
-here. The matrix build above still completes independently and its result is reported.
-
-If the OmniScript exists but references a different action-element name, report the mismatch and the
-required name (`IsSTPApplication`) rather than silently renaming either side.
-
-## Idempotency and rollback
-
-- Reuse an exact-match `IsSTPApplication` matrix rather than creating a duplicate; on a shape mismatch
-  present the diff and stop.
-- Rollback removes only rows added by this run, and only after confirming the OmniScript does not
-  depend on them.
-- Never modify or delete the delivered OmniScript.
-
-## Output contract
-
-Return the `IsSTPApplication` matrix ID/version, active status, verified columns and rows, the live BRE
-lookup result proving the matrix evaluates (a credit score above the cutoff returns `IsSTP=true`, below
-returns `false`), and the OmniScript verification result (present, active, and references
-`IsSTPApplication`, or the specific blocker/mismatch).
-
-## Definition of done
-
-The `IsSTPApplication` matrix is Active with the approval/rejection rows **and returns a decision from a
-live `POST /connect/business-rules/decision-matrices/IsSTPApplication` lookup** (not merely readable via
-the builder GET), and the `DigitalLendingDFIsSTPApplication` OmniScript is verified to reference it and is
-Active — or the missing-OmniScript blocker is reported explicitly. A partial run is never reported as
-complete.