Judge each agent's best roles against its CV as skills, experience and career, a stage after summarise

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-03 22:00:18 +02:00
1 parent 4fc474c437
commit 9960799b96
14 files changed
+866 -44

No files matched your search

+3 -3
View File
@@ -174,12 +174,12 @@
<h2>Runs</h2>
<button type="button" id="pull-now" class="secondary">Run the pull now</button>
</div>
<p class="lede">On the schedule below the pull reads every board, embed and score rank every role, extract fills in what the best postings say, score runs again with what it filled, and summarise writes the summaries.</p>
<p class="lede">On the schedule below the pull reads every board, embed and score rank every role, extract fills in what the best postings say, score runs again with what it filled, summarise writes the summaries, and judge scores the best roles against each search agent's CV.</p>
{# The two stages that ask a model, switched here rather than in config.yaml
{# The three stages that ask a model, switched here rather than in config.yaml
(`GET /api/stages`); jobs.js draws the rows into #stages-list. #}
<h3 id="stages">What the model reads</h3>
<p class="lede">Extract and summarise ask a model, which costs tokens on the API. Turning one on starts nothing: the next pull runs it, and Run the pull now does so at once. How deep each reads is set per search agent, under <a href="/settings/agents">Search agents</a>.</p>
<p class="lede">Extract, summarise and judge ask a model, which costs tokens on the API. Turning one on starts nothing: the next pull runs it, and Run the pull now does so at once. How deep each reads is set per search agent, under <a href="/settings/agents">Search agents</a>.</p>
<div id="stages-list" class="srows"></div>
<p id="stages-answer" class="count" role="status"></p>