Simplify default composite evaluation management by andresgutgon · Pull Request #2093 · latitude-dev/latitude-llm

andresgutgon · 2026-01-07T18:23:38Z

What?

Now documents always have one composite evaluation of type average. This way, we simplify the UI, and we don't need all the alerts and toast system to notify when this composite evaluation goes out of sync.

TODO

Run migration to add mainEvaluationUuid in my dev db.
Test create eval with issue and see how composite is created
Test assign issue to eval and see how it's added to composite
Test un-assign issue from eval and see how is removed from composite
Test remove eval with assigned issue and see how is removed from composite
Check that composite is removed after last eval with issue assigned is removed or updated.
Check that defaultTarget is not used in the evals table
Check that defaultTarget is not used in Composite Form issues selector
Double-check all the alerts and toast related with sync-composite are gone

Default composite evaluation lifecycle

A composite of type average is created by Latitude in the document
This evaluation composite is pointed to document.mainEvaluationUuid
This is used in optimizations when selecting what evaluation to pick. By default we select this one for the users to use.
If user add a new evaluation with an issue linked for that document we add that evaluation to the composite/average
If user remove the issue from one evaluation that was included in the composite evaluation we remove that eval.uuid from the configuration
If user removes the evaluation (and had issue linked) we remove it from the composite
If the evaluation removed is the last one we do 2 things: Remove the composite evaluation and set to null -> mainEvaluationUuid in the document

From `defaultTarget` to `mainEvaluationUuid`

Before we had defaultTarget as part of the jsonb config of the composite evalution. Now we do a real link from this evaluation to the document.
Also we don't allow users to chose what of the composite evaluations they have in the document is the one that is the default. The default is manage by us. The constrain here is that is always of type average. The other types like weighted demands manual intervention. We let users manage their own evaluations but this one is auto updated and for that we're removing all the Alerts and Toast we had to let users know the main evaluation was out of sync. Makes UI and understanding more complicated

andresgutgon · 2026-01-08T09:54:46Z

@copilot review the PR and let me know if I'm missing something. Do not open another PR or make changes to this one. Just comment if you see something wrong. Otherwise congratulate me for the great work I did

Copilot · 2026-01-08T09:54:59Z

@andresgutgon I've opened a new pull request, #2094, to work on those changes. Once the pull request is ready, I'll request review from you.

andresgutgon · 2026-01-08T09:56:52Z

Eres muy tonto

.../[documentUuid]/(withTabs)/optimizations/_components/OptimizationForm/EvaluationSelector.tsx

neoxelox · 2026-01-08T10:46:03Z

packages/core/src/services/evaluationsV2/composite/index.ts

  }

-  const validating = await validateSubEvaluations({ uuid, configuration, evaluations }) // prettier-ignore
+  const validating = await validateSubEvaluations({


I let prettier free always I see this

packages/core/src/services/evaluationsV2/sync.ts

neoxelox

The document cannot be updated with a simple sql query!

Now the system is allowing to have a default composite evaluation of any type. We're changing that here to always have one composite evaluation of type `average`. This way with this we simplify the UI and we don't need all the alerts and toast system to notify when this composite evaluation goes out of sync when a evaluation is removed from an issue for example.

andresgutgon force-pushed the fix/simplify-default-composite-evaluation-management branch 2 times, most recently from e5d3968 to 3a14a6b Compare January 8, 2026 09:29

Copilot AI mentioned this pull request Jan 8, 2026

Code review completed - no changes needed #2094

Closed

andresgutgon requested a review from neoxelox January 8, 2026 09:55