livepilot 1.10.7 → 1.10.8

package/livepilot/commands/evaluate.md

@@ -1,49 +0,0 @@
----
-name: evaluate
-description: Evaluate recent changes — run the full before/after evaluation loop and recommend keep or undo
----
-
-Run the universal evaluation loop on recent production changes.
-
-1. **Check capability state** — `get_capability_state` to see what evaluation modes are available:
-   - `normal` — full measured evaluation with analyzer data
-   - `measured_degraded` — analyzer online but stale data
-   - `judgment_only` — no analyzer, parameter-level heuristics only
-   - `read_only` — session disconnected
-
-2. **Ensure analyzer** — if mode is `judgment_only`, try to get full perception:
-   - `find_and_load_device(track_index=-1000, device_name="LivePilot_Analyzer")`
-   - Wait 2s, then `get_master_spectrum` to test the bridge
-   - If bridge disconnected: `reconnect_bridge`
-   - If still unavailable: proceed with `judgment_only` but tell the user
-
-3. **Get the last move** — `get_last_move` to understand what was changed. If no recent move, `get_recent_actions` for history.
-
-4. **Ask what the goal was** — what were they trying to achieve? More clarity? Wider stereo? Punchier drums?
-
-5. **Compile the goal** — `compile_goal_vector(goal_description, mode="improve")`
-
-6. **Capture current state** — full perception snapshot:
-   - `get_master_spectrum` + `get_master_rms` (if analyzer available)
-   - `get_track_meters(include_stereo=true)` — verify all tracks producing audio
-   - `get_mix_snapshot` — full volume/pan/send state
-   - Optionally: `capture_audio` + `analyze_loudness` + `analyze_spectrum_offline` for ground truth
-
-7. **Undo the change** — `undo()` to restore the before state
-
-8. **Capture before state** — same reads as step 6
-
-9. **Redo the change** — `redo()` to restore the after state
-
-10. **Evaluate** — `evaluate_move(before_snapshot, after_snapshot, goal)` or use engine-specific:
-    - Mix changes: `evaluate_mix_move`
-    - Composition changes: `evaluate_composition_move`
-    - Multi-dimensional: `evaluate_with_fabric`
-
-11. **Report results** — show: score (0-1), keep_change recommendation, goal_progress, collateral_damage, dimension changes
-
-12. **Act on recommendation:**
-    - If `keep_change=true` — keep, suggest `memory_learn` if score > 0.7
-    - If `keep_change=false` — `undo()`, explain why (collateral damage, goal regression)
-
-Use the livepilot-evaluation skill for the full evaluation loop details.

package/livepilot/commands/memory.md

@@ -1,22 +0,0 @@
----
-name: memory
-description: Browse, search, and manage your saved technique library
----
-
-Show the user's technique memory library. Follow these steps:
-
-1. Call `memory_list(limit=20)` to get an overview of saved techniques
-2. Format as an organized list grouped by type:
-   - **Beats** — beat_pattern techniques
-   - **Device Chains** — device_chain techniques
-   - **Mix Templates** — mix_template techniques
-   - **Browser Pins** — browser_pin techniques
-   - **Preferences** — preference techniques
-3. For each technique show: name, summary, rating (stars), favorite marker, tags
-4. Show total count and breakdown by type
-
-After presenting, ask if the user wants to:
-- **Search** — "search for [query]" → use memory_recall
-- **View details** — "show me [name]" → use memory_get
-- **Delete** — "delete [name]" → use memory_delete (confirm first)
-- **Rate** — "rate [name] 5 stars" → use memory_favorite

package/livepilot/commands/mix.md

