Impact Analysis: Where-Used for Vocabularies and Rulesets Before You Rename

## The rename problem

In IBM ODM, renaming a BOM term required running a "where-used" search in Decision Center before committing — to understand which action rules, decision tables, and ruleflows referenced the term. Without that check, a rename broke every ruleset that used the term silently.

DecisionManager's Impact Analysis page (`/impact`) brings the same capability to the browser console, with two scan modes: vocabulary-level (BOM impact) and ruleset-level (cross-artifact dependency).

Vocabulary impact scan

The vocabulary impact scan answers: "if I rename `applicant.riskScore` to `applicant.creditRisk`, which rulesets break?"

Navigate to `/impact?vocabulary=<vocabularyId>`, select a term from the vocabulary tree, and click "Scan for references". The scanner queries every ruleset in the current project for `vocabularyRef` bindings to the selected term and returns:

- Ruleset name and version - Rule ID and rule name within the ruleset - The full binding expression containing the term - Whether the reference is in a condition, conclusion, or action statement

The result is a flat list with deep links into each referencing rule.

Ruleset dependency scan

The ruleset dependency scan answers: "if I change the output contract of ruleset A, which other rulesets will be affected?"

Navigate to `/impact?ruleset=<rulesetId>`. The scanner checks for:

- **Direct invocation**: rulesets that invoke the target via a `call` statement in a ruleflow - **Schema binding**: rulesets that reference the target's output schema as an input type - **Test suite coverage**: test suites that use the target as their execution subject (affected by an output contract change)

This is the dependency graph a platform team needs before refactoring a shared ruleset that multiple services consume.

Governance integration

The impact scan results are displayed with governance-aware context:

- The referencing version's state (draft, in_review, approved, published) - Whether a suite run exists for that version (does the impact have test coverage?) - A link to the compare page showing the current version vs the previous published version

This gives the reviewer answering "is it safe to rename this term?" the full picture: not just what references it, but whether those references have test coverage and whether they're currently under active development.

ODM where-used parity

ODM Decision Center's where-used search covered: - BOM terms referenced in action rules and decision tables - Shared ruleset invocations from ruleflows

DecisionManager's impact scan covers both, with additions: - **Version-aware**: results show the governance state of each referencing version - **Schema binding**: not just lexical reference but output-type binding - **Test coverage indicator**: shows whether each reference has active suite coverage

Typical pre-rename workflow

1. Open `/impact?vocabulary=<id>` 2. Select the term you intend to rename 3. Scan for references → review the list 4. For each referencing ruleset: open its current version, apply the rename, run its test suite 5. Promote each updated version through the normal governance lifecycle 6. Once all referencing versions are published with the new term name, rename the vocabulary term itself

This is a breaking change across multiple rulesets — the vocabulary scan makes the scope visible before you start, not after you've already committed.