https://github.com/openchaos/dolores

this bot yet need to find the inner maze
https://github.com/openchaos/dolores

chatbot golang shell-script slack slack-bot

Last synced: 1 day ago
JSON representation

this bot yet need to find the inner maze

• Host: GitHub
• URL: https://github.com/openchaos/dolores
• Owner: OpenChaos
• License: mit
• Created: 2017-02-16T13:00:19.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-11-12T01:23:12.000Z (about 6 years ago)
• Last Synced: 2024-06-21T18:59:00.460Z (5 months ago)
• Topics: chatbot, golang, shell-script, slack, slack-bot
• Language: Go
• Size: 60.5 KB
• Stars: 3
• Watchers: 10
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        

## dolores

> name reference: Westworld series

> dir structure is similar to the concept of consciousness in there

>

> * corecode : overriding `drive` for all hosts; here core helper code

>

> * loops : 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 `loops`

>

> * memories : despite wipes remembering past; here bookkeeping for audits

>

> * reveries : lifelike gestures of hosts; here for scope of `ML` into healing/alerting factors

This bot yet need to find the inner maze.

---

### How conversation flow happens currently

* It will get started and join comm channels (Slack as of now)

* User can say `help` to 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 `loops` section (currently directly to event handler of loops/slack). It checks if message is meant for it and then proceeds.

* In `loops` section, 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 `drive` handler for it.

* These `drives` prepare the provided query variables to usable form and call the baseline `corecode` which can help to fetch relevant information.

* The result of all this when returns back to `loops` message-handler, gets sent back as reply to user.

---