Decision Log (Locked)

ID	Decision	Status	Rationale	Impacted Phases
MX-001	Canonical model is `Pipeline -> Track -> Stage`	Locked	Supports multi-track orchestration cleanly	01-07
MX-002	Project progression stored in `ProjectStageState` records	Locked	Replaces brittle single-pointer round state	01-07
MX-003	Intake is stage-native (`INTAKE`) rather than implicit pre-round behavior	Locked	Removes hidden workflow behavior	01-04
MX-004	Full-cutover delivery with no compatibility bridge	Locked	Faster convergence to clean runtime	00-07
MX-005	Special awards are first-class `Track` entities	Locked	Prevents duplicated orchestration logic	01-06
MX-006	Award routing modes are `parallel`, `exclusive`, `post_main`	Locked	Supports real sponsor policy diversity	02,05
MX-007	Award governance modes include `JURY_VOTE`, `AWARD_MASTER`, `ADMIN`	Locked	Explicit and policy-aligned control surfaces	05
MX-008	Live progression source of truth is admin cursor	Locked	Needed for non-linear live event control	02,04
MX-009	Voting windows are explicit open/close operations	Locked	Schedules alone are insufficient during live operations	02,04
MX-010	Assignment engine guarantees eligible project coverage	Locked	Operational fairness and delivery reliability	02,04
MX-011	Overrides require reason and immutable audit entries	Locked	Governance and explainability	02,05,07
MX-012	Release is blocked by legacy symbol sweep failures	Locked	Prevents half-migrated runtime behavior	06,07