Only-Copy Interlock

A NAS skill that decides whether a cleanup is allowed to run.

Cleanup tools count files. Storage dashboards count bytes. Duplicate finders count copies. None of them answers the only question that matters before a deletion: after this runs, does anything become the last copy?

Only-Copy Interlock builds a coverage map of the library, simulates the proposed operation against it, and returns one of four outcomes: ALLOW, WARN, BLOCK or UNEVALUABLE. On a block it names the loss in the terms a person actually experiences it: this person, this event, this album. It also says whether the recycle bin still holds a recoverable copy.

The setup that makes it different

A copy count is not a loss. Three files of one photograph look like three photographs right up until two of them go. So the skill resolves content identity first (checksums, the library's duplicate index), then attributes that identity to person albums, object and pet albums, dated events and timeline buckets. Loss is then computed per protected entity, not per file, and never averaged: one lost person is a block regardless of how many other people survive.

Recovery is counted separately from coverage. The recycle bin is capacity, not a copy, and if the operation would empty it, a single remaining copy inside it counts as zero.

Why the thresholds are fixed

The decision rules live in the package, not in the conversation: two live copies, or one live copy plus recovery the operation does not remove. A verdict that can be argued into a pass is not a verdict. Unreadable scope returns UNEVALUABLE, and an unevaluable result is never treated as safe.

Why this belongs on a NAS, locally

The verdict requires the whole library at once: every checksum, every album membership, every face group. That is a local computation over private data, and it is exactly the thing you cannot ship to a cloud service. Only the final verdict leaves the device.

Built with the UGREEN AI NAS capabilities: files and checksums, the duplicate index, file tags, photo albums with person and timeline attribution, knowledge save, and the file workflow for the approved operation only.

Status

The skill package, the coverage model, the verdict format and the disclosures are complete. It passes the official checker with zero errors and zero warnings. Runtime validation on a real NAS, and face and album field verification, are the next steps on the assigned test day.

Disclosures: no third-party components are bundled. AI tools used in authoring: Claude and Codex for drafting and static checks.

Built With

Share this project:

Updates

Submission history