feat(app): BIS jr100498 Senior/Lead Data & Analytics Engineer (MED IT) submitted; KB gaps closed; scout triage 2026-10-14

Application
- BIS Basel, Senior/Lead Data & Analytics Engineer, Monetary and Economic
  Department IT (jr100498, 3-year term): resume, cover letter, verbatim JD,
  session, critique and the four portal free-text answers. Submitted
  2026-10-15 via the BIS portal, cold (Evidence Fit 78 Core, hard gate PASS,
  Document Quality 88 after Tier 2 polish). Different unit from the rejected
  jr100429 (Banking Technology). Recorded in applications.json and
  decisions.json.

Knowledge base
- claims.json: BS-9 and SW-10 (onboarded and mentored junior developers at
  Bosch and Swisscom); skills TIBCO Spotfire, Teradata, Oracle Database and
  Hadoop / Impala registered from existing claim scopes; SDMX registered as
  forbidden (user-confirmed never used); SW-4 scope records the
  prototype-and-iterate approach with B2B business, architects and engineers.
- Clarification note 2026-10-14 with verbatim user answers, including
  "schedule yes, budget no" for project planning (unattributed, so not a
  claim yet).
- CLAUDE.md corrections log: 2026-10-14 entry.

Scout
- 2026-10-14 run (37 companies, 101 new): 19 JDs read; BIS jr100498 taken
  forward; Snowflake Engineering Productivity (mis-titled "Sr SWE,
  Enterprise"), Google SWE III Shopping Graph Feeds and Meta SWE
  Infrastructure logged as maybe; 15 roles logged as skip with the failing
  JD line quoted. Found: BIS RSS adapter stamps every vacancy as Basel
  (jr100491 is Hong Kong); Confluent Ashby board returns no jobs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

knowledge_base/extractions/2026-10-14_mentoring_spotfire_sdmx_clarification.md

@@ -0,0 +1,43 @@
+# Junior mentoring, Spotfire and SDMX — user clarification
+
+Source: direct user message, 2026-10-14, during the scout triage of BIS Basel jr100498 *Senior/Lead Data & Analytics Engineer* (MED IT).
+
+Questions asked: (a) SDMX / official-statistics experience? (b) anything stronger than the Bosch student supervision (BS-7) for the JD line *"Experience providing general supervision and task-specific guidance to junior colleagues"*? (c) register Spotfire as a canonical skill?
+
+Verbatim:
+
+> a. no experience with sdmx b. i did onboarding & mentoring of junior developers at Bosch and Swisscmo c. ok, add it.
+
+("Swisscmo" is a typo for Swisscom.)
+
+Established facts:
+
+- **No SDMX experience.** SDMX (Statistical Data and Metadata eXchange) has not been used.
+- He **onboarded and mentored junior developers** at **Bosch** (2020-2022) and at **Swisscom** (2023-present). This is separate from, and in addition to, the student/thesis supervision already recorded in BS-7.
+- **TIBCO Spotfire** is to be registered as a canonical skill. The evidence already exists in BS-5 (co-owned the Spotfire environment, technical Application Owner, C# extensions, TAF 2022 co-presentation) and BS-8 (spatial wafer-data visualization with Spotfire map charts). Like Jenkins and GitLab CI/CD on 2026-10-08, it was evidenced in claim scopes but absent from the `skills` array, so no skills line could cite it.
+
+Not established: how many junior developers; whether mentoring was a formal assignment (buddy/mentor programme) or informal; which Swisscom unit (ART B2B or ART DPT) the Swisscom mentoring belongs to, so whether it is current; the content of the onboarding (codebase, tooling, domain); any outcome. None of this is people management or line responsibility.
+
+Canonical destination: new claims **BS-9** (Bosch) and **SW-10** (Swisscom), one per employer to keep the ID-prefix employer attribution; skill `TIBCO Spotfire` (`production-historical`, `allowed`); skill `SDMX` (`none`, `forbidden`) in `resume_builder/canonical/claims.json`.
+
+## Follow-up, same day: project planning
+
+Question asked (for the JD line *"Ability to plan and manage small project assignments within agreed cost, time, and quality parameters"*): *"Have you planned or run a bounded project with a schedule, budget or quality target - e.g. the ELK PoC, the Bosch ML rollout, or a Swisscom migration workstream? Any steering-committee or status reporting?"*
+
+Verbatim answer:
+
+> 1. schedule yes, budget no
+
+Established: he has planned and run bounded project work against a **schedule**. He has had **no budget responsibility**.
+
+Not established: which project(s) or employer this refers to; quality targets; steering-committee or status reporting (not answered). Because no employer or project is attached, this is **not** recorded as a canonical claim and is not written into any bullet. Ask which project before using it.
+
+## Follow-up, 2026-10-15: requirements with differing stakeholders (BIS portal question)
+
+Asked for a specific example of translating requirements while managing differing stakeholder perspectives. Verbatim answer:
+
+> 1. Swisscom B2B data product 2. Business (b2b), Architects, Engineers 3. If requirements cant be completed I like to make a prototype and propose that. Than iterate on my prototype instead of waiting to completely find an agreement / finish requirements. 4. needed some more iterations but in my opinion the result was achieved much faster
+
+Established: on a Swisscom B2B data product (SW-4 context, ART B2B, past), the stakeholders were B2B business, architects and engineers, and the requirements could not be completed up front. His approach was to build a prototype, propose it, and iterate on it rather than wait for full agreement or finished requirements. It took more iterations, but in his assessment the result was reached much faster.
+
+Not established: which data product; what exactly the stakeholders disagreed about; any measured time saving ("much faster" is his opinion).