HUE-048 — Build universal inbox routing proposals and correction workflow
Canonical source:
docs/roadmap/issues.json·HUE-048Specification status:
TBI· Readiness:agent:ready
Let users capture unfiled work while HUE proposes a correctable destination Space, Session type, topic and expected output.
- Create Inbox capture and routing-proposal records
- Implement initial rule/LLM-assisted proposal service
- Build Accept/Change/Keep UI
- Record transparent user corrections without hidden permanent learning
- Dispatch accepted item into a Session/task
Acceptance criteria
Section titled “Acceptance criteria”- Proposal shows original text and rationale
- User can change each field before dispatch
- Keep in inbox performs no hidden work
- Correction provenance is inspectable/deletable
- Dispatch creates exactly one idempotent destination object
Dependencies
Section titled “Dependencies”HUE-009HUE-012HUE-013
Non-goals
Section titled “Non-goals”- Build advanced learned routing optimization
Product contract
Section titled “Product contract”Implementation handoff requirements
Section titled “Implementation handoff requirements”- Preserve the documented security, project, memory and event boundaries.
- Add or update automated tests for every observable acceptance criterion.
- Provide real verification output; do not rely on a worker/agent self-report.
- Update only the exact documentation sections whose status changed.
- Include screenshots or a recording for user-interface changes.
- Include migration, rollback and recovery notes for data/state changes.
- Link the pull request to this issue with
Closes #<issue-number>.