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

+13 -12
View File
@@ -1,5 +1,5 @@
"""Whether the three model stages of a pull, `extract`, `summarise` and
`judge`, and the `enrich` stage run.
`judge`, and the `fetch_text` stage run.
`extract.enabled`, `summarise.enabled` and `judge.enabled` in config.yaml are
read at startup and say nothing on the page, so the switch lives in the
@@ -10,16 +10,17 @@ deployment that never uses the switch behaves as it did. `stage_on` is the
one place that decides, and the tasks' finders ask it
(`extract.extract_task`, `summarise.summarise_task`, `judge.judge_task`).
`enrich` (reading the best roles on their own pages, `app/jobs/enrich.py`)
asks no model and is on by default (`enrich.enabled`); its switch is
`stage:enrich`, set the same way as the others: by the Runs page
(`PUT /api/stages/enrich`) and by `app stages enrich on|off`.
`fetch_text` (reading the role's own page for the roles in the cut,
`app/jobs/fetch_text.py`) asks no model and is on by default
(`fetch_text.enabled`); its switch is `stage:fetch_text`, set the same way
as the others: by the Runs page (`PUT /api/stages/fetch_text`) and by
`app stages fetch_text on|off`.
`describe` is what `GET /api/stages` and `app stages` show: for each stage
with a switch, the model stages and `enrich`, whether it is on, where that comes from, the model it uses, and who
would answer. The model is the one a call is made with: `agent.model` when
set, since it overrides the per-task model everywhere (`desk/modeltask.py`),
else the stage's own.
with a switch, the model stages and `fetch_text`, whether it is on, where
that comes from, the model it uses, and who would answer. The model is the
one a call is made with: `agent.model` when set, since it overrides the
per-task model everywhere (`desk/modeltask.py`), else the stage's own.
"""
from __future__ import annotations
@@ -34,8 +35,8 @@ from desk.tools import agent
NAMES = ("extract", "summarise", "judge")
#: Every stage with a switch: the model stages and `enrich`.
SWITCHES = (*NAMES, "enrich")
#: Every stage with a switch: the model stages and `fetch_text`.
SWITCHES = (*NAMES, "fetch_text")
#: What `describe_one` says of a stage that asks no model.
NO_ASK = "reads role pages, asks no model"
@@ -53,7 +54,7 @@ class Stage(BaseModel):
`backend` is `agent.backend`'s answer, "" for nobody, and `answer` says
it in words."""
name: Literal["extract", "summarise", "judge", "enrich"]
name: Literal["extract", "summarise", "judge", "fetch_text"]
on: bool
source: Literal["stored", "config"]
model: str