From ae11d5c9503e4d96bb6a3dd2b3e099c92a03fbab Mon Sep 17 00:00:00 2001 From: adam Date: Tue, 17 Aug 2021 08:52:20 -0400 Subject: [PATCH] Add 'Home' --- Home.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 Home.md diff --git a/Home.md b/Home.md new file mode 100644 index 0000000..e4cf015 --- /dev/null +++ b/Home.md @@ -0,0 +1,9 @@ +the director translates between what must be done, and commands. + +usual course of events should be: both are always running. Dave is doing his calendar checks every hour. He should emit a message whenever he sees an event added or removed like 2 weeks into the future (but not going into the past). (on startup the director should ask him to reply with the next 2 weeks as though he too just started up). + +director hears of event added. +* if it's a YT release, run some kind of "yt event checklist". These events can start bothering me as soon as they get added to the calendar. + * is the calendar event tied to a yt link? if not, human intervention needed + * check with the YT agent; does that yt release have all the metadata it needs? (name, thumbnail, playlist, etc) +* if it's a twitch show, ask dave to make a folder with the checklist for adam, then kick me into gear 4 hours ahead of time - I'll parse config.json and read that for how to direct a show. right next to that should be config-companion.json, which should kick off to companion. \ No newline at end of file