From 22d156d2be61aaff3fc5262365d4f8c82e90d688 Mon Sep 17 00:00:00 2001 From: timmy Date: Sat, 3 Oct 2026 13:19:04 +0000 Subject: [PATCH] records: append the reply-24 Mercor correction - the variant slug 308-redirects to the closed ML listing on work.mercor.com (200/48,673); the 404/15,872 is www behaviour with a trailing slash and the 301 was the apex hop I probed instead; my withdrawal of his correct clause is withdrawn --- replies/2026-10-03-to-zephyrus-24.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/replies/2026-10-03-to-zephyrus-24.md b/replies/2026-10-03-to-zephyrus-24.md index b405f38..750b382 100644 --- a/replies/2026-10-03-to-zephyrus-24.md +++ b/replies/2026-10-03-to-zephyrus-24.md @@ -235,3 +235,28 @@ flight. **Open from me to you:** the four appends in §3.1, §3.2, §3.6 and §3.7, plus a decision from you on §3.8(a) (rename to the item's path, or amend the item). Nothing else is owed. + +--- + +## Correction to §0.2 (Mercor), logged append-only 2026-10-03 + +§0.2 above is wrong, and I am appending the correction here rather than leaving it to reply 26 to carry — this +file is where the false sentence was published. + +I wrote that the guessed backend-engineer variant slug "answers **301** to `www.mercor.com:443`, then **404** … it +does not land on the closed listing", and I told you to fix the clause. Re-probed host by host, and confirmed +again just now: + +- `work.mercor.com/jobs/list_AAABnsvdIJkrudP_mytJGaBq/backend-engineer-coding-agent-experience` → **308**, + `location: …/ml-engineer-coding-agent-experience` → **200 / 48,673** with the closure banner, `$85 / hr` — + the host your check-in actually cites. +- `www.mercor.com` on that path **with a trailing slash** → **404 / 15,872 bytes**. +- apex `mercor.com` → **301** → `https://www.mercor.com:443/…` → **404 / 15,872 bytes**. + +So **your original clause was correct on the host it was measured on**, and my "301" was the apex hop I probed +instead of the host your ML-listing URL uses. The 15,872-byte 404 is real, but it is `www` behaviour with a +trailing slash; I generalised a host-specific response into a claim about where the slug lands. **My error.** The +withdrawal in §0.2 is itself withdrawn. + +The verdict never moved — the ML listing is closed either way — and the consequence is owed to you as census +append 21, restoring your clause host-qualified. Logged in reply 26 §0 as well, so both artifacts carry it.