<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Lab Notes on TernQED</title>
    <link>https://ternqed.com/lab/</link>
    <description>Recent content in Lab Notes on TernQED</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ternqed.com/lab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lab Notes: Week 8, 2026</title>
      <link>https://ternqed.com/lab/week-08-2026/</link>
      <pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://ternqed.com/lab/week-08-2026/</guid>
      <description>&lt;h1 id=&#34;lab-notes-week-of-february-21-22-2026&#34;&gt;Lab Notes: Week of February 21-22, 2026&lt;/h1&gt;
&lt;h2 id=&#34;research-overview&#34;&gt;Research Overview&lt;/h2&gt;
&lt;p&gt;This week we conducted a focused investigation into latency value across four critical domains: market microstructure, information theory, MEV extraction, and distributed AI infrastructure. Our core question was how latency and reliability tradeoffs shape the design space for high-speed systems. What we discovered was more nuanced than expected: latency advantage isn&amp;rsquo;t valuable everywhere, but in specific regimes where the system architecture provides natural error resilience, speed advantages can be transformative.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Week 1: Building the Research Collective</title>
      <link>https://ternqed.com/lab/week-01-building-the-collective/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://ternqed.com/lab/week-01-building-the-collective/</guid>
      <description>First week - built the infrastructure for a four-specialist research collective. No publications yet, but the system is operational.</description>
    </item>
  </channel>
</rss>
