ProjectsWorking now
Project containers for organizing songs, stems, prompts, notes, lyrics, and future AI work.
Why it matters
Projects are becoming the central containers that connect sounds, metadata, navigation, and future generation systems.
Manual
The Muzes Garden Manual
This manual is the beginning of the built-in encyclopedia and help layer for The Muzes Garden. The long-term goal is a connected knowledge system where pages, concepts, routes, music ideas, and future tools explain each other through linked information.
What this manual is becoming
Right now, the manual explains the major systems of the app. Over time, important concepts inside the text should also become linkable. A user should eventually be able to move from a page like Find It into deeper pages explaining navigation structure, metadata search, relationship graphs, and future routing systems.
The long-term idea is closer to a living encyclopedia than a normal help page. The system should eventually support pages within pages, relationship browsing, visual trees, and explanation layers similar to large creative software manuals.
This manual is also meant to reduce confusion for users with ADD by making routes, explanations, and relationships easier to follow step by step.
Core Systems
These are the systems currently shaping the foundation of The Muzes Garden.
Metadata SystemBuilding now
Structured music knowledge using shelves, sections, records, and relationships.
Why it matters
Metadata is the foundation for reusable music knowledge, future AI understanding, and relationship-aware navigation.
Find ItBuilding now
ADD-friendly navigation helper for finding routes, pages, records, and future knowledge links.
Why it matters
The app will eventually become too deep to navigate comfortably without intelligent guidance.
Global PlayerWorking now
Persistent playback while moving through projects, metadata, and future creation tools.
Why it matters
Music work often begins with hearing something. The player keeps sound connected to the rest of the system.
Future Systems
These systems are planned or partially started and will expand as the architecture grows.
AI Music GeneratorPlanned
Future prompt-based music creation with pronunciation planning and regeneration pipelines.
Why it matters
The goal is a controllable professional creation system, not a random prompt toy.
Site Tree / RoadmapBuilding now
Track what is done, what is being built, and how systems connect together.
Why it matters
As the app grows, users need a clear map of where systems live and how they relate.
How the systems connect
The important architectural idea is that these systems are not supposed to remain isolated from each other.
A future workflow might look like:
Project → Track → Metadata Record → Relationship → Prompt → Generator → Playback → Explanation → Navigation Path
That means a sound being played in the Global Player could eventually connect directly to metadata explanations, AI generation history, lyric meaning, project context, or future editing tools.
The Find It System is also evolving from a simple route helper into a true knowledge navigation layer.
Current philosophy
The Muzes Garden is intentionally being built slowly and structurally instead of rushing random disconnected features into the app.
The current focus is:
- • Keep the build green.
- • Split oversized files before architecture becomes unstable.
- • Create reusable systems instead of one-off hacks.
- • Make navigation understandable for ADD-style workflows.
- • Build future AI systems on structured metadata foundations.
The result should eventually feel less like a normal music app and more like a connected creative operating system.