@@ -1,44 +0,0 @@
----
-name: mix
-description: Mixing assistant — analyze and balance track levels, panning, and sends
----
-
-Help the user mix their session using the V2 orchestration pipeline.
-
-## Orchestration Flow
-
-1. **Session kernel** — `get_session_kernel(request_text=<user's request>, mode="improve")` for the full turn snapshot
-2. **Route** — `route_request(<user's request>)` to get engine routes + semantic move recommendations
-3. **Ensure analyzer** — if `get_master_spectrum` errors, load it: `find_and_load_device(track_index=-1000, device_name="LivePilot_Analyzer")`. If bridge disconnected, try `reconnect_bridge`.
-
-## Analysis Phase
-
-4. **Quick status** — `get_mix_summary` for track count, dynamics, stereo, issues
-5. **Run critics** — `get_mix_issues` for problems. `get_masking_report` for frequency collisions.
-6. **Spectral check** — `get_master_spectrum` for 8-band balance. Genre targets:
-   - Hip-hop: sub dominant, centroid 400-800 Hz
-   - Electronic: balanced, centroid 800-1500 Hz
-   - Ambient: mid-focused, low sub, centroid 500-1000 Hz
-7. **Musical intelligence** — `detect_role_conflicts` to find tracks competing for the same space. `detect_repetition_fatigue` if arrangement feels stale.
-
-## Decision Phase
-
-8. **Propose semantic moves** — `propose_next_best_move(request_text=<user's request>)` for ranked suggestions (e.g., `make_punchier`, `widen_stereo`, `tighten_low_end`)
-9. **Preview chosen move** — `preview_semantic_move(move_id)` to see the full compile plan before executing
-10. **Rank by taste** — if user has history, `rank_moves_by_taste(move_specs)` to personalize ordering
-
-## Execution Phase
-
-11. **Apply with approval** — `apply_semantic_move(move_id, mode="improve")` returns the compiled plan. Present it to the user: "I'd suggest: push Drums to 0.75, pull Pad to 0.25. Shall I do it?"
-12. **Verify after EVERY change** — read `value_string` in response, call `get_track_meters(include_stereo=true)`, check no track went silent
-13. **Capture + analyze** — `capture_audio` then `analyze_loudness` for LUFS/LRA, `analyze_spectrum_offline` for centroid/balance
-14. **Evaluate** — `evaluate_mix_move` with before/after snapshots. If `keep_change` is false, `undo` immediately.
-
-## Summary
-
-15. **Report** — "What I did / what improved / what I protected / what remains"
-16. **Session memory** — `add_session_memory` for notable decisions
-17. **Taste update** — successful moves update the TasteGraph automatically
-
-For deeper critic-driven iterative improvement, use the livepilot-mix-engine skill.
-For exploratory mode (try multiple ideas), use `create_experiment` + `run_experiment` + `compare_experiments`.

package/livepilot/commands/perform.md

@@ -1,42 +0,0 @@
----
-name: perform
-description: Performance mode — enter a safety-constrained live performance context with energy tracking and safe moves
----
-
-Enter performance mode with safety constraints and energy tracking.
-
-## Orchestration Flow
-
-1. **Session kernel** — `get_session_kernel(request_text="live performance", mode="improve")`
-2. **Route** — `route_request("live performance")` → workflow_mode should be `performance_safe`
-3. **Performance state** — `get_performance_state` for current scene, energy level, and safe moves
-
-## Safety-First Rules
-
-- **NEVER** execute moves rated "high risk" during performance
-- **ALWAYS** use `get_performance_safe_moves` before ANY change
-- Only fire scenes, adjust volumes, and trigger safe effects
-- No device loading, track creation, or destructive operations
-
-## Performance Tools
-
-4. **Safe moves** — `get_performance_safe_moves` for available actions
-5. **Scene handoff** — `plan_scene_handoff` for safe transitions between scenes
-6. **Energy tracking** — monitor energy level across scene transitions
-7. **Semantic moves** — only performance-safe semantic moves:
-   - `smooth_scene_handoff` — safe transition between scenes
-   - Gesture templates: `pre_arrival_vacuum`, `re_entry_spotlight`
-
-## Live Dashboard
-
-8. **Monitor** — `get_track_meters(include_stereo=true)` for real-time levels
-9. **Spectrum** — `get_master_spectrum` for frequency balance during performance
-10. **Playing clips** — `get_playing_clips` to see what's active
-
-## Recovery
-
-11. **If something goes wrong** — `undo` immediately
-12. **Emergency** — `stop_all_clips` if audio goes haywire
-13. **Check safety** — `check_safety` to verify constraints are holding
-
-Keep the user informed of what's happening. Never make surprise changes during a live set.

package/livepilot/commands/session.md

