German Mittelstand AI deployment in 2026 hits two compliance surfaces most US-headquartered AI vendors do not handle out of the box: BetrVG §87(1) point 6 co-determination triggers at the first AI assistant or agent that touches employee work activity (Bundesarbeitsgericht broad interpretation covers any system that captures, processes, or analyses employee work activity, primary purpose immaterial); DSGVO Article 35 + Datenschutzkonferenz Muss-Liste require pre-deployment DPIA for most AI-employee-data deployments. The early-engagement workflow (works council notified at vendor selection, DPIA in parallel with vendor evaluation, joint Betriebsvereinbarung drafting, documented pilot at one team for 60-90 days, broader rollout after pilot review) compresses Mittelstand AI timeline from 12-18 months (late engagement) to 6-9 months.
German-Mittelstand cut of the same labour-relations surface AM-120 covers at multinational scale and OPS-038 at SMB collective-agreement scale. Statutory anchors: BetrVG §1 (Betriebsrat threshold at five permanent employees), §87(1) point 6 (technical equipment monitoring scope), DSGVO Article 35 (DPIA requirement), DSGVO Article 37 (DPO threshold). Bitkom Mittelstand AI study 2025 corroborates compliance-uncertainty bottleneck. Vendor categories: Microsoft 365 Copilot (uneven §87 documentation by region), Notion/ClickUp/Asana AI (US-coded gap), German-native vendors (Aleph Alpha, DeepL Write Pro, SAP Joule) ship native legal-framework documentation.
/holding/OPS-049/Embed this claimiframe + oEmbed
The card auto-updates when the claim's status, last-reviewed date, or correction log changes. Embedders never need to refresh — the card is rendered live from the canonical record.