A UX model that I think is more powerful (but less sexy) is to focus on the "dumb" parts of the question, that is: surfacing url's and fragments from those url'

A UX model that I think is more powerful (but less sexy) is to focus on the "dumb" parts of the question, that is: surfacing url's and fragments from those url's that relate to the question, and then sprinkle some LLM summarising on top. Instead of leading with a meandering LLM explanation of the subject with some references thrown on top. I want to AI to assist instead of lead. The UX of an unravelling conversation should be the sideline of my quest for answers, not the main show. If this was a preferable UX to developers we would design our existing documentation sites very differently. Unrelated, a search I made: I asked it how state management could be handled in html Web Components. It described how server side state works in Microsoft's Blazor, described React and Redux, and then briefly mentioned hooks and class based components in React. None of which is related to Web Components.