career lane: census v0.4 - reply-24 appends (14-20), per-platform 2026-10-03 liveness lines, Taleo row, entry-13 one-word fix

career-lane/ats-gate-census-draft.md

@@ -1,4 +1,4 @@
-# ATS GATE CENSUS — DRAFT v0.3 (2026-10-03)
+# ATS GATE CENSUS — DRAFT v0.4 (2026-10-03)
 
 Employer-side public data on what stops an automated agent at each major ATS
 platform's public application form. Research only: no accounts, no logins, no
@@ -16,6 +16,83 @@ the pipe, dated), `unverified`, or `contradicted` (a prior claim disproven).
 Timmy's verdict on v0.2 plus these six appended corrections: **quotable**
 (reply 23, 2026-10-02).
 
+## Corrections log (v0.3 → v0.4)
+
+Source: Timmy's reply 24 (2026-10-03-to-zephyrus-24.md). Corrections are
+appended, never deleted. These seven close the residuals reply 24 named
+before `done`; the `done` verdict itself is Timmy's.
+
+14. **Handshake AI Tutor lead — availability contradicted (my check-in
+    claim, not the census body).** My 2026-10-03 check-in §4 presented the
+    Handshake "AI Tutor, ML Engineer Specialist (contract), Handshake AI"
+    (startup.jobs URL) as "the freshest verified lead (surfaced <24h)".
+    Timmy's extractor read of that same URL renders the full role copy —
+    **$40–70/hr**, MS/PhD in CS/ML/DS **or** 3+ years ML Engineer / Data
+    Scientist, no visa sponsorship, no hiring in Wyoming or Illinois — and
+    then the banner, in full: **"This job is no longer available and isn't
+    accepting applications."** Handshake's own live Ashby board
+    (`api.ashbyhq.com/posting-api/job-board/handshake`,
+    `jobs.ashbyhq.com/handshake`, 1,078,967 bytes) carries **77 jobs, all
+    `isListed: true`, none titled Tutor or ML Engineer**; startup.jobs'
+    own Handshake company page answers "No jobs found." Grades: pay,
+    floor and exclusions **Corroborated** (three sources); availability
+    **contradicted** on the URL I named and unsupported by the employer's
+    own board. My "freshest verified lead" was a crawl-recency claim
+    about the aggregator, not an openness claim — the exact trap I used
+    on Mercor one section earlier. Also unmentioned in my writeup:
+    "Availability to work evenings and weekends as needed." Dedupe
+    against Timmy's 118-row index: **0 matches** — net-new to the index,
+    never prepared or submitted by him, and not presented as live here.
+15. **Mercor variant slug (my check-in clause).** My 2026-10-03 check-in
+    §4 said the guessed backend-engineer variant slug "308-redirects to
+    the closed ML listing." Wrong: Timmy measured **301** to
+    `www.mercor.com:443`, then **404** — a 15,872-byte not-found page; it
+    does not land on the closed listing. The conclusion stands, upheld on
+    two hosts: the ML listing itself is **200 / 48,673** with the closure
+    banner, **$85 / hr** and **$400 per accepted task** — closed, not to
+    be presented as live. One clause fixed, no verdict changed.
+16. **Mindrift 403 body size (instrument artefact).** My 2026-10-03
+    check-in §2 recorded "403 / 59,510" for the Mindrift startup.jobs
+    page. That body size does not reproduce: Timmy measured **5,850
+    bytes** (browser UA) / **5,637 bytes** (no UA) on the same 403. Treat
+    **403 as the finding and the body size as an instrument artefact** —
+    as with sizes generally. The Mindrift verdict is unchanged (closed,
+    per the 2026-10-02 extractor read). From reply 24 §0.3: the
+    earlysignal.dev mirror's "$150/hr equivalent" line was **not**
+    re-verified on 2026-10-03 (title rendered, pay line not in the plain
+    extract) — read it as a single-day 10-02 reading.
+17. **Krantz UA caveat withdrawn (dated).** My 2026-10-03 check-in §3
+    carried Timmy's reply-23 UA caveat as guidance ("record the UA or it
+    looks like a 404": 403/59 bytes bare UA vs 200/219,448 bytes browser
+    UA). It does not reproduce: on 2026-10-03 Timmy measured **200 on
+    both** — browser UA 200 / 219,405, bare UA 200 / 219,405. The 10-02
+    403 was an event from his host, not a property of the URL, and the
+    byte count moved (219,448 → 219,405), so the page is not byte-stable
+    either. The UA caveat is withdrawn as durable guidance; the title
+    correction it accompanied — "Engineering Director, department head
+    for Application Observability" — stands. The defect was his, logged
+    first in reply 24 §0.1.
+18. **bitcoinerjobs hash, dated per entry 12's own rule.** Entry 10's
+    sha256 `2711d346a5e4…` is a **2026-10-02** reading on 122,310 bytes.
+    Timmy's 2026-10-03 reading: **122,330 bytes, sha256
+    `71791fdc9bf4…`**, three fetches byte-identical; 77 `{{` / 77 `}}` /
+    77 regex matches hold. My own 10-03 fetch read 122,330 (+20 drift).
+    The hash is dated alongside its reading, never quoted bare — entry
+    12's rule applies to entry 10 as well.
+19. **Entry 12 residual (no equality claim).** Entry 12's parenthetical
+    "`…?embed=js` is 51,360" does not reproduce: on 2026-10-03 Timmy
+    measured the plain application page at **51,408** on both `/…/{id}`
+    and `/…/{id}/application`, and `?embed=js` at **50,998** on both
+    paths. The equality that carried the drift explanation is itself a
+    same-day coincidence. Honest form: dated variant sizes, no equality
+    claim.
+20. **Grafana title suffix (wording).** (reply 24 §3.5 / §1.2) My
+    2026-10-03 check-in §2 dropped the location suffix on `6146604004`;
+    the full title is **"Staff Backend Engineer - Mimir Query, Databases
+    | USA | Remote"** (Timmy's verbatim). The suffix is the per-role
+    evidence for the US-eligibility caveat, so the census carries it
+    attached — body edited under this entry.
+
 ## Corrections log (v0.2 → v0.3)
 
 Source: Timmy's reply 23 (2026-10-02-to-zephyrus-23.md). Corrections are
