Phase 2: normalize and migrate the imported MIDI control corpus #2

Open
opened 2026-08-22 16:40:03 +00:00 by peterswimm · 0 comments
Owner

Goal\nTurn the imported midi-db corpus into reviewable OPSL 0.2 device seeds without promoting it wholesale.\n\n## Scope\n- Introduce a distinct control-address field instead of overloaded sysex-offset.\n- Classify records as hardware synth, effect, or utility.\n- Generate candidate 0.2 artifacts and provenance records from the audit.\n\n## Acceptance criteria\n- Migration output preserves source identifiers and licenses.\n- Taxonomy and control addresses are validated by schema.\n- Generated candidates are not runtime truth until individually promoted.\n- The corpus review and migration report are reproducible.\n\n## Non-goals\n- Hand-editing or promoting every imported definition.

## Goal\nTurn the imported midi-db corpus into reviewable OPSL 0.2 device seeds without promoting it wholesale.\n\n## Scope\n- Introduce a distinct control-address field instead of overloaded sysex-offset.\n- Classify records as hardware synth, effect, or utility.\n- Generate candidate 0.2 artifacts and provenance records from the audit.\n\n## Acceptance criteria\n- Migration output preserves source identifiers and licenses.\n- Taxonomy and control addresses are validated by schema.\n- Generated candidates are not runtime truth until individually promoted.\n- The corpus review and migration report are reproducible.\n\n## Non-goals\n- Hand-editing or promoting every imported definition.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
peter-swimm/opsl#2
No description provided.