{
  "format": "vercy-enterprise-profile-fixtures/v1",
  "profileName": "Enterprise Project and Change Management",
  "cases": [
    {"id":"shared-tracker","kind":"positive","input":"Projects P-A and P-B share tracker T and product X; each work item resolves its project explicitly.","expect":"P-A and P-B remain distinct; T and X create no project identity merge."},
    {"id":"successor-baseline","kind":"positive","input":"Approved change CR-7 cites BL-1 and causes project P-A to issue BL-2.","expect":"BL-2 supersedes BL-1 with explicit effectivity while BL-1 remains resolvable."},
    {"id":"acceptance-survives","kind":"positive","input":"A deliverable accepted under criteria C1 is unchanged when BL-2 succeeds BL-1.","expect":"The acceptance remains pinned to C1 and is not silently rebound."},
    {"id":"baseline-pins-plan-revision","kind":"positive","input":"BL-1 pins plan revision P-R7; the working plan later advances to P-R8 before BL-2 is approved.","expect":"BL-1 continues to resolve P-R7 and all historical variance remains reproducible."},
    {"id":"partial-rebaseline-complete-package","kind":"positive","input":"Only schedule changes; BL-2 is created with new schedule pins and the unchanged BL-1 scope and cost pins.","expect":"BL-2 is a complete atomic package while unchanged dimensions remain traceable to their immutable pins."},
    {"id":"milestone-achievement-evidence","kind":"positive","input":"A milestone is recorded met with effective time, authority and evidence while related tasks remain independently tracked.","expect":"Achievement is valid without collapsing task completion into milestone identity."},
    {"id":"tracker-is-project","kind":"negative","input":"One long-lived Jira project is declared to be one business Project for all initiatives.","expect":"The profile rejects tracker-container identity as Project identity."},
    {"id":"approved-change-mutates","kind":"negative","input":"Approving CR-7 overwrites BL-1 in place.","expect":"The mutation is rejected; approval may only trigger a successor baseline."},
    {"id":"baseline-live-head","kind":"negative","input":"BL-1 references the current mutable plan head instead of an immutable revision or snapshot.","expect":"The package is rejected because later plan edits would rewrite BL-1 meaning."},
    {"id":"acceptance-same-row","kind":"negative","input":"A deliverable row is updated in place to represent its acceptance decision.","expect":"The update is rejected; Acceptance requires a separate immutable identity and pinned basis."},
    {"id":"snapshot-becomes-master","kind":"negative","input":"A copied plan snapshot inside BL-1 is edited and treated as the authoritative WM-ACT-008 plan revision.","expect":"The edit is rejected because snapshots are non-authoritative copies with immutable source provenance."},
    {"id":"change-reopens-acceptance","kind":"negative","input":"BL-2 automatically reopens every acceptance bound to BL-1 without an impact assertion.","expect":"The automatic reopening is rejected; re-verification requires explicit approved-change impact."},
    {"id":"task-is-milestone","kind":"negative","input":"A completed task automatically marks a milestone achieved without milestone evidence.","expect":"The inference is rejected."},
    {"id":"closure-closes-product","kind":"negative","input":"Closing project P-A retires shared product X and deletes its open change requests.","expect":"Both effects are rejected; product and unresolved obligations retain separate lifecycles."}
  ]
}