List fetch text, judge before summarise, seniority and the job kinds in the module docstrings and drop the order name and deleted plan from three comments

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-10-05 09:32:43 +02:00
1 parent c3bc2cd7f3
commit 9b120a3b94
5 files changed
+28 -21

No files matched your search

+2 -1
View File
@@ -1,12 +1,13 @@
"""The command line.
app serve [--host H] [--port P] [--reload]
app job pull|extract|embed|score [--payload JSON]
app job pull|fetch_text|prep|embed|score|extract|judge|summarise [--payload JSON]
app worker [--workers http=8,cpu=1] [--until-idle]
app companies seed|add|edit|checked|remove|by-hand|set-board|detach|discover|check|size
app searches add|list|remove
app agents list|prompt
app stages [extract|summarise|judge|fetch_text on|off]
app seniority
app dupes
app prep [unmapped|unlinked] [--remap]
app db init
+22 -16
View File
@@ -1,22 +1,28 @@
"""The work roledesk queues. Importing this package registers every job, every
task in `pipeline.TASKS` and the default schedule in `pipeline.SCHEDULES`.
pull.py read every board and search and store the roles they yield
prep.py the `prep` stage: `app.prep` over what a pull stored, then the fold
extract.py title and description into the gate columns, on Haiku
embed.py one vector per open role, for fit
score.py every open role scored for every enabled search agent
summarise.py about 60 words on each of the best roles, on Haiku
judge.py each agent's best roles against its CV: skills, experience, career
cascade.py pull → prep → embed → score → ... → summarise → judge, what `TASKS`
offers, the `pull` job a schedule fires, and that schedule
stages.py whether extract, summarise and judge run: the switch, else config.yaml
sources.py what a pull reads, changed by hand: boards and searches
added, switched on or off
discover.py which ATS a company's careers site runs on, from its pages
posting.py one role's posting page fetched as text, on demand
reach.py which countries a pull asks each big board for, from the agents
limits.py what limits a board's read, in words, for the Companies list
pull.py read every board and search and store the roles they yield
prep.py the `prep` stage: `app.prep` over what a pull stored, then the fold
embed.py one vector per open role, for prompt closeness and CV closeness
score.py every open role scored for every enabled search agent, and each
agent's cut
fetch_text.py the roles in the cut that came without text, read on their own
pages, with no model
extract.py title and description into the gate columns, on Haiku
judge.py each agent's cut against its CV: skills, experience, career
summarise.py about 60 words on the top of both orders and the roles liked or
saved, on Haiku
cascade.py pull → prep → embed → score → fetch_text → prep → embed → score
→ extract → score → judge → summarise, what `TASKS` offers, the
`pull` and `fetch_text` jobs that start it, and the default schedule
stages.py whether extract, summarise, judge and fetch text run: the switch,
else config.yaml
sources.py what a pull reads, changed by hand: boards and searches
added, switched on or off
discover.py which ATS a company's careers site runs on, from its pages
posting.py one role's posting page fetched as text, on demand
reach.py which countries a pull asks each big board for, from the agents
limits.py what limits a board's read, in words, for the Companies list
"""
from __future__ import annotations
+2 -2
View File
@@ -1,5 +1,5 @@
/* The Search agents page: what Agent match on the Roles tab is measured
* against, one agent at a time.
/* The Search agents page: what the order What I'm looking for on the Roles
* tab is measured against, one agent at a time.
*
* Every agent from `/api/agents` is a card, newest first: its name, its
* switch, its prompts, its gates in words, its weights, and a link to the
+1 -1
View File
@@ -268,7 +268,7 @@ def test_cv_match_orders_the_unjudged_by_closeness_then_score(store: Store) -> N
assert [r.uid for r in store.roles(agent=owner.id, by_cv=True)] == [
judged, close, far, none_b, none_a]
assert [r.uid for r in store.roles_page(agent=owner.id)] == [
far, none_b, none_a, close, judged], "Agent match ignores it"
far, none_b, none_a, close, judged], "What I'm looking for ignores it"
found = store.role(close, owner.id)
assert found is not None and found.cv_fit == 0.9
+1 -1
View File
@@ -1,6 +1,6 @@
"""Where a remote role may be worked from: the `remote:` tokens, a remote
role's area in prep, the chips and gates that read it, the model's answer and
migration 27. The place texts are the live boards' (docs/plan-remote.md)."""
migration 27. The place texts are the live boards'."""
from __future__ import annotations