BS-1 operating constraint - the F07 open item, resolved by the user
The user clarified what the 24/7 constraint actually is: a defect in the
software could, worst case, halt production - an outcome that must never occur.
That is a FAILURE-CONSEQUENCE constraint, and the submitted NVIDIA cover letter
states something different: "a production line that could not be stopped for a
deployment" describes a scheduling window. The distinction matters in both
directions - the letter is inaccurate, and the truth is the stronger claim.
- BS-1 scope now records the real constraint and how to write it.
- Both variants of the letter's phrasing are added to BS-1 `forbidden`, so the
scanner catches them. Verified: it now flags the submitted letter.
- BS-1 evidence filled from a real source (this clarification) rather than left
unrecorded, including ownership - integration and operation, not model work.
- The submitted letter is NOT rewritten (F17). experience_bosch.md records the
resolution and the wording to use instead.
Scanner false positive fixed: the employer-date check now runs on CVs only. A
cover letter naming an employer in prose is not claiming a date.
Cleanup, authorised by the user
- 136 LaTeX build artefacts removed (already gitignored, regenerable).
- 7 superseded intermediate QA renders removed, 6 of them in NATO_AI_ENGINEER
which carried nine PDFs for two documents.
- Nothing evidential touched: 36 submitted PDFs, 41 e2e deliverables, 44 sources,
54 session/critique files and 20 JD files are intact. The Kraken PDF was
checked before deleting and turned out to be the saved job description, not a
render.
- output/ 16M -> 13M.
37/37 tests pass.
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
BS-5 was a thin "C# extensions" note; now records the verified reality
(Playwright scrape of community.spotfire.com, 2026-06-15): co-ownership
of Bosch's Spotfire analytics platform and the TAF 2022 co-presentation
"Understanding Spatial Variability in Semiconductor Products with
Spotfire Map Charts". Reframing bumped to MED-HIGH for BI-bridged JDs;
new 1L/2L variants. First consumed by the Microsoft ISE package (merged
BS-3+BS-5 bullet; TAF talk reserved for the CL).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dennisthiessenandClaude Opus 5