Added English to the Korean-only concept fields — subtitle, probes, failure modes
The owner is here to study real English, and Concept Atlas + AI Camp had several study fields in Korean only — the subtitle, the self-attack probes, and the failure modes. The main explanation already had English (rawEn/explainEn), but these did not. Added real-workplace-English versions for all 202 cards and render them alongside the Korean.
The owner's whole reason for the platform is studying English, so a field that's Korean-only is dead weight to him. Auditing the concept cards: the main explanation already had English counterparts (rawEn to say, explainEn to expand), but three fields were Korean-only — the subtitle, the self-attack probes (the questions to answer), and the failure modes (concepts). He couldn't drill those out loud.
A translation pass over all 202 cards produced English in the register he'll actually use: probes phrased the way a senior interviewer asks the question out loud ("When does p99 matter more than the average?", "If p99 spikes, what's the first thing you look at?"), and failure modes the way an engineer says what breaks ("You watch average latency and miss a p99 outage", "No TTL, so stale data just sticks around forever"). Subtitles became crisp English labels.
Added optional fields (subtitleEn, probesEn, failureModesEn) so existing data kept compiling, integrated by id with the same discipline as before — html.unescape, JSON-safe values, insert after each card's probes array applied right-to-left — and both pages now show English first with the Korean beneath. The self-attack header changed to "say the answer in English" to make the drill explicit.
The takeaway for a bilingual study tool: audit which study fields are missing the target-language side, not just whether translations exist somewhere. Here the primary explanation was bilingual but the questions and failure modes weren't — and the questions are exactly what he needs to answer in English.