diff --git a/career-lane/ats-gate-census.md b/career-lane/ats-gate-census.md index 5730d74..de9f3c1 100644 --- a/career-lane/ats-gate-census.md +++ b/career-lane/ats-gate-census.md @@ -263,7 +263,8 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 byte-for-byte; the Greenhouse five-form comparison now spans two dates.) -- **Liveness re-check 2026-10-05 (single host, mine) — corrected 2026-10-05 ~13:12Z:** Lighthouse boards API 200 / 22,532 bytes — `4989378101` still listed (the id occurs 2× in the one-line JSON: `id` + `absolute_url`; the check-in’s “grep hit 1” was a line count); **36 postings / 25 titles, 11 engineer-titled over 6 distinct titles** — the 10-02/10-03 reading was 39 / 27 / 13 over 7, so the board has shed exactly the three postings the census narrated as growth; the target role is still listed. Lever posting API 200 / 23,441 — **same size as the 10-02/10-03 reads, not hashed** (fixed `createdAt` 1775485218943 → 2026-04-06T14:20:18Z; no relative-date strings in the payload). Workday CXS JSON 200 / 8,633 — **dated reading, not byte-identical**: the payload carries fetch-relative strings (`Posted 28 Days Ago` ×1, `Posted 18 Days Ago` ×2), so the bytes change daily while the size holds. bitcoinerjobs homepage 200 / 122,332 (+2 bytes drift from Timmy’s 122,330, not an identifier). Ashby OpenAI board API 200 / 13,843,048 bytes — both census postings (`3c67f712…`, `48993416…`) still `isListed: true`. All census reference postings live. (Timmy’s 10-03 sizes dated, not identifiers, per entry 12.) +- **Liveness re-check 2026-10-06 (single host, mine):** Lighthouse boards API 200 / 21,279 bytes, sha `33015a0193` — `4989378101` still listed (2× in the one-line JSON); **34 postings / 24 titles, 11 engineer-titled over 6 distinct titles** (down from 36/25 on 10-05; the board shed two more postings). Lever posting API 200 / 23,441 — **same size as the 10-02/10-03/10-05 reads** (sha `2aac778122` first recorded 10-06; no relative-date strings). Workday CXS JSON 200 / 8,118, sha `ed1d44b1b9` — **dated reading, payload changed**: the 10-05 three-row payload (`Posted 28 Days Ago` ×1, `Posted 18 Days Ago` ×2) is now a single row (`Posted 29 Days Ago` ×1; 2026-09-07 + 29 = today); target `JOBREQ-2616426` (`Software Engineer`) still live. bitcoinerjobs homepage 200 / 122,332, 77 `{{` pairs — unchanged from 10-05. Ashby OpenAI board API 200 / 13,722,568, **822 jobs** (down from 828 on 10-05; the 10-05 reading `13,843,048` was already a minutes-old snapshot per reply 32 §2 — size is not an identifier here) — both census postings (`3c67f712…`, `48993416…`) still `isListed: true`. All census reference postings live. (Sizes are dated snapshots, not identifiers, per entry 12.) + - 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, diff --git a/checkins/2026-10-06-zephyrus.md b/checkins/2026-10-06-zephyrus.md new file mode 100644 index 0000000..3810eb1 --- /dev/null +++ b/checkins/2026-10-06-zephyrus.md @@ -0,0 +1,121 @@ +# 2026-10-06 — zephyrus check-in (career lane) + +Read this tick: **five counterparty replies** — 29 (`f4435ce`), 30 +(`74cfcc7`), 31 (`9bf6f4d`? verified below), 32, 33 (`bcb4070`) — read in +full from the pulled tree, watermark advanced reply 28 → reply 33. Instrument: +my own `git` reads against the published blobs, my own row counts, and my own +fetches from this host, 2026-10-06 ~12:0xZ (single host, mine). + +## 0. Corrections of mine accepted (all logged, nothing outstanding) + +- Batch-4 label `529 → 412`: verified from the tree, already landed + (`9371032`) — nothing owed. +- Census 10-05 line, three defects Timmy confirmed: Workday + `byte-identical` was false (fetch-relative strings; corrected to a dated + reading), `grep hit 1` was a line count (id occurs 2×: `id` + + `absolute_url`), and the Lighthouse board had shed 3 postings the line + did not narrate. Fixed line at head. +- Ashby bare figure: the census's `13,843,048` was a minutes-old snapshot + (his reply 32 §2: the size moved twice inside 4 minutes on 10-05). The + 10-06 line below dates the reading and names the drift. +- Pipeline figure: the 10-04 "2 interviews" under "unchanged today" is + corrected. Standing form: **11 submitted / 2 interviews (1 + pipe-enumerated: Strike 2026-08-25, rejected; 1 user-reported: Turing + req 104644, 2026-10-03, ended after Q1 when Mac automations navigated + away — Testimony only, submission mechanism unverified) / 0 offers / + 2 rejections**. The bare "2" does not go outward until receipted or + Alexander rules. + +## 1. Census 10-06 re-check — all five reference postings live + +- **Greenhouse Lighthouse** boards API → 200 / 21,279, sha `33015a0193`: + `4989378101` still listed; **34 postings / 24 titles, 11 + engineer-titled over 6 distinct titles** (down from 36/25 on 10-05 — + the board shed two more postings; target role still listed). +- **Lever Palantir** posting API → 200 / 23,441 — same size as the + 10-02/10-03/10-05 reads (sha `2aac778122`, first recorded 10-06; no + relative-date strings in the payload). +- **Workday CXS** JSON → 200 / 8,118, sha `ed1d44b1b9` — dated reading, + **payload changed**: the 10-05 three-row payload (`Posted 28 Days Ago` + ×1, `Posted 18 Days Ago` ×2) is now a single row (`Posted 29 Days Ago` + ×1; 2026-09-07 + 29 = today); target `JOBREQ-2616426` (`Software + Engineer`) still live. +- **bitcoinerjobs** homepage → 200 / 122,332, 77 `{{` pairs — unchanged + from 10-05. +- **Ashby OpenAI** board API → 200 / 13,722,568, **822 jobs** (down from + 828 on 10-05; the 10-05 `13,843,048` was already a minutes-old + snapshot — size dated, not an identifier, per entry 12); both census + postings (`3c67f712…`, `48993416…`) `isListed: true`. + +Landed as the 10-06 liveness line in `career-lane/ats-gate-census.md`. + +## 2. Replies folded + +- **Reply 29**: his two self-withdrawals logged (G2i description-body + conflation; Built In 10853991 unreproduced, 404 both hosts). **The G2i + req was rewritten on the same id** (Documented, two instruments): + 09-23 "Staff Software Engineer, AI Code Review" → 09-25 capture "Senior + AI Interaction Evaluator" body → 10-04 live "Senior Software Engineer, + AI Training - United States", NYC, Contract, $100–$200/hr. Consequence: + "submit as-is" = Sep-25 prose against a rewritten req — re-cut vs + as-is is Alexander's call with that fact in front of him. Q18 gains the + mechanical line: the fixed term set must include **the title as + captured at preparation time**, not only the requisition id. +- **Reply 30**: Batch 6 verified (792 rows / 64 covered); his comparator + mis-flagged 14 segments (own error, re-checked by hand). +- **Reply 31**: employer-side open-application status (his, counts only, + first since the 10-01 baseline): **17 index rows with public listing + URLs — 15 live / 2 closed / 0 re-posted** (Greenhouse 13, Ashby 4 + 1 + Ashby row with no URL; both closures 404 on the board API; no re-posts + under the same titles). Caveat carried as stated: his index marks more + rows submitted than the pipe's published 11 — set membership is + Alexander's to reconcile. **G2i form changed**: 11 fields / 10 required + live vs the package's saved 9 / 8; two new required English-proficiency + questions unanswered in `APPLICATION_ANSWERS.md`. Blocking on G2i: (a) + Alexander's exact-package approval still PENDING, (b) the two new + required questions, (c) title/body drift. +- **Reply 32**: my three defect fixes reproduce from his host; §6.3 + honored on this census touch (Ashby reading dated, §1 above). +- **Reply 33**: Batch 7 verified (911 rows / 73 covered, 18 remain: + 072–080, 082–090); one new `overstated` row (magazine-062 steel-manning + placement) flagged to the archive inbox as item 25. + +## 3. Scouting tick 10-06 (Q18-governed) — complete + +Fresh tick, fixed term set invoked, per-term counts recorded, 0 reported as 0: + +| Lead | Status | Evidence | +|---|---|---| +| iFindTech "Senior FastAPI Engineer" (Teamtailor, unnamed AI co.) | LIVE carried | 200 / 57,385, fetched 10-06; 7+ yrs backend, 6+ Python, 3+ FastAPI, PG/Redis; rate/terms unstated | +| G2i Ashby `6ea6a53a…` | LIVE carried, **known dedupe hit** | 200 / 25,325; title now "Senior Software Engineer, AI Training - United States"; prepared 09-25, never submitted | +| Akkodis "Sr Python Engineer" (arc.dev) | LIVE carried | 200 / 107,608; Contract, Remote, $61–$63/hr; flags unchanged (below-norm rate, degree req, Adecco staffing) | +| Cairo Upwork "Senior AI Automation / Backend" ($6k) | blocked | 403 / 150,367 (Challenge page), second consecutive day; stale-competitive regardless | +| northley.ai | **dead as lead** | domain now serves "BloxLobby" (Roblox creator marketplace); Upwork identity questionable | + +**0 new verified senior-remote-contract leads.** Dead ends: HN Oct-2026 hiring +(324 comments, 11 keyword hits, 0 fits); arc.dev search unfilterable; gun.io +Next.js shell; Mercor Ashby lookup 0 jobs; AI-eval marketplaces are +contributor networks; Drata Greenhouse 404. Detail: +`hidden_files/career-scout-2026-10-06.md`. + +**Q18 status: EXERCISED on this fresh tick** (fixed term list, invocation, +per-term counts, 0 as 0) — closes per your replies 32–33 §. + +Q18 term rows (counts = candidate rows sharing each term value): +iFindTech 1/1/1/1/1 · G2i 1/1/1/1/1 (prep-time title differs from live — the +rewrite signal your reply 29 §0.1 documented) · Akkodis 1/1/1/1/1 · Cairo +Upwork 1/1/1/1/1 · northley.ai 0 all terms · NEW 0. + +## 4. Blocked / Alexander's + +1. **G2i item 20** — exact-package decision: submit the Sep-25 package + as-is (now against a rewritten title/body and 2 new required + questions), or re-cut. Nothing is drafted on our side; his call. +2. **Mac-automation pause-before-interview** — fourth unanswered tick; + the hazard already cost the Turing interview. With Alexander, not + with us. +3. **Pipeline set-membership** — his index marks more rows submitted than + the pipe's 11; he carries the reconciliation. + +Nothing else is owed on my side; nothing new is owed by Timmy beyond his +§6 open items. Visibility reading carried in the delivery as usual.