From f56f2343b1332cd6258a6cabde976fe43200fa08 Mon Sep 17 00:00:00 2001 From: timmy Date: Sun, 4 Oct 2026 13:13:07 +0000 Subject: [PATCH] queue Q8/Q17/Q18: record 9371032 as the commit that closed the batch-4 529->412 label append, verified from the pre-edit tree f3afc18^ (exactly 412 rows, none in 032-040: 355 entries 001-031 + 57 rows 041/051/061/071/081/091) and by the escape census at f3afc18 (all 113 escaped rows inside 032-040, zero on the 412 earlier rows), both halves Documented, and with the byte count named as not-a-check since 529 and 412 are the same length; Q17's source lane marked clear; Q18 gains a second status from the same tick - a matching requisition id is not a stable key, because the one matched row was rewritten on the same id (09-23 'Staff SWE, AI Code Review' -> 09-25 Evaluator body -> 10-04 'Senior SWE, AI Training - United States', New York City), Documented from G2i's public posting API and the live JSON-LD, so the fixed term set must include the title as captured at preparation time; reply-28's description-body sentence logged as withdrawn and the Built In citation re-graded 404 (family live under other ids); the prepared-package drift carried to Alexander as a distinct option from re-cut; visibility fifteenth identical reading with a new blocker sentence for the pending inbox item's text now sitting in an anonymously-answering repo (named, not quoted) --- WORK-QUEUE.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 7454ee1..8142a3c 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -1154,3 +1154,34 @@ with the terms named, and a match is reported with its key and prepared/submitte **Status, 2026-10-04 — opened; the rule is stated above and the G2i reconciliation is recorded in reply 28 §2. Not yet applied to a fresh scouting tick.** +**Second status, 2026-10-04 (same tick, after his second check-in `61724d3`) — a matching requisition id is not a +stable key, and that is a harder version of the same defect.** Re-fetching the one matched row this tick found the +requisition **rewritten on the same id**: published 2026-09-23 as *"Staff Software Engineer, AI Code Review - +Python, Go, Rust, C#"* (my index/2026-09-25 capture), captured 2026-09-25 carrying the *"Senior AI Interaction +Evaluator (Codex / Claude Code)"* body, and live today as *"Senior Software Engineer, AI Training - United States"*, +location **New York City**, Contract. Two independent instruments agree against my capture: G2i's public posting API +(`api.ashbyhq.com/posting-api/job-board/g2i?includeCompensation=true` → 200 / 251,652, **23 jobs**; **13** +`AI Training - ` titles, **zero** containing "Evaluator") and the live page's own JSON-LD. **Grade: +Documented.** + +- **The rule gains a term, on the evidence of this miss:** the fixed set must include the **title as captured at + preparation time**, not only the requisition id and the current titles — an id can carry a rewritten title and + body, and a check keyed on the id alone would pass while the mapping to the prepared package has drifted. +- **This corrects a sentence of mine, logged not deleted:** reply 28 §2 said the live req's description body opens + with the Evaluator block. It does not; that text is my 2026-09-25 capture. Withdrawn in reply 29 §0.1, with the + evidence, and the discrepancy is what produced the finding above rather than the reverse. +- **Consequence carried to Alexander with the exact-package decision:** the 2026-09-25 package was prepared against + a requisition since retitled and re-described, so "submit as-is" means Sep-25 prose addressed to the old title + against the current req text — a distinct option from "re-cut". Named in reply 29 §4 and in the 2026-10-04 + delivery; nothing is drafted or submitted meanwhile. +- **Built In, re-graded by fetching:** the id cited in reply 28 §5 (`builtin.com/job/10853991`, 200 / 92,316 at + 12:24Z) returns **404 / 22,632** on all three URL forms this tick, from both hosts. The family is live under + other ids (`…/rust-senior-engineer-ai-interaction-evaluator/10854511`, posted 4 days ago) beside removed ones + (`10678117` removed 2026-08-26, `9291569` removed 2026-08-14). The specific citation is **not reproduced**. +- **Visibility, and one new sentence for the blocker:** the counterparty's second check-in carries a **pending inbox + item's text** (item 20) inside a repo that answers anonymously (fifteenth identical `private: false` / + `internal: false` reading, `updated_at 2026-10-04T13:09:24Z`). It is a proposal about a requisition, it quotes no + personal data, and **nothing of it is quoted or duplicated by the pipe** — but it is pending review material in a + public tree, which is the same rule that keeps `inbox/pending.json` out. Still exactly `7c4cf1b` and `2eb50b7` + touching `inbox/` or `decisions/`. The ruling remains Q14's and Alexander's. +