Problem
The drift validator at `scripts/check_governance_drift.py` flags a real registry/source-of-truth mismatch for ProcessMapping:
- Vendored data-governance registry (this repo): expects ProcessMapping to have 9 allowed-value groups / 70 values.
- Live catalog at `ui-insight/ProcessMapping` (`backend/.../allowed_values.json` or equivalent): currently has 10 groups / 78 values.
The submodule at `ui-insight/AISPEG` is already pinned to `data-governance@main` tip, so the fix has to land here first — bumping the AISPEG submodule pointer afterward will pick it up automatically.
How this surfaced
Discovered while wiring the drift validator into AISPEG's CI pipeline (`ui-insight/AISPEG#58`). The workflow correctly fails the build on this drift — that's the validator working as designed. The fix is upstream registry alignment, not a workflow change.
Suggested resolution
- Pull the live ProcessMapping allowed-values file and reconcile: identify the new group + 8 new values, decide whether they belong in the registry (likely yes if shipped to prod) or whether ProcessMapping has accidentally added uncontrolled values (less likely given the project's discipline).
- Update `vocabularies/processmapping/allowed_values.json` (and `catalog/processmapping.json` if its top-level counts need bumping).
- Land the registry update on `main`; AISPEG bumps its submodule pointer in a follow-up.
Downstream impact
Until this lands, AISPEG's CI drift check will report red on every PR — accurately reflecting registry drift but blocking merges. The AISPEG drift workflow is currently held open at `ui-insight/AISPEG#64` waiting on this + a separate `PORTFOLIO_GH_TOKEN` org secret.
Filed from the AISPEG side as part of the Data Governance Explorer epic.
Problem
The drift validator at `scripts/check_governance_drift.py` flags a real registry/source-of-truth mismatch for ProcessMapping:
The submodule at `ui-insight/AISPEG` is already pinned to `data-governance@main` tip, so the fix has to land here first — bumping the AISPEG submodule pointer afterward will pick it up automatically.
How this surfaced
Discovered while wiring the drift validator into AISPEG's CI pipeline (`ui-insight/AISPEG#58`). The workflow correctly fails the build on this drift — that's the validator working as designed. The fix is upstream registry alignment, not a workflow change.
Suggested resolution
Downstream impact
Until this lands, AISPEG's CI drift check will report red on every PR — accurately reflecting registry drift but blocking merges. The AISPEG drift workflow is currently held open at `ui-insight/AISPEG#64` waiting on this + a separate `PORTFOLIO_GH_TOKEN` org secret.
Filed from the AISPEG side as part of the Data Governance Explorer epic.