Files
product-vamp/docs/composer/musical_capability_matrix.md
T
khodowany 68df7292ee Cleanup
2026-10-04 17:14:13 -05:00

2.0 KiB
Raw Blame History

Capabilities and boundaries

Relationship Active support Limit
Theme/return Source-derived feature and actual home realization Technical similarity does not prove recognition
Mapped/chord movement Complete sequences, chord traversal, contract-conditioned routes Bounded search can miss alternatives
Anticipation Joint arrival/hold and future-harmony contract Bounded early window
On-time/delayed arrival Selected pitch and uninterrupted tail No compulsory arrival per cell
Approach into anticipation Shared exact future target, both contracts Wrong octave/changed target rejects
Enclosure Both orders, semitone or mapped whole-tone upper Must surround under the exact rule
Minor sixth Bounded stable tonic/predominant color Written semantics/function authoritative
Other colors/suspensions/blues Existing explicit policies Annotation is not permission
Rhythm Coherent binary/tuplet groups and editable internal subdivision No arbitrary tuplet slicing
Guitar Strings 1–6, frets 1–12, no open strings Not full ergonomic certification
Accompaniment Independent canonical sparse comping No reactive solo-gap filling
Reference review All events, original labels, rule recognition Observations distinguished from validated support

Independent tests in tests/test_joint_arrivals.py extend the existing timing, evaluator, importer, physical, expression and dependency coverage. The four target files are not required fixtures.

All four target solos have legal positions under the explicitly confirmed guitar-written octave convention. Four Autumn electric events extend beyond the source-derived production vocal cutoff. This is reported, not repaired by changing either input.

Unexplained reference events remain explicit. Recognizing a relationship does not inject it into construction; selecting more expression contracts does not prove a better melody. Audition remains necessary.