Register iids-portfolio domain in data-governance catalog - #172
Merged
Conversation
Closes #168, closes #159. Step 5 of 5 in the lifecycle-taxonomy rollout (ADR 0001). The IIDS Portfolio site's controlled vocabularies are now registered upstream in ui-insight/data-governance and policed by the drift workflow on every PR. What lands: - Bumps vendor/data-governance submodule pointer to f6afe34 (ui-insight/data-governance#13), which adds vocabularies/iids-portfolio/allowed_values.json — six vocab groups (InterventionStatus, PublicStage, ProductionScope, Visibility, AI4RARelationship, WorkCategory). - Extends VocabularyValue with verificationRule?: string (ADR 0001 per-value extension; populated only on InterventionStatus and PublicStage in the iids-portfolio domain). - Updates scripts/build-governance-catalog.ts to read the new Verification_Rule field (with the snake_case fallback to match the existing field-handling pattern). - Regenerates lib/governance/vocabularies.ts: 49 → 55 vocab groups (+6 iids-portfolio groups). Catalog table count unchanged (iids-portfolio is a vocabularies-only domain — no DB schema is tracked here). Browser-verified at /standards/data-model/vocabularies — all 6 iids-portfolio groups linked and rendering with descriptions and allowed values. Refs ADR #164, schema PR #169, verifier PR #170, UI PR #171. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Governance catalog changes6 vocabulary group(s) added, 0 removed. Vocabulary groups (+6 / -0)Added
Posted by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What lands
vendor/data-governance→ f6afe34 (the merged ui-insight/data-governance#13), which addsvocabularies/iids-portfolio/allowed_values.jsonwith six vocabulary groups:InterventionStatus(10),PublicStage(5),ProductionScope(3),Visibility(3),AI4RARelationship(5),WorkCategory(8).VocabularyValuegains an optionalverificationRule?: stringfield (ADR 0001 per-value extension). Populated only for theInterventionStatusandPublicStagegroups in theiids-portfoliodomain — other domains/groups leave it unset and continue to work unchanged.scripts/build-governance-catalog.tsreads the newVerification_Rulefield (with the snake_case fallback that matches the existing field-handling pattern).lib/governance/vocabularies.tsrebuilt — 49 → 55 vocabulary groups. Table count unchanged (iids-portfoliois vocabularies-only; no DB schema tracked here).Test plan
npm run build:governanceregenerates with the new domainnpm run buildpasses/standards/data-model/vocabularies— all 6iids-portfoliogroups linked/standards/data-model/vocabularies/iids-portfolio/InterventionStatus— 10 allowed values render with descriptionsGovernance Driftworkflow passes (no false positives from the new domain),Catalog change summaryPR comment renders the new domain's diff correctlyRefs
🤖 Generated with Claude Code