====== Hivemind Feature ====== Hivemind is the space where teams create, discuss, and approve recommendation ideas before they become live. ===== What Hivemind Does ===== * Gives teams a clear way to submit new recommendation ideas. * Keeps all discussion for each idea in one place. * Sends ideas to admin review before release. * Prevents unfinished or rejected ideas from going live. * Keeps a visible history of feedback and decisions. ===== Who Uses It ===== * Organization and group users can submit ideas. * Admin reviewers approve, reject, or request changes. * Proposal participants can follow progress and discuss updates. ===== How It Works ===== - A user creates a proposal with: - strategy - implementation - micro-script - avoid micro-script - target audiences - The proposal appears in the Hivemind queue. - Participants discuss and refine the proposal. - Admin review sets one of three outcomes: - **Approved**: proposal is released. - **Needs Revision**: proposal returns for updates. - **Rejected**: proposal is closed. ===== Proposal Statuses ===== * **Draft**: created and still being prepared. * **Needs Revision**: feedback was given and updates are required. * **Approved**: accepted and released. * **Rejected**: closed and no longer active. ===== User Experience ===== * Proposal lists are grouped by status so teams can track progress quickly. * Proposal pages show full content and discussion in one view. * Users can send messages inside each proposal thread. * Review notes are visible in the same thread for context. * Email notifications keep participants informed of updates. ===== Current Boundaries ===== * Rejected proposals are locked for new discussion. * Approved and rejected proposals are not editable. * Message editing controls are limited in the current UI. ===== Outcome ===== Hivemind provides a structured, collaborative approval flow that improves quality control, keeps decision-making transparent, and ensures only reviewed recommendation content is released.