Music Port now follows the work across the site.
Bands, charters, songs, practice plans, rehearsals, room requests, gear, gigs, learning records and Lighthouse session ideas are stored locally on this device and summarized here. Nothing is uploaded.
The public magazine ends here. Your working tools begin.
This local prototype demonstrates how a participant could control day-of participation and a Music & Access Profile without making diagnosis the center of the system. It is not a secure production account system.
How are you participating today?
Choosing a mode should not disclose a diagnosis to the ensemble. In production, staff would see only the operational accommodations they need.
Practice should connect to the band, course and current song version.
Use Practice Lab to define the exact musical target, evidence and access setup. Drumojo can carry rhythm-specific work; Songbook keeps the current chart/reference; Lighthouse courses can assign and review work without turning practice into attendance surveillance.
Equipment library
Request/checkout instruments, hearing protection, stands, electronic percussion, adaptive mounts, tablets and mobile recording kits; view maintenance status and regional pickup/return.
Open Gear Library →No data entered here is sent to ANCHOR. A production system would need authentication, encryption, role-based access, consent, youth/guardian rules, retention limits and a clear distinction between optional access preferences and protected education/health records.
Music Port stores records. Scene Board asks what comes next.
The prototype now spans players, bands, charters, songs, rehearsals, rooms, gear, sets, riders, gigs, EPKs, credit drafts, sound plans, courses and saved opportunities. Scene Board reads those local records and points to missing links instead of treating data entry as the outcome.
Coursework belongs beside the musician’s rehearsal life.
Saved course interests and TeleClass notes now surface in the same local Music Port summary as bands, songs, rehearsals, gear and shows. A production system would use explicit permissions and separate youth/school privacy controls.
The participant record now touches the infrastructure around the music.
A production Music Port should not become a giant profile. It should expose only the records the participant needs: what I am playing, what I am practicing, where the room is, what gear is assigned, what I am learning, what the show needs, and what I chose to share.