ChoréoVault — the spec

An AI-powered internal tool for solo choreographers to digitize, tag, and retrieve their movement sequences in one organized archive. Built for working dance business owners who need to capture choreography quickly during or between rehearsals and find it again without digging through notebooks, video folders, or memory.

Decisions locked

The core loop

1. Capture — User opens the mobile app mid-rehearsal and records a movement sequence via video or voice note.
2. Tag — Immediately after capture, the app prompts for key metadata: music, style, duration, difficulty level.
3. AI processing — The system transcribes the movement notation and applies suggested tags based on content and prior entries.
4. Archive — The entry is saved to the choreography library, indexed and searchable.
5. Retrieve — User searches by style, music title, or tag during a future rehearsal and pulls up the sequence in seconds.
6. Revise — User updates or annotates the entry; a new version is saved without overwriting the original.

v1 scope

Mobile app for rehearsal access — A lightweight iOS and Android app that gives instant access to the full archive during live rehearsal. Hosts the capture flow, tag prompt, and search — the complete core loop in one interface.

Metadata tagging — Each choreography entry stores music, style, duration, and difficulty level, set at capture and editable any time. Tags power all search and filtering across the archive.

Full-text search across choreographies and tags — A search bar on the library screen queries titles, tags, notes, and transcribed notation simultaneously. Returns ranked results so the right sequence surfaces in under three taps.

Version history — Every edit creates a numbered version rather than overwriting. The version panel on the entry screen shows timestamps and change notes, letting the user roll back or compare revisions.

AI movement transcription — Video or voice input is processed by the AI layer to produce a written movement description attached to the entry. Reduces manual note-taking and makes entries text-searchable without extra effort from the user.

Deliberately later

• Side-by-side video comparison — meaningful only once users have accumulated enough versions to need visual diffing; premature in v1.
• Collaborative annotation and timing markers — targets multi-user workflows; v1 serves solo owners exclusively.
• One-click portfolio export (PDF or web link) — a sharing and client-facing feature that belongs after the archive itself is proven stable and valuable.
• AI-suggested movement variations and remix ideas — generative layer that requires a rich personal dataset to produce relevant suggestions; earns its place after the archive has depth.

Data model sketch

• users — id, email, phone, created\_at, notification\_preference
• choreographies — id, user\_id, title, recorded\_at, duration\_seconds, difficulty\_level, style, music\_title, ai\_transcription\_text, current\_version\_id
• versions — id, choreography\_id, version\_number, video\_url, voice\_note\_url, change\_note, created\_at
• tags — id, label, user\_id (user-scoped tag vocabulary)
• choreography_tags — choreography\_id, tag\_id (join table)
• notifications — id, user\_id, channel (email/SMS), event\_type, sent\_at, status

Screens

• Home / Dashboard — recent entries, quick-capture button, and search bar as the primary entry point.
• Capture screen — record video or voice note, then immediately fill metadata fields before saving.
• Library / Archive — full filterable list of choreographies; supports search by tag, style, and music.
• Entry detail — displays transcription, all metadata, version list, and playback for the attached media.
• Version panel — lists all versions of one entry with timestamps; allows rollback and change-note viewing.
• Settings / Account — manages profile, notification channel (email or SMS), and subscription if applicable.

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are ready to act on immediately.
• Keep it as the single source of truth while you build, so every decision about priority and trade-offs traces back to one place.