Fold the remote area plan into the decisions and delete it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9e2631ffe3
commit
bf6ef72b15
2 files changed
+8
-96
No files matched your search
@@ -118,6 +118,14 @@ What was decided for roledesk and the one reason for each. The longer reasoning
|
||||
|
||||
**A role has a list of places, resolved against a gazetteer.** Readers kept one place of several, joined them, or the host posted a copy per place. A reader now returns every place and never multiplies a row. `places` (city, region, country, continent, with `place_includes` for Øresund across two countries) and `place_aliases` are seeded from the dictionaries that were in code; `role_places` links each place of a role, and an unknown text is listed by `unresolved_places` until an alias links it. The Place filter and the gates join over the tree, which halved their time and dropped the `EU` fallback. Copies of one posting per place, same host, company and title and texts at least 30% alike, fold into one role that keeps each copy's place and link; the rule applies to every host, since the 5,024 such roles came mostly from hosts that do not declare copies.
|
||||
|
||||
**A remote role has a remote area: the places a remote hire may live in** (migration 27, `role_remote`, `app/prep/area.py`). On 2026-09-30 the Place field listed "USA (Remote)", "Remote US" and "United States (Remote)" as three towns, and no filter said which of 3,177 remote roles someone in Denmark could take. Those lines came from a few whole-read Greenhouse and Ashby boards (Grafana Labs, Cloudflare, Monzo, Talkdesk), not from an ingest filter. Danish employers barely post remote roles (11 of 1,395 open Danish roles). The remote roles open to Denmark are the roughly 300 scoped to Europe or EMEA and the 210 scoped to anywhere. The area is the first of these that names a place: the model's `remote_where`, the parts of the place texts that say remote ("Germany (Remote)", "Home Based - EMEA"; "Worldwide" or "Global" in such a part is Anywhere), and the role's resolved places lifted to their countries. "Remote" alone names none, so such a role is remote with no stated area. Anywhere is a standalone place with no aliases and nothing under it, so the Place filter and `under` never reach every role through it, and it never counts as a place for a country gate's empty check. Remote lines are no longer suggested as towns.
|
||||
|
||||
**A remote chip matches by overlap, and Anywhere is in every one.** `remote:country:DK` ("Remote · Denmark") finds a remote role whose area is Denmark or in it, a place Denmark lies in (Europe, Øresund), or Anywhere: the roles a person living in Denmark can take. `remote:country:EU` finds every European remote role, "Germany (Remote)" included. The owner wanted Remote · Denmark to hold the Europe-wide and worldwide roles rather than have a separate "Remote · anywhere" chip, so `remote:anywhere` is a valid token that is never suggested. A remote role with no stated area matches no `remote:<place>` chip. On the live data of 2026-09-30, Remote · Denmark found 499 roles, Sweden 531, Germany 760 and Europe 1,395, and 122 remote roles had no stated area.
|
||||
|
||||
**An agent's scope is the first line of the Where block, and plain Remote is every remote role within it.** "Only roles in: Europe / these countries / everywhere" reads and writes the agent's `require` gate on country, which was the implicit scope before, and which a company set to All countries is already read within. The token `remote:any` ("Remote", suggested first for "remote") and the agent's `remote: [remote]` any gate both mean every remote role in that scope: a `require` gate on country reads a remote role that has an area through the area alone, so "Home Based - Worldwide", "Germany (Remote)" and "Remote - Europe" meet Europe, and "Remote US" does not. `any` and `prefer` gates on country keep the place reading. The Where block's Remote line is a choice of no, anywhere within the scope (the plain gate, so the live agent loads and saves unchanged), or only when open to someone in a list of countries and regions (`remote_from`, which matches as the chips do). The remote suggestions are kept to the asking agent's scope, so an agent kept to Europe is not offered Remote · United States. This supersedes the "remote within Europe or anywhere" select of the Where block below.
|
||||
|
||||
**For remote, the model wins, as it does for seniority.** `remote` is `remote_model`, else the host's word, else the place line (prep `VERSION` 3). Black Forest Labs' Freiburg roles are `OnSite` on Ashby while the text offers remote work with an office week a month, and "the board wins" kept them onsite. 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. Extract also answers `remote_where`, the names of where a remote hire may live, and a role waits while `remote_where_model` is NULL, so the roles read before are read once more within the agents' existing limits. Migration 27 moved a board role's stored `remote` into `remote_host` where that was empty, since composing `remote` outright would have wiped 1,280 values that an older reader had mapped. "Remote sensing", "remote control" and "remote monitoring" in a title are not remote.
|
||||
|
||||
**A company has aliases.** `company_aliases` maps a folded name (marks stripped, ø to o, legal form dropped) to a company, so "Orsted" and "Ørsted" are one company without changing `company_key`. `merge_companies` moves roles, subscriptions and ratings. Empty enrichment columns (sector, stage, size band, founded, last funding, source and date) wait for the startupmap.one and The Hub readers.
|
||||
|
||||
**A list teaser is kept.** A short description in a listing (Phenom, Oracle, Jobylon, Jobindex, Adzuna) is `roles.teaser`, shown and embedded until the full text arrives, when the vector is dropped and the text replaces it.
|
||||
|
||||
Reference in new issue
Block a user