Merge main (the R3 bug fixes) into wp-review-docs

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-30 15:46:52 +02:00
commit dd0eee9ebb
9 files changed
+119 -22

No files matched your search

+2
View File
@@ -164,6 +164,8 @@ What was decided for roledesk and the one reason for each. The longer reasoning
**Gates match loosely where the column is free text.** `place` takes the Place filter's tokens on whole folded words, so `Berlin` matches "Berlin, Germany" and `Lund` no longer matches "Billund"; `company` compares company keys, `languages` passes when every required language is a value, `salary_min` is at least the smallest value, and the rest are case-insensitive equality. Each gate is one SQL `CASE` column, so a require gate filters while the gated row keeps every failed gate as its reason.
**`exclude` gates titles out by phrase, not by `function`.** Sales titles (Account Executive, Account Director, Client Partner) and individual data engineering ranked high for the owner's agent, since their postings read like the sales engineering and data leadership the prompts describe. `function = sales` could not remove them: the keyword classifier files "Solutions Engineer" and "pre-sales" under sales, so on the data of 2026-09-30 it would also have gated Field CTO, Director Field Engineering, Staff Solutions Engineer and every AI Deployment Strategist in the agent's top 400. The fourth mode, `exclude`, gates a role that matches any of its values, and the gate's `CASE` column returns the position of the first value that matched so the reason names it ("title account executive"). It applies to favourites, which skip only the `any` group. The new `title` field matches a value as whole words of `title_key`, `LIKE '% phrase %'` over the padded key, so `data engineer` gates "Senior MLOps/Data Engineer" and not "Data Engineering Manager", and Forward Deployed Engineer is untouched. The form has a Leave out titles line under Where. Bare `sales` and `vice president` stay off the owner's list, because they would take Sales Engineer and VP roles, and `account manager` stays off because it would take Technical Account Manager. Measured on the agent's 5,089 ranked roles, the list the owner took gated 283, 13 of them in the top 100.
**A role with no vector is scored without `fit`.** The fit weight leaves the denominator, so a role `embed` has not reached yet ranks on recency, affinity and prefer gates instead of sinking to the bottom. It is gated as "no vector" only when fit is the only weighted term, and as "no intent vector" when the intent could not be embedded.
**Each run replaces an agent's scores.** `replace_scores` deletes and inserts in one transaction, so a role closed or muted since the last run drops out rather than keeping a stale score, and a reader sees one list or the other.
+3 -1
View File
@@ -42,7 +42,9 @@ Open roles without copies: 20,578. `remote` is `remote` on 3,177, `hybrid` on 3,
4. **A role whose area is not stated matches no remote chip in the feed.** In an agent's gate it is empty, which by the gate rule neither passes nor fails, so it ranks, `extract` reads it and the rescore gates it.
5. **For remote, the model wins, as it does for seniority.** `remote_model` is new, and `remote` is the model's value, else the host's word, else the place line. The prompt says remote when the hire works from home most of the time, even with a regular office week, and hybrid when there are set office days each week. Black Forest Labs then reads as remote.
6. **Extract reads the area once more for the roles it has read.** A role waits while `remote_where_model` is NULL (never asked). `[]` means asked and not stated. The existing per-agent bounds apply, so no new cost bound is needed.
7. **Agents get a gate field `remote_from`, whose values are place tokens.** It matches as the chip does. The live agent's `remote: [remote]` gate keeps working until the owner edits it, since the Where block then writes `remote_from`.
7. **An agent's scope is explicit** (owner, 2026-09-30). The `require` gate on `country`, Europe for the owner's agent, is the first line of the Where block: "Only roles in: Europe / these countries / everywhere". A company set to All countries is read within it, as `reach` already does. A remote role is in scope when its area overlaps the scope or is Anywhere, so the scope gate reads a remote role through its area, and "Home Based - Worldwide" stays in Europe's scope.
8. **Plain Remote is every remote role within the scope.** The token `remote:any` (label "Remote") and the agent's existing `remote: [remote]` any gate both mean it. "Remote · Denmark" narrows it to the roles open to someone living in Denmark, which includes Europe-wide and Anywhere roles. There is no "Remote · anywhere" suggestion. Anywhere is part of every remote chip, and the badge still says "remote · anywhere".
9. **Agents get a gate field `remote_from`, whose values are place tokens.** It matches as the chip does and is the Where block's "only when open to someone in" line. The `remote: [remote]` gate stays the plain "remote within the scope" line, so the live agent loads and saves unchanged.
## Contract between the packages