chore(citadel): record submission, and the form had no Zurich option

Submitted 2026-08-26. Cohort entry added (Adjacent 2/2, cohort now
4/10, channel weak x3) and decision logged.

The finding that matters is not the submission. The application form's
preferred-work-location selector offered no Zurich, despite the JD body
reading "in Miami, Zurich or New York", the posting header listing
Zurich, and the site's own Zurich location filter returning this exact
req when checked on 2026-08-25. The careers site footer reads Citadel
Enterprise Americas LLC, so the likeliest explanation is a US-entity
apply flow with European seats routed elsewhere, or a Zurich seat that
is closed while the multi-location posting stands.

This partly supersedes the working-model risk that blocked Phase 2. If
no Zurich seat is reachable through that form, whether Zurich runs
hybrid or five-day onsite is moot, and the application may be sitting
against a US requisition - a hard no under the standing no-relocation
constraint.

Carry-forward rule recorded in both CLAUDE.md and the session file:
check the application form's location selector before investing in a
package. Two independent signals - the posting's stated locations and
the employer's own location filter - both proved unreliable as evidence
that a seat is actually reachable. Phase 0 treated the filter result as
confirmation that the req was live in Zurich; that inference was weaker
than it looked.

Package itself is finished and reusable: both documents cleared the
validator with zero warnings and the Tier 1 fixes lifted JD term
coverage from 51% to 68%. Nothing about the documents is the weak point.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK

output/CitadelSecurities_PlatformEngineer/session_citadel_securities_platform_engineer.md

@@ -327,6 +327,44 @@ not a re-scored critique.
   Direct preferred hit but never written. File: `critique_citadel_securities_platform_engineer.md`
 - **STILL BLOCKED on the working-model question** — resume built at user direction with that
   question open. If Zurich is 5-day onsite, this package does not get submitted.
+## SUBMITTED 2026-08-26 — and a finding that outranks the working-model question
+
+**Application sent.** Cohort entry and decision log both recorded.
+
+### The form had no Zurich option
+
+The user reports that the application form's **preferred-work-location selector offered no Zurich**,
+despite:
+
+- the JD body reading "in Miami, **Zurich** or New York";
+- the posting header listing "New York, Miami, **Zurich**";
+- the site's own **Zurich location filter returning this exact req** (verified 2026-08-25, 10 Zurich roles).
+
+The careers site footer reads **"Citadel Enterprise Americas LLC"**, so the most likely explanation is
+that the apply flow is a US-entity form and European seats route elsewhere — or that the Zurich seat
+is closed while the multi-location posting has not been updated. A form bug is possible but least likely.
+
+**Consequence.** This partly supersedes the working-model risk. If there is no Zurich seat reachable
+through this form, whether Zurich is hybrid or 5-day onsite is moot — the application may be sitting
+against a US requisition, which is a hard NO on relocation (`user_international_mobility`: no
+relocation, keep a Swiss home base).
+
+**Carry-forward rule for any future Citadel Securities application: check the application form's
+location selector BEFORE investing in a package.** The posting's stated locations and the site's own
+filter both proved unreliable as evidence that a Zurich seat is actually reachable.
+
+### Expectation
+
+User submitted with low effort on the form fields and low expectation of a reply. That is a
+reasonable read: cold channel, an evergreen standing req, an ex-Google/ETH-staffed office, and now a
+location mismatch in the apply flow itself.
+
+### Package status
+
+Documents are finished and reusable. Nothing about the package is the weak point here — the resume
+and letter both cleared the validator with zero warnings and the Tier 1 fixes lifted JD coverage
+51% → 68%. If a better-matched Citadel or market-maker req appears, the package retargets cheaply.
+
 ## Finalization (2026-08-26)
 
 Per `shared_ops.md` → Finalization:
@@ -335,9 +373,8 @@ Per `shared_ops.md` → Finalization:
 2. ✅ Cover letter `.tex`/`.pdf` present (session decision YES)
 3. ✅ Canonical validator re-run on **both** submitted documents → **PASS, 0 warnings each**
 4. ✅ Final PDFs copied to `Dennis_Thiessen_Resume.pdf` and `Dennis_Thiessen_Cover_Letter.pdf`
-5. ⏸ **Submission date NOT yet recorded** — user directed "apply as is" but has not confirmed the
-   application was actually sent. Do not stamp a date that has not happened.
-6. ⏸ **Cohort entry NOT yet added** — same reason. Would be Adjacent 2/2.
+5. ✅ **Submission recorded 2026-08-26** in `job_scout/state/decisions.json`
+6. ✅ **Cohort entry added** — Adjacent **2/2** (cohort now 4/10; channel weak ×3)
 
 **On confirmation of submission, run both:**