End the enrich cascade behind an agent's save with judge, so a changed CV or like text is judged again at once

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-03 22:59:51 +02:00
1 parent 8da0f4512a
commit 1d0a4c37f2
2 files changed
+7 -4

No files matched your search

+5 -2
View File
@@ -23,7 +23,10 @@ roles of each enabled agent, as deep and as low as that agent's own `limits`
say; the second score then applies the gates to the columns it filled.
Summarise follows, on the best roles by the same agent's summarise limits,
and judge runs last, reading each agent's best roles against its CV by its
judge limits.
judge limits. The `enrich` cascade, which follows the rescore after an agent
is saved, ends with judge too, so a changed CV, prompt or like text is read
again at once rather than at the next pull; a pair whose `input_key` did not
change costs nothing.
A batch that failed, or a stage somebody killed, does not stop the chain: the
work comes round on the next pull, and a rescore of what did arrive is worth
@@ -55,7 +58,7 @@ STEP = "app.jobs.cascade:step"
CASCADES: dict[str, tuple[str, ...]] = {
"pull": ("pull", "prep", "embed", "score", "enrich", "prep", "embed", "score", "extract",
"score", "summarise", "judge"),
"enrich": ("enrich", "prep", "embed", "score"),
"enrich": ("enrich", "prep", "embed", "score", "judge"),
}
#: What follows `enrich` for the roles it filled, passed over when it filled none.