Switch the extract and summarise stages on the page, over config.yaml
A stored `stage:extract` / `stage:summarise` in the state table overrides extract.enabled / summarise.enabled; with none, the file applies. One function, stages.stage_on, decides, and both tasks' finders ask it. GET/PUT /api/stages and `app stages` show and set it with who would answer; Runs has a "What the model reads" block, and a search agent's card says when a stage is off and links to the switch. Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
This commit is contained in:
1 parent
a629eda8de
commit
471ace703c
15 files changed
+593
-23
No files matched your search
+2
-2
@@ -8,7 +8,7 @@ Nothing is alive between two tasks. A stage is addressed by its position in
|
||||
the tuple, not its name, since `score` runs twice.
|
||||
|
||||
Every stage is always in the chain, and a stage that is switched off finds
|
||||
nothing: `extract.enabled: false`, or an `on_ingest` this pull does not
|
||||
nothing: a stage switched off (`stages.stage_on`), or an `on_ingest` this pull does not
|
||||
satisfy, is an extract stage with no batches whose final job moves straight
|
||||
on. The free stages go first: embed and score cost no tokens, and the score
|
||||
they produce is what bounds the two that do. Extract reads only the best
|
||||
@@ -69,7 +69,7 @@ def _extract(cascade: str) -> Task:
|
||||
def _summarise(cascade: str) -> Task:
|
||||
"""`summarise` as a stage: nothing with no model reachable, so a machine
|
||||
without one pulls in silence rather than failing a batch per pull. Off
|
||||
(`summarise.enabled: false`) is nothing in either case. Standing on its
|
||||
(`stages.stage_on`) is nothing in either case. Standing on its
|
||||
own, as the button, a missing model fails the batch with a notice."""
|
||||
stage = summarise.summarise_task()
|
||||
if not cascade:
|
||||
|
||||
Reference in new issue
Block a user