@@ -1,13 +0,0 @@
----
-name: session
-description: Get a full overview of the current Ableton Live session
----
-
-Get a comprehensive overview of the current Ableton Live session by calling `get_session_info`. Format the results as an organized report showing:
-
-1. **Transport** — tempo, time signature, playing state, loop settings
-2. **Tracks** — list all tracks with type, name, color, arm/mute/solo state
-3. **Scenes** — scene names and clip occupancy
-4. **Master** — master volume and devices
-
-After presenting the overview, ask if the user wants to dive deeper into any specific track, device, or area.

package/livepilot/commands/sounddesign.md

@@ -1,43 +0,0 @@
----
-name: sounddesign
-description: Sound design workflow — load instruments and effects, shape parameters for a target sound
----
-
-Guide the user through designing a sound using the V2 orchestration pipeline.
-
-## Orchestration Flow
-
-1. **Session kernel** — `get_session_kernel(request_text=<user's request>, mode="improve")`
-2. **Route** — `route_request(<user's request>)` for engine routes + semantic moves
-
-## Design Phase
-
-3. **Ask about target** — what character? (warm pad, aggressive bass, shimmering lead, etc.)
-4. **Choose instrument** — `search_browser` to find devices, `load_browser_item` to load
-5. **Verify health** — `get_device_info` to confirm plugin initialized. Read `value_string` from `get_device_parameters` to understand actual units.
-6. **Shape sound** — `set_device_parameter` or `batch_set_parameters`. **ALWAYS read `value_string` in response** to confirm Hz/dB/% values make sense.
-7. **Verify after every change** — `get_track_meters(include_stereo=true)` — if stereo drops to 0, the effect killed the signal.
-
-## Critic Phase
-
-8. **Run critics** — `analyze_sound_design(track_index)` for static timbre, missing modulation, spectral imbalance
-9. **Plan improvements** — `plan_sound_design_move(track_index)` for suggested changes
-10. **Patch model** — `get_patch_model(track_index)` to see chain structure and controllable blocks
-
-## Effects & Automation
-
-11. **Add effects** — load with `find_and_load_device(track_index, device_name)`. Verify health.
-12. **Organic movement** — `apply_automation_shape(curve_type="perlin")` for filter/send drift
-13. **Automation recipes** — `apply_automation_recipe` for breathing, vinyl_crackle, auto_pan. Verify after applying.
-
-## Evaluation
-
-14. **Perception check** — `get_master_spectrum` or `capture_audio` + `analyze_spectrum_offline`
-15. **Evaluate** — `evaluate_move(goal_vector, before_snapshot, after_snapshot)` to score improvement
-
-## Summary
-
-16. **Report** — "What I changed / what improved / what I protected"
-17. **Memory** — if score > 0.7, suggest `memory_learn` to save the technique
-
-For critic-driven iterative refinement, use the livepilot-sound-design-engine skill.

package/livepilot/skills/livepilot-arrangement/SKILL.md

