Settle that extract and judge stay two calls

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-04 08:54:43 +02:00
1 parent 16e0323198
commit ccf6b3fd1c
1 file changed
+1 -1
+1 -1
View File
@@ -87,7 +87,7 @@ The form wording for the sizes becomes "at most N, each scoring at least X", in
**Cost.** Every model read happens once per role (judge once per role and CV), so a larger cut costs mostly a one-off catch-up. With a cut of about 650 roles, that catch-up is about 16 minutes of extract and about an hour of judge on the live backend (`claude_code`, the subscription, so no per-token bill). After it, each pull reads only the roles new to the cut.
**Open.** Whether extract and judge become one call. Arguments for keeping two: extract is per role and needs no CV, while judge is per agent and role with the CV in the system prompt; and extract's location and remote answers feed the gates before judge reads anything. The argument for one call is that the posting is read once instead of twice.
**Decided: extract and judge stay two calls.** Extract needs no CV and its location and remote answers feed the rescore before judge reads anything. Judge works per agent and role, with the CV in the system prompt.
## 5 Feed