Application
- Kongsberg Discovery / Seatex, Lead Engineer DevOps and Test Infrastructure
(Trondheim): resume, cover letter (+ paste text), verbatim JD, session and
critique. Submitted 2026-10-08 via EasyCruit as a deliberate cold application
on a user override of the embedded-SW hard gate (Evidence Fit 69, Document
Quality 84). Recorded in applications.json and decisions.json.
- Google Senior SWE Full Stack Commerce: session and verbatim JD from
2026-10-03 (no-go on the frontend gap, held, not submitted).
Knowledge base
- claims.json: ED-1 (embedded/robotics coursework, none since studies),
SW-9 (current unit testing, pytest), new skills (pytest, unit testing,
embedded systems (coursework), VHDL, robotics (coursework)), and Jenkins and
GitLab CI/CD registered from existing GN-1/FC-1/BS-6/SW-3 scopes.
- Earlier uncommitted KB work: 2026-09-18 Python frameworks / enterprise SaaS
clarification, 2026-10-03 data-product design / no-frontend clarification,
2026-10-06 working-model rule (3 homeoffice days baseline) in config.md and
application_strategy.md, plus related experience/bundle/taxonomy updates.
- CLAUDE.md corrections log: 2026-10-08 entry for the three canonical gaps.
Scout
- 2026-10-08 run triaged by JD read: NVIDIA DGX Cloud Senior Production
Engineer, Google SRE III Prod AI / Senior SRE / Staff Shopping Graph and
Amazon RIVR DevOps logged as maybe; GenAI FDE family, Kraken AI Platform,
PostFinance DevOps and five Kdo Cy reqs logged as skip with reasons.
Housekeeping
- .gitignore: ignore .cache/ and raw HTML page dumps under output/.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Second-pass review of this session's work by another agent. It corrected several
real mistakes of mine and finished F06 gaps I had left open. Reviewed, verified
and committed as-is.
THE MISS THAT MATTERS
`job_scout/state/applications.json` — the authoritative application registry
introduced by F02 — was never actually tracked. `job_scout/state/*` in
.gitignore silently excluded it, so my checkpoint commit afdef7e claimed to add
it and did not. Only `application_cohort.json`, the GENERATED projection, was
version-controlled; the source of truth and the migration history backup were
not. .gitignore now carries explicit negations for both.
MY ERRORS, CORRECTED
- "kastellaun" was in CH_LOCATION_KEYWORDS. Kastellaun is in Rhineland-Palatinate.
I took it from a Bundeswehr reserve listing and filed it under Switzerland -
precisely the class of bug F12 existed to fix.
- The F12 fix only widened the keyword list; SmartRecruiters still discarded the
structured country, which was the concrete case the review named
(city=Baar, country=CH). The adapter now preserves it, and a COUNTRY_NAMES
mapping gives country precedence over a bare town name.
- F15 was applied to Taleo and Prospective only. Greenhouse still wrote
`updated_at` into `posted`; it now uses `published_at` and carries provenance.
- My negation guard `\b(no|not|...)\b[^.;]{0,60}$` was too loose - an unrelated
"not" within 60 characters could mask a real claim. Tightened to require the
negation to govern the term.
- F18's retirement of the macro-count rule missed "Four to six compact skills
lines" in the workflow; removed now.
F06 GAPS I LEFT OPEN, NOW CLOSED
Date-format validation on education/employment periods (the 2035-99 case named
in the review), evidence-structure validation, referential integrity on evidence
source files, and the missing-identity KeyError.
F10 TAKEN FURTHER, AND RIGHTLY
I demoted the US-GPA fields to *_orientation_only. They are now removed
entirely, with grade_output_rule saying what to do instead: use the German grade
and scale, and if a recipient requires a US GPA, use THEIR method and record it.
Keeping a number derived by a non-recognised method invites its use.
Also: the Capgemini omit-preference now sits in experience_capgemini.md itself,
alongside the instruction not to fill or explain the intentional gap.
BIS BASEL - REJECTED 2026-09-11
jr100429, applied 2026-07-10, no interview, no reason given. Recorded in the
registry with a dated event and in the decision log; the "prep interview brief
when screening lands" next action is cleared. This also settles the 2026-09-04
observation that the req had vanished from the BIS board - it was a real
rejection, not just a closed posting.
VERIFICATION I RAN MYSELF BEFORE COMMITTING
49/49 tests. Validator PASS with 0 advisory warnings. Package manifest and
registry views current. All 12 F12 location cases still correct, including
Kastellaun now rejecting. The F05 counter-proof still catches all 9 violations.
SBB, NVIDIA, RUAG and Kdo Cy resumes still scan clean. Diffs are net-additive
across every reference file - the deletions are replacements, not losses.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM
The review's key point is that the error ran BOTH ways.
Overstatement, narrowed to canonical scope:
- BS-1 variants claimed "eliminated manual wafer inspection", "no manual
intervention" and "unattended quality monitoring". Canonical BS-1 supports a
qualitative reduction whose size is unverified. Reworded; the scope limit is
now stated inline where the variants are written.
- bundle_data_platform called BS-1 a "zero-downtime constrained deployment".
Integration into a fab that runs continuously is not a measured zero-downtime
property.
- experience_swisscom carried "grounded retrieval" as a skill and ATS keyword
while SW-8 records retrieval implementation as explicitly unknown, and its
reframing note invited "evaluation discipline" although formal model
evaluation is a globally forbidden pattern. Both removed.
- PyTorch sat in bundle_ml_ai_engineer as a bold tool and an ATS must-include
with no certification context - the exact way the context gets lost.
Undervaluation, the half that quietly costs him roles:
- BS-6 (Linux administration, intensive Ansible incl. self-written extensions)
has been canonical since 2026-08-27 but appeared in NO bundle, so the normal
selection paths could not see it. Added to the data-platform and data-engineer
bundles with its currency limit (employer-side ended Dec 2022; PP-3 is
personal) and the standing GitOps prohibition.
- Linux, Ansible and Bash were missing from skills_taxonomy entirely.
- skills_taxonomy still said the IBM certification year was "not recorded" and
that PyTorch needed verification; both were settled on 2026-08-27.
Not rewritten, deliberately: the NVIDIA and RUAG cover letters state the
production line could not be stopped. That exceeds the canonical record but is
plausible and both are already submitted. Recorded as an OPEN ITEM in
experience_bosch.md to be confirmed with the user before any reuse.
Validator PASS, 31/31 tests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM
- Add ai_fingerprint_rules.md with banned words, structural rules, and
12-item post-gen checklist
- Fix Fellowships/Honors template format: --- to period separator
- Fix Publications under-review template format
- Update all 4 skills to load fingerprint rules during generation
- Add AI scan section to critique framework
- Update resume_reference and cl_reference with em-dash limits
- Reduce em-dashes in example files
Co-Authored-By: Akhil Peeketi <peeketiakhilreddy@gmail.com>
dennisthiessenandClaude Opus 5.5