refactor: update RAM RequirementArtifactType taxonomy#56
Merged
Conversation
refactor: update RAM RequirementArtifactType taxonomy Remove BUSINESS_RISK (consolidated into RISK) and add DEPENDENCY. - RequirementArtifactType: drop BUSINESS_RISK, add DEPENDENCY - ArtifactKeyPrefix: map RISK->RSK, DEPENDENCY->DEP, remove BR - frontend types.ts: sync REQUIREMENT_ARTIFACT_TYPES with backend enum - V4 Flyway migration: alter requirement_artifact and artifact_key_sequence enum columns for prod/staging - VISION_SCOPE.yml: rename BUSINESS_RISKS section to RISKS and align example identifiers with key prefixes Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> @
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
Updates the RAM
RequirementArtifactTypetaxonomy: removesBUSINESS_RISK(consolidated intoRISK) and adds a newDEPENDENCYtype.Changes
RequirementArtifactType— dropBUSINESS_RISK, addDEPENDENCY. Persisted via@Enumerated(EnumType.STRING), so the reordering is safe (no ordinal dependency).ArtifactKeyPrefix— mapRISK -> RSK,DEPENDENCY -> DEP; remove the oldBRprefix.frontend/src/apis/ram/types.ts— syncREQUIREMENT_ARTIFACT_TYPESwith the backend enum (content + order).V4__update_requirement_artifact_type_taxonomy.sql— new Flyway migration altering therequirement_artifactandartifact_key_sequenceenum columns for prod/staging (column attributes preserved). No data migration needed: prod/staging hold noBUSINESS_RISKorRISKrows.VISION_SCOPE.yml— rename theBUSINESS_RISKSsection toRISKSand align example identifiers with the key prefixes (RSK-,ASM-,DEP-).Notes
ddl-auto: create, so dev/integration tests build the schema from the entity; the V4 migration is the source of truth for prod/staging (ddl-auto: none).V2__ram_schema.sqlis intentionally left untouched (immutable applied migration).🤖 Generated with Claude Code
@