Score each role's closeness to the agent's CV, let the judge also read the 50 closest the score leaves out, and order CV match's unjudged roles by it

The CV is cut into chunks inside e5's window, embedded like a prompt and
cached per agent under a hash of the model, chunking and text. A role's
cv_fit (scores.cv_fit, migration 31) is its best chunk cosine, scaled with
its own calibration band: fit's clipped 88 of agent 2's ungated roles to 1.
It is no term of the Agent match score. judge_cv_top (default 50) sits
beside judge_top and judge_min on the agents page and card.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-03 23:35:21 +02:00
1 parent b481cb5692
commit c23594507a
23 files changed
+603 -85

No files matched your search

+4 -3
View File
@@ -14,9 +14,10 @@ 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
among its best ungated scores as deep and as low as its own `limits` say
(`judge_top`, `judge_min`) with some text, that has no judgement yet, or one
read from another CV, prompts, like, avoid or must text or role text than today's
(`input_key`). A pair is named by the composite key `"<agent_id>:<uid>"`,
(`judge_top`, `judge_min`), or among the `judge_cv_top` ungated roles closest
to its CV (`scores.cv_fit`) that those leave out, with some text, that has
no judgement yet, or one read from another CV, prompts, like, avoid or must
text or role text than today's (`input_key`). A pair is named by the composite key `"<agent_id>:<uid>"`,
which is what `desk.modeltask` hands round as a uid, so `desk/` is untouched.
A batch holds one agent's pairs, since the profile is in the system prompt;
the finder cuts per agent (`_finder`) and the job runs one call per agent it