<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Socio-Technical AI | Jason S. Lucas</title><link>https://www.jasonslucas.com/tag/socio-technical-ai/</link><atom:link href="https://www.jasonslucas.com/tag/socio-technical-ai/index.xml" rel="self" type="application/rss+xml"/><description>Socio-Technical AI</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.jasonslucas.com/media/icon_hu_1b2044c02ce09a43.png</url><title>Socio-Technical AI</title><link>https://www.jasonslucas.com/tag/socio-technical-ai/</link></image><item><title>Position: Breaking the Dual Curse of Multilingual AI Requires Socio-Technical Guardrails, Not Post-Hoc Alignment</title><link>https://www.jasonslucas.com/publication/conference-paper-dual-curse-multilingual/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.jasonslucas.com/publication/conference-paper-dual-curse-multilingual/</guid><description>&lt;p&gt;&lt;strong&gt;Position:&lt;/strong&gt; Multilingual AI safety cannot be retrofitted through post-hoc alignment. We identify a &lt;strong&gt;dual curse&lt;/strong&gt; in current systems and argue for socio-technical guardrails built in from pre-training.&lt;/p&gt;
&lt;p&gt;Key contributions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dual Curse documented&lt;/strong&gt;: Harmful content generation rises to &lt;strong&gt;35% in low-resource languages&lt;/strong&gt; (vs. 1% in English), while instruction-following capability declines sharply across the same languages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Systematic review of 207 studies&lt;/strong&gt;: Reward models achieve only &lt;strong&gt;49–50% accuracy in low-resource languages&lt;/strong&gt; — equivalent to random chance — undermining post-deployment safety pipelines.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Socio-technical prescription&lt;/strong&gt;: Pre-training interventions, &lt;strong&gt;community-led harm specification&lt;/strong&gt;, and multilingual evaluation metrics that balance security and usability jointly, rather than trading one off for the other.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Call to action&lt;/strong&gt;: Treat multilingual safety as a first-class design constraint, not a downstream patch applied through RLHF or filtering.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>