Legacy Migration Backlog

Controlled reconstruction plan for the historical MCC codebases.

Collaboration diagram for Legacy Migration Backlog:

Controlled reconstruction plan for the historical MCC codebases.

Historical code is design input, not source to copy without review. Every migrated concept must define its namespace, ownership, invalid states, embedded constraints, Foundation dependencies, tests, examples, and Doxygen contract before becoming public.

ID	State	Candidate domain
MIG-001	IN PROGRESS	Inventory and reconcile legacy public concepts; pitch, interval, scale, chord, key, and notation concepts are reconciled; rhythm continues in ACTION_PLAN.md phase 9
MIG-002	DONE	Pitch: letters, accidentals, octave, ordering (ACTION_PLAN.md phases 3 and 4)
MIG-003	IN PROGRESS	Musical note and textual formatting; formatting and keys are done (ACTION_PLAN.md phase 8), MCC::Note follows in phase 9
MIG-004	DONE	Musical interval representation and arithmetic (ACTION_PLAN.md phase 5)
MIG-005	DONE	Scale structure, properties, and definitions (ACTION_PLAN.md phase 6)
MIG-006	MOVED	MIDI note, message, and protocol representations belong to MIDILAR, not MCC (ACTION_PLAN.md phase 10)
MIG-007	TODO	Evaluate communications/ports as a separate library
MIG-008	TODO	Validate MCC as a dependency of MIDILAR

Communications, hardware ports, and runtime MIDI transports should not enter the composition core merely because they existed in an old monolithic tree. Their ownership will be decided during the inventory.