/MRS-Specification-RFC#11-data-model
The Problem
Early-stage composition is inherently incomplete:- You know the harmony before the orchestration
- You have a melody before the accompaniment
- You have rhythm sketches before final pitches
- Forced completeness leads to hallucinated filler
- Empty measures are ambiguous (rest or TBD?)
- Intent is lost — an empty measure might mean “rest” or “to be filled”
Placeholder Primitives
Placeholder Region
Mark a region as intentionally incomplete:| Field | Description |
|---|---|
:measures | UUID range |
:instruments | Affected instruments |
:intent | What kind of content is planned |
:description | Human-readable description |
Intent Types
| Intent | Description |
|---|---|
:melody | Melodic content TBD |
:accompaniment | Accompaniment pattern TBD |
:countermelody | Counter-line TBD |
:harmony | Harmonic content TBD |
:orchestration | Orchestration TBD |
:texture | General texture/pad TBD |
:rhythm | Rhythmic pattern TBD |
Sketch Rhythm
Provide rhythm without final pitches:Harmonic Sketch
Provide harmony without voicing:Validation Levels
MRS supports validation levels to accommodate draft states:| Level | Allows |
|---|---|
strict | No placeholders; all content complete |
permissive | Placeholders allowed; validates what exists |
sketch | Minimal validation; for early drafts |
Strict Validation
Permissive Validation
- Existing content is well-formed
- References are valid
- Placeholder intents are recognized
Sketch Validation
- Basic syntax
- UUID validity
- No content requirements