Problem/Motivation
Getting a raw explanation from OpenAI is a good step. To augment this, allowing a dev or site owner to add a 'solution' or series of notes in for each tracked explanation may help teams keep a rolodex of known errors and what they did to solve them in the past.
Proposed resolution
Add operation links on a log to add/update a 'solution'.
User interface changes
Add operation links on a log to add/update a 'solution'.
API changes
None, so far.
Data model changes
Add a 'solution' column to the openai_dblog table.
In addition, it may be nice to think of ways to solidify the data and look for a possible pathway to integrate these user-added solutions as a custom Solution Provider for the https://www.drupal.org/project/ignition module. See: https://github.com/spatie/ignition#using-solution-providers
Comments
Comment #2
kevinquillen CreditAttribution: kevinquillen at Velir commentedComment #3
kevinquillen CreditAttribution: kevinquillen at Velir commentedComment #4
kevinquillen CreditAttribution: kevinquillen at Velir commentedIdea - we could also create a way to 'fine tune' a model with the provided solutions so the results from OpenAI get better.
https://platform.openai.com/docs/guides/fine-tuning
Then feed the API with error/solution data:
Using the API: https://platform.openai.com/docs/api-reference/fine-tunes/create
Comment #5
kevinquillen CreditAttribution: kevinquillen at Velir commentedComment #6
kevinquillen CreditAttribution: kevinquillen at Velir commentedWhile I would love to see this happen, I think it needs to take a lower priority for now. DX improvement in #3353653: Add support for AI powered solutions for developers should be sufficient.
Comment #7
kevinquillen CreditAttribution: kevinquillen at Velir commentedComment #8
kevinquillen CreditAttribution: kevinquillen at Velir commented