KR comes in from a public-facing form (e.g. Google, Tally or built into Discord using embeds).
Notion gets updated by Zapier bot
Zapier bot sends a notification to ping the requested subDAO(s) in Discord about the new KR. Could also ping the MedicoLegal as well/instead to provide some oversight, transparency, accountability & routing support for subDAOs. → [MedicoLegal Chat](https://meddao.notion.site/MedicoLegal-Chat-fbe6fe47b1a94cc4b12a82fbfce2e161) 1.
DeWork issues a task/bounty on-chain
SubDAOs respond by updating Knowledge Request Tracker to claim KR
Sub-tasks are added to DeWork bounty until the subDAO submits it for final review
MedicoLegal WG and submitter of the KR either approve/deny the submission
Bounty is paid out on-chain to the subDAO, or directly to contributor(s), depending on the subDAOs governance.
If bounty is paid directly to the subDAO, they could distribute the amount via Coordinape or use some internal accounting to allocate remuneration to individual contributors.
@flowscience What do you know about https://dework.xyz/
That's a fantastic idea. It's gotten pretty popular and I've used it on a variety of teams. It makes sense to track KRs with a kanban style workflow and having an on-chain MVP would be ideal. Issuing KRs as bounties also makes sense and each subDAO can link DeWork to a subDAO-specific Coordinape round so contributors can have a monthly/seasonal peer-reward system integrated with the record of tasks completed for KRs they responded to. DeWork has a great discord bot too.
DeWork also integrates with Notion & Github so tasks can be issued directly from those platforms.