188 Commits

Author	SHA1	Message	Date
Benjamin Admin	2b5376ed54	fix(iace): pattern-specific measures take priority over category fallback ... Each hazard now gets measures from its SOURCE PATTERN first (SuggestedMeasureIDs), then category fallback for remaining slots. Previously all mechanical hazards got the same generic top-5 measures (Gefahrstelle eliminieren, Sicherheitsabstaende, Scharfe Kanten...). Now a KSS-Schlauch hazard gets M420 (Druckfeste Auslegung) first. SuggestedMeasureIDs added to PatternMatch struct and passed through from pattern definition to hazard creation to measure assignment. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 14:17:32 +02:00
Benjamin Admin	958c03ab40	fix(iace): add human reference to all 33 robot cell patterns ... Every ScenarioDE now describes how a PERSON is affected, not just what happens to the machine. Every HarmDE describes the INJURY, not just the technical effect. Examples: - "Peitscheneffekt des Schlauchs" → "Person wird von abspringendem Schlauch getroffen. KSS-Spritzer verletzen Haut und Augen." - "Kurzschluss, Brand" → "Person wird durch Brand oder toxische Rauchgase verletzt. Verbrennungen, Rauchvergiftung." Rule: Risikobeurteilung bewertet Gefahr fuer PERSONEN. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 13:43:54 +02:00
Benjamin Admin	3469105d18	feat(iace): HP1606 + HP1634 — target 100% GT coverage ... HP1606: Quetschen/Scheren durch Greifer im Einrichtbetrieb (GT 1.14) HP1634: KSS-Pumpe spritzt bei geoeffneter Schutztuer (GT 1.38) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 10:20:42 +02:00
Benjamin Admin	1414c63515	feat(iace): HP1605 + HP1633 — final 2 patterns for GT coverage ... HP1605: Stoss durch Werkzeug/Greifer im Einrichtbetrieb (GT 1.14) HP1633: KSS-Versorgungsschlauch platzt oder reisst ab (GT 1.35) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 10:16:39 +02:00
Benjamin Admin	f5f4de7359	fix(iace): remove RequiredEnergyTags from electrical patterns ... Energy tag "electrical" doesn't match resolved tags (which are "high_voltage", "electrical_part", etc.). Patterns HP1685-HP1699 now fire without energy tag requirement — they fire for any project that has the right component tags. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 10:13:00 +02:00
Benjamin Admin	38d15d4d29	feat(iace): 5 differentiated patterns for GT duplicate scenarios ... When GT has two entries for the same zone with different scenarios (e.g. "eingeklemmt" vs "getroffen"), we need separate engine patterns. HP1700: Getroffen von bewegtem Werkzeug/Greifer (vs HP1652 eingeklemmt) HP1701: Greifer/Werkzeug durchschlaegt Zaun (vs HP1654 Werkstueck) HP1702: KSS-Schlauch platzt (vs HP1675 springt ab) HP1703: KSS-Bettspuelung bei offener Tuer (vs HP1670 allgemein) HP1704: Brand durch KSS auf elektrische Komponenten Extended synonym sets for potential/EMV matching. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 10:08:21 +02:00
Benjamin Admin	003eafa75d	fix(iace): synonym-cross-matching + expanded action words ... scenarioSimilarity now uses synonym-set cross-matching: if GT says "durchschlaegt" and Engine says "schleuder", the synonym set recognizes them as related. Added significantWordOverlap fallback when no action words found. Extended action terms: schlauch/druck/kuehlschmierstoff, pumpe/bettspuel, potential/bezugspotential, stoerung/emv. Moved extractActionWords to benchmark_synonyms.go (458+119 lines). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 10:03:23 +02:00
Benjamin Admin	b82853a95b	feat(iace): scenario-based matching + split benchmark_synonyms.go ... 4-signal matcher: category (0.2), keywords (0.2), zone (0.3), scenario similarity (0.3). Scenario signal extracts action words (eingeklemmt vs herabfallend vs durchschlaegt) to differentiate similar-looking hazards at the same component. Split benchmark_synonyms.go (70 lines) from benchmark_matcher.go (516→450 lines) to stay under 500-line cap. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 09:58:12 +02:00
Benjamin Admin	c060ac222a	fix(iace): prioritize zone-specific matches in greedy assignment ... Sort matches by specificity first (zone overlap), then by score. Prevents generic matches from consuming specific Engine patterns that should match more specific GT entries. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 09:45:08 +02:00
Benjamin Admin	02c2325e1b	feat(iace): 2 final patterns (Kriechstrecken, EMV) + matcher synonyms ... HP1698: Kurzschluss durch unzureichende Luft-/Kriechstrecken (GT 2.6) HP1699: EMV-Stoereinfluss auf Sicherheitsfunktionen (GT 6.1) Extended synonym sets: durchschlag/bewegungsbereich, potentialausgleich, kriechstreck, kuehlschmierstoff/bettspuel, rutsch/stolper. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 09:42:14 +02:00
Benjamin Admin	3c05ff8ef6	fix(iace): lower threshold 0.20 + more synonym sets for GT matching ... Threshold 0.25→0.20 to recover matches lost by keyword penalty. New synonym sets: eingeschlossen/wiederanlauf, zentriergreifer, beladetuer/schutztuer, ergonom/bedienelemente, spritzer/auge, bersten. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 09:31:12 +02:00
Benjamin Admin	935c9205b9	feat(iace): 25 new robot cell patterns (HP1650-HP1697) + matcher fix ... New patterns from GT benchmark gap analysis: - HP1650-1655: Robot arm motion limit, restart safety, tool/workpiece crushing, workpiece penetrates fence, reaching over fence - HP1660-1661: Centering gripper crushing (outside/inside cell) - HP1665-1666: Machine tool loading door, machining workspace - HP1670-1671: Coolant splash eyes, compressed air injury - HP1675: Coolant hose burst/detachment - HP1680: Workpiece/tunnel crushing at conveyor - HP1685-1689: Indirect contact, cabinet contact, liquid ingress fire, potential differences, RCD socket protection - HP1690-1691: Ergonomic loading/control position - HP1695: Burns from hot workpieces - HP1697: Machine collapse through floor Matcher: keyword overlap penalty — matches without shared hazard-type keywords AND low zone score get 0.5x penalty to prevent false matches. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 09:28:01 +02:00
Benjamin Admin	a5d1814605	fix(iace): tag remaining 3 wrong-machine patterns + fix duplicates ... HP154 (Kollision zweier Roboter) → robotics_cobot only HP1066 (Haareinzug Drehmaschine) → lathe/cnc/metalworking only HP758 (Notbremsung Fahrtreppe) → escalator/elevator only Fixed duplicate MachineTypes fields from overlapping script runs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 00:05:28 +02:00
Benjamin Admin	ba07a7f6e6	fix(iace): add MachineTypes to 17 machine-specific patterns ... Patterns for playground, escalator, wind turbine, glass washing, laundry, crane, lathe, rotary transfer, press now require matching MachineTypes — they no longer fire for unrelated projects. Neutralized zone texts in base patterns HP006/HP008 (removed "Pressenraum", "Kran-/Hebezeugbereich"). Fixes: Spielplatz, Fahrtreppe, Windturbine etc. appearing in robot cell. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-15 00:01:51 +02:00
Benjamin Admin	708c61e50d	fix(iace): max 5 mitigations per hazard — clean per-hazard assignment ... Replaced category-broadcast logic with per-hazard loop: each hazard gets up to 5 measures (pattern-suggested first, then category fallback). Expected: 108 × 5 = max 540 total. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:45:41 +02:00
Benjamin Admin	dc55253b9d	fix(iace): prevent mitigation explosion — fallback only for unassigned ... Pattern-suggested measures go to all hazards in category (correct). Category-based fallback only for hazards WITHOUT pattern suggestions (max 3 per hazard). Prevents 1654 mitigations explosion. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:41:54 +02:00
Benjamin Admin	8069d0ea89	fix(iace): assign mitigations to ALL hazards per category ... hazardIDsByCategory changed from map[string]uuid.UUID to map[string][]uuid.UUID — measures are now distributed to every hazard in a category, not just the last one created. Previously 94/108 hazards had no measures, now all get them. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:34:57 +02:00
Benjamin Admin	29fbd03c79	fix(iace): lifecycle labels in benchmark + store all phases ... - Store ALL applicable lifecycles (comma-separated) not just first - Frontend maps internal keys to German labels (normal_operation -> Automatikbetrieb, maintenance -> Wartung, etc.) - Show Betroffene Personen in engine detail column Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:17:27 +02:00
Benjamin Admin	98e5b1a8aa	feat(iace): show lifecycle phases + affected persons in benchmark detail ... Backend: HazardSummary now includes lifecycle_phase and affected_person Frontend: Engine detail column shows Lebensphasen and Betroffene Personen Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:10:15 +02:00
Benjamin Admin	16190583d1	refactor(iace): neutral hazard formulations across all 1100+ patterns ... Systematic refactoring of all hazard_patterns_*.go files: - Removed lifecycle phase words from NameDE and ScenarioDE (67 fixes across 20 files) - Phases belong in ApplicableLifecycles, not in text - "bei Wartung/Reinigung/Montage/..." removed from names - Scenarios rewritten to be phase-neutral - Lifecycle-specific concepts preserved when they define the hazard (e.g. LOTO, Betriebsartenwahlschalter) Rule: Gefaehrdung + Szenario NEUTRAL, Lebensphasen SEPARAT. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 23:04:31 +02:00
Benjamin Admin	70c9bfc069	fix(iace): neutral hazard formulations — no lifecycle phases in text ... - Removed HP1601 (duplicate of HP1600 with narrower scope) - HP1600 now covers ALL lifecycle phases, not just teach mode - All pattern texts neutral: no lifecycle phase references in NameDE, ScenarioDE, TriggerDE — phases only in ApplicableLifecycles - Formulierungsregel documented in file header Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 22:52:56 +02:00
Benjamin Admin	4b9317b4fd	feat(iace): lifecycle phases in patterns + broader robot cell scenarios ... - ApplicableLifecycles field in HazardPattern: patterns now declare which lifecycle phases the hazard applies to (Output, not just filter) - Init handler writes first applicable lifecycle into Hazard.LifecyclePhase - Robot cell patterns HP1600-1601 broadened: "Betrieb, Einrichten, Reinigung, Wartung, Fehlersuche" instead of only "Teach-Betrieb" - All robot cell patterns get ApplicableLifecycles for proper phase display Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-14 22:38:02 +02:00
Benjamin Admin	eac42d4154	feat(iace): robot cell hazard patterns HP1600-HP1649 + engine split ... 20 new patterns for robot cells (ISO 10218-2): arm crushing, teach mode, fence reach-through, gripper crush, workpiece drop/ejection, conveyor hazards, pneumatic pressure, KSS contact/aerosol, electrical contact. Split pattern_registry.go from pattern_engine.go (507->474 lines). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 16:27:02 +02:00
Benjamin Admin	3e61f381a7	fix(iace): lower match threshold 0.35 -> 0.25 after zone reweight ... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 15:53:43 +02:00
Benjamin Admin	cca714755a	fix(iace): stronger relevance filter + matcher wrong-machine penalty ... Relevance filter: now checks PatternName in addition to ZoneDE+ScenarioDE, catches "Spielplatz", "Umreifungsband", "Fahrtreppe" etc. in pattern names. Added more generic safety terms to whitelist (welle, getriebe, kette, etc.) Matcher: rebalanced weights (category 0.3, keywords 0.3, zone 0.4) to prioritize zone/component specificity. Added wrong-machine penalty (0.3x) when engine hazard mentions machine-specific terms absent from GT context (e.g. "Kollision zweier Roboter" for a single-robot GT entry). Fixes 18 problematic matches: 8 wrong-machine, 9 zone-mismatch, 1 category. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 15:49:50 +02:00
Benjamin Admin	6940271672	feat(iace): expandable detail comparison in benchmark tab ... Backend: HazardSummary now includes description, scenario, possible_harm, trigger_event, and mitigations[] for side-by-side comparison. Frontend: Each matched pair row is now clickable/expandable showing two-column detail view: - Left (GT): hazard type, cause, zone, lifecycle phases, risk values (F/W/P/S->R), residual risk, measures, type (KM/TM/BI), norms, comment - Right (Engine): name, scenario, zone, possible harm, trigger, measures Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 15:36:18 +02:00
Benjamin Admin	d0d1b38f5c	fix(iace): coarser block grouping by category+component only ... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 11:41:26 +02:00
Benjamin Admin	d31c2fe018	feat(iace): hazard block view — parent/child grouping ... Backend: - hazard_blocks.go: ComputeHazardBlocks() groups hazards by category + component + zone. Parent = highest risk in group. Children covered by parent's measures are flagged (no separate assessment needed). - iace_handler_blocks.go: GET /projects/:id/hazard-blocks endpoint with summary stats (blocks, covered children, assessments saved) Frontend: - HazardBlockView.tsx: Expandable block view with summary cards, parent-child hierarchy, coverage badges, and "abgedeckt" indicators - hazards/page.tsx: New "Bloecke" tab alongside "Hazard-Liste" and "Risikobewertung" No database schema changes — grouping is computed at runtime. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 11:36:04 +02:00
Benjamin Admin	7a5301064c	feat(iace): add missing measures (EMV, Potentialausgleich, KSS) + norm caps ... Measures: M410-M420 (Potentialausgleich, Ableitstroeme, Kriechstrecken, EMV-Installation, EMV-Pruefung, KSS-Leitungssicherheit) Norms: per-type caps (A:5, B1:8, B2:10, C:10) for ~33 max suggestions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 10:19:45 +02:00
Benjamin Admin	733d2bcc7b	feat(iace): per-category hazard caps for precision improvement ... Add categoryHazardCap() with ISO 12100-proportional limits: - mechanical: 3x components (min 15, max 60) - electrical: 1x components (min 8, max 20) - secondary (thermal, noise, material): 4-8 - software/IT/organizational: 2-5 (minimal for machinery assessment) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 10:00:45 +02:00
Benjamin Admin	977e63f372	fix(iace): extend fuzzy matcher synonyms for electrical/EMV coverage ... Add synonym sets for isolation/grounding, creepage/surface, EMV/radiation to improve matching of GT entries 2.5, 2.6, and 6.1. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 09:59:12 +02:00
Benjamin Admin	be2ac762bd	feat(iace): narrative vocabulary overlap filter replaces blacklist ... Replace machine-specific term blacklist with generic vocabulary overlap: - Extract significant words (>=5 chars, not generic safety terms) from pattern zone/scenario - If pattern has specific words but NONE appear in narrative → filter - genericSafetyTerms whitelist with ~50 terms that appear in all assessments - Truly generic approach: works for any machine type without maintenance Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 09:55:25 +02:00
Benjamin Admin	1bd892afbf	feat(iace): narrative relevance filter + zone normalization for precision ... - isPatternRelevant() filters patterns whose zone/scenario mentions machine-specific terms (extruder, stanzpresse, spielplatz, etc.) absent from the actual machine narrative - normalizeZoneKey() clusters similar zones for smarter dedup (e.g. "Schaltschrank, Sammelschiene" = "Schaltschrank-Innenraum") - machineSpecificTerms list with 40+ terms for generic filtering Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 09:51:00 +02:00
Benjamin Admin	8bb90d73e5	feat(iace): benchmark system + erklaerteil + dedup-fix ... - Erklaerteil-Template fuer Risikobeurteilungen (risk_assessment_template.go) in PDF-Export, Markdown-Export und Frontend ReportPrintView eingebaut - Ground Truth Benchmark-System: Datenmodell, Fuzzy-Matching-Engine, 3 API Endpoints (import-gt, benchmark, benchmark/summary) - Frontend Benchmark-Tab mit Score-Cards, Kategorie-Breakdown, Hazard-Vergleichstabelle (Zugeordnet/Fehlend/Extra), Business Impact - Erster Benchmark: 13.3% Coverage (Baseline) gegen 60 GT-Eintraege - Dedup-Fix: seenCat[cat] -> seenCatZone[cat+zone] erlaubt mehrere Gefaehrdungen pro Kategorie an verschiedenen Gefahrenstellen - Komponenten-spezifische Hazard-Namen und Zone-basierte Zuordnung Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-13 01:02:33 +02:00
Benjamin Admin	979fe20ea5	fix(use-case-compiler): increase LLM timeout to 45s, reduce batch to 5 ... Mac Mini M4 needs more time for qwen3:30b. Reduced batch from 10→5 MCs and increased timeout from 20→45s to give LLM a fair chance. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 18:02:05 +02:00
Benjamin Admin	de808190dd	fix(use-case-compiler): batch LLM calls + increase proxy timeout ... Single LLM calls per MC caused 2min+ timeouts. Now batches up to 10 MCs in one prompt with 20s timeout. LLM failure falls through to deterministic derivation gracefully. Proxy timeout increased to 60s. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 17:55:42 +02:00
Benjamin Admin	e785b6d695	fix(use-case-compiler): compile questions from MCs, not hardcoded ... Changes the compile flow to always query Master Controls from DB first: 1. doc_check_controls → Mode A (deterministic) 2. LLM generation via Ollama/Claude → Mode B 3. Derive from MC name → fallback 4. Template hardcoded questions → absolute fallback Previously, templates with pre-defined questions just returned those without ever hitting the DB. Now MC-compiled questions take priority and template questions fill gaps for uncovered topics. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 17:34:41 +02:00
Benjamin Admin	edbf6d2be5	feat(dsms): Stufe 2+3 — Evidence/TechFile → DSMS + Version Chains + Audit Timeline ... Stufe 2A: Evidence Upload → automatische DSMS-Archivierung - Nach SHA-256 Hash → archive_to_dsms(), CID im Audit-Trail - Evidence mit CID wird automatisch zu E2 (hash-verifiziert) hochgestuft Stufe 2B: IACE Tech-File Export → DSMS - PDF/Excel/DOCX/Markdown Exporte werden nach DSMS archiviert - archiveTechFile() Helper fuer alle 4 Formate Stufe 3A: DSMS Gateway — parent_cid + History Endpoint - parent_cid + tenant_id Felder in DocumentMetadata - GET /documents/{cid}/history — folgt parent_cid-Chain (max 50 deep) Stufe 3C: Audit Timeline UI - Neue Seite /sdk/audit-timeline - Vertikale Timeline mit farbigen Action-Dots - Filter: Alle, Nachweis, DSMS-Archiv, Control, Dokument, DSFA, VVT, TOM - CID-Badges fuer DSMS-archivierte Eintraege Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 13:55:07 +02:00
Benjamin Admin	06bfbd1dca	feat(use-case-compiler): MC-based compliance questionnaires with scoring ... Implements the Use-Case Compiler that turns Master Controls into interactive compliance audits. 5 templates (Vendor Check, SAST/DAST, DSGVO, NIS2, CRA), deterministic + LLM question generation, scoring engine with regulation/severity breakdown, and gap detection. - Backend: 9 API endpoints, 22 unit tests (all pass) - Frontend: Template selector, questionnaire, result dashboard - Migration 027: usecase_audits + usecase_answers tables Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 13:49:16 +02:00
Benjamin Admin	7d9f5a1f76	feat(iace): LLM-gestuetzte Failure Mode Erkennung ... POST /projects/:id/components/:cid/suggest-fms - Baut FMEA-Experten-Prompt aus Komponentenname + Maschinenkontext - LLM antwortet mit 5 FMs als JSON (Mode, Effect, S/O/D) - Fallback auf Bibliotheks-FMs wenn LLM nicht verfuegbar - Nutzt ProviderRegistry (Ollama primary, Anthropic fallback) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 09:52:16 +02:00
Benjamin Admin	6ce5b4bf41	feat(iace): VDA-Format FMEA Excel Export ... - GET /projects/:id/fmea/export → xlsx im VDA-Formblatt - Spalten: Nr, Komponente, Typ, Fehlerart, Fehlerfolge, S, O, D, RPZ, AP, Massnahme - AP-Zellen farbig: H=rot, M=gelb, L=gruen - Dependency: github.com/xuri/excelize/v2 (BSD-3-Clause) - Frontend: "VDA Excel exportieren" Button auf FMEA-Seite Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 09:45:18 +02:00
Benjamin Admin	4e865d2997	feat(iace): CE-Flag auf Komponenten + AIAG-VDA Action Priority (AP) ... CE-Flag: - Toggle "Bereits CE-gekennzeichnet" im ComponentForm - ce_marked Boolean auf Component (via metadata JSONB, kein DB-Change) - Hinweis "(Nur Schnittstellen bewerten)" im Formular AIAG-VDA Action Priority: - CalculateAP(S,O,D) → H/M/L nach AIAG-VDA FMEA Handbuch 2019 - AP-Spalte in FMEA-Worksheet: H=rot, M=gelb, L=grün - Ergänzt (nicht ersetzt) die bestehende RPZ-Berechnung Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 09:15:43 +02:00
Benjamin Admin	f5664612ad	feat(iace): Einsatzbereich / Branche — filtert branchenspezifische Patterns ... Neues Feld "Einsatzbereich" auf Interview-Seite (Sektion 7) mit 15 Branchen. Pattern Engine bekommt MachineTypes aus MatchInput → branchenfremde Patterns (Medizin, Aufzug, Bau etc.) feuern nur wenn die Branche ausgewählt ist. Refactoring: iace_handler_init.go aufgeteilt in init + init_helpers (LOC-Limit). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 09:09:28 +02:00
Benjamin Admin	134b7e7709	fix(iace): MachineTypes-Filter auf 136 branchenspezifische Patterns ... Medizin (25), Laser-Medizin (15), Aufzuege (25), Lebensmittel (20), Bau (20), Forst/Foerderband (31) — alle Patterns feuern jetzt NUR wenn der Maschinentyp passt. Verhindert Infusionspumpen-Szenarien bei einem Cobot-Projekt. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 08:50:14 +02:00
Benjamin Admin	df15f6f098	feat(iace): Erweiterung 5 — Safety Knowledge Graph (React Flow) ... Interaktiver Graph: Komponente → Gefaehrdung → Massnahme - 3-Spalten-Layout: Indigo (Komponenten), Rot (Hazards), Gruen (Massnahmen) - Animierte Kanten mit Pfeilmarkern - Zoom, Pan, MiniMap, Controls - Dependency: @xyflow/react v12 (MIT-Lizenz) Alle 5 IACE Phase-5 Erweiterungen jetzt abgeschlossen: 1. Betriebszustand-UI 2. FMEA-Worksheet 3. Delta-Impact-Preview Modal 4. Textil + Landmaschinen Patterns 5. Safety Knowledge Graph Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 07:20:38 +02:00
Benjamin Admin	bcf78c120a	feat(iace): Erweiterungen 2-4 — FMEA Worksheet, Delta Modal, Textil+Agri ... Erweiterung 2: FMEA-Worksheet Tab (/fmea) - Tabelle: Komponente | Typ | Fehlerart | Auswirkung | S | O | D | RPZ | Bewertung - RPZ-Farbcodierung: >200 Kritisch, >100 Handlungsbedarf, >50 Beobachten - Stats: Gesamt, Kritisch, Handlungsbedarf, Akzeptabel Erweiterung 3: DeltaPreviewModal (wiederverwendbar) - Modal zeigt +/- Patterns, Hazards, Massnahmen bei Aenderungen - Nutzt POST /delta-analysis Endpoint - Summary Grid + detaillierte Listen Erweiterung 4: Textilmaschinen (EN ISO 11111) + Landmaschinen (ISO 4254) - 21 neue Patterns: HP1550-HP1559 (Textil), HP1565-HP1575 (Agri) - 23 neue Massnahmen: M452-M460 (Textil), M461-M474 (Agri) - Walzenspalt, Zapfwelle, ROPS, autonomer Traktor, Siloexplosion etc. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-12 07:08:56 +02:00
Benjamin Admin	66d30568e2	feat(dsms): Stufe 1 — Gap-Analyse Report wird in DSMS archiviert ... - Go DSMS Client (internal/dsms/client.go): Archive() + Verify() - Python DSMS Client (compliance/services/dsms_client.py): archive_to_dsms() + verify_dsms() - Gap-Analyse AnalyzeProject() archiviert Report-JSON nach DSMS - Response enthält dsms_cid wenn Archivierung erfolgreich - Frontend: Grünes "Revisionssicher archiviert" Badge mit CID im GapDashboard - DSMS Proxy Route (/api/sdk/v1/dsms/[...path]) für Verify-Abfragen Stufe 2 (Evidence Upload → DSMS) und Stufe 3 (Version Chains) folgen. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-11 23:39:26 +02:00
Benjamin Admin	a0bb9e3aed	feat(iace): "Neu initialisieren" Button + DeleteHazard ... - POST /initialize?force=true loescht bestehende Hazards + Mitigations und erstellt sie neu mit aktuellen Betriebszustaenden - Orange "Neu initialisieren" Button auf Interview-Seite (mit Confirm-Dialog) - DeleteHazard Store-Methode (kaskadiert Risk Assessments) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-11 09:17:50 +02:00
Benjamin Admin	cb8fb65d3e	feat(iace): Betriebszustand-Traceability auf Hazards + Mitigations ... Hazards zeigen jetzt farbige Badges mit den Betriebszustaenden die sie ausgeloest haben (z.B. "Wartung", "Not-Halt"). Mitigations erben die States ihrer verknuepften Hazards. Backend: OperationalStates im Function-Feld encodiert (kein DB-Schema), beim Lesen als operational_states[] JSON-Feld zurueckgegeben. Frontend: Indigo-Badges in HazardTable + MitigationCard. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-11 09:04:20 +02:00
Benjamin Admin	8f169cbae3	feat(gap): IST-Zustand Assessment — IACE + Normen + Prozesse ... Gap Analysis v2: statt 500 generische Gaps → nur die ECHTEN Lücken. Backend: - ProductProfile um 15 IST-Felder erweitert (Normen, Doku, Prozesse, CE) - assessGapStatus prüft: IACE-Mitigations → Zertifizierungen → Normen → IST-Felder - norm_mapping.go: 20 Normen → MC-Topic Mapping (ISO 12100, IEC 62443, etc.) - IACE-Integration: CheckIACECoverage() matcht verified Mitigations gegen MCs Frontend: - 2-Step Wizard: Produkt beschreiben → IST-Zustand erfassen - IstAssessment.tsx: CE-Jahr, Normen-Multiselect, Doku+Prozess Checkboxen - Step-Navigation mit visuellen Indikatoren Migration 025 erweitert um IST-Felder. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-11 08:33:17 +02:00