Let the model report a verdict per must-have and cap career at 39 in code when one is broken
The judge numbers an agent's must-haves (one per line) and answers met, broken or unclear for each; career is stored as the model gave it and counts as at most BROKEN_CAP when a role is served, in cv_score, Store.judgement and the SQL of Best CV match. Migration 29 adds role_judgements.musts and broken; the judge's input_key carries a format version so earlier judgements are made again. The reader lists the must-haves with their verdicts and the cap. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
64fecf57ad
commit
001fc9002b
19 files changed
+336
-61
No files matched your search
@@ -21,6 +21,9 @@
|
||||
* The CV fieldset holds what the judge stage reads a role against: the CV as
|
||||
* text (typed, or read from a .md/.txt file by the browser), the languages it
|
||||
* states as rows of a code and a level, and the avoid and must-have texts.
|
||||
* The must-have text is one must-have per line, which the judge answers one
|
||||
* verdict each; a broken one caps career at 39 in code (the hint in
|
||||
* settings/agents.html says so).
|
||||
* Every save sends all four, and the card's switch re-posts the row as the
|
||||
* server gave it, so neither drops them.
|
||||
*
|
||||
|
||||
Reference in new issue
Block a user