name reference: Westworld series dir structure is similar to the concept of consciousness in there
corecode : overriding
drivefor all hosts; here core helper codeloops : the general narrative that bot stick to; here for presence on Slack, etc
drives : the goal to host's actions; here for Actions driven/demanded by presence in
loopsmemories : despite wipes remembering past; here bookkeeping for audits
reveries : lifelike gestures of hosts; here for scope of
MLinto healing/alerting factors
This bot yet need to find the inner maze.
-
It will get started and join comm channels (Slack as of now)
-
User can say
helpto Dolores for set of command-syntax it responds to. Yeah it's not to play friendly catch-up, yet. -
When any command (even 'help') is recieved by Dolores, they get passed to
loopssection (currently directly to event handler of loops/slack). It checks if message is meant for it and then proceeds. -
In
loopssection, recieved message is processed and identified for which message-handler it is meant. -
The message-handler extracts variable query from message and passes it to relevant
drivehandler for it. -
These
drivesprepare the provided query variables to usable form and call the baselinecorecodewhich can help to fetch relevant information. -
The result of all this when returns back to
loopsmessage-handler, gets sent back as reply to user.