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>
This commit is contained in:
WolfandClaude Sonnet 5.5 committed 2026-10-03 22:48:46 +02:00
1 parent 82afa831f2
commit 8c6cbdf002
18 files changed
+144 -75

No files matched your search

+18 -4
View File
@@ -328,9 +328,10 @@ END;
-- as JSON: a key it lacks means the `Limits` default. fetch_terms is a JSON
-- list of words that narrow what big boards send (app/jobs/reach.py); empty
-- means no narrowing. cv_text, cv_languages (a JSON list of {language,
-- level}), avoid_text (what drains) and must_text (must-haves and
-- deal-breakers) are what judge reads a role against; an agent with no CV
-- is not judged.
-- level}), like_text (what they like: the work, the workplace, situations),
-- avoid_text (what they do not like) and must_text (must-haves and
-- deal-breakers, set through the API only) are what judge reads a role
-- against; an agent with no CV is not judged.
CREATE TABLE IF NOT EXISTS agents (
id INTEGER PRIMARY KEY,
name TEXT NOT NULL UNIQUE,
@@ -343,7 +344,8 @@ CREATE TABLE IF NOT EXISTS agents (
cv_text TEXT NOT NULL DEFAULT '',
cv_languages TEXT NOT NULL DEFAULT '[]',
avoid_text TEXT NOT NULL DEFAULT '',
must_text TEXT NOT NULL DEFAULT ''
must_text TEXT NOT NULL DEFAULT '',
like_text TEXT NOT NULL DEFAULT ''
);
-- What an agent looks for, as several named texts in order; a role's fit is
@@ -707,6 +709,10 @@ UPDATE roles SET seniority = COALESCE(NULLIF(seniority_model, ''),
# keep their numbers; the judge reads them again (judge.FORMAT).
(29, "role_judgements.musts and broken: the verdict on each must-have, and how many are "
"broken", lambda conn: _add_musts(conn)),
# A Python step: it adds the column only where it is missing. The judge
# reads every role again (judge.FORMAT).
(30, "agents.like_text: what the person likes, beside what they do not like",
lambda conn: _add_like_text(conn)),
)
#: What a file created from `SCHEMA` today is already at.
@@ -1047,6 +1053,14 @@ def _add_musts(conn: sqlite3.Connection) -> None:
conn.execute(f"ALTER TABLE role_judgements ADD COLUMN {column} {ddl}")
def _add_like_text(conn: sqlite3.Connection) -> None:
"""Migration 30's step: `agents.like_text`, empty on every agent. Runs
twice without harm."""
columns = {r[1] for r in conn.execute("PRAGMA table_info(agents)")}
if "like_text" not in columns:
conn.execute("ALTER TABLE agents ADD COLUMN like_text TEXT NOT NULL DEFAULT ''")
def _add_all_roles(conn: sqlite3.Connection) -> None:
"""Migration 21's step. The column; the tag for every company that is a
favourite of any agent, since favourite no longer widens what a pull