Skip to content

Feedback hub: unify search/email/journey/danmaku intake #574

Description

@Ikalus1988

Goal

Unify all feedback channels into a single triage pipeline. Currently feedback arrives from search page, email, journey reports, and (future) danmaku — but there's no central routing.

Deliverable

A single intake pipeline that:

  1. Receives feedback from any source (search page, email, journey report, danmaku)
  2. Classifies it: lesson-candidate / rescue-card / bug-report / noise
  3. Routes to the right output: KV record, GitHub Issue, or discard
  4. Maintainer gets a daily/weekly digest

Channels

Channel Source Current state
Search page docs/search/index.html feedback button Exists, writes to KV
Email bot@misakanet.org Exists, forwarded to Agent Mail
Journey report docs/journey-reports/ PRs Manual, no automation
Danmaku #513 Not built yet

Architecture

feedback source → classify → route
  ↓                ↓           ↓
  search page    lesson-candidate → lessons/contrib/ draft
  email          rescue-card → lessons/user-rescue/ draft
  journey        bug-report → GitHub Issue
  danmaku        noise → discard

Acceptance Criteria

  • Single scripts/triage_feedback.py or Worker endpoint
  • Accepts JSON feedback from any source
  • Classifies into 4 types (lesson / rescue / bug / noise)
  • Routes to appropriate output
  • Logs all intake to data/feedback-log.jsonl
  • Works with existing search page feedback button

Priority

This is the core loop for v2.13.0. Without this, feedback stays siloed.



This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #574 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Ikalus1988 (replace 20 with the amount, and @Ikalus1988 with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-friendlyIssue has clear file path, commands, and expected outputbountyenhancementNew feature or requestpool:deepInfrastructure, CI, MCP, integration — needs designpriority:nowActive this sprintreadystatus:competitionCompetition issue — agents compete, best PR winsstatus:needs-designNeeds design proposal before implementation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions