Something like this can be somewhat useful (not saying I would pay though!)
I would like to have 1000 or so vetted docs (can manually or AI vet). E.g. public API doc > internal API doc > Internal RFC > Some guys internal note they made public.
Take RFC and higher links and surface the ones I need for thw project. Chuck them in the Jira ticket.
That would be handy. But it isn't my biggest problem. So not sure how that squares up. With AI I can build this internally in a bespoke way (this is the general disruption AI has on any SaaS idea lol!) so not sure what sauce you would need.
The other AI problem is you are fighting the bitter lesson. By October CC might do this as a one sentence one shot.
Just to clarify my scope: I’m starting with a personal, individual workflow (toC) where you control the sources end-to-end — local files, bookmarks, email, personal docs, etc. I’m not assuming company integrations, approval flows, or “drop into Jira” as the primary surface (those are a different product/compliance game).
That said, your “vetted docs + provenance + surface into the place you already work” framing is still useful in the personal setting too: a small trusted set of sources, always show citations/snippets, and a low-friction output surface (e.g. a task/project note you already use).
If you were applying the same idea personally, what would your “output surface” be — a todo app, calendar, a project doc, or just a weekly review note?