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

+4 -4
View File
@@ -93,11 +93,11 @@
<button type="button" id="a-add-language" class="secondary">Add language</button>
<button type="button" id="a-suggest-languages" class="secondary">Suggest languages</button>
<span class="hint">A two-letter code such as <code>en</code> or <code>da</code>, and how well. Roles that ask for a language you lack, or a level above yours, get a warning on Roles; a role that names one of yours as a plus gets a star. With none, no role is flagged. Suggest languages reads them from the CV with one model call and replaces the rows above; nothing is saved until Save.</span>
<label>Avoid / drains me
<label>What I like
<textarea id="a-like-text" rows="4" placeholder="Building a team from scratch, close work with the product side, small companies, a say in the roadmap"></textarea></label>
<label>What I don't like
<textarea id="a-avoid-text" rows="4" placeholder="Constant on-call, sales targets, large consultancies, open-plan offices"></textarea></label>
<label>Must-haves and deal-breakers
<textarea id="a-must-text" rows="4" placeholder="Permanent contract&#10;A say in the roadmap&#10;At most one day a week in the office"></textarea></label>
<span class="hint">One must-have per line. The judge reports for each whether a posting meets it, clearly breaks it or does not say; a broken one caps the role's career score at 39 in code, whatever the model scored. Rules that must hold go under Where or Other rules instead.</span>
<span class="hint">The work, the workplace, situations; read by the CV match for the career score. Rules that must hold go under Where or Other rules instead.</span>
</fieldset>
<fieldset class="weights">
<legend>How much each counts</legend>