head_music 8.3.0 → 11.0.0

data/user_stories/done/percussion_set.md

@@ -0,0 +1,260 @@
+# Percussion Set Staff
+
+As a composer or arranger
+
+I want to create percussion set or drum kit parts in a score
+
+So that I can notate multiple unpitched percussion instruments on a single staff
+
+## Background
+
+Individual percussion instruments (timpani, snare_drum, bass_drum, etc.) already exist in the codebase and use the `neutral_clef` (also known as percussion_clef). However, there's no way to represent a **percussion set** or **drum kit** where multiple unpitched instruments are notated on a single staff with each instrument assigned to a specific line or space.
+
+This is distinct from a clef. The `neutral_clef` already exists in `HeadMusic::Rudiment::Clef`. What's needed is:
+1. A new instrument definition for percussion sets (e.g., `drum_kit`, `percussion_set`)
+2. A staff scheme that uses the `neutral_clef`
+3. A percussion mapping system that defines which instruments appear on which staff lines/spaces
+
+## Scenario: Create a standard drum kit staff
+
+Given I am composing a piece with drum kit
+
+When I create a drum_kit instrument
+
+Then it should use the neutral_clef
+
+And it should have a default percussion mapping for standard drum kit instruments
+
+## Scenario: Map percussion instruments to staff positions
+
+Given I have a drum_kit instrument
+
+When I request the percussion mapping
+
+Then I should see which line or space each percussion instrument occupies
+
+Examples:
+- Crash cymbal → line 5
+- Hi-hat → line 4 (or space above)
+- Snare drum → line 3 (center line)
+- Bass drum → line 1 (or space below)
+- Floor tom → line 2
+
+## Scenario: Create custom percussion set configurations
+
+Given I want to notate a non-standard percussion ensemble
+
+When I define a custom percussion_set
+
+Then I should be able to specify which percussion instruments map to which staff positions
+
+And the system should use the neutral_clef for the staff
+
+## Technical Notes
+
+### Architecture
+
+A percussion set is:
+- **NOT a clef** - it uses the existing `neutral_clef`
+- **An instrument** with a special staff scheme configuration
+- **A mapping system** that assigns percussion instruments to staff positions
+
+### Proposed Implementation
+
+Add to `lib/head_music/instruments/instruments.yml`:
+
+```yaml
+drum_kit:
+  family_key: percussion_set
+  variants:
+    default:
+      staff_schemes:
+        default:
+          - clef: neutral_clef
+            percussion_mapping:
+              line_5: crash_cymbal
+              space_4: ride_cymbal
+              line_4: hi_hat
+              space_3: high_tom
+              line_3: snare_drum
+              space_2: mid_tom
+              line_2: floor_tom
+              space_1: bass_drum
+              line_1: bass_drum
+
+percussion_set:
+  family_key: percussion_set
+  variants:
+    default:
+      staff_schemes:
+        default:
+          - clef: neutral_clef
+```
+
+### New Concepts to Implement
+
+1. **Percussion mapping attribute** on `HeadMusic::Instruments::Staff`
+2. **Percussion family or category** to identify instruments as unpitched/percussion
+3. **Position resolution** to determine which line/space a percussion instrument should use
+
+### Related Components
+
+- `HeadMusic::Rudiment::Clef` - neutral_clef already exists (line 115-128 in clefs.yml)
+- `HeadMusic::Instruments::Staff` - would need to handle percussion_mapping attribute
+- `HeadMusic::Instruments::StaffScheme` - provides the staff configuration
+- Individual percussion instruments (timpani, snare_drum, etc.) already exist
+
+## Acceptance Criteria
+
+- Can create a drum_kit instrument
+- drum_kit uses neutral_clef by default
+- Can query which percussion instrument is assigned to each staff position
+- Can create custom percussion_set configurations with custom mappings
+- Maintains 90%+ test coverage
+- Follows existing HeadMusic patterns (factory methods, YAML data-driven)
+
+## Implementation Plan
+
+### Design Decisions
+
+Based on research and discussion:
+
+1. **Naming**: Use `instrument_mapping` (not `percussion_mapping`) for flexibility
+2. **Mapping Format**: Use instrument keys (strings/symbols), not objects
+3. **Validation**:
+   - Mapped instruments must exist
+   - No requirement that they be percussion instruments
+   - Valid positions: `line_0` through `line_6`, `space_0` through `space_5`
+4. **Flexibility**: Mappings are immutable (YAML-defined only) for now
+5. **Stem Direction**: Rendering concern, not part of infrastructure
+6. **Composite Instruments**: No special type needed - just regular instruments with `instrument_mapping`
+7. **Family**: Use `drum_kit` family (not generic `percussion_set`)
+
+### Standard Drum Kit Notation Mapping
+
+Research shows there is no single universal standard, but most common convention:
+
+```yaml
+instrument_mapping:
+  space_0: hi_hat_pedal        # below staff
+  line_1: bass_drum
+  line_2: floor_tom
+  line_3: snare_drum            # middle line - most consistent
+  line_4: mid_tom
+  space_4: high_tom
+  line_5: ride_cymbal
+  space_5: hi_hat               # above staff
+  line_6: crash_cymbal          # first ledger line above
+```
+
+### Implementation Steps
+
+#### 1. Add New Instrument Families
+To `lib/head_music/instruments/instrument_families.yml`:
+- `tom_tom` family
+- `hi_hat` family
+- `drum_kit` family
+
+#### 2. Add New Individual Instruments
+To `lib/head_music/instruments/instruments.yml`:
+- `hi_hat` (family: hi_hat)
+- `hi_hat_pedal` (family: hi_hat)
+- `crash_cymbal` (family: cymbal)
+- `ride_cymbal` (family: cymbal)
+- `high_tom` (family: tom_tom)
+- `mid_tom` (family: tom_tom)
+- `floor_tom` (family: tom_tom)
+
+Each with:
+- Appropriate aliases
+- `family_key` reference
+- Single `default` variant
+- `neutral_clef` staff scheme
+
+#### 3. Add Composite Instrument
+To `lib/head_music/instruments/instruments.yml`:
+- `drum_kit` (alias: `drum_set`) with standard instrument_mapping
+
+#### 4. Enhance Staff Class
+To `lib/head_music/instruments/staff.rb`:
+- Add `instrument_mapping` attribute (hash)
+- Add `#instrument_for_position(position_key)` method
+- Add `#position_for_instrument(instrument_name)` method
+- Add `#components` method (derives instruments from mapping)
+- Handle parsing `instrument_mapping` from YAML
+- Validate:
+  - Position keys match pattern (line_0-6, space_0-5)
+  - Referenced instruments exist
+
+#### 5. Tests
+- Specs for all new instrument families
+- Specs for all new individual instruments
+- Specs for `Staff#instrument_mapping` functionality
+- Specs for `drum_kit` composite instrument
+- Maintain 90%+ code coverage
+
+---
+
+## Refactoring Notes (Post-Implementation)
+
+After the initial implementation, the design was refactored to better model playing techniques as a first-class concept rather than treating them as separate instruments.
+
+### Key Changes:
+
+1. **Introduced `PlayingTechnique` class**
+   - Playing techniques (pedal, stick, mallet, etc.) are now modeled as objects
+   - Includes `HeadMusic::Named` for potential future i18n support
+   - Common techniques defined: stick, pedal, mallet, hand, brush, rim_shot, cross_stick, open, closed, etc.
+
+2. **Created `StaffMapping` class** (replaces simple hash-based approach)
+   - Represents the mapping of an instrument + optional playing technique to a staff position
+   - Uses `StaffPosition` with index-based positions (even = lines, odd = spaces)
+   - Attributes: `staff_position`, `instrument_key`, `playing_technique_key`
+   - Methods: `#instrument`, `#playing_technique`, `#position_index`, `#to_s`
+
+3. **Removed `hi_hat_pedal` as separate instrument**
+   - Hi-hat pedal is now correctly modeled as a playing technique of the hi-hat instrument
+   - The hi-hat appears at two positions in drum_kit mapping:
+     - Position -1 (space below staff): hi_hat with pedal technique
+     - Position 9 (space above staff): hi_hat with stick technique
+
+4. **Updated `Staff` class API**
+   - `#mappings` → returns array of `StaffMapping` objects
+   - `#mapping_for_position(index)` → get full mapping at position
+   - `#instrument_for_position(index)` → get instrument at position
+   - `#positions_for_instrument(key)` → returns all positions (handles multiple mappings)
+   - `#components` → returns unique instruments
+
+5. **Changed YAML format** from hash to array:
+   ```yaml
+   # Old format:
+   instrument_mapping:
+     line_3: snare_drum
+     space_5: hi_hat
+
+   # New format:
+   mappings:
+     - staff_position: 4        # index 4 = line 3
+       instrument: snare_drum
+     - staff_position: 9        # index 9 = space above staff
+       instrument: hi_hat
+       playing_technique: stick
+   ```
+
+6. **Added comprehensive YARD documentation**
+   - All new classes and public methods documented
+   - Examples provided for common use cases
+
+### Benefits of Refactoring:
+
+- **Semantic clarity**: Hi-hat pedal is a technique, not an instrument
+- **Extensibility**: Easy to add new playing techniques (bow techniques for strings, breath techniques for winds, etc.)
+- **Flexibility**: Instruments can appear at multiple positions with different techniques
+- **Type safety**: StaffPosition validates position indices, StaffMapping provides structured access
+
+### Test Results:
+
+- **1040 examples, 0 failures** ✅
+- **91.54% line coverage, 84.44% branch coverage** ✅
+- All existing functionality preserved
+- New tests verify multiple technique mappings

