5.3 KiB
Open
What is known and not yet fixed, checked against the code on 2026-10-06, after the architecture review of 2026-10-05. What was decided is in decisions.md, the target design in documentation/, the unbuilt readers in plan-hosts-wave-2.md. Counts are of the live database on that day.
For the owner to decide
- Remote on hosts that take one country a request. SmartRecruiters, SuccessFactors and Eightfold (14 boards, about 15,000 roles) are still asked for DK, SE alone when the agents want remote, since Europe there is the whole board. Reading them whole is the only way to their remote roles elsewhere.
- Remote listings across countries. A job posted remote once per country is now one role per country (the fold keeps to one country), which lists a pan-European remote posting several times.
- A search cut at its page cap leaves no record. In the last pull 4 of 26 searches stopped at a cap (Jobbank and freehire at 1,000 rows, two Jobindex searches at 200). Nothing on a page says so, and Jobbank's feed is not sorted by date, so new ads can lie past the cap.
What the ADRs still do not say
ADR Fetch prep and score was brought up to the code on 2026-10-06; left for the owner's read as a whole.
ADR Plugins was rewritten on 2026-10-06 and names a target the code has not reached: a broken plugin left out instead of stopping the app; providers declaring their params with label, kind and choices, so form, CLI and API follow from the module; detail state kept for a search's roles as for a board's; a national provider declaring its implied country; page markers for hosts on a company's own domain; a contract test that names no reader.
Structure
From the review of the plugin layer and the inbound flow.
- Per-target state is string keys written and read in six files (
_runner.stamp,ats.py,pull.py,limits.py,reach.py,api.py). One typed accessor in the runner would own them. - Detail handling is spread over five places (
ats._board,_runner.read_details,ats.read_board_details,fetch_text.plan, and none of it insearch.py), which is why a search role's detail places are not kept across pulls. plugins/ats.pyholds three things: the source, compatibility names only tests use (_PARSERS,_parse_dt,_greenhouse_salary,_parse_teamtailor,_Refused,DETAIL_FIELDS), and the app's function classifier (FUNCTIONS,classify), which search roles never pass through.pluginsis not in the layering test's trees, soappimports the private_runnerin four files and single readers in two, andmodels.py,config.pyanddupes.pyreach the registry through a path hack.- The two sources build an item each their own way (
ats.py,search.py) and already differ. - The contract test names readers (
POSTED_BY_DETAIL,SEARCH_PARAMS), so a new reader that dates by detail edits the shared test. has_keyre-implementsresolve_key, andsearch_paramsraisesKeyErrorfor a provider param other than q, area, country, where, region or remote.pipeline/only logs when a cascade's next stage fails to start (queue.py); the fix lands in the boilerplate first.pipeline/,auth/,deploy/anddesk/lag their upstreams.
Text
- A hand-fetched posting is not embedded or extracted. "Fetch the posting" stores
article_text, which only summarise and the judge read. - An edited posting is not embedded again unless its text ranks better than before (title, teaser, description). A hash of the embedded text would catch any change.
- Lever keeps only the intro paragraph (
lists[]andadditionalare dropped), and Recruitee dropsrequirements. - Pay stated only in the text is not in the fields unless extract has read the role.
- A role ranked on its title alone has no mark in the feed.
Sources
- A mistyped SmartRecruiters, Gem or Ashby slug attaches as an empty board, and nine boards have never listed a role.
set_boardkeeps a board that lists nothing. - Six hosts' dates are not trusted (Eightfold, Jibe, Gem, Deel, HiBob, HR Manager declare
posted="listed"); each needs one check on a live board. Greenhouse declarestrustedand falls back toupdated_at. - The hosts added on 2026-09-29 were read from this machine only; read one Workday and one SuccessFactors board from the deployed server.
- robots.txt decisions wait for the owner: SmartRecruiters' API host disallows
/for every agent but LinkedInBot and is read meanwhile; HR Manager is attached although its record says "owner to decide". Whether SmartRecruiters' identifier is case-sensitive is unsettled. Crawl-delayis not honoured.- A SuccessFactors site on a company's own domain is not discovered.
- freehire states seniority and employment and the reader declares neither. Stripe's places carry a "Locations" suffix.
- The 10% guard compares only reads with the same filter, so the first read after an agent's locations change is unguarded.
The pages
- ★ means two things on Roles: on a row it saves the role, in the company strip it marks a favourite.
- All locations and All roles answer without a score job id, so the company view is stale until the rescore has run and the page is reloaded.
- Place suggestions split every place line on each request.
company_keykeepsø; aliases make "Orsted" and "Ørsted" one company.