Example report
This is a fictional archive and an illustrative report, not a measured model evaluation. Scores show the kind of output to expect.
The archive
old-work/
garden-sensor/
design-notes.md
enclosure.stl
backup/garden-sensor/
design-notes.md
enclosure.stl
workshop-organizer/
sketches.md
prototype-notes.txt
tutorials/
starter-project/
The owner's profile values original designs and unfinished tools, and lists Garden sensor as a known project.
A review queue
| Score | Action | Folder | Why |
|---|---|---|---|
| 94 | review | /garden-sensor | Design notes and a model suggest an original hardware prototype. |
| 86 | review | /workshop-organizer | Substantial prototype notes may belong to an unfamiliar personal project. |
| 83 | review | /backup/garden-sensor | A possible copy worth comparing before choosing a source. |
| 18 | skim | /tutorials | Appears to be learning material; check for original modifications. |
The unknown workshop-organizer project could also appear in novel.md. The duplicate report would group the two garden-sensor folders if their relative filenames and sizes match. Both remain in the review queue: that metadata does not establish that their contents are equal.
Follow the evidence
Read the source notes, inspect the STL, compare candidate copies, and decide which material belongs in your preservation workflow. ArchiveTuna supplies leads and context. It does not choose a canonical copy or move/delete files.
For actual results, begin with your first inventory.