Audit streaming playlists against an owned music library

Why use this

1. A listener may have a streaming playlist whose tracks do not map cleanly to an owned library. Different releases, remasters and artist spellings can make an apparently complete local playlist contain the wrong recordings.

2. A track-matching review sheet could show which selections have reliable local matches and which remain missing or ambiguous. The owner could review collection gaps without treating an unavailable track as permission to acquire an unauthorized copy.

Why an agent / simpler alternative

Useful judgment

Compare title, artist and version information while recognizing ambiguous recordings.

Simpler alternative

Use identifier-based playlist sync when both libraries share reliable recording IDs.

Unsuitable when

Tracks lack sufficient metadata or the task depends on unauthorized music acquisition.

Proposed inputs

1. Name

   Streaming playlist export

   Owner

   Playlist owner

   Minimum scope

   Selected track order, artists and available version identifiers

   Quality check

   Confirm the intended playlist snapshot.

2. Name

   Owned-library index

   Owner

   Library owner

   Minimum scope

   Relevant local track metadata and existing playlists

   Quality check

   Check file availability and preserve original playlists.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only metadata exports and an offline match manifest.

Compatibility unknowns

1. Unknown: exact runtime, streaming access, Navidrome interfaces and note-writing support.

External actions requiring approval

1. Writing playlists or notes, altering library files or acquiring recordings.

Expected deliverable and review checks

Proposed artifact

Proposed local playlist mapping and missing-or-ambiguous track note.

Critical checks

1. Track order and recording versions are preserved where verified.

2. Uncertain matches are not silently substituted.

Missing output evidence

No new playlist sync, file inspection or playback test occurs here.

Failure signals and proposed responses

1. Signal

   A live recording replaces the requested studio version.

   Why it matters

   The mirrored playlist no longer matches the intended listening experience.

   Proposed response

   Mark the version mismatch and seek an exact local match.

2. Signal

   Two local files have indistinguishable metadata.

   Why it matters

   A confident mapping could select the wrong recording.

   Proposed response

   Retain both candidates and request owner review.

Effort and cost — unknown

Setup work

1. Normalize track metadata and agree match rules.

Ongoing review

1. Resolve ambiguous versions and review new missing tracks.

Unknowns

1. Unknown: API access, metadata quality and synchronization costs.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional playlist requests a studio track, while the local index offers a live version, an exact match for another track and no third track.

Acceptance checks

1. Exact, mismatched and missing outcomes remain separate.

2. No acquisition or file modification is proposed as completed.

Stop conditions

1. Copyright access or recording identity is unresolved.

Limits

1. Editorial collection audit; no rights, current app access or playback success is established.