Rank by the cut: fetch gate overrides in scoring, the cut per agent, stages read the cut, fetch text renamed from enrich, the feed kept to the fetch gate, and migration 32

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-04 15:11:43 +02:00
1 parent 060ccf66e6
commit 617356e60c
35 files changed
+1054 -751

No files matched your search

+7 -6
View File
@@ -6,12 +6,13 @@ what the model is told, the schema it answers in, what to do with the
answer), and running it is `desk.modeltask`'s.
A role is waiting while it has no summary, has some text, is open and no copy,
and is either in the top of an enabled agent's ungated scores as deep and as
low as that agent's own `limits` say (`summarise_top`, `summarise_min`), or
one the owner cares about whatever its rank: saved (it has an application, the
star) or voted up by an enabled agent. The limits keep the cost flat: a pull
summarises the roles somebody will look at, not the 30k that are open, and the
saved and liked roles are a handful the owner picked. Each is summarised
and is either in the top of an enabled agent's feed, the best `summarise_top`
final scores among the roles its fetch gate passes (its `limits`), or one the
owner cares about whatever its rank: saved (it has an application, the star)
or voted up by an enabled agent. Summarise is no part of any score and runs
last in the pull, once the final scores are set. The limit keeps the cost
flat: a pull summarises the roles somebody will look at, not the 30k that are
open, and the saved and liked roles are a handful the owner picked. Each is summarised
once, with the same give-up rule (`GIVE_UP_AFTER` replies that left it
without). Saving or liking a role queues a batch for that one uid at once,
while the stage is on (`web.api`), rather than waiting for the next pull. A