REQ-FUN-113
Post-baseline schedule changes require approved Change Request
What
After a schedule baseline is approved for a project, any change to an activity's planned_start, planned_finish, estimated_duration, or its dependency edges SHALL require a referenced approved Change Request (change_request_id field on the mutation) and produce an audit row including that reference.
Why
established project management guidelines Perform Integrated Change Control mandates baseline-affecting changes go through the formal change-control process. This is the schedule side of the existing REQ-NFR-062 / REQ-BUS-003 rule.
How
Server-side check on activity PATCH/DELETE and dependency PATCH/DELETE: if an approved baseline exists for the project AND the field being changed is baseline-controlled, require change_request_id with state=approved; otherwise return HTTP 409 with code missing_change_request.
Done when
Attempting a baseline-affecting edit without a CR is rejected; the same edit succeeds when accompanied by an approved CR; audit row records the CR id.
Out of scope
Automatic re-baselining; CR templating beyond what the change-management-plan already provides.
established project management guidelines Mapping
Enforces Perform Integrated Change Control on schedule baseline.