@@ -1,155 +0,0 @@
----
-name: livepilot-arrangement
-description: This skill should be used when the user asks to "arrange", "structure a song", "add an intro", "build a verse", "create sections", "scene to arrangement", "cue points", "record to arrangement", or wants to organize song structure in Ableton Live.
----
-
-# Arrangement — Song Structure and Session Organization
-
-Organize clips into scenes, build arrangements on the timeline, navigate with cue points, and record performances in Ableton Live.
-
-## Session View vs Arrangement View
-
-Ableton has two complementary views:
-
-- **Session view** — a grid of clip slots organized by track (columns) and scene (rows). Clips loop independently. Fire scenes to trigger rows of clips simultaneously. Use for jamming, live performance, and building ideas.
-- **Arrangement view** — a linear timeline where clips play in sequence from left to right. Use for final song structure, recording automation, and export.
-
-Use `back_to_arranger` to switch from session playback to arrangement playback. When session clips are playing, they override arrangement content on their tracks.
-
-## Scene Workflow
-
-Scenes are horizontal rows in session view. Each scene can trigger all its clips at once.
-
-### Creating and Managing Scenes
-
-- `create_scene(index)` — insert a new scene at the given position
-- `set_scene_name(scene_index, name)` — name scenes after song sections: "Intro", "Verse 1", "Chorus", "Bridge", "Drop", "Outro"
-- `set_scene_color(scene_index, color_index)` — color-code sections (0-69 palette). Use consistent colors: green for verses, red for choruses, blue for bridges.
-- `set_scene_tempo(scene_index, tempo)` — set a per-scene tempo change (triggers when scene fires)
-- `duplicate_scene(scene_index)` — copy a scene for variations. Duplicate, rename, then modify clips in the copy.
-- `delete_scene(scene_index)` — remove a scene
-
-### Firing and Monitoring
-
-- `fire_scene(scene_index)` — launch all clips in a scene simultaneously
-- `fire_scene_clips(scene_index)` — launch only the clips that exist in a scene (skips empty slots)
-- `stop_all_clips` — stop everything in session view
-- `get_playing_clips` — see which clips are currently playing across all tracks
-
-### Scene Inspection
-
-- `get_scenes_info` — list all scenes with names, tempos, and colors
-- `get_scene_matrix` — see which clips exist in which slots across the entire session grid. Returns a track-by-scene matrix showing clip presence, names, and states.
-
-## Arrangement View
-
-Build linear song structures on the timeline.
-
-### Creating Arrangement Clips
-
-- `create_arrangement_clip(track_index, clip_slot_index, start_time, length)` — duplicate a session clip into Arrangement View at a specific beat position
-- `create_native_arrangement_clip(track_index, start_time, length)` — create arrangement clip with full automation envelope (12.1.10+)
-- `set_arrangement_clip_name(track_index, clip_index, name)` — name arrangement clips for clarity
-- `force_arrangement()` — force all tracks to play from arrangement (not session clips)
-
-### Arrangement Notes
-
-- `add_arrangement_notes(track_index, clip_index, notes)` — write MIDI notes into an arrangement clip
-- `get_arrangement_notes(track_index, clip_index)` — read notes from an arrangement clip
-- `remove_arrangement_notes(track_index, clip_index, start_time, duration, pitch_start, pitch_end)` — clear notes in a region
-- `remove_arrangement_notes_by_id(track_index, clip_index, note_ids)` — surgical deletion
-- `modify_arrangement_notes(track_index, clip_index, modifications)` — update existing notes by ID
-- `duplicate_arrangement_notes(track_index, clip_index, time_offset)` — copy notes forward
-- `transpose_arrangement_notes(track_index, clip_index, semitones, start_time, duration)` — pitch shift a region
-
-### Arrangement Clips Inspection
-
-- `get_arrangement_clips(track_index)` — list all clips on a track's arrangement timeline with positions, lengths, and names
-
-### Arrangement Automation
-
-- `set_arrangement_automation(track_index, parameter_name, points)` — write automation on the arrangement timeline. Points are `[{time, value}, ...]` pairs at absolute beat positions.
-
-## Navigation
-
-### Transport Position
-
-- `jump_to_time(beat_time)` — move the playback cursor to a specific beat position on the timeline
-- `start_playback` / `stop_playback` / `continue_playback` — basic transport control
-
-### Cue Points
-
-Cue points are markers on the arrangement timeline for quick navigation.
-
-- `toggle_cue_point` — add or remove a cue point at the current playback position
-- `get_cue_points` — list all cue points with their beat positions and names
-- `jump_to_cue(cue_index)` — jump to a specific cue point by index
-
-Use cue points to mark section boundaries: place one at beat 0 (Intro), beat 16 (Verse), beat 48 (Chorus), etc. This makes navigation fast during arrangement.
-
-## Recording
-
-### Live Recording
-
-- `start_recording` — begin recording into the arrangement or session (depends on which view is active and which tracks are armed)
-- `stop_recording` — stop recording
-- `capture_midi` — retroactive MIDI capture. Grabs whatever was played on armed MIDI tracks even if recording was not active. Live 12 keeps a buffer of recent MIDI input.
-
-### Recording Workflow
-
-1. Arm tracks with `set_track_arm(track_index, arm=true)`
-2. Optionally set input monitoring with `set_track_input_monitoring(track_index, mode)`
-3. `start_recording` — records into arrangement if in arrangement view, into session slots if in session view
-4. Play or trigger clips
-5. `stop_recording` — finalize the take
-
-For retroactive capture: if the user just played something without recording, call `capture_midi` immediately to grab it.
-
-## Section Analysis
-
-- `get_section_graph` — infer song structure from scene names and clip arrangement. Returns a graph of sections with their relationships, durations, and transitions.
-- `analyze_composition` — deeper structural analysis including phrase lengths, repetition patterns, and harmonic arcs
-- `get_phrase_grid` — see how phrases align across tracks
-
-Use `get_section_graph` to understand the current form before adding new sections. It helps identify what is missing (e.g., no bridge, no outro, chorus only appears once).
-
-## Common Song Structures
-
-When building arrangements, use these as starting templates:
-
-- **Pop:** Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus - Outro
-- **EDM/Dance:** Intro (16 bars) - Build - Drop (16) - Break (8) - Build - Drop (16) - Outro (8)
-- **Hip-hop:** Intro - Verse (16 bars) - Hook (8) - Verse (16) - Hook (8) - Bridge - Hook - Outro
-- **Lo-fi:** Intro (4) - A (8) - B (8) - A (8) - B variation (8) - Outro (4)
-
-Adapt these to the user's needs. Use `plan_arrangement` from the planner domain for algorithmic structure suggestions, and `transform_section` to create variations of existing sections.
-
-## Section-Aware Sample Roles
-
-`plan_arrangement` returns `sample_hints` per section — suggested roles for sample-based elements:
-
-| Section | Default Hints |
-|---------|--------------|
-| Intro | `texture_bed`, `fill_one_shot` |
-| Verse | `texture_bed`, `fill_one_shot` |
-| Build | `transition_fx`, `texture_bed` |
-| Chorus/Drop | `hook_sample`, `break_layer`, `fill_one_shot` |
-| Bridge/Breakdown | `texture_bed`, `transition_fx` |
-| Outro | `texture_bed`, `fill_one_shot` |
-
-Use `plan_sample_workflow(section_type=..., desired_role=...)` to generate concrete sample plans for each role. Use `plan_slice_workflow(intent=..., target_section=...)` for slice-based patterns.
-
-## Composition Engine
-
-For deeper compositional analysis beyond basic arrangement:
-
-- `plan_gesture(type, parameters)` — plan a musical gesture (build, release, tension, resolution)
-- `apply_gesture_template(track_index, gesture)` — apply a gesture pattern to a track
-- `evaluate_composition_move(proposed_change)` — score a proposed structural change before making it
-- `get_harmony_field(section)` — see the harmonic landscape of a section
-- `get_transition_analysis(from_section, to_section)` — analyze how two sections connect
-
-## Reference
-
-Supporting references live in the `livepilot-core` skill's `references/` directory:
-- `livepilot-core/references/ableton-workflow-patterns.md` — session/arrangement workflows, song structures by genre, follow actions, clip launch modes, export settings