data/user_stories/done/sonority-identification.md

@@ -0,0 +1,37 @@
+# Sonority Identification
+
+As a music theorist or composer
+
+I want to identify and work with named sonorities
+
+So that I can analyze and create harmonic structures
+
+## Scenario: Get sonority by identifier
+
+Given I need a specific sonority
+
+When I call Sonority.get with an identifier like "major_triad"
+
+Then I should receive the corresponding sonority object
+
+And it should contain the correct interval structure
+
+## Scenario: Generate pitch collection from sonority
+
+Given I have a sonority identifier and a root pitch
+
+When I call a method to generate pitches
+
+Then I should receive the correct pitches for that sonority
+
+And they should be in the specified inversion
+
+## Scenario: Access sonority from pitch collection
+
+Given I have a PitchCollection object
+
+When I call the sonority method
+
+Then I should receive the corresponding Sonority object
+
+And it should correctly identify the harmonic content

data/user_stories/done/superclass-for-note.md

@@ -0,0 +1,30 @@
+IN ORDER TO accurately model sound events
+AS a developer
+I WANT a clear way to group the notion of a Note (pitch + rhythmic value) and an unpitched note.
+
+We need a hierarchy of classes
+
+class RhythmicEvent
+  attr_accessor :rhythmic_value
+
+class Note < RhythmicEvent
+  attr_accessor :pitch
+  def sounded?
+    true
+  end
+
+class UnpitchedNote < RhythmicEvent
+  def sounded?
+    true
+  end
+
+class Rest < RhythmicEvent
+  def sounded?
+    false
+  end
+
+
+acceptance criteria
+- the above class hierarchy and implementation requirements
+- full test coverage
+- use NotImplementedError instead of NotImplementedError in RhythmicEvent if and where appropriate.

