marvin
marvin copied to clipboard
allow configurable feedback mechanism
since we already have a weekly process in place to human-curate discourse posts and we have update_knowledge.py which already ingests discourse posts for the slack bot, persisting quality QA interactions to Discourse instead of chroma seems to solve the potential duplication problem, without introducing an additional location to write flat files
also updates Marvin's answer to the user after QA message is Edited