# ai-planning-20250414 ![alt text](https://files.slack.com/files-pri/T0HTW3H0V-F08MH958S3Y/img_1542.jpg?pub_secret=0ab0e7bd02) ## ai related events this week * **Language Center AI Workshop**, Mon 4–6pm, Main Studio * AI check in wednesday * AI@fas Thursday * **AI Working Group**, Fri 8:30–10am, Main Studio ### upcoming * louisa * taleen ## notes on last week * helped beginners work on python notebooks - moved from getting a transcript of a recorded video lecture to quiz questions * if we want to share a notebook publically, we want to go through and dress it up with comments and formatting (show mk) * if it's a participant notebook, it can be anonymous and we can be less intense about quality control * ALWAYS sending out links and summaries * more public facing book * section for each * links to instagram posts * news round up or summary, with links to all the stories that we printed ### tasks related to last week * summary post: what did we do? image from the lab. screenshot of code. link to a notebook. * another post from last week: gened1189 visit * another post from last week: madeleine on sts panel * posts/resources for when it quiets down a bit * activity (paper polling as http request) * backburner resource * vision for paper polling (+tutorial) * csv parsing notebook (+ tutorial) made for GENED1189 ## notes on this week upcoming * live transcription editing * connected to louisa and taleen * connected to what ask from chris ## tasks for up and coming things * launch slack in a meaningful way * things in slack by THURSDAY AM * reach out to chris and huit - "so at these internal meetings on friday we've started on taking your use cases as the problem statement for the meeting. we've worked on polling and generating quizzes. this coming week -- " * prep for wednesday * doc of everything (internal) * and prep for thursday * show things that are public (like the public facing hackmd book) * for bok ai lab on live transcription * slackbots, gdrive listener? * typing into slack * typing into google docs * polling * live parsing (prompt engineering in coping with a live feed - how often do you ask, what sorts of things do you ask, ) * web transcriptions API * editing (might be manual) * figure out release schedule for * slack * instagram ## duplicated # ai-lab-timeline-of-tasks dani create docs each week housed in an AI lab book * doc for the day of * we'll work on it earlier * post-mortem * summary of what happened good for structure to mirror the assets we need (tools for thinking, news, things that people are making) ## brainstorming notes ### Saturday & Sunday: * add slack news and notes, tools etc. (MK, KH, EW?) ### Monday: * mk+mw: review post-mortem notes in hackmd of what happened and/or if there's time, on camera reflection of what happened * dd: start doc for the upcoming friday * dd and mw confirm with mk the tasks/projects for the week related to digesting the last lab and prepping the next: * news + commentary from last lab * tutorials + show and tells from last lab * o1 research / tools for thinking from last lab * project launch for next lab with basic parameters for * activity * toolset * ll-project related to activity * o1 research tasks * by end of day: Post on Bok Instagram about previous week's Bok AI Lab * slack (insert details) * add news ### Tuesday: * planning for things ahead: * look ahead at what's upcoming * look back at what we didn't get to * determine which things we might want to focus on for the week ahed * slack (insert details) * add news ### Wednesday: * firm up what we will focus on for upcoming lab * deadline: Post on Bok Instagram about upcoming week's Bok AI Lab * slack * add news * start o1 research ### Thursday: * finalize plan for next day * slack * add news & print * finalize & print o1 research ### Friday: * Bok AI Lab happens * then immediate post-mortem summary of what happened * if there's time, on camera reflection of what happened * slack * summary of the week * summary of the lab (automated) ## schema for understanding the above - some days have specific events - some days have specific deadlines - each day involves human input to slack - each day involves ai input to slack - each day involves automated ai digestion/synthesis of slack and external sources