data/user_stories/epics/notation-module.md

@@ -0,0 +1,135 @@
+# EPIC: Notation Module
+
+AS a developer
+
+I WANT to organize notation-related features in a dedicated HeadMusic::Notation module
+
+SO THAT I can clearly separate visual representation concerns from music theory, instrument properties, and musical content
+
+## Vision
+
+Music notation is about visual representation - how musical concepts appear on paper, screen, or other media. This is conceptually distinct from:
+- **Music theory** (abstract concepts like pitch, interval, harmony)
+- **Instrument properties** (range, transposition, acoustic characteristics)
+- **Musical content** (compositions, temporal organization)
+
+A dedicated Notation module provides a clear home for all visual representation concerns, making the codebase more organized and enabling future expansion into comprehensive music engraving capabilities.
+
+## Background
+
+Currently, notation-related code is scattered across multiple modules:
+- **HeadMusic::Instruments** contains `StaffPosition`, `Staff`, `StaffMapping`, and `StaffScheme`
+- **HeadMusic::Rudiment** contains `Clef`, `MusicalSymbol`, and notation aspects of `Alteration` and `RhythmicUnit`
+- **HeadMusic::Content** has its own minimal `Staff` class
+
+A TODO comment in `lib/head_music/instruments/staff_position.rb:5` suggests: "consider moving to a HeadMusic::Notation module"
+
+This scattered organization makes it unclear where new notation features should live and conflates distinct concerns.
+
+## Module Boundaries
+
+### HeadMusic::Notation (visual representation)
+- Staff positions, lines, spaces, ledger lines
+- Musical symbols (ASCII, Unicode, HTML entities)
+- Notehead shapes and placement on staff
+- Stem direction and flags
+- Clef symbols and their staff placement
+- Accidental symbol placement
+- Future: beaming, ties, slurs, articulations, dynamics
+
+### HeadMusic::Rudiment (music theory)
+- Abstract concepts: pitch, interval, scale, chord
+- Duration concepts (without visual representation)
+- Keys, meters (as musical concepts, not visual symbols)
+- Core theory that notation represents visually
+
+### HeadMusic::Instruments (instrument properties)
+- Instrument families and classification
+- Pitch ranges and transposition
+- Playing techniques
+- Score ordering
+- References to default clef (but doesn't own clef rendering)
+
+### HeadMusic::Content (musical content)
+- Compositions, voices, bars
+- Notes in context (pitch + duration + placement)
+- Temporal organization
+- Uses Notation for visual representation
+
+## Scope
+
+### Phase 1: Foundation & Core Moves (Current Focus)
+- Establish module infrastructure
+- Move `StaffPosition` from Instruments to Notation
+- Move `MusicalSymbol` from Rudiment to Notation
+- Move `StaffMapping` from Instruments to Notation
+
+**User Stories:**
+- [Notation Module Foundation](../backlog/notation-module-foundation.md)
+- [Move StaffPosition to Notation](../backlog/move-staff-position-to-notation.md)
+- [Move MusicalSymbol to Notation](../backlog/move-musical-symbol-to-notation.md)
+- [Move StaffMapping to Notation](../backlog/move-staff-mapping-to-notation.md)
+
+### Phase 2: Extract Notation Aspects (Future)
+- Create `ClefPlacement` - extract visual clef positioning from `Rudiment::Clef`
+- Create `AccidentalPlacement` - extract accidental display rules from `Rudiment::Alteration`
+- Create `RhythmicNotation` - extract notehead, stem, flag logic from `Rudiment::RhythmicUnit`
+- Refactor `StaffScheme` to `Notation::StaffSystem`
+
+### Phase 3: Advanced Notation Features (Long-term Vision)
+- Beaming (connecting note stems across beats)
+- Stems (direction and length calculation)
+- Ties (connecting same pitches across bars)
+- Slurs (phrase markings)
+- Articulations (staccato, accent, tenuto, etc.)
+- Dynamics (forte, piano, crescendo, etc.)
+- Tuplets (triplets, quintuplets, etc.)
+- Barlines (single, double, repeat)
+- Ornaments (trills, mordents, turns)
+- Fermatas (pause markings)
+
+### Beyond Western Staff Notation (Future Exploration)
+
+The Notation module could eventually support multiple notation systems:
+
+**Traditional notation systems:**
+- Western staff notation (current focus)
+- Tablature (tab) - finger positions for guitar, bass, lute
+- Shaped note notation - different note head shapes for scale degrees
+- Drum notation - modified staff notation for percussion
+
+**Alphanumeric and shorthand systems:**
+- Lead sheet notation - melody with chord symbols
+- Nashville Number System - scale degrees instead of chord names
+- Roman numeral analysis - functional harmony labels
+- ABC notation - text-based system for folk music
+- Figured bass - Baroque-era interval shorthand
+
+**Digital/computer formats:**
+- MIDI - note events with pitch, velocity, timing
+- MusicXML - XML-based interchange format
+- Lilypond - text-based music engraving
+- MEI (Music Encoding Initiative) - scholarly encoding
+
+## Success Criteria
+
+**Module Organization:**
+- Clear separation between theory (Rudiment), notation (Notation), instruments (Instruments), and content (Content)
+- All visual representation concerns organized under `HeadMusic::Notation`
+- Documentation clearly explains what belongs in each module
+
+**Code Quality:**
+- All moved classes maintain existing functionality
+- 90%+ test coverage maintained throughout
+- No breaking changes for internal usage
+- All TODO comments resolved
+
+**Extensibility:**
+- Module designed for future expansion (beams, ties, dynamics, etc.)
+- Support for multiple output formats (Unicode, MusicXML, SVG)
+- Clear patterns established for adding new notation features
+
+**Developer Experience:**
+- Clear guidance in CLAUDE.md about where notation features belong
+- Easy to find and use notation-related classes
+- Logical organization that matches mental model of music notation

data/user_stories/visioning/agentic-daw.md

@@ -0,0 +1,2 @@
+agent-centric multimedia scoring
+(A/V DAW)

metadata

@@ -1,29 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: head_music
 version: !ruby/object:Gem::Version
-  version: 8.3.0
+  version: 11.0.0
 platform: ruby
 authors:
 - Rob Head
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-07-26 00:00:00.000000000 Z
+date: 2026-01-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: '7.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '10'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: '7.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '10'
 - !ruby/object:Gem::Dependency
   name: humanize
   requirement: !ruby/object:Gem::Requirement
@@ -150,13 +156,12 @@ files:
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
+- MUSIC_THEORY.md
 - README.md
 - Rakefile
-- TODO.md
 - bin/check_instrument_consistency.rb
 - bin/console
 - bin/setup
-- check_instrument_consistency.rb
 - head_music.gemspec
 - lib/head_music.rb
 - lib/head_music/analysis/circle.rb
@@ -166,27 +171,40 @@ files:
 - lib/head_music/analysis/diatonic_interval/parser.rb
 - lib/head_music/analysis/diatonic_interval/semitones.rb
 - lib/head_music/analysis/diatonic_interval/size.rb
+- lib/head_music/analysis/dyad.rb
 - lib/head_music/analysis/harmonic_interval.rb
+- lib/head_music/analysis/interval_consonance.rb
 - lib/head_music/analysis/interval_cycle.rb
 - lib/head_music/analysis/melodic_interval.rb
 - lib/head_music/analysis/motion.rb
 - lib/head_music/analysis/pitch_class_set.rb
-- lib/head_music/analysis/pitch_set.rb
+- lib/head_music/analysis/pitch_collection.rb
 - lib/head_music/analysis/sonority.rb
 - lib/head_music/content/bar.rb
 - lib/head_music/content/composition.rb
 - lib/head_music/content/note.rb
 - lib/head_music/content/placement.rb
 - lib/head_music/content/position.rb
-- lib/head_music/content/rhythmic_value.rb
 - lib/head_music/content/staff.rb
 - lib/head_music/content/voice.rb
+- lib/head_music/instruments/alternate_tuning.rb
+- lib/head_music/instruments/alternate_tunings.yml
 - lib/head_music/instruments/instrument.rb
+- lib/head_music/instruments/instrument_configuration.rb
+- lib/head_music/instruments/instrument_configuration_option.rb
+- lib/head_music/instruments/instrument_configurations.yml
 - lib/head_music/instruments/instrument_families.yml
 - lib/head_music/instruments/instrument_family.rb
 - lib/head_music/instruments/instruments.yml
+- lib/head_music/instruments/playing_technique.rb
+- lib/head_music/instruments/playing_techniques.yml
+- lib/head_music/instruments/score_order.rb
+- lib/head_music/instruments/score_orders.yml
 - lib/head_music/instruments/staff.rb
 - lib/head_music/instruments/staff_scheme.rb
+- lib/head_music/instruments/stringing.rb
+- lib/head_music/instruments/stringing_course.rb
+- lib/head_music/instruments/stringings.yml
 - lib/head_music/instruments/variant.rb
 - lib/head_music/locales/de.yml
 - lib/head_music/locales/en.yml
@@ -196,35 +214,54 @@ files:
 - lib/head_music/locales/it.yml
 - lib/head_music/locales/ru.yml
 - lib/head_music/named.rb
+- lib/head_music/notation.rb
+- lib/head_music/notation/musical_symbol.rb
+- lib/head_music/notation/staff_mapping.rb
+- lib/head_music/notation/staff_position.rb
 - lib/head_music/rudiment/alteration.rb
+- lib/head_music/rudiment/alterations.yml
+- lib/head_music/rudiment/base.rb
 - lib/head_music/rudiment/chromatic_interval.rb
 - lib/head_music/rudiment/clef.rb
 - lib/head_music/rudiment/clefs.yml
 - lib/head_music/rudiment/consonance.rb
+- lib/head_music/rudiment/diatonic_context.rb
+- lib/head_music/rudiment/key.rb
 - lib/head_music/rudiment/key_signature.rb
 - lib/head_music/rudiment/key_signature/enharmonic_equivalence.rb
 - lib/head_music/rudiment/letter_name.rb
 - lib/head_music/rudiment/meter.rb
-- lib/head_music/rudiment/musical_symbol.rb
+- lib/head_music/rudiment/mode.rb
+- lib/head_music/rudiment/note.rb
 - lib/head_music/rudiment/pitch.rb
 - lib/head_music/rudiment/pitch/enharmonic_equivalence.rb
 - lib/head_music/rudiment/pitch/octave_equivalence.rb
+- lib/head_music/rudiment/pitch/parser.rb
 - lib/head_music/rudiment/pitch_class.rb
 - lib/head_music/rudiment/quality.rb
 - lib/head_music/rudiment/reference_pitch.rb
 - lib/head_music/rudiment/register.rb
+- lib/head_music/rudiment/rest.rb
 - lib/head_music/rudiment/rhythm.rb
+- lib/head_music/rudiment/rhythmic_element.rb
 - lib/head_music/rudiment/rhythmic_unit.rb
+- lib/head_music/rudiment/rhythmic_unit/parser.rb
+- lib/head_music/rudiment/rhythmic_units.yml
+- lib/head_music/rudiment/rhythmic_value.rb
+- lib/head_music/rudiment/rhythmic_value/parser.rb
 - lib/head_music/rudiment/scale.rb
 - lib/head_music/rudiment/scale_degree.rb
 - lib/head_music/rudiment/scale_type.rb
 - lib/head_music/rudiment/solmization.rb
 - lib/head_music/rudiment/solmizations.yml
 - lib/head_music/rudiment/spelling.rb
+- lib/head_music/rudiment/tempo.rb
+- lib/head_music/rudiment/tonal_context.rb
 - lib/head_music/rudiment/tuning.rb
 - lib/head_music/rudiment/tuning/just_intonation.rb
 - lib/head_music/rudiment/tuning/meantone.rb
 - lib/head_music/rudiment/tuning/pythagorean.rb
+- lib/head_music/rudiment/unpitched_note.rb
 - lib/head_music/style/analysis.rb
 - lib/head_music/style/annotation.rb
 - lib/head_music/style/guidelines/always_move.rb
@@ -265,17 +302,46 @@ files:
 - lib/head_music/style/guides/fux_cantus_firmus.rb
 - lib/head_music/style/guides/modern_cantus_firmus.rb
 - lib/head_music/style/mark.rb
+- lib/head_music/style/medieval_tradition.rb
+- lib/head_music/style/modern_tradition.rb
+- lib/head_music/style/renaissance_tradition.rb
+- lib/head_music/style/tradition.rb
+- lib/head_music/time.rb
+- lib/head_music/time/clock_position.rb
+- lib/head_music/time/conductor.rb
+- lib/head_music/time/meter_event.rb
+- lib/head_music/time/meter_map.rb
+- lib/head_music/time/musical_position.rb
+- lib/head_music/time/smpte_timecode.rb
+- lib/head_music/time/tempo_event.rb
+- lib/head_music/time/tempo_map.rb
+- lib/head_music/utilities/case.rb
 - lib/head_music/utilities/hash_key.rb
 - lib/head_music/version.rb
-- test_translations.rb
-- user_stories/backlog/band-score-order.md
-- user_stories/backlog/chamber-ensemble-score-order.md
-- user_stories/backlog/consonance-dissonance-classification.md
-- user_stories/backlog/dyad-analysis.md
-- user_stories/backlog/orchestral-score-order.md
-- user_stories/backlog/pitch-class-set-analysis.md
-- user_stories/backlog/pitch-set-classification.md
-- user_stories/backlog/sonority-identification.md
+- user_stories/active/string-pitches.md
+- user_stories/backlog/notation-style.md
+- user_stories/backlog/organizing-content.md
+- user_stories/done/consonance-dissonance-classification.md
+- user_stories/done/dyad-analysis.md
+- user_stories/done/epic--score-order/PLAN.md
+- user_stories/done/epic--score-order/band-score-order.md
+- user_stories/done/epic--score-order/chamber-ensemble-score-order.md
+- user_stories/done/epic--score-order/orchestral-score-order.md
+- user_stories/done/expand-playing-techniques.md
+- user_stories/done/handle-time.md
+- user_stories/done/handle-time.rb
+- user_stories/done/instrument-architecture.md
+- user_stories/done/instrument-variant.md
+- user_stories/done/move-musical-symbol-to-notation.md
+- user_stories/done/move-staff-mapping-to-notation.md
+- user_stories/done/move-staff-position-to-notation.md
+- user_stories/done/notation-module-foundation.md
+- user_stories/done/percussion_set.md
+- user_stories/done/pitch-class-set-analysis.md
+- user_stories/done/sonority-identification.md
+- user_stories/done/superclass-for-note.md
+- user_stories/epics/notation-module.md
+- user_stories/visioning/agentic-daw.md
 homepage: https://github.com/roberthead/head_music
 licenses:
 - MIT