Urgent.News

What's breaking now, across thousands of outlets.

Tech

GDPR Article 22's "right to an explanation" is an engineering requirement in disguise

Every time Article 22 comes up, the same argument starts. Lawyers debate what "meaningful information about the logic involved" is supposed to mean, and engineers start reaching for SHAP plots. I think both camps are overcomplicating it. I've been on the receiving end of this requirement — fintech, hiring tools, the usual suspects — and what actually gets you in trouble is never "the model is a…

Every time Article 22 comes up, lawyers debate the meaning of "meaningful information about the logic involved," while engineers rush to SHAP plots. However, the true difficulty lies not in the model being a black box, but in the inability to locate the specific decision in question. The right to an explanation under Article 22 requires that you can locate the decision, reconstruct its inputs, and provide a human-readable explanation.

This involves retrieving the decision for that particular person on that date, ensuring the inputs are accurate, and explaining the outcome in simple terms. The explanation must be understandable without technical jargon and must be recorded in a tamper-proof manner. Teams often struggle to locate the relevant data, and without a proper audit trail, the process becomes futile.

The core issue is not technical but organizational — ensuring each automated decision is treated as a first-class, immutable event, with inputs and explanations recorded and preserved. The challenge is retrofitting auditability into existing systems, which can be a significant undertaking. To test compliance, pick an automated decision from last week and determine if you can produce all necessary information for a regulator's review. If you can, the system is on the right path.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Cheaper HMI Is Costing You More: A TCO Breakdown for Engineers

Every procurement cycle hits the same wall. The membrane switch assembly quotes at a fraction of the panel PC price. The spreadsheet says “option A.” The line engineer says “option B.” Someone in…

  • Membrane switches suffer from drift-induced quality loss over time.
  • Membrane switch panels risk obsolescence with limited supplier alternatives.
  • Panel PCs reduce changeover time by up to 67% compared to membrane switches.

Nothing dead — giving every experiment a decision date

A system that only adds will eventually be mostly additions. That sounds obvious and is easy to forget in practice. An optional tool gets merged "for now"; a pilot document stays a pilot; a flag…

  • "Nothing dead" rule prevents accumulation of unused experiments
  • Every experiment, flag, tool, document, and code path must go ahead or be retired by a decision date
  • Systematic registry tracks experiments, owners, start and decision dates, and consumer status

Turn a Live Q&A Transcript Into a Lesson and Recap With Python

If you run a community, a course, or even a team office hour, you probably record live Q&A sessions. Then the recording sits there. Nobody rewatches an hour of video.

  • Python script automates turning live Q&A transcripts into lessons and recaps
  • Transcript parsed into questions and answers using regex and file handling
  • Best answer identified as longest answer for lesson creation

More from Friday 20 November →