Make the three CV match weights a per-agent setting, applied when a role is served

cv_skills, cv_experience and cv_career live in agents.weights (30, 25, 30 by
default), edited on the Search agents page beside fit and recency. cv_score is
worked out at read time in the feed order, the row and the reader, so changing
them asks the model for nothing and leaves the judge's input_key alone.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Sonnet 5.5 committed 2026-10-03 22:25:44 +02:00
1 parent d5df707148
commit 585c332d74
8 files changed
+147 -28

No files matched your search

+4 -2
View File
@@ -3,8 +3,10 @@
A `ModelTask` beside `summarise`, after the `/rank` of
github.com/MadsLorentzen/ai-job-search: the model reads a posting against a
written profile and scores skills, experience and career 0 to 100, with one
to three strengths and gaps. The total is `app.models.cv_score`, what the
feed's Best CV match sorts by. Culture and location are left out: the first
to three strengths and gaps. The total is `app.models.cv_score`, the three
numbers under the agent's `cv_*` weights, worked out when a role is served and
not stored, so the weights are no part of `input_key`; it is what the feed's
Best CV match sorts by. Culture and location are left out: the first
is guessed from ad text, the second is what the gates do.
The work is pairs, `(agent, role)`: an enabled agent with a CV, and a role