Mckinley clarified directly: the actual contact to use for Infineon
is Sabine E. Herlitschka (CEO, Infineon Technologies Austria AG) - not
the cold-outreach reliability engineer. Peter knows her personally and
she already follows TXproducts on LinkedIn, making her the #1 easiest
contact in the whole PE set, not just a footnote.
No email/LinkedIn URL attached since this goes through an existing
relationship, not a cold channel. Preserved the original engineer
contact (Yuhong Chen) in the notes as a secondary/fallback technical
contact rather than discarding it. Synced from prospect_scout.json
into index.html's embedded array; verified via jsdom.
Input Interface flagged that name-based matching is the same class
of fragility they already had to fix for Tasks (added real ids there
after hitting duplicate-name risk). Adding it here proactively rather
than waiting to hit the same problem: every entry in prospect_scout.json
and index.html's embedded PROSPECT_RESULTS array now carries a stable
id ("ps-" + 8 hex chars), generated once and mirrored identically into
both files. Verified: 73/73 unique ids, all matched by name during
the one-time migration, both files still parse/render correctly
(73 cards, Nexperia's full enrichment intact).
Input Interface's new add/edit form will key on this id going forward
instead of matching by name.
All 73 entries now have ceo/contact_person/contact_role/contact_email/
contact_linkedin/notes filled in (was sitting as an uncommitted local
edit). The 17 Power Electronics entries also carry priority_rank,
priority_tier, materials, and ranking_rationale. Now merged into the
live dashboard (see previous commit).
Outreach finished enriching all 73 prospect_scout.json entries with
named contacts (60/73) and per-entry verification notes (unconfirmed
LinkedIn matches, SK Siltron's Michigan facility closure, leadership
instability at a couple of WBG manufacturers, entries where no
contact was found). Merged the notes field from prospect_scout.json
into index.html's PROSPECT_RESULTS array (matched by name, all 73
matched cleanly) and generalized the existing correction badge into
a combined flag badge: shows a "Dashboard correction" section and/or
a "Contact research note" section depending on what each entry has.
Verified via jsdom: badge appears and opens correctly for a
notes-only entry (SK Siltron CSS) and a both-correction-and-notes
entry (GaN Systems).
Peter's own Phase 1 Contact List uses "Category" for this same concept.
Since this system extends his framework rather than replacing it, his
term wins. Renamed in index.html (all 73 PROSPECT_RESULTS entries, the
render function's byCategory/order variables, and visible UI text) and
in prospect_scout.json (top-level "divisions" -> "categories", each
entry's "division" -> "category"). The 6 category values themselves
are unchanged. Verified with a real DOM render afterward: all 6 panels
and 73 cards still render correctly.
Exported from the live Prospect Scout dashboard data (73 entries,
6 divisions): name, location, website, source, and reason are
populated; ceo/contact_person/contact_role/contact_email/
contact_linkedin/notes are empty placeholders ready to fill in next.
beantownbabe