Recording session runner desk
Lists before the session. Folders after wrap. You still mix.
shared by @alanvcurran ↗
How it's set up
They want input lists and recall notes before the session, then folder, refs, backup, and email after wrap. We have the tweet. We did not sit in the room.
- 01Before the session: input list and recall notes from a real setup you already use.
- 02The bot does not invent a mic or a track.
- 03After wrap: organize the folder, export refs, back up, draft the email.
- 04You send the email. You mix.
- 05One session this week. Not a week of dates.
Prompt
We cannot write an honest starter prompt from what was published. Use the steps above.
How the money works
A session that starts on time is hours you can bill. First proof is one input list you used and one wrap email you sent — not a studio day we have not seen.
What to try first
This week: one session, one input list before, one wrap folder after. You still mix.
Watch out
- Tokens: cap the run so one desk does not burn the week.
- Time: one checked result beats a pile you did not review.
- Claim: The session runner job is what they posted. Not a session we sat in. Not a public install.