Summarise every saved or liked role whatever its rank, queue it at once on save or like, and shorten the order labels to Agent match, CV match and Newest so they fit one line
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
1d0a4c37f2
commit
ee8e450640
20 files changed
+208
-60
No files matched your search
+1
-1
@@ -6,7 +6,7 @@ written profile and scores skills, experience and career 0 to 100, with one
|
||||
to three strengths and gaps. The total is `app.models.cv_score`, the three
|
||||
numbers under the agent's `cv_*` weights, worked out when a role is served and
|
||||
not stored, so the weights are no part of `input_key`; it is what the feed's
|
||||
Best CV match sorts by. The model also reports a verdict on each of the
|
||||
CV match sorts by. The model also reports a verdict on each of the
|
||||
agent's must-haves (one per line of its must text, numbered M1..Mn in the
|
||||
prompt); it does not apply them. The rule is code's: a "broken" one makes
|
||||
career count as at most `app.models.BROKEN_CAP`, when the role is served. Culture and location are left out: the first
|
||||
|
||||
+12
-6
@@ -5,12 +5,18 @@ this module is the content (which roles are waiting, what one batch carries,
|
||||
what the model is told, the schema it answers in, what to do with the
|
||||
answer), and running it is `desk.modeltask`'s.
|
||||
|
||||
A role is waiting while it has no summary, has some text, and is in the top
|
||||
of an enabled agent's ungated scores as deep and as low as that agent's own
|
||||
`limits` say (`summarise_top`, `summarise_min`). That bound is what keeps the
|
||||
cost flat: a pull summarises the roles somebody will look at, not the 30k
|
||||
that are open. A batch built for named uids (the read page's Summarise
|
||||
button) takes those roles whatever their rank. See `Store.summarise_waiting`.
|
||||
A role is waiting while it has no summary, has some text, is open and no copy,
|
||||
and is either in the top of an enabled agent's ungated scores as deep and as
|
||||
low as that agent's own `limits` say (`summarise_top`, `summarise_min`), or
|
||||
one the owner cares about whatever its rank: saved (it has an application, the
|
||||
star) or voted up by an enabled agent. The limits keep the cost flat: a pull
|
||||
summarises the roles somebody will look at, not the 30k that are open, and the
|
||||
saved and liked roles are a handful the owner picked. Each is summarised
|
||||
once, with the same give-up rule (`GIVE_UP_AFTER` replies that left it
|
||||
without). Saving or liking a role queues a batch for that one uid at once,
|
||||
while the stage is on (`web.api`), rather than waiting for the next pull. A
|
||||
batch built for named uids (the read page's Summarise button) takes those
|
||||
roles whatever their rank. See `Store.summarise_waiting`.
|
||||
|
||||
The text is `article_text` when the posting page was fetched, else
|
||||
`description`. A role with neither is not waiting at all, so it is never sent.
|
||||
|
||||
Reference in new issue
Block a user