Map cues
Preview strict UTF-8 CSV, TSV, or pasted lines and commit accepted cues atomically.
Private · local · DAW-neutral
Keep every cue tied to the right take.
Move from an authorized script to take decisions, pickup rounds, collision-safe filenames, local WAV/AIFF metadata, and a frozen delivery receipt. No account. No upload. No microphone.
C017 · REVISION 2
Keep the script change and the selected take in the same view.orchard_s01_c017_t02.wav
Script cuesStable revisions
AudioMetadata only
RuntimeLocal and offline
Script to session. Session to pickup. Folder to proof.
The product earns its place between your script spreadsheet and recording software by preserving the operational links both tend to lose.
Log takes
Number attempts quickly while every take retains its exact cue revision and session.
Preserve why
Freeze the reason, direction, previous choice, response, and resolution.
Reconcile files
Match expected names to local header metadata and freeze what was observed.
Useful because it refuses the wrong jobs.
No script or audio upload
Projects stay in browser storage. Audio bytes and paths are never retained.
No recording imitation
Your recording tool stays responsible for capture, listening, editing, and mastering.
No quality or rights score
Header observations and user-entered labels never become compliance or approval claims.
Complete fictional evaluation includedOrchard Signal contains 100 original cues, 236 take records, three sessions, two pickup rounds, one prior delivery freeze, and deliberate recoverable findings. It represents no real person, client, production, quotation, or recording.
Worked example
The shortest honest answer to what this is: a local ledger that keeps a script cue, the take that was read against it, the file that take will be delivered as, and the reason anything was redone, all in one record that survives a browser reload and travels as a file you own. It sits between your script spreadsheet and your recording software, and it does not try to become either.
The bundled Orchard Signal evaluation shows why that matters. It holds 100 original cues, 236 take records, three night-survey sessions, two pickup rounds and one prior delivery freeze. Since that freeze four things have gone wrong on purpose. Cue C017 was amended to a second revision, so its selected take now reads superseded script text. Cue C042 sits in issued pickup round P02 with no response take linked. Cue C055 is required, has takes, and has no current selection. The selected take for C090 renders an expected filename of CON.wav, a reserved device name on Windows, while cue codes C-071 and C_071 collapse onto one filename token once case and separators are normalized. A folder listing shows none of that. Working the stations in order shows all of it.
Method
The workspace is nine stations in a fixed order: session, cues, intake, takes, filenames, pickups, preflight, delivery, projects. Each station writes one kind of record and refuses to write the others, so a filename decision cannot quietly become a take decision and a pickup round cannot quietly rewrite the session it came from. Every take carries the exact cue revision that was read, which is the single link that makes a stale selection detectable later.
Projects live in IndexedDB in the current browser profile, with a session-only fallback when that storage will not open. Nothing is uploaded, and the pages carry a content policy that blocks outbound connections outright. Portability comes from versioned JSON checkpoints you download yourself; a restore is transactional and refuses a file whose schema or digest does not check out.
What this does not do
- It does not record, play, decode, transcode or assess audio, and it never asks for microphone permission.
- It does not judge quality, pronunciation, noise, loudness or synchronization, because it never reads a single audio sample.
- It does not decide rights, consent, union status, compensation or permitted use.
- It does not transmit files, and a frozen delivery record is not proof of receipt, approval or acceptance.
- It is not a backup service. No operator can recover a project for you, so download checkpoints.
Do this in the app
Fifteen minutes with the bundled evaluation is a faster answer than any feature list.
- Open the workspace and load the Orchard Signal evaluation at station 01 Session.
- Read station 05 Filenames and station 07 Preflight first; that is where the four planted problems surface.
- Download a checkpoint from station 09 Projects to prove the project moves between browsers.
Open the local workspace at station 01 Session