9 Commits
Author SHA1 Message Date
WolfandClaude Fable 5.1 2159c7925f Remove the must-haves the form dropped on 2026-10-03: the agent's must text, the judge's verdicts and the career cap they set, with migration 34 dropping their columns and the judge's format at 6 so every role is judged again
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 13:55:59 +02:00
WolfandClaude Opus 5.5 6d82287402 Bring the Python side to the ADR: the judge scores 0 to 10 with the cap at 4 and migration 33 clears every judgement, summarise reads the top 30 of the want and the match order, a hidden company's roles are never in the feed, and the company switch is called All locations.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 21:40:32 +02:00
WolfandClaude Opus 5.5 8b6c6d5ac3 Test migration 32, the cut, saved filters and the override rescore, and bring the READMEs and config comments to fetch text and the cut
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 15:16:38 +02:00
WolfandClaude Opus 5.5 617356e60c Rank by the cut: fetch gate overrides in scoring, the cut per agent, stages read the cut, fetch text renamed from enrich, the feed kept to the fetch gate, and migration 32
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 15:11:43 +02:00
WolfandClaude Sonnet 5.5 ee8e450640 Summarise every saved or liked role whatever its rank, queue it at once on save or like, and shorten the order labels to Agent match, CV match and Newest so they fit one line
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 23:14:12 +02:00
WolfandClaude Sonnet 5.5 8c6cbdf002 Give an agent a soft profile of likes and dislikes and take the must-haves off the form (wp-likes)
Add agents.like_text (migration 30) beside avoid_text, now shown as "What I don't like". The judge reads both under <likes> and <dislikes>, its career rubric judges against the prompts, the likes and the dislikes, and FORMAT 3 makes earlier judgements be made again. The form drops the must-haves box and no longer sends must_text, so a stored one is kept and still caps career in code.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 22:48:46 +02:00
WolfandClaude Sonnet 5.5 001fc9002b 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>
2026-10-03 22:40:54 +02:00
WolfandClaude Sonnet 5.5 585c332d74 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>
2026-10-03 22:25:44 +02:00
WolfandClaude Opus 5.5 14076e988d Serve Best CV match, Closing soon, the language flag and the deadline in the feed, and suggest an agent's languages from its CV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 22:04:54 +02:00