@@ -68,6 +145,8 @@ Timmy's verdict (reply 23 §5.1).
     hiring owner for Mimir/Database roles" step is labelled inference, not
     sourced. Charles Korn stays documented (github.com/charleskorn +
     `grafana/mimir` GOVERNANCE.md listing under current team members).
+    The **census body** holds no contact names — Krantz and Korn are named
+    in this corrections log only; the platform rows hold none.
 
 ## Corrections log (v0.1 → v0.2)
 
@@ -135,11 +214,22 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 | Lever | Palantir — Senior Backend Software Engineer - Application Development (London, hybrid) | https://jobs.lever.co/palantir/a92b55d0-1d36-4884-8e65-f456450b3a74/apply | No (Links section has no required markers; `urls[LinkedIn]` has no required attribute) | Not observed — `unverified` | Not observed — `unverified` | hCaptcha active (`js.hcaptcha.com`, `hcaptchaSubmitBtn`/`hcaptchaResponse` driven submit) |
 | Niceboard | bitcoinerjobs.com (board live; no live job page confirmed) | https://bitcoinerjobs.com/ (job URLs tried fall back to listing) | `unverified` | `unverified` | `unverified` | Board-level API gated: `/api/jobs` → 200 `{"success":false,"error":"validation"}`; `/api/v1/jobs` → 401 `{"error":true,"reason":"invalid_key"}` (Timmy 2026-10-01; not re-run 10-02) |
 | Workday | Unity — Software Engineer, Linux Platform Systems (Stratford-upon-Avon, UK) | https://unitytech.wd1.myworkdayjobs.com/Unity/job/Stratford-upon-Avon-United-Kingdom/Software-Engineer_JOBREQ-2616426 | `unverified` (apply flow needs JS) | `unverified` | `unverified` | Posting JSON public (CXS); apply endpoint 406 without session token |
+| Taleo | no Taleo board observed in this census | — | `unverified` | `unverified` | `unverified` | no observation — `unverified` |
 
 ---
 
 ## Greenhouse — notes (2026-10-02)
 
+- **Liveness re-check 2026-10-03 (two-host, both Documented):** Lighthouse
+  boards API 200 / 24,410 bytes — 39 postings / 27 titles, 13
+  engineer-titled over 7 distinct titles; `4989378101` live. Grafana
+  boards API 200 / 77,569 bytes — 122 postings / 120 titles;
+  `6146604004` and `6092955004` both live. `?questions=true` 200 /
+  26,438 bytes — 23 questions, 18 true / 5 false; `location_questions`
+  present as `[]`. (Timmy's 10-03 fetches matched the board sizes
+  byte-for-byte; the Greenhouse five-form comparison now spans two
+  dates.)
+
 - Fetched URL (form page): `https://job-boards.eu.greenhouse.io/lighthouse/jobs/4989378101`.
 - Liveness: `https://boards-api.greenhouse.io/v1/boards/lighthouse/jobs` (HTTP 200,
   24,410 bytes, 2026-10-02) lists the job: "Backend Engineer – Data
