The Help Foundation is the navigation and learning system for The Muzes Garden. It explains where things are, how to get there, how to use them, and what they mean.
Verified workflows come first. Planned systems can be named, but instructions should stay tied to real tested routes whenever possible.
Help is now organized like a dropdown tree instead of a giant wall of information. Start with Find It when you feel lost, or open the branch that matches the thing you are trying to understand.
Best first stop when the member knows what they want but does not know where it lives.
Step-by-step guidance for common member workflows.
Plain-language meaning for app labels, areas, and controls.
Click-order paths for getting from one app area to another.
Fast answers for common confusion without opening the whole knowledge base.
Small definitions that keep Help language consistent.
Find It, Route Maps, How Do I, What Is This, Quick Answers, Glossary, Tips, and What's New work together so members can find places, follow routes, understand words, and recover when they feel lost.
This page can get much bigger over time, but it should stay split into data files, small panels, and dropdown branches so the route stays easy to protect.
Use this when you know what you want to do but do not know where it lives yet.
Find where things live inside The Muzes Garden using route cards, category filters, search keywords, presets, and step-by-step navigation paths.
These buttons fill the search so matching Help routes appear below.
Finding tracks, uploaded music, tags, filters, and track details.
Opening projects, reviewing tracks, managing setlists, and project playback.
Comparing, loading, analyzing, and reviewing track intelligence.
Finding shelves, sections, records, details, and knowledge relationships.
Project organization areas and future workspace navigation.
Common navigation questions and app-wide orientation.
Now playing, playback controls, and track information.
Library, metadata, project, help, and future global search paths.
Linked records, future project links, and future track relationships.
Find It, Route Maps, Quick Answers, Glossary, and What's New.
Step-by-step routes for the things members will do most often. Verified workflows come first.
Use this when songs are still on your computer and need to be added to The Muzes Garden.
Use this when the upload finished but you do not see the song yet.
Use this when you know a track title, tag, mood, source, or keyword and need to narrow the Library.
Use this when the Library looks empty because a search term or filter is hiding the track list.
Use this when you remember a sound idea, mood, genre, or tag but not the exact track name.
Use this when you want to start listening from the Library instead of a project.
Use this when you need to know whether a track is uploaded, seeded, stored, or connected to a project.
Use this after songs are already in your Library and you want them inside a project.
Use this when you want to return to an existing project from the main navigation.
Use this when you need the main summary area for a project.
Use this when you need to see which songs are currently inside a project.
Use this when you need ranking, favorites, or the strongest tracks inside a project.
Use this when a project already has tracks linked and you want to hear the project.
Use this when you want project playback controls instead of only the global player.
Use the project setlist area when the project track order needs to change before playback.
Use this when one song needs to play earlier in the project order.
Use this when one song needs to play later in the project order.
Use this when you need project notes, details, or future metadata connections.
Use this when you want the metadata panel focused on a specific track.
Use this when you want to hear whether two tracks work together or inspect their musical relationship.
Use this when you need to choose the first song for comparison.
Use this when you need to choose the second song for comparison.
Use this after Track A and Track B are loaded and you want analysis panels.
Use this when you need pitch, tempo, or key information for the loaded tracks.
Use this when you want to understand which Track Matcher lanes exist and what they do.
Use this when you want to understand how comparison lanes connect to each other.
Use this when you want deeper analysis summaries, diagnostics, or future AI comparison panels.
Use this when you need music knowledge records, shelves, sections, or deeper explanations.
Use this when you need the top-level metadata group before choosing a record.
Use this when you are inside a shelf and need the smaller group that holds records.
Use this when you need one detailed music knowledge page.
Use this when you need connected concepts, related records, or linked music knowledge.
Use this when a short record card is not enough and you need the deeper explanation path.
Use this when you need the C Major reference page or music theory explanation.
Use this when you need to know which track is currently selected or playing.
Use this when you need play, pause, or other listening controls.
Use this when you want a different song to become the active player track.
Use the real TitleBar Help dropdown. Help owns Find It, How Do I, What Is This, Routes, Tips, and What's New.
Use this when you know what you need but do not know where it lives inside the app.
Use this when you need a literal click path instead of a general explanation.
Use this when you need a short answer to a common confusion.
Use this when a word, feature name, or app term needs a plain-language definition.
Use this when you need recent Help Foundation updates or planned improvements.
Use this when you do not know where you are or what to click next.
Plain-language explanations for the major areas of The Muzes Garden.
A project is where uploaded Library tracks become an organized working collection with playback, setlist order, notes, metadata, and future relationships.
The Library is the main place where tracks live after upload. From there, tracks can be searched, filtered, played, and sent into projects.
Upload brings audio from the computer into the app. The verified folder route sends songs into the Library first.
The Player is the listening area. It shows what is playing, gives playback controls, and helps confirm which track is active.
Metadata is not just tags. It is the app knowledge system for libraries, shelves, sections, records, relationships, and explanations.
Track Matcher is the audio intelligence workspace for comparing, preparing, and eventually matching musical material.
The setlist is the ordered track list inside a project. It controls project playback order and helps arrange songs.
Find It is the navigation encyclopedia. Use it when you know what you need but do not know where that thing lives in the app.
Route Maps are literal click paths. Use them when you need step-by-step navigation instead of a general explanation.
How Do I cards explain the action workflow: uploading, finding, comparing, organizing, playing, and recovering when lost.
Quick Answers are short Help answers for common confusion. They should be fast to scan and not overloaded with technical detail.
The Glossary explains app words in plain language so a user does not have to guess what a feature name means.
Workspace means the organized working areas of the app. Projects are the current main workspace, with future workspace areas planned.
Relationships are links between records, tracks, projects, notes, lanes, and future intelligence results. They help the app explain how things connect.
Search is the path for narrowing information. It currently appears in focused areas like Library and Help, with future global search planned.
Navigation paths for moving through the app without guessing.
Use this full route when starting with songs on your computer.
Use this route when uploaded songs only need to be findable in the Library first.
Use this shorter route when songs are already uploaded.
Use this route when you need to find one track and start playback.
Use this when you are inside a project and want to focus metadata on one track.
Use this when you need project song order controls.
Use this when you want to review the strongest or ranked songs in a project.
Use this route when you want to compare two songs from the Track Matcher page.
Use this route when you want the lane registry or lane relationship explanation.
Use this route when you want to browse from Metadata home into records.
Use this when you need related concepts after opening a metadata record.
Use this route when you need the app guide instead of guessing through page links.
Use this when you want the navigation encyclopedia.
Use this when you want step-by-step app paths.
Use this when you need a plain-language meaning.
Short answers for things that can cause confusion during real use.
Upload puts the song into the Library first. After that, select it in Library, choose the project, and use Send To.
Open Projects, choose the project, then use the project player or track row play controls.
Find It belongs under Help because it answers how to locate a page, tool, or workflow.
Help can name planned areas, but step-by-step instructions should stay based on verified workflows.
Open Help, then use Find It. Search for the thing you want, read the route, and follow the route chips one step at a time.
Find It tells you where something lives. Route Maps give the literal click path to get there.
How Do I is for full workflows. Quick Answers are short answers for common confusion.
Uploaded tracks should live in the Library first. Projects use Library tracks after they are selected and sent into a project.
A search term or filter may be too narrow. Clear the search box first, then try a shorter word, tag, source, or mood.
Use Track Matcher. Load Track A, load Track B, then compare or analyze.
Track A is the first comparison track. Track B is the second comparison track.
Use Track Matcher analysis areas after loading tracks. Key and BPM content belongs with comparison and analysis panels.
The Lane Registry explains the Track Matcher lanes and keeps the comparison architecture easier to understand as it grows.
Lane Relationships explain how Track Matcher lanes connect, support each other, and prepare for deeper intelligence.
Metadata explains meaning, relationships, details, and knowledge. It is deeper than a quick tag.
Tags are quick labels for filtering. Metadata is a deeper knowledge system with records, relationships, and explanations.
Open Metadata, enter the Library, choose a shelf or section, then open a record.
Metadata relationships show how records connect to other records, concepts, tracks, projects, or future knowledge objects.
A project is an organized working collection made from Library tracks, with playback, setlist order, notes, metadata, and future relationships.
Open the project, then use the Setlist area. Move Up means earlier; Move Down means later.
Open a project, go to Overview, then look for Top Tracks.
The Player is the listening area that shows the current track, now-playing information, and playback controls.
Choose a different track from Library or Projects, press play, then confirm the Player updates.
Use Upload from the title bar when it is available. Upload adds computer audio files into the Library first.
Workspace means the organized working areas of the app. Projects are the current main workspace, with future workspace areas planned.
Future relationships will connect tracks, versions, metadata records, project notes, Track Matcher results, and related ideas.
No. Navigation shows where pages are. Help explains what those pages mean and how to move through them.
Use Route Maps. They are meant to show the literal path from one app area to another.
Use the Glossary or What Is This sections. They explain app words in plain language.
Clear search and filters before assuming data is gone. A hidden search term is often the reason.
Help for uploaded tracks, Library search, tags, filters, track details, and audio sources.
Uploaded Tracks are songs brought into the app from the computer. They should be findable from the Library after upload.
Library Search narrows tracks by title, tag, source, mood, or keyword so the user does not have to scan the whole Library.
Filters narrow the Library to a smaller set of tracks. If the list looks wrong, clear the search or filter before assuming tracks are missing.
Tags are quick labels attached to tracks. They are useful for fast filtering, but they are not the same as deeper Metadata records.
Track Details show extra information about one track, such as title, source, tags, or future metadata links.
Audio Source explains where a track came from: uploaded file, seed data, storage, project link, or future source type.
Help for project overview, project tracks, top tracks, project playback, metadata, and future relationships.
Project Overview is the main summary for a project. It should help the user understand the project before opening deeper areas.
Project Tracks are the songs connected to one project. This area explains what belongs to the project.
Top Tracks are highlighted or ranked tracks inside a project. They help identify important songs quickly.
The Project Player is the playback area for music inside a project. It should make project listening feel separate from simple Library browsing.
Project Metadata is the project-level information, notes, or future relationships connected to a project.
Future Project Relationships will connect projects to tracks, metadata, notes, and other projects.
Help for now playing, playback controls, current track information, and switching tracks.
The Player is where the app confirms the current track and gives listening controls like play and pause.
Now Playing tells you which track is currently selected or active. Check this first when you are not sure what song is playing.
Playback controls are the play, pause, and listening controls attached to the current track or player area.
Track information includes the current track title, source, and related details shown near the player or track row.
Switching tracks usually starts from Library or Projects. Choose another track, press play, and confirm the Player updates.
Help for finding tracks, metadata, projects, Help answers, and future global results.
Use Library Search when the user needs to narrow tracks by title, tag, source, mood, or keyword.
Use Find It and Quick Answers when the user needs to search Help guidance instead of scrolling the whole page.
Use Metadata search or browse paths when the user needs to find a record, shelf, section, concept, or explanation.
Use project areas when the user needs tracks, setlists, overview information, or project metadata.
Future global search should eventually connect tracks, projects, metadata, and Help from one search path.
Click-order maps for moving through the app without guessing.
The full verified song intake path from computer files to project playback.
The shorter intake path for getting songs into the app before organizing projects.
The verified route for songs that are already inside the Library.
The listening path for finding a track and starting playback.
The foundation path for changing the order of songs in a project.
The path for reviewing a project's strongest or featured tracks.
The foundation path for playing tracks from inside a project.
The route for comparing two loaded tracks.
The route for understanding lane registry and lane relationships.
The route from Metadata home to one detailed metadata record.
The route for finding related concepts after a metadata record is open.
The foundation route for opening deeper metadata explanations.
The foundation route for finding instructions without redesigning navigation.
The safe restart path when the user does not know where they are in the app.
The planned route for one search path across tracks, projects, metadata, and help.
Plain-language guidance for comparing tracks, loading Track A and Track B, reviewing lanes, and understanding future intelligence panels.
Track Matcher is the workspace for deeper audio comparison and future intelligence tools. It should explain what a track is doing and how pieces may relate.
Start by opening Track Matcher from the TitleBar. Load Track A and Track B, then use the verified comparison and analysis areas.
Library stores and filters tracks. Track Matcher is for analysis, preparation, and matching workflows that are bigger than simple storage.
Track A is the first track in a comparison. It is usually the source, reference, or first song you want to test.
Track B is the second track in a comparison. It is usually the candidate, match, or second song you want to compare against Track A.
The Lane Registry explains the available Track Matcher lanes and keeps lane architecture easier to understand as the system grows.
Lane Relationships explain how Track Matcher lanes connect, support each other, and prepare the app for richer future intelligence.
Intelligence panels are the places where analysis summaries, comparison clues, diagnostics, and future AI-assisted results can live.
Key and BPM information helps compare musical compatibility, tempo, pitch, and future transition or matching options.
Future stem tools may compare vocals, drums, bass, instruments, and other separated audio parts once those workflows are built.
Help guidance for the app knowledge system: library, shelves, sections, records, relationships, and details.
Metadata is not just tags. It is the app knowledge system: libraries, shelves, sections, records, relationships, and explanations.
Use Metadata when you need meaning, notes, relationships, or detailed information attached to a musical object.
Tags are quick labels. Metadata is deeper information that explains what something is, how it connects, and why it matters.
The Metadata Library is the main knowledge area where shelves, sections, and records can be browsed.
Shelves are top-level groups inside Metadata. They keep large knowledge areas separated and easier to browse.
Sections live inside shelves. They break a shelf into smaller groups so records do not become one giant pile.
Records are individual metadata knowledge pages. A record can explain a key, concept, relationship, sound idea, or future music object.
Record Details are the deeper view for one metadata record. Use details when the short summary does not explain enough.
Metadata Relationships show how records connect to other records, concepts, tracks, projects, or future knowledge objects.
More Information is the deeper explanation path planned for records, cards, and pages that need more context than a small panel can hold.
Help for understanding how metadata records, Track Matcher lanes, projects, tracks, and future intelligence results connect.
Metadata relationships connect records, concepts, explanations, and future knowledge objects.
Lane relationships explain how Track Matcher analysis lanes connect and support each other.
Future project relationships will connect projects to tracks, notes, metadata, and other projects.
Future track relationships will connect versions, similar tracks, references, and Track Matcher results.
Basic guidance for understanding project order and future setlist controls.
A setlist is the ordered list of tracks inside a project. It helps decide what plays first, next, and last.
Use the project Setlist area when the order needs to change. Keep Help instructions literal after the exact controls are verified.
Project playback, review flow, and future live/listening tools can all depend on the order chosen in the setlist.
Move Up means the selected song should happen earlier in the project order.
Move Down means the selected song should happen later in the project order.
Project playback order should follow the setlist when the project player is using the organized project sequence.
Help for Projects as the current workspace, Track Matcher as the comparison workspace, and future app organization areas.
Projects are the current main workspace for organizing tracks into a working collection.
The project overview gives the user a starting point before opening tracks, setlists, playback, or metadata.
Track Matcher is the workspace for comparing, analyzing, preparing, and eventually matching tracks.
Future workspace areas can grow after Projects and Track Matcher are stable.
Help for Find It, Route Maps, How Do I, What Is This, Tips, and What's New.
Find It answers the question: where is this thing in the app?
Route Maps answer the question: what exact path do I click to get there?
How Do I answers the question: what workflow should I follow to do the task?
What Is This explains app areas and feature names in plain language.
Tips are small reminders that prevent common workflow mistakes.
What's New explains recent or planned Help Foundation improvements.
Quick reminders for workflows that can be easy to miss.
Use Choose Folder when you want to upload a whole song folder. Use Choose Files when you only want one or a few selected files.
Uploading songs does not automatically mean they are inside a project. Upload first, then send tracks from Library into the project.
Use Metadata when you only want to focus the metadata panel. Use Inspect when you want to preview and focus metadata together.
Navigation should answer where can I go. Help should answer how do I get there and what does it mean.
When a page has too many cards or tracks, search first. A short word is often better than a long exact phrase.
If something appears missing, clear the search box or filters before assuming the data is gone.
Find It is the safe restart point when the user knows the goal but not the app location.
Route Maps should be used when the user needs exact click order, not just the name of a page.
Metadata should explain what something means, what it connects to, and why it matters.
Track Matcher should be used when the question is about comparing, matching, analyzing, or preparing tracks.
Meanings for Help, Navigation, Routes, verified workflows, app areas, and future systems.
The member guide for how to use the app, what things mean, and how to get from one place to another.
Use Help when the question starts with how, what, where, or why.
The title bar and dropdowns that show where a member can go inside the app.
Use Navigation when the question is about moving to a page.
A route is a visible click path through the app, written step by step.
Use Routes when a member needs a literal path from one area to another.
A workflow that has been tested in the real app and should be safe to document.
Use verified workflow labels when Help content is based on real testing.
A foundation item is built enough to explain, but may still need more testing, wiring, or final UI polish.
Use foundation when the direction is real but the feature is not fully finished.
A planned item is a future feature or future route that should not be treated as finished.
Use planned when Help needs to name the future idea without pretending it is done.
The navigation encyclopedia that answers where something lives inside The Muzes Garden.
Use Find It when the user knows the goal but not the app location.
Step-by-step click paths that show how to move from one app area to another.
Use Route Maps when exact click order matters.
Workflow help that explains how to complete a task, not just where a page is.
Use How Do I for actions like upload, compare, search, organize, play, or recover.
Short answers for common confusion.
Use Quick Answers when the user needs a fast explanation, not a long workflow.
Plain-language explanations of app areas, features, and labels.
Use What Is This when a user asks what a word or page means.
A list of plain-language definitions for app terms.
Use the Glossary when a single term needs meaning.
The main place where uploaded and available tracks live before or outside project organization.
Use Library to find, search, filter, tag, inspect, or play tracks.
The path that brings audio files from the computer into The Muzes Garden.
Use Upload when songs are still on the computer and not in the app yet.
Tracks that were brought into the app from computer files.
Use Uploaded Tracks when a song was uploaded but needs to be found in the Library.
An organized working collection made from Library tracks, with playback, setlist order, notes, metadata, and future relationships.
Use Projects when tracks need to become an organized collection.
The organized working areas of the app. Projects are the current main workspace.
Use Workspace when talking about broader app organization areas.
The ordered track list inside a project.
Use Setlist when project song order matters.
A project area for highlighted, ranked, or important tracks.
Use Top Tracks when looking for standout songs inside a project.
The playback area connected to music inside a project.
Use Project Player when the user wants to listen from inside a project.
The listening area that shows now-playing information and playback controls.
Use Player when the question is about what is playing or how to control playback.
The current track or audio item selected in the player.
Use Now Playing when a user needs to confirm the active track.
Controls such as play and pause that affect listening.
Use Playback Controls when the user wants to start, stop, or change listening.
Extra information about one track, such as title, source, tags, or future metadata links.
Use Track Details when one track needs closer inspection.
The origin of a track, such as upload, seed data, storage, project link, or future source type.
Use Audio Source when a user needs to know where a track came from.
A way to narrow tracks, records, help cards, or future global results using words.
Use Search when a list is too large or the user knows a keyword.
A narrower view of content based on selected conditions or search text.
Use Filter when only certain tracks or cards should be visible.
A quick label used for finding and grouping tracks.
Use Tags for fast Library filtering, not deep explanation.
The deeper knowledge system for libraries, shelves, sections, records, relationships, and explanations.
Use Metadata when the question is about meaning, context, or relationships.
The main knowledge area where metadata shelves, sections, and records can be browsed.
Use Metadata Library when browsing music knowledge.
A top-level group inside Metadata.
Use Shelves to keep large metadata knowledge areas separated.
A smaller group inside a Metadata shelf.
Use Sections when a shelf needs smaller organization.
An individual metadata knowledge page.
Use Records for one concept, key, relationship, sound idea, or future music object.
The deeper view for one metadata record.
Use Record Details when the short card is not enough.
A link between records, tracks, projects, notes, lanes, or future intelligence results.
Use Relationships when explaining how things connect.
A deeper explanation path for a card, record, page, or feature.
Use More Information when the user needs context beyond a small summary.
The audio intelligence workspace for comparing, preparing, and eventually matching musical material.
Use Track Matcher when the task is comparison, matching, analysis, or preparation.
The first track loaded for Track Matcher comparison.
Use Track A for the source, reference, or first comparison song.
The second track loaded for Track Matcher comparison.
Use Track B for the candidate, match, or second comparison song.
The Track Matcher area that explains which comparison lanes exist and what they do.
Use Lane Registry when the user needs the lane architecture overview.
The Track Matcher area that explains how lanes connect and support each other.
Use Lane Relationships when explaining how comparison systems fit together.
Panels for analysis summaries, diagnostics, comparison clues, and future AI-assisted results.
Use Intelligence Panels when the user wants deeper analysis information.
Musical comparison information about pitch key and tempo.
Use Key And BPM when matching, comparison, or transition planning needs musical compatibility details.
A planned app-wide search path for tracks, projects, metadata, and help.
Use Future Global Search only as a planned concept until it is built.
Recent Help foundation updates and verified app guidance.
Folder upload works and sends uploaded songs into the Library.
Library tracks can be selected and sent into a project.
Project tracks can be opened and played after being sent.
Help now owns Find It, How Do I, What Is This, Routes, Tips, and What's New.
Help content is now split into dedicated data, presentation, styles, controller, and encyclopedia files.
The Help home page now includes overview, statistics, featured topics, and recovery guidance.
Find It grew into a navigation encyclopedia with categories, routes, filters, and search.
Quick Answers now covers many common areas of confusion across the app.
The Help glossary now explains core app concepts, workflows, and future systems.
Route Maps now provide step-by-step navigation guidance between major app areas.
Library support expanded to include uploaded tracks, search, filters, tags, and track discovery guidance.
Projects now have dedicated Help coverage for overview, playback, tracks, top tracks, and setlists.
Player documentation now includes now-playing concepts and playback guidance.
Workspace guidance now explains Projects as the primary working area of the app.
Metadata Help now explains libraries, shelves, sections, records, relationships, and record details.
Metadata is documented as a knowledge system rather than a simple tagging system.
Track Matcher now has dedicated Help coverage for comparison workflows and future audio intelligence systems.
Track Matcher Help now explains the Lane Registry architecture and lane purpose.
Track Matcher Help now explains how comparison lanes connect and support each other.
Track Matcher Help now introduces future intelligence panel concepts.
Help styling now follows the black-background and white-text visual system used throughout the app.
Help emphasizes Find It, Route Maps, and step-by-step navigation paths to reduce confusion.
The Help controller now organizes content into Library, Projects, Player, Search, Relationships, Workspace, and Help areas.
Context-sensitive You're Here guidance remains planned for a future phase.
Global search across tracks, projects, metadata, and Help remains planned.
Relationship-driven navigation between tracks, projects, metadata, and analysis remains planned.
The Help system will eventually support deeper in-app contextual assistance.