<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Release on UnGathered.com</title>
    <link>https://ungathered.com/tags/release/</link>
    <description>Recent content in Release on UnGathered.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ungathered.com/tags/release/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UnGathered Finds Missing Companions in Local Collections</title>
      <link>https://ungathered.com/ungathered-finds-missing-companions-in-local-collections/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ungathered.com/ungathered-finds-missing-companions-in-local-collections/</guid>
      <description>&lt;p&gt;The inspection record is the sort of file nobody notices until somebody needs it. A product folder can contain drawings, notes and several revisions of a specification, while still lacking the one document needed to release a job. UnGathered starts with that awkward possibility. Its first release checks local collections against explicit rules and reports the companions that are missing or fail their declared checks.&lt;/p&gt;&#xA;&lt;p&gt;A small JSON manifest supplies the expectations. It selects items, such as one directory per product, and names the files each item needs. A rule can require a nonempty drawing, a directory for supporting material or a line of credit text inside an article. The scanner handles file and directory anchors, expands companion paths and keeps each result visible in text, JSON or a self-contained HTML report.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