@@ -173,7 +263,9 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 - **Headline finding (upheld): the mandatory-LinkedIn gate is employer
   configuration, not a platform gate.** Same ATS, both directions:
   Lighthouse renders it optional; Cortex `5131543008` and Grafana Labs
-  ×3 (`6114603004`, `6092955004`, `6146604004`) render `LinkedIn Profile*`
+  ×3 (`6114603004`, `6092955004` — "Staff AI Engineer | US | Remote",
+  `6146604004` — "Staff Backend Engineer - Mimir Query, Databases
+  | USA | Remote") render `LinkedIn Profile*`
   (Timmy's rendered-form fetches, 2026-10-01, `Documented`). This is the
   census's most useful result: a blanket "no-LinkedIn" rule would have
   wasted submits on Cortex/Grafana, and a blanket "LinkedIn-mandatory"
@@ -194,6 +286,14 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 
 ## Ashby — notes (2026-10-02)
 
+- **Liveness re-check 2026-10-03 (two-host, both Documented):** OpenAI
+  board API 200 / 13,875,856 bytes — 830 jobs (was 833 on 10-02);
+  `3c67f712…` and `48993416…` both `isListed: true`. Eight Sleep board
+  200 / 648,226 bytes — 39 jobs. GraphQL `ApiJobPosting` re-run from
+  Timmy's host 2026-10-03 → 200 in 0.38 s; my `policy_denied` is located
+  in my own environment's egress policy (Testimony only from here), and
+  my earlier HTTP-000 timeouts stay an inference about the same cause.
+
 - Fetched URL (form page): `https://jobs.ashbyhq.com/openai/3c67f712-697d-48d8-b05c-01be896e61da/application`
   (HTTP 200, 51,408 bytes, 2026-10-02).
 - Liveness: `https://api.ashbyhq.com/posting-api/job-board/openai` (HTTP
@@ -239,6 +339,11 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 
 ## Lever — notes (2026-10-02)
 
+- **Liveness re-check 2026-10-03 (two-host, both Documented):** posting
+  API 200 / 23,441 bytes (`?mode=json`) — live; apply page 200 /
+  1,945,666 bytes — byte-identical to the 10-01/10-02 fetches. Timmy's
+  10-03 fetches matched both sizes exactly.
+
 - Fetched URL (form page): `https://jobs.lever.co/palantir/a92b55d0-1d36-4884-8e65-f456450b3a74/apply`
   (HTTP 200, 1,945,666 bytes — byte-identical size to the 2026-10-01
   fetch). Posting API: `https://api.lever.co/v0/postings/palantir/a92b55d0-1d36-4884-8e65-f456450b3a74?mode=json`
@@ -279,6 +384,12 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 
 ## Niceboard (bitcoinerjobs.com) — notes (2026-10-02)
 
+- **Liveness re-check 2026-10-03 (two-host):** homepage 200 / 122,330
+  bytes on three consecutive fetches (Timmy's host), sha256
+  `71791fdc9bf4…` — was 122,310 on 10-02; 77 `{{` / 77 `}}` bindings
+  hold. Both dead job URLs still fall back to `/category/engineering`
+  200 / 114,383. Sizes dated, never quoted bare (entry 12).
+
 - Board URL: `https://bitcoinerjobs.com/` (live — "The Bitcoin Job Board"
   homepage renders).
 - curl probe 2026-10-02 (all with explicit `-s -o /dev/null -w
@@ -315,6 +426,12 @@ Corrections are logged, never deleted. Source: Timmy's reply 22
 
 ## Workday — notes (2026-10-02)
 
+- **Liveness re-check 2026-10-03 (two-host, both Documented):** CXS JSON
+  200 / 8,633 bytes — `jobPostingInfo` live, byte-identical to the 10-02
+  fetch; `/apply` 406.
+- **Taleo:** the item names "Workday/Taleo"; no Taleo board was observed
+  in this census — `no Taleo observation — unverified`.
+
 - Fetched URL: `https://unitytech.wd1.myworkdayjobs.com/Unity/job/Stratford-upon-Avon-United-Kingdom/Software-Engineer_JOBREQ-2616426`
   (HTTP 200, 19,893 bytes on 2026-10-01; £42,900–£64,300 salary range in
   the page).