package/livepilot/skills/livepilot-composition-engine/SKILL.md

@@ -1,107 +0,0 @@
----
-name: livepilot-composition-engine
-description: This skill should be used when the user asks to "analyze song structure", "improve transitions", "check song flow", "plan an arrangement", "detect motifs", "transform a section", or wants compositional analysis, transition planning, and translation checking.
----
-
-# Composition Engine — Structure, Transitions, and Form
-
-The composition engine operates three sub-engines: compositional analysis (structure and motifs), transition planning (section-to-section flow), and translation checking (how the mix survives different playback systems). It also provides form-level tools for emotional arc and arrangement planning.
-
-## Composition Sub-Engine
-
-Analyze and transform the structural elements of a track.
-
-### Analysis Flow
-
-1. Call `analyze_composition` — runs a full structural pass returning sections, motifs, phrase grid, and form classification
-2. Call `get_section_graph` — returns the section map: intro, verse, chorus, bridge, drop, breakdown, outro with bar ranges
-3. Call `get_phrase_grid` — returns the rhythmic and melodic phrase boundaries within each section
-4. Call `get_motif_graph` — returns detected melodic and rhythmic motifs with their occurrence locations and transformation history
-
-### Transformation
-
-Once you understand the structure:
-
-- `transform_motif(motif_id, transformation)` — apply a transformation to a detected motif. Transformations include: inversion, retrograde, augmentation, diminution, transposition, fragmentation, sequence
-- `transform_section(section_id, transformation)` — apply a structural transformation to an entire section. Transformations include: extend, compress, strip_down, build_up, reharmonize, rhythmic_variation
-
-Always capture before state with `get_notes` or `get_arrangement_notes` before transforming. Evaluate the result with `evaluate_composition_move`.
-
-### Motif Work
-
-The motif graph tracks recurring melodic and rhythmic patterns:
-
-- Each motif has an `id`, `pitches`, `rhythms`, `first_occurrence`, and `occurrences` list
-- Related motifs are linked by transformation edges (e.g., motif_2 is an inversion of motif_1)
-- Use the motif graph to ensure thematic coherence — transformations should derive from existing material
-
-## Transition Sub-Engine
-
-Plan and execute smooth transitions between sections.
-
-### Transition Flow
-
-1. `analyze_transition(from_section, to_section)` — examine the current transition between two sections. Returns energy delta, timbral shift, harmonic distance, and detected issues
-2. `plan_transition(from_section, to_section)` — generate a transition plan based on detected issues. Returns an ordered list of moves (filter sweeps, risers, drum drops, fills, automation curves)
-3. `score_transition(from_section, to_section)` — rate the current transition quality (0.0-1.0) with breakdown by energy, harmony, rhythm, and timbral continuity
-4. Execute the planned moves using appropriate tools (`set_clip_automation`, `add_notes`, `set_device_parameter`, `apply_automation_shape`)
-5. `evaluate_composition_move` — judge whether the transition improved
-
-See `references/transition-archetypes.md` for common transition patterns and when to use each.
-
-### Transition Principles
-
-- Energy changes should be gradual unless a hard cut is intentional
-- Harmonic transitions need a pivot chord or shared tone
-- Rhythmic transitions benefit from a fill or break at the boundary
-- Timbral shifts should start 1-2 bars before the section change
-- The most effective transitions prepare the listener's ear before the change lands
-
-## Translation Sub-Engine
-
-Check how the mix translates across playback systems.
-
-### Translation Flow
-
-1. `check_translation` — run translation analysis on the current mix
-2. `get_translation_issues` — return specific problems:
-   - **mono_collapse**: elements that disappear or phase-cancel in mono playback
-   - **spectral_consistency**: frequency balance shifts between monitoring contexts
-   - **low_end_translation**: bass content that may vanish on small speakers
-   - **loudness_consistency**: perceived loudness variation across systems
-
-Translation issues feed back into the mix engine — a mono collapse issue becomes a stereo_width critic issue for the mix loop.
-
-## Form Sub-Engine
-
-High-level arrangement and emotional arc tools.
-
-### Form Flow
-
-1. `get_emotional_arc` — map the energy/intensity curve across the entire track, identifying peaks, valleys, and plateaus
-2. `plan_arrangement` — generate an arrangement plan based on the current form, suggesting section order, lengths, and energy targets
-3. `apply_gesture_template` — apply a predefined arrangement gesture (build, drop, breakdown, outro_fade, intro_build) to a bar range
-
-See `references/form-patterns.md` for common song forms and energy curves by genre.
-
-### Arrangement Principles
-
-- Every section should have a clear purpose: introduce, develop, contrast, resolve, release
-- The energy arc should have at least one clear peak — flat energy across the entire track lacks emotional impact
-- Contrast drives interest: loud/quiet, dense/sparse, bright/dark
-- Repetition builds familiarity but needs variation to avoid fatigue — transform on repeat, do not copy verbatim
-- Transitions are as important as sections — budget time for them in the arrangement
-
-## Combining Sub-Engines
-
-A typical compositional improvement session:
-
-1. `analyze_composition` to understand current structure
-2. `get_emotional_arc` to see the energy shape
-3. Identify the weakest section or transition
-4. Use the transition sub-engine to fix section boundaries
-5. Use motif transformations to add thematic development
-6. `check_translation` to verify the changes survive mono/small speakers
-7. `evaluate_composition_move` after each change
-
-Always work one change at a time. Verify and evaluate before moving to the next intervention.

