Description

Guests:

🎙️ Lukas Bromig - Co-CEO & Founder at UniteLabs (Munich), building infrastructure for AI-ready labs

👩‍🔬 Hosts: Sura Hadi & Mike Ouren

🎧 Episode Title:

“Standardization Before Intelligence: Building the AI-Ready Lab Stack”

AI is moving fast - but labs are still stuck in the interface gap.

In this episode, Lukas Bromig joins Helical Brew to explain why standardization is the real bottleneck before AI can safely and reliably run anything in the lab.

If every instrument speaks a different protocol, orchestration becomes faith-based. If your workflows live inside black boxes, AI can generate intent — but it won’t generate executable reality.

We break down what “AI-ready” actually means, why “just integrate it” is a dangerous phrase, and why the future lab needs an operating system — not another stack of point solutions.

🎯 What You’ll Learn

• The “non-controversial” standard labs still argue about endlessly (and why).
• Why Bluetooth/USB-level interoperability doesn’t exist in labs (yet).
• The 3 layers of standardization: device interface → data structure → workflow language.
• Why most automation projects stall because of just a few instruments.
• What “AI-ready” means in practical terms inside the lab (not the boardroom).
• Why AI-generated code is often pseudocode that won’t run — and what fixes that.
• Where AI should NOT execute in robotics workflows (and why you need a “compiler layer”).
• Why “no black boxes” + full visibility is the core requirement of a Lab OS.
• How buyers can force change: making open interfaces a procurement requirement.

💡 Picks of the Week

🧠 Lukas — Claude Code for rapid prototyping + fountain pens (bring handwriting back)

🧰 Mike — SLAS Boston + Passport to Prizes (win a trip to SLAS Europe Vienna 2026)

👩‍🔬 Sura — Making interoperability + ownership a first-class requirement in lab design

👇 Discussion Prompt

If AI exposes weak foundations faster than it creates new capability…what should labs standardize first: device protocols, data structures, or workflow language?

Drop your take — we’ll pin the best answers.

🎬 Chapters

00:00 – Cold Open: Standardization Before Intelligence

00:18 – Welcome to Helical Brew + Introducing Lukas Bromig

01:10 – Icebreaker: The lab standard that shouldn’t be controversial

03:00 – Why every instrument interface is different

05:05 – “Just integrate it” is a dangerous phrase

07:10 – The black box problem in lab automation software

10:00 – Rebuilding the same integrations over and over

13:10 – Why standardization is the real bottleneck

15:30 – The three layers of lab standardization

19:10 – Data structure vs data format (why context matters)

22:40 – Why AI-generated SOP code doesn’t actually run

26:10 – The missing compiler layer: validation + error handling

29:40 – Why AI should never directly control instruments

32:30 – What a real Lab Operating System enables

36:10 – Scientists vs automation engineers: future roles

39:40 – Standardization without killing flexibility

43:00 – Procurement leverage: demanding open interfaces

46:00 – Infrastructure decisions that matter in 5 years

49:10 – Picks of the Week

53:20 – SLAS Boston, UniteLabs & Wrap-Up

🔔 Subscribe to Helical BrewWe explore the intersection of AI, automation, and the future of science.Subscribe →    / @helicalbrew  

📩 Want to promote or be a guest? helicalbrew@gmail.com

🌐 Easy link hub: helicalbrew.com

📍 TikTok/IG + more: @helicalbrew

📌 SHORTS (Quick Clips from the Episode)

▶️    • Why Lab Automation Still Has No “Bluetooth...  

▶️    • Where AI Should NOT Touch Your Lab Robots ...  

#HelicalBrew #AIThoughtLeaders #LabAutomation #AIReadyLab #LabInformatics #ScientificSoftware #Robotics #AutomationEngineering #Interoperability #OpenAPIs #DigitalTransformation #AIinBiotech #SystemsEngineering #SLAS #FutureOfScience #ai #podcast #viralvideo #viralshorts