ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend
Evaluation: Update score rendering system
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem?
Score rendering currently assumes a cosine similarity on a 0–1 scale. The new v2 model provides three judge metrics—Adherence to Ground Truth, Adherence to Prompt, Adherence to Knowledge Base—as integers from 0–5, which are only applied per row if the necessary inputs are provided.
Describe the solution you'd like
- Update
app/lib/types/evaluation.tsto support the 0–5 range and the per-tracereasoningfield with traffic light colors 0–1 needs improvement(red), 2–3 could improve(yellow) and 4–5 good(green)
Screenshot of Glific UI for reference
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in app/lib/types/evaluation.ts and trace the score-rendering consumers that use its evaluation values. Verify support for integer scores from 0–5, the per-trace reasoning field, and the requested red, yellow, and green ranges for the three judge metrics. Confirm the rendering only applies metrics when their required inputs are provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100