package/livepilot/skills/livepilot-composition-engine/references/form-patterns.md

@@ -1,97 +0,0 @@
-# Form Patterns Reference
-
-Common song forms and energy curves used by `plan_arrangement` and `get_emotional_arc`.
-
-## Standard Forms
-
-### verse_chorus (Pop / Rock / R&B)
-```
-Intro (4-8 bars) -> Verse 1 (8-16) -> Pre-Chorus (4-8) -> Chorus 1 (8-16)
--> Verse 2 (8-16) -> Pre-Chorus (4-8) -> Chorus 2 (8-16)
--> Bridge (8) -> Final Chorus (8-16) -> Outro (4-8)
-```
-Energy curve: low -> medium -> high -> medium -> high -> peak -> fade
-
-### drop_form (EDM / House / Techno)
-```
-Intro (16-32 bars) -> Build 1 (8-16) -> Drop 1 (16-32)
--> Breakdown (8-16) -> Build 2 (8-16) -> Drop 2 (16-32)
--> Outro (8-16)
-```
-Energy curve: building -> peak -> valley -> building -> peak -> fade
-
-### through_composed (Ambient / Cinematic / Experimental)
-```
-Section A (variable) -> Section B (variable) -> Section C (variable) -> ...
-```
-No repeating sections. Energy curve follows the narrative arc. Each section introduces new material.
-
-### aaba (Jazz / Classic Pop)
-```
-A (8 bars) -> A (8) -> B (8) -> A (8)
-```
-Energy curve: establish -> reinforce -> contrast -> resolve
-
-### rondo (Classical-influenced / Progressive)
-```
-A -> B -> A -> C -> A -> D -> A
-```
-Recurring theme (A) alternates with contrasting episodes. Energy varies per episode.
-
-### loop_form (Hip-Hop / Trap / Lo-Fi)
-```
-Intro (4-8) -> Loop (4-8 bars, repeated throughout)
-Verse 1 over loop -> Hook over loop -> Verse 2 over loop -> Hook -> Outro
-```
-Energy modulation through vocal density and arrangement layering, not harmonic progression.
-
-## Energy Curve Targets
-
-The emotional arc maps energy on a 0.0-1.0 scale across the track duration.
-
-### Peak-Valley Model
-Most effective for dance and pop music:
-- At least one peak reaching 0.8-1.0
-- At least one valley dropping to 0.2-0.4
-- Energy delta between adjacent sections: 0.15-0.4
-- Gradual builds (4+ bars) feel more natural than instant jumps
-
-### Plateau Model
-For ambient, drone, and minimalist music:
-- Energy stays within a narrow band (0.3-0.6)
-- Changes are subtle: timbral, textural, not dynamic
-- Slow evolution over minutes, not bars
-
-### Escalation Model
-For builds, film scoring, and progressive tracks:
-- Monotonically increasing energy from 0.1 to 1.0
-- Each section is louder, denser, or brighter than the previous
-- No significant drops until the final resolution
-
-## Section Energy Targets by Genre
-
-| Section | Pop | EDM | Hip-Hop | Ambient |
-|---------|-----|-----|---------|---------|
-| Intro | 0.2 | 0.3 | 0.3 | 0.2 |
-| Verse | 0.4 | 0.4 | 0.5 | 0.3 |
-| Pre-Chorus | 0.6 | 0.6 | — | — |
-| Chorus/Drop | 0.8 | 1.0 | 0.7 | 0.5 |
-| Bridge | 0.5 | — | 0.4 | 0.4 |
-| Breakdown | — | 0.2 | — | 0.3 |
-| Outro | 0.3 | 0.2 | 0.2 | 0.1 |
-
-## Section Length Guidelines
-
-- **4 bars**: minimum for a recognizable section (short intros, transitions)
-- **8 bars**: standard phrase length, feels complete for most sections
-- **16 bars**: full development, typical for verses and choruses in electronic music
-- **32 bars**: extended development for drops, long builds, or ambient passages
-- **Odd lengths** (6, 10, 12 bars): create subtle tension and asymmetry — use intentionally
-
-## Arrangement Planning Rules
-
-1. Start from the emotional peak and work backwards — place the climax first, then build toward it
-2. Every section serves one of five functions: introduce, develop, contrast, climax, resolve
-3. Do not repeat a section more than 3 times without significant variation
-4. The first 30 seconds determine whether the listener stays — make them count
-5. Endings matter — an abrupt end can be intentional, but a trailing reverb wash is rarely wrong