Profiles

Scopes

Profiles can be saved as:

  • song
  • album
  • artist
  • collection

Directory Layout

profiles/
  songs/
  albums/
  artists/
  collections/

Example:

profiles/
  albums/
    example-artist/
      midnight-signals/
        core.json
        harmony.json
        rhythm.json
        arrangement.json
        prompt.json
        bundle.json

Domains

  • core.json key, tempo, structure, arrangement, pitch summaries
  • harmony.json harmonic rhythm, chord vocabulary, progressions, bass motion
  • rhythm.json onset density, syncopation, step patterns
  • arrangement.json energy curve, layer combinations, entry order, section-level role signals
  • prompt.json compact prompt-ready profile distilled from the domains above
  • bundle.json manifest that links the profile domains together

Why prompt.json Exists

Album bundles can be too large for clean prompting. prompt.json compresses the useful musical signals into a smaller context:

  • role presence
  • role constraints, including anchor, recurring, occasional, and sparse roles
  • section-level active/inactive role signals
  • section-position archetypes for aggregate bundles
  • harmonic behavior
  • rhythmic fingerprints
  • arrangement hints

generate --style bundle.json automatically prefers prompt.json.

During generation, role presence ratios are treated as section-count budgets. This prevents recurring or sparse roles from becoming always-on parts unless the profile actually supports near-constant presence.

Edit this page