UnGathered Names the Things That Have Not Been Collected

UnGathered begins with the part of a collection that is easiest to overlook: the things that have not been gathered. A folder can look substantial because it contains many files. That visual impression says very little about whether the particular companions needed for a job are present.

The name fits the direction of the search. A normal listing starts with the files on disk and shows them to you. UnGathered starts with selected items and declared expectations, then asks which checks fail. The missing drawing receives a name in the report even though there is no drawing file to list. An empty inspection record can receive attention without pretending that its filename proves the work was recorded.

The tool is not meant to guess the unwritten checklist. Its first release makes the checklist explicit in a JSON manifest. That choice keeps the conclusion inspectable: the report identifies the item, requirement, expected path and outcome, so a reader can see why it was flagged. If an expectation is wrong, it is possible to correct the rule rather than argue with an unexplained score.

There is room for several kinds of collection under that simple idea. A manufacturing pack and an article asset folder need different companions, while sharing the same operation: select an item, expand its expected paths and check the declared conditions. The quick start is intentionally small. One incomplete pack is enough to see what the name is getting at.