<?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>My Daily Logs on My Hugo Project</title><link>https://ostensible-paradox.pages.dev/en/categories/my-daily-logs/</link><description>Recent content in My Daily Logs on My Hugo Project</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 21 May 2026 03:20:06 +0800</lastBuildDate><atom:link href="https://ostensible-paradox.pages.dev/en/categories/my-daily-logs/index.xml" rel="self" type="application/rss+xml"/><item><title>Why mealy machine, Why?</title><link>https://ostensible-paradox.pages.dev/en/posts/the-death-of-the-mealy-machine/</link><pubDate>Thu, 21 May 2026 03:20:06 +0800</pubDate><guid>https://ostensible-paradox.pages.dev/en/posts/the-death-of-the-mealy-machine/</guid><description>&lt;p>Why did the Mealy machine linger for so long?&lt;/p>
&lt;p>It was the first formal object that perfectly encoded a core obsession, and because of that, it became impossible to let go of—even long after its utility had expired.&lt;/p>
&lt;p>The digital trail of drafts and planning sessions reveals this reluctance. In the preparation notes, the verdict was clear:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>§3.2 Mealy notation | M = (Q, Σ, Δ, δ, λ, q₀) | Drop
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>App A.1 | Theorem 1 + Mealy proof | Drop
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>It was marked for deletion. Even the prism agent had pointed out the redundancy: &lt;em>&amp;ldquo;The Mealy machine result is simply the zero-cut special case of the static certificate&amp;rdquo;&lt;/em>—strictly weaker, less general, and less rigorous than what followed. Yet, like a ghost in the machine, it kept reappearing. It haunted &lt;code>2026jan.tex&lt;/code>, lingered on &lt;code>Desktop/cc.tex&lt;/code>, and found its way back into the AIES submission. Every attempt to excise it failed; it kept surviving.&lt;/p></description><content:encoded><![CDATA[<p>Why did the Mealy machine linger for so long?</p>
<p>It was the first formal object that perfectly encoded a core obsession, and because of that, it became impossible to let go of—even long after its utility had expired.</p>
<p>The digital trail of drafts and planning sessions reveals this reluctance. In the preparation notes, the verdict was clear:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>§3.2 Mealy notation | M = (Q, Σ, Δ, δ, λ, q₀) | Drop
</span></span><span style="display:flex;"><span>App A.1 | Theorem 1 + Mealy proof | Drop
</span></span></code></pre></div><p>It was marked for deletion. Even the prism agent had pointed out the redundancy: <em>&ldquo;The Mealy machine result is simply the zero-cut special case of the static certificate&rdquo;</em>—strictly weaker, less general, and less rigorous than what followed. Yet, like a ghost in the machine, it kept reappearing. It haunted <code>2026jan.tex</code>, lingered on <code>Desktop/cc.tex</code>, and found its way back into the AIES submission. Every attempt to excise it failed; it kept surviving.</p>
<p>The truth is that the Mealy machine was never really about AI liability. It was about a personal epistemic preoccupation. It formalized the exact structural boundary that defines every paper in the bibliography:</p>
<table>
  <thead>
      <tr>
          <th style="text-align: left">Paper</th>
          <th style="text-align: left">The Obsession, Dressed Differently</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td style="text-align: left"><strong>ccModel / 2026jan</strong></td>
          <td style="text-align: left">Mealy machine: $\lambda$ is non-injective $\to$ no decoder exists from outputs to states.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>Double Certificates</strong></td>
          <td style="text-align: left">$\varepsilon_{\text{state}}^{\text{UB}}$: a cut-set bound on the leakage of hidden-state information to public traces.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>cascade/paper</strong></td>
          <td style="text-align: left">Epistemic boundary: demonstrating that output-only review cannot reconstruct internal execution states.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>POPL d-separation</strong></td>
          <td style="text-align: left"><code>Reachable</code> as a <code>Prop</code>-value versus <code>StaticRoute</code> as a $\Sigma$-type—showing how reachability conceals a structure that must be decompiled.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>Liability Paradox</strong></td>
          <td style="text-align: left">The fundamental claim that no finite sequence of observations can uniquely determine an internal state.</td>
      </tr>
  </tbody>
</table>
<p>The attraction was never to automata theory itself, but rather to that precise, visceral moment when observation fails to reconstruct cause. The Mealy machine was the simplest, most elegant caricature of that failure: a closed box with hidden gears where turning the crank produces outputs that could have been generated by multiple, incompatible internal configurations.</p>
<p><img alt="A closed box with hidden gears" loading="lazy" src="/images/mealy-machine/hidden-gears.jpg"></p>
<p>But the tragedy of the Mealy machine was its simplicity. It could only yield a blunt, binary verdict—non-injectivity leading to undecidability—when the actual goal was a graded, constructive, and decompilable account of epistemic loss.</p>
<p>That is what the POPL paper finally achieves. It replaces hand-waving claims about the impossibility of state recovery with a mechanical witness extractor. Through the well-founded measure of <code>route_improves_of_bad</code>, the <code>StaticRoute</code> witness extractor, and the <code>dSeparated_iff_dSeparates</code> bisimulation, the POPL paper represents the Mealy machine fully grown.</p>
<p>Keeping the Mealy machine around was a lingering attachment to the object that first made this obsession legible. But legibility is not the same as rigor. The POPL paper marks the transition to a proper formal home—moving from automata theory to causal graphs, from prose proofs to Lean 4, and from binary undecidability to explicit witness extraction.</p>
<p>The Mealy machine had to die so that <code>route_improves_of_bad</code> could live.</p>
]]></content:encoded></item></channel></rss>