Extract and summarise bounds are each agent's own limits, set on its form

agents.limits holds extract_top, extract_min, summarise_top and
summarise_min; the scope query reads them per ranked row, and a row saved
before this behaves like a fresh agent. The four global config keys go.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-28 16:02:06 +02:00
1 parent e602eb3388
commit cebe62ddc9
20 files changed
+229 -147

No files matched your search

+15 -13
View File
@@ -49,28 +49,21 @@ agent:
# Title and description in, gate columns out (app/jobs/extract.py). Off by
# default: on the API backend every batch of 20 roles is a paid call. On, a
# pull reads only the best per_agent roles of every enabled agent (the
# backstop) that score at least min_score (the real stop), after a first
# score; a second score then applies the gates to what was filled. A fresh
# role with the worst fit scores about 0.27 on the default weights, a good
# one 0.6 or more, so 0.3 is loose.
# pull reads only the best roles of every enabled agent, as deep and as low
# as that agent's own limits say (see agents below), after a first score; a
# second score then applies the gates to what was filled.
extract:
enabled: false
model: claude-haiku-4-5-20251001
per_agent: 500
min_score: 0.3
# About 60 words on a role: what it is, the stack, where, the pay if stated
# (app/jobs/summarise.py). Off by default. On, each pull summarises the best
# per_agent roles of every enabled agent that have none yet and score at least
# min_score, so the cost stays bounded however many roles are open; stricter
# than extract's floor, since a summary is the long answer. The Summarise
# button on a role's page asks for that one role either way.
# roles of every enabled agent that have none yet, by that agent's limits, so
# the cost stays bounded however many roles are open. The Summarise button on
# a role's page asks for that one role either way.
summarise:
enabled: false
model: claude-haiku-4-5-20251001
per_agent: 30
min_score: 0.5
# A role and each agent's intent as vectors, for the fit term of a score
# (app/jobs/embed.py). Needs the `embeddings` extra; without it `embed` posts
@@ -94,6 +87,14 @@ sources: {}
# 0.2}; taste is how close a role is to the ones the agent liked minus the
# ones it passed. A country is an ISO code, filled from the board's location
# line; EU is a role open anywhere in Europe.
# limits is how deep into this agent's ranking the two model stages read,
# each a top N (the backstop) and a minimum score (the real stop): extract
# reads the best extract_top roles at extract_min or more, summarise the best
# summarise_top at summarise_min or more. A fresh role with the worst fit
# scores about 0.27 on the default weights and a good one 0.6 or more. The
# defaults are {extract_top: 500, extract_min: 0.3, summarise_top: 30,
# summarise_min: 0.5}; a wide monitoring search raises them, a narrow hunt
# lowers them.
# The Search agents sub-tab lists and edits them; the order menu on Roles
# picks one by name. Two more, beside the starter in config.yaml:
agents: []
@@ -107,6 +108,7 @@ agents: []
# - {field: country, values: [AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT,
# LV, LT, LU, MT, NL, PL, PT, RO, SK, SI, ES, SE, IS, LI, NO,
# GB, CH, EU], mode: require}
# limits: {extract_top: 1000, extract_min: 0.3, summarise_top: 50, summarise_min: 0.5}
# - name: Europe hybrid
# intent: >-
# Senior backend or platform engineer in a European tech hub, hybrid or