<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Renest — field reports</title>
    <link>https://renest.ai/Blog.html</link>
    <description>Real measured runs on real hardware, failures included.</description>
    <language>en</language>
    <item>
      <title>Every file verified, environment still dead: the host-side failures</title>
      <link>https://renest.ai/verified-files-not-a-working-environment.html</link>
      <guid isPermaLink="true">https://renest.ai/verified-files-not-a-working-environment.html</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <category>Mechanisms</category>
      <description>Every file came back checked and the app still would not run: a GPU newer than the packed kernels, a CPU missing avx2, a driver too old. What we check now.</description>
    </item>
    <item>
      <title>The pack we verified that no clean machine could restore</title>
      <link>https://renest.ai/same-machine-verification-trap.html</link>
      <guid isPermaLink="true">https://renest.ai/same-machine-verification-trap.html</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <category>Self-reports</category>
      <description>A pack that verified on the machine that made it failed to install on a clean one: half its lock came from the OS image. What same-machine checks prove.</description>
    </item>
    <item>
      <title>Right vendor table, wrong install path: how our driver check turned away good machines</title>
      <link>https://renest.ai/driver-floor-wrong-install-path.html</link>
      <guid isPermaLink="true">https://renest.ai/driver-floor-wrong-install-path.html</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <category>Self-reports</category>
      <description>Our pre-check rejected machines that worked: the driver floor came from the right vendor table for the wrong install path. Three corrections, one measured fix.</description>
    </item>
    <item>
      <title>Same GPU, two images: the CPU vendor decided which one came back</title>
      <link>https://renest.ai/cpu-vendor-decides-identical-images.html</link>
      <guid isPermaLink="true">https://renest.ai/cpu-vendor-decides-identical-images.html</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <category>Field reports</category>
      <description>One archived ComfyUI workflow, same-model GPUs: regenerated images split into two byte-identical groups, and the host's CPU vendor decided which. Aug 2026.</description>
    </item>
    <item>
      <title>A 23GB video nest, and the exact boundary of 'identical'</title>
      <link>https://renest.ai/field-report-vol-3.html</link>
      <guid isPermaLink="true">https://renest.ai/field-report-vol-3.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Field reports</category>
      <description>Same GPU model: the regenerated video is literally the same file. Different model — even same architecture: a uniform ~0.94 plateau. And the 0.9814 mystery is solved: it was the CPU vendor.</description>
    </item>
    <item>
      <title>A real workflow survives its first exam — and two clean conclusions get caveats</title>
      <link>https://renest.ai/field-report-vol-2.html</link>
      <guid isPermaLink="true">https://renest.ai/field-report-vol-2.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Field reports</category>
      <description>A workflow with 3 custom nodes and a LoRA is captured and revived intact — including a node that was already broken — while new data forces honest revisions to Vol. 1.</description>
    </item>
    <item>
      <title>Pack once, revive anywhere: 26 restores across 2 clouds for $1.21</title>
      <link>https://renest.ai/field-report-vol-1.html</link>
      <guid isPermaLink="true">https://renest.ai/field-report-vol-1.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Field reports</category>
      <description>We packed one ComfyUI + SDXL environment, destroyed the machine, and revived it 26 times across 2 clouds, 7 datacenters, and 6 GPU types — every copy verified byte-for-byte.</description>
    </item>
  </channel>
</rss>
