Per-agent ranking: votes, affinity and a taste term; settings are three sub-tabs

Votes on roles and company affinity move to role_votes and agent_companies,
one row per search agent, so two agents rank the same roles differently. The
score gains taste, the cosine to mean(liked) - mean(passed) of the agent's
votes, as newsdesk ranks articles. The API takes agent on roles, votes and
companies and falls back to the default agent, the enabled one with the
lowest id.

Settings become Search agents (a list again, with New and Delete), Sources
(job boards, company boards and runs with the message log, one section per
plugin) and Account. Old paths answer 301 to their section.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-28 12:53:41 +02:00
1 parent 515d2250fc
commit a0772519b3
28 files changed
+1461 -668

No files matched your search

+8 -9
View File
@@ -15,9 +15,9 @@ uv run app serve # http://127.0.0.1:8790
`uv run app worker` drains the queue without the web app, and `uv run pytest` runs the app's tests and the copied modules' own. `config.yaml` is the committed default, with one starter agent and four Copenhagen searches on Jobindex; `config.example.yaml` documents every key, including the `summarise:` block below.
## Searches and companies
## Sources: job boards and company boards
The Searches and Companies sub-tabs do all of this; the same actions exist on the command line:
The Sources sub-tab does all of this; the same actions exist on the command line:
```bash
uv run app searches add jobindex "Copenhagen golang" --q "golang go-udvikler" --area 1
@@ -34,20 +34,19 @@ Two tabs, and a cog for settings.
| | |
|---|---|
| **Roles** | open roles, newest or by Best match, with filters, votes (▲ like ● neither way ▼ pass) and a Save button. A title opens the role's own read page |
| **Roles** | open roles, newest or by Best match for one search agent, with filters, votes (▲ like ● neither way ▼ pass) and a Save button. A title opens the role's own read page |
| **Applications** | the saved roles and their status, each change recorded as an event |
The cog opens `/settings`, one shell with six sub-tabs:
The cog opens `/settings`, one shell with three sub-tabs:
| | |
|---|---|
| **Ranking** | the one search agent the UI edits: intent, weights, and require/prefer gates behind an Advanced disclosure. Saving rescores it |
| **Searches** | saved searches that find roles across companies (try, save, edit, remove) |
| **Companies** | every company whose board is read, its open roles, and its affinity: hidden, neutral, liked, favourite; following a company and pruning boards by region live here too |
| **Pulls** | a Pull now button and what is running, the pull schedule, and the extract/embed/score buttons behind a disclosure |
| **Messages** | everything the server said that nobody has cleared |
| **Search agents** | the list of agents the Roles tab ranks by, and the form for one: name, intent, weights, and require/prefer gates behind an Advanced disclosure. Saving rescores; deleting one takes its votes, liked companies and scores with it |
| **Sources** | one page, one section per plugin: job boards (queries on Jobindex or Adzuna: try, save, edit, remove), company boards (every company whose board is read, its open roles and its affinity for the picked agent, following a company, pruning boards by region) and runs (Pull now, what is running, the schedule, one stage at a time, and the message log) |
| **Account** | the password, sessions and passkeys. Open on loopback, locked on anything else |
Likes, hidden companies and votes belong to a search agent, not to the account: two agents rank the same roles differently, and one may hide a company the other favours. An agent also learns from votes: its `taste` weight scores a role by how close it is to the roles the agent liked minus the ones it passed.
A role's read page, `/roles/{uid}`, shows the full posting: the same vote and Save controls, the company's own affinity, and the summary when there is one. A search role's posting is a teaser; its page offers a Fetch button that scrapes the original listing once and stores the text. A Summarise button asks for a short summary of that one role; `config.yaml`'s `summarise:` block turns summarising on for the pull itself, bounded to the top `per_agent` roles of each agent so the cost stays flat.
## Docs