Design: suggestion UI for edit components

[jimmoffet]

As a user, I want to be able to see what is being suggested and accept (implement the change) or decline (make the suggestion go away).

Acceptance:

• [ ] User can see suggested change and accept or decline
• [ ] Suggested changes include changes to language, suggestion to delete
• [ ] Suggestion to change component or pattern type (eng will come later, but can design now)

Overview

As a , I would like , so that I can _.

Context

Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.

• [ ]

Acceptance Criteria

Required outcomes of the story

• [ ]

Research Questions

• Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

• [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

• [ ] Behavior
  • [ ] Acceptance criteria met
  • [ ] Implementation matches design decisions
• [ ] Documentation
  • [ ] ADRs (/documents/adr folder)
  • [ ] Relevant README.md(s)
• [ ] Code quality
  • [ ] Code refactored for clarity and no design/technical debt
  • [ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
  • [ ] Code is reviewed by team member
  • [ ] Code quality checks passed
• [ ] Security and privacy
  • [ ] Automated security and privacy gates passed
• [ ] Testing tasks completed
  • [ ] Automated tests pass
  • [ ] Unit test coverage of our code >= 90%
• [ ] Build and deploy
  • [ ] Build process updated
  • [ ] API(s) are versioned
  • [ ] Feature toggles created and/or deleted. Document the feature toggle
  • [ ] Source code is merged to the main branch

Decisions

• Optional: Any decisions we've made while working on this story

[JennyRichards-Flexion]

This is a ticket to make clear to design that we can build AI-powered suggestions, if we want. This could be read for a narrower set of use cases - we could write deterministic rules that pops help text. Or situations where we always want to provide a given suggestion.

Dan: This brings up the idea of a form specification - You as a form author document the behavior of your form so others could understand it. Could be useful for someone who's collaborating with building the form, but also legal aid folks who are helping others complete the form (this would allow them to understand the intention of the form). Could be defined by LLM also - would you like us to suggest some specification materials (for unit testing).