Rebuild the agent form as the fetch gate, the feed order, the cut and summarise, and name fetch text and the overrides as built

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Sonnet 5.5 committed 2026-10-04 15:27:03 +02:00
1 parent fbc0f16c4a
commit 61aadff681
7 files changed
+185 -198

No files matched your search

+5 -5
View File
@@ -104,7 +104,7 @@
<section class="card" id="company-boards" data-section>
<h2>Company boards</h2>
<p class="lede">Every company roledesk has seen, and how many of its roles are open. Switching a board off stops reading it and closes its roles; hiding a company keeps reading it but leaves its roles out of the list and unscored, and favourite or like lifts one instead, in Agent match.</p>
<p class="lede">Every company roledesk has seen, and how many of its roles are open. Switching a board off stops reading it and closes its roles; hiding a company keeps reading it but leaves its roles out of the list and unscored. Like or favourite raises a company's roles a little in the cut and in the feed order, in each search agent's own ranking (a liked company about 0.05, a favourite about 0.1), and passes nothing the fetch gate rejects. All countries and All roles are for every agent: the first skips the place part of the fetch gate, the second the fetch terms and the titles to leave out.</p>
<form id="board-form" class="agent-form source-form" autocomplete="off">
<h3>Follow a company</h3>
@@ -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, summarise writes the summaries, and judge scores the best roles against each search agent's CV.</p>
<p class="lede">On the schedule below the pull reads every board and every search, embed and score rank every role and fix each agent's cut, fetch text reads the own page of the cut roles that came without text, extract fills in what the cut postings say, score runs again with what it filled, judge scores the cut against each search agent's CV, and summarise writes the summaries for the top of the feed.</p>
{# The three stages that ask a model, switched here rather than in config.yaml
{# The stages with a switch, 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, 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>
<h3 id="stages">What the pull reads</h3>
<p class="lede">Extract, summarise and judge ask a model, which costs tokens on the API; fetch text asks none. 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>: fetch text, extract and judge read the agent's cut, and summarise reads its own size.</p>
<div id="stages-list" class="srows"></div>
<p id="stages-answer" class="count" role="status"></p>