[Design] Decisions display with assistant-ui Elements (option list, question flow)
lavaman131 opened ·
## Proposal Render Decisions questions with [Option list](https://www.assistant-ui.com/elements/option-list) and [Question flow](https://www.assistant-ui.com/elements/question-flow) from assistant-ui's standalone Elements, as display and input surfaces only.
## Constraints - **Records own decisions** (AGENTS.md). Answers still go through `claimSubmit()` and the sidecar records, and the document projection is updated by domain operations only. The elements never become the authority. - Shared drafts, frozen definitions with appended options (`question:option`, at most 10, no case-insensitive duplicates), and the four relationship states (pending, linked, empty, orphaned) are preserved. - No new free-text custom answers. Existing `custom` answers still render.
## Acceptance criteria - [ ] Open, answered and appended-option states render with these elements. The receipt shows the recorded answer. - [ ] Question domain tests and Decisions E2E tests pass unchanged or are ported. `bun run ci` passes.
## Related - #306 (stack base), #163 (decisions design).
Assistant-workflow: inline Assistant-duration: unmeasured Assistant-verification: code inspection passed: mapped existing Chopin features to the assistant-ui Elements catalog (standalone elements-* registry items, no @assistant-ui/react runtime)
lavaman131added label enhancementlast month on GitHub
lavaman131assigned lavaman131last month on GitHub
- LA
Closing to avoid overlapping the in-flight design work: Maggie owns the chat, composer, decisions and research UI (#296, #278, #294, #285, #302, the [Design] issues #160-#164) and Krzysztof owns the research offers (#304). Any UI library choice belongs in that track.
Assistant-workflow: inline
lavaman131renamed Decisions display with assistant-ui Elements (option list, question flow) to [Design] Decisions display with assistant-ui Elements (option list, question flow)last month on GitHub