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>
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>
A Your CV fieldset in the edit form: the CV as text or read from a .md/.txt
file, language rows of a code and a level with Suggest languages from the
CV, and the Avoid / drains me and Must-haves and deal-breakers texts. The
judge limits sit beside extract and summarise, the card's limits line gets a
judge clause and one more line says whether a CV is set and its languages.
Save sends all four fields, and the card switch re-posts the row with them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Provider names, the CLI's choices and the dupes rule's search hosts now come from readers.PROVIDERS, and the regions, work modes and remote words from the modules' REGIONS, MODES and REMOTE, read with getattr so main works before and after the readers merge.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The readers flattened a posting's HTML into one line with strip_html, so
sections and bullets ran together. _shared.html_text gives a line per
paragraph, '• ' before a list item and '## ' before a heading; every
reader's description goes through it, sections read per role get their
own headings, and the reader pane draws the lines as h3, ul and p.
Excerpts leave the marks out.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/api/suggest/places offers "Remote" (remote:any) first for "remote", counted in the scope of the agent asked for or the default agent, then the countries, then "Remote · <place>".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
remote_where is a list of names, [] when not stated. Remote is remote with a regular office week and hybrid with set office days each week.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The area is the model's names, else the parts of the place texts that say remote, else the resolved places as their countries. VERSION 3 maps every open role again. run_roles maps the roles extract answered. "Remote Sensing" in a title is no remote work.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
roles.remote_model, roles.remote_where_model and role_remote, with a stored remote no host word gives kept as the host's word. The remote tokens filter over role_remote, remote_from and a require gate on country read a remote role through its area, extract waits while remote_where_model is NULL and writes the model's remote outright, and rows carry remote_where.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
remote:country:DK is a remote role whose area overlaps Denmark: what lies in it, what it lies in, Anywhere. remote:anywhere is Anywhere alone and remote:any the viewing agent's scope. Anywhere is a continent outside the tree with no alias. Remote parts of a line are no town, and the suggestions offer the remote tokens after the countries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ten entries were shadowed by their modules. A test now holds that no entry
names a reader, which replaces the per-host checks.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A role whose title holds one of the agent's phrases as whole words is gated
with the phrase as its reason, a favourite's too. The agent form has a
Leave out titles line under Where. function = sales could not do it, since
the classifier files Solutions Engineer and pre-sales under sales.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>