Metadata System

Metadata is not just tags. In The Muzes Garden, metadata is the structured knowledge system that lets the app describe music, project work, ideas, relationships, and future AI decisions.

The current model is built as: Library → Shelves → Sections → Records → Relationships. That gives the app a stable way to organize music theory ideas, songwriting concepts, artist references, project phases, and eventually very detailed sound-shaping information.

This structure matters because the app should not only store files. It should explain what those files mean and how they connect.

The seed metadata library already contains starter shelves for music theory, songwriting, artists, and projects. It also includes records such as C Major, Verse / Chorus Form, and the Metadata Foundation Phase.

Those starter records prove the shape of the system: records can have titles, slugs, visibility, excerpts, descriptions, fields, and relationships. That is enough to begin connecting metadata into Find It without guessing fake fields.

The next important step is making metadata records searchable, navigable, and understandable from multiple places in the app.

The long-term metadata system should support very deep explanation and relationship browsing. A word in a song, a chord change, a sound, an instrument, a lyric meaning, or a project note could all point to related records.

This is the foundation for a future knowledge graph. Instead of only browsing pages, users should be able to follow meaning: a project can point to a song, the song can point to a chorus, the chorus can point to a chord progression, and the chord progression can point to a music theory explanation.

Later, AI generation should use this same metadata foundation so prompts and outputs are not lost as random one-time events.

This tree is intentionally simple right now. The goal is to keep the shape understandable before adding deeper relationship tools and large UI systems.