hf-increment

To distinguish a scope change increment from a hotfix, use fixed baseline assessment to determine if a change request modifies requirements, scope, or constraints versus performing defect repair, producing a structured change package for proper routing.

When a requirements increment is introduced, approved artifacts may need re-baselining by explicitly marking invalidated approvals, tasks, and evidence, while synchronizing Current Stage, Workflow Profile, Current Active Task, and Pending Reviews.

To route a change request to the correct canonical re-entry node, the structured change analysis selects a single canonical re-entry node and synchronizes the workflow profile, preventing unintended in-place patches during requirements modifications.

You need to re-baseline acceptance criteria and constraints when a change request represents an increment that explicitly invalidates existing approvals and tasks, requiring targeted updates to status fields without implementing the actual changes.

Yes, structured change analysis performs minimal, targeted updates to artifacts and status fields, outputting a change package and impact matrix without implementing the actual modifications to the approved artifacts.