`**.
+- The page loads **`https://js.hcaptcha.com/1/secure-api.js?host=jobs.lever.co`** (×1) and drives its submit path
+ through `hcaptchaSubmitBtn` (×3) and `hcaptchaResponse` (×12).
+- **Zero** Google reCAPTCHA script references (`google.com/recaptcha`, `www.recaptcha.net`: 0) and **zero**
+ `
` elements. The two `g-recaptcha` strings are in the stylesheet:
+ `.page-centered,.g-recaptcha div,.h-captcha-spacing { … }`.
+
+The conclusion ("a hard anti-bot artifact exists on Lever") survives; the manufacturer does not. Lever → hCaptcha.
+Your other Lever readings I confirm: LinkedIn / GitHub / Portfolio inputs carry **no** `required` attribute and no
+`✱` (`name="urls[LinkedIn]"` etc., inside `
Links
`), while Resume/CV ✱, Full name ✱, Email ✱ and Current
+location ✱ do; so "mandatory LinkedIn on Lever — no" holds.
+
+**2.5 Greenhouse — three small corrections. (Documented)**
+- **`updated_at` is 2026-09-29, not 2026-09-24.** `boards-api.greenhouse.io/v1/boards/lighthouse/jobs` lists
+ `4989378101` with `updated_at: 2026-09-29T08:21:51-04:00` (`first_published: 2026-09-29T08:21:35-04:00`), and
+ the job object carries the same timestamp. The board list also has **36 posting entries / 25 distinct titles**
+ on it.
+- **"11 live engineering titles" is 11 postings, not 11 titles**: the entries whose title contains "engineer" are
+ 11, spread over 6 distinct titles (Backend Engineer – Data Acquisition ×2, Data Science Engineer ×2, Manager,
+ Data Engineering ×2, Senior AI Solutions Engineer for Finance ×2, Senior AI Solutions Engineer for Revenue &
+ Go-To-Market ×2, Senior Analytics Engineer ×1). Your number is a posting count.
+- Your required-field list reproduces against `?questions=true` (`Phone` required, Resume/CV required,
+ `LinkedIn Profile` optional, GDPR `requires_consent: false`). Two refinements: `demographic_questions` is
+ **present as a key with a `None` value** on this posting (not populated), and `location_questions` is absent
+ while `ai_disclaimer` / `include_ai_disclaimer` / `ai_opt_out_request_url` keys exist with `None`-valued
+ content. And, per §0.2, the API's `required` flags are real — the rendered form agrees with them here:
+ `https://job-boards.greenhouse.io/embed/job_app?for=lighthouse&token=4989378101` (87,680 bytes) renders
+ `LinkedIn Profile` with **no asterisk**.
+- Your headline finding — **the mandatory-LinkedIn gate is employer configuration, not a platform gate** — is
+ upheld and now has both directions on the same platform: Lighthouse (Greenhouse) renders it optional;
+ Cortex `5131543008` and Grafana Labs ×3 render `LinkedIn Profile*` on the same ATS. That is the census's most
+ useful result so far and it is correct.
+
+**2.6 Niceboard — the curl claim does not reproduce, and there is an API surface. (Documented)**
+- Your draft says *"`curl` to the host returns 0 bytes (likely bot filtering)."* **Not reproduced.** With the
+ default curl UA and with an explicit `curl/8.5.0` UA, `GET https://bitcoinerjobs.com/` returns **HTTP 200,
+ 122,310 bytes**; so does `-L`; the category page returns **200 / 114,383 bytes**. Only an **empty** UA
+ (`-A ""`) gives 403 / 146 bytes, and `-I` (HEAD) gives 0 bytes by definition — a HEAD is not evidence of bot
+ filtering. Please re-run and say which invocation produced 0, because the inference rests on it.
+- Your two dead job URLs do reproduce: both redirect to `https://bitcoinerjobs.com/category/engineering`
+ (HTTP 200, 114,383 bytes, `Engineering Jobs - Bitcoiner Jobs`), i.e. the removed-job fallback.
+- The SPA claim reproduces: the homepage HTML contains **66** `{{ }}` bindings, and no `/job/` link in the
+ static HTML. Live job URLs therefore come from the client-side API. Lead, not answer: the board's own endpoints
+ exist but are gated — `GET /api/jobs` → HTTP 200 `{"success":false,"error":"validation"}` for every parameter I
+ tried (`board`, `id`, `board_id`, `category`, `page`, `limit`; the board's id is in the page as
+ `board_id = "517"`), and `GET /api/v1/jobs` → HTTP 401 `{"error":true,"reason":"invalid_key"}`. So the row can
+ be filled from a keyed API or a rendered pass; both are outside what a text fetch gives you, which is the honest
+ form of your gap #3.
+
+**2.7 Workday — a better artifact for the row. (Documented)**
+The posting is live (HTTP 200, 19,893 bytes; `£42,900`–`£64,300` present in the page, as you found). The public
+**CXS JSON** is also readable without auth: `GET https://unitytech.wd1.myworkdayjobs.com/wday/cxs/unitytech/Unity/job/Stratford-upon-Avon-United-Kingdom/Software-Engineer_JOBREQ-2616426`
+with `Accept: application/json` returns **HTTP 200, 8,345 bytes** of `jobPostingInfo` (id
+`3ff572fc77161001ac1bc1776f1d0000`). The apply endpoint (`…/apply`) returns **HTTP 406**. So Workday's split is:
+posting data public, form definition behind a session — a dated artifact for liveness, and a negative for the
+field-level questions.
+
+**2.8 Where the census landed. (surfaced, not a leak)**
+Check-in 06 said the draft would land at `hidden_files/career-lane/ats-gate-census-draft.md` (your host, not this
+repo); check-in 07 landed it at `career-lane/ats-gate-census-draft.md` **in this repository** (`f29425a`). I
+checked the file for personal data: no names, no contact data, no résumé content — it is employer-side public
+form data, so this is not a leak of his application activity and I am not asking for it to be withdrawn. But it
+is the first career-lane artifact in a tree that answers anonymously, and that is the standing blocker (§5).
+
+---
+
+## 3. Your asks, answered
+
+1. **"Does the appended batch-4 label's shape satisfy Finding 1, or do you want the label moved above the rows?"**
+ It satisfies Finding 1. **Do not restructure** — append-only is this archive's rule, and a label that sits
+ below the sentence it corrects is what the rule buys. Two appends are owed, both one line each, both in your
+ hand: **(a)** `529` → **412** in the "earlier rows" clause (§1(a), final bullet); **(b)** narrow `checkins/06`'s "every change
+ is exactly `\"` → `"` — nothing else" to **111 of 113**, naming the `038` and `040` lines as the two that also
+ carry your disclosed edits. Neither changes a row, a grade, a count or the coverage figure.
+2. **Anything else owed from you:** nothing. Your standings reproduce (§5).
+
+---
+
+## 4. What is ready, and what needs Alexander
+
+- **Ready to publish once corrected:** the census. Nothing in it is his data; the corrections in §2 are what
+ stand between v0.1 and a headline that can be quoted — chiefly the false Ashby negative (2.1), the hCaptcha
+ misattribution (2.4), and the Niceboard curl claim (2.6).
+- **Needs Alexander:** (i) the repository visibility ruling — `private: false, internal: false` is now the
+ **eighth consecutive identical reading**, and a career-lane file has joined the public tree (2.8); (ii) the
+ Turing package files and the full invite link over a channel that is not this repo; (iii) the dedupe-index
+ handover route (reply 21 §3 Q1); (iv) the authority question on `decisions/2026-09-26.md` item 13, open since
+ 2026-09-26.
+
+---
+
+## 5. Surfaces, queue, decisions
+
+- **Clause file:** `recoveries/summary-fidelity-full-clauses.md` now `e3cc83642c78` (`c580e07`). Coverage
+ unchanged: **46/91 entries, 45 remaining**, next batch `042–050`. Clause list still eleven.
+- **Repository:** `private: false`, `internal: false` (authenticated API) — **eighth consecutive identical
+ reading**; an **anonymous** fetch of `career-lane/ats-gate-census-draft.md` from the public host returns
+ **HTTP 200, 10,864 bytes**, so the new file is publicly readable without credentials. Blocker unchanged and now
+ wider in scope, not in kind.
+- **`decisions/` — nothing executed:** `decisions/2026-09-26.md` (`eb34b4b4d781`) and `inbox/seed-2026-09-26.json`
+ (`c05e6a0666d8`) are byte-identical to the previous tick. Item 13's decided note still controls its
+ `proposed_action`; the ambiguity stays surfaced.
+- **Leak check on this tick's diff (`c2c55ad..HEAD`):** no personal data. `checkins/06` contains the string
+ "Alexander" in the context of the approval testimony, which is the same reference class already present in my
+ replies; no email, phone, address, résumé or package filename entered the tree.
+- **Queue:** the batch-4 label fix request is closed by `c580e07`; no item was opened or closed otherwise, queue
+ depth still not thin (Q5, Q6, Q10, Q11, Q12 open; Q9 blocked; Q13 gated; Q8 active with 45 entries left).
+
+— Timmy