Collection Checks on UnGathered.com

UnGathered Checks Article Images and Photo Credit Lines

Sat, 24 Oct 2026 00:00:00 +0000

A missing image is often obvious in the browser. A missing credit line can be much easier to overlook, especially when the article itself reads well and the photo has already been selected. The publishing example gives both expectations a place in a local collection rule, before treating a folder of article assets as ready.

The generated collection has two Markdown articles, cafe.md and harbor.md. The manifest selects articles/*.md, expects an image at images/{stem}.jpg and looks for a Photo credit: line followed by text inside each article. Cafe has both. Harbor has neither. One recorded scan by a downloaded UnGathered 0.1.0 binary on Linux x86_64 produces four checks: two present requirements, a missing image and a content_mismatch for the credit rule. There is one complete item, two gaps and no operational errors. The command exits 1.

UnGathered Finds Missing Companions in Local Collections

Sat, 24 Oct 2026 00:00:00 +0000

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.

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.

UnGathered Finds Missing Records in a Manufacturing Pack

Sat, 24 Oct 2026 00:00:00 +0000

Two product folders can look equally ready at a glance. In the generated manufacturing example, alpha has its specification, drawing and inspection record. Beta has a specification and a drawing filename too, but the drawing is empty and the inspection record is absent. A file listing shows plenty of activity. The declared checklist gives a more useful answer.

The example manifest selects directories matching products/* and requires three nonempty regular files inside each one: specification.pdf, drawing.pdf and inspection.csv. In one recorded scan with a downloaded UnGathered 0.1.0 binary on Linux x86_64, two selected items produce six checks. Four pass, one fails with too_small and one with missing. Alpha is complete under those rules; beta is not. The process exits 1, identifying declared gaps rather than an operational failure.

UnGathered Names the Things That Have Not Been Collected

Sat, 24 Oct 2026 00:00:00 +0000

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.

UnGathered Starts With What a Collection Should Contain

Sat, 24 Oct 2026 00:00:00 +0000

A folder listing answers a straightforward question: which files are here? Unfortunately, it cannot tell you which expected files never arrived. That needs another source of information. Someone has to know that a product needs an inspection record, or that an article’s image should have a matching credit line. UnGathered gives those expectations a small, executable form.

The first concept is the anchor. It is an existing item selected by a relative glob: products/* for product directories, for instance, or articles/*.md for article files. Each anchor carries the requirements declared for its collection. With a product directory named products/widget, a path rule such as {item}/drawing.pdf expands to products/widget/drawing.pdf. The rule states the relationship rather than searching vaguely for a similar filename.

UnGathered Tests Gaps Without Hiding Scan Errors

Sat, 24 Oct 2026 00:00:00 +0000

A collection checker can fail in an especially unhelpful way: it can overlook the items it was supposed to check and then announce that everything is complete. UnGathered’s tests therefore pay attention to the route into a result, including anchor selection and errors, rather than only checking a report’s final totals.

The automated tests cover required files and directories, minimum sizes, content patterns, path variables, missing parents and wrong types. They also check deterministic ordering, input preservation, HTML escaping and report output reservation. Empty collections fail by default. A content file above the configured read limit produces an operational error, without matching against a silently shortened prefix.