Parent
A page, term, control, record, or future create item can become a parent when it leads to child concepts, deeper examples, advanced explanations, or related branches.
MetadataSystemFoundationQuery
Metadata System
Metadata Control Surface
This page is now meant to stay tighter and more usable. The query system stays near the top. The deeper explanations stay available below in collapsible sections instead of stretching the whole page into a giant scroll.
Metadata Query Engine
Search the Metadata Brain
Query across direct, inherited, related, expanded, and fallback metadata layers.
Enter a query like "groove" and click "Run Query".
Layers
Results Flow
Dedicated Results Page
121 entries • 328 links available
Next Page Flow Enabled
This panel now sends your query and filter state to the dedicated metadata results page instead of rendering results inline here.
Query: none
Mode: all
Target Type: all
Kind: all
Limit: 50
Destination: /metadata/results?mode=all&targetType=all&kind=all&limit=50&includeDirect=true&includeInherited=true&includeRelated=true&includeExpanded=true&includeFallback=true
Core Principle
Deep Underneath, Clean on the Surface
Open / Close
Core Principle
Deep Underneath, Clean on the Surface
The system is being designed so that important things can have parent-child structure, related records, deeper pages, examples, and future tutorial branches. At the same time, the visible page should not overwhelm the user with too many buttons, links, or distractions.
This means the architecture can be deep even when the page looks simple. A user who wants only the basics can stay near the top. A user who wants to explore can keep going deeper through more information pages, relationship links, context actions, or future create tools.
Structure Model
Shared Parenthood Ability
Open / Close
Structure Model
Shared Parenthood Ability
Child
A child can be a deeper explanation page, a practical example, a tutorial branch, a system note, a music concept, or a future create-system record.
Related
Not everything has to be parent and child. Some records should connect sideways through relationships so users can move across the knowledge network instead of only down a single chain.
Depth
The rabbit hole can go as deep as needed. The important rule is that the UI should only expose that depth when it helps the user instead of cluttering the surface.
Entry Paths
Ways Users Can Go Deeper
Open / Close
Entry Paths
Ways Users Can Go Deeper
More Information Buttons
Major pages and important records can expose a visible More Information button when a deeper explanation makes sense.
Hover Help
Short help text can appear on hover for quick explanations. This keeps the interface friendly for beginners without forcing them into long pages immediately.
Right-Click Context Actions
Advanced users can use right-click or future context menus to go deeper directly from the thing they are interacting with.
Top-Bar Systems
Top-bar areas like Metadata and the future Create tab can act as clean entry points into the deeper knowledge structure.
Create Connection
Future Create-System Expansion
Open / Close
Create Connection
Future Create-System Expansion
The future Create system can use this same structure. A create item can have a short explanation, a beginner example, a More Information page, and future child pages beneath it. That means the create layer and the metadata layer do not need separate help systems.
This allows the app to grow without becoming inconsistent. Buttons, records, controls, pages, and future create items can all plug into the same deeper knowledge model.
Future Slots
What Can Grow Here Later
Open / Close
Future Slots
What Can Grow Here Later
Tutorials
Step-by-step walkthroughs for beginners and advanced users.
Examples
Practical musical and interface examples that show how concepts work in real situations.
Help Records
Dedicated system explanations for controls, labels, tabs, and future create actions.
Media
Later this can grow into embedded demos, screenshots, and video guidance.