Sorting a library nobody ever filed

VergeLabs Library → Folders.

The Folders screen #

One screen, in four steps (a fifth, Rename, is shown greyed out for later). You can skip any of them.

Propose folders asks the AI service for a tree and costs 10 credits, said on the button before you press it. Plan my folders builds a tree from what the described pictures show and costs 30 credits plus 15 per 100 labels. Neither changes anything on its own: you read the tree, edit it, and only then confirm it with This is my tree.

Propose and apply are separate steps, always.

Confirming profiles the folders your draft says nothing about: the first 100 folders are free, then it is 1 credit per 6 folders. When it costs anything, the price is on the button.

Re-filing the pictures into a confirmed tree costs no credits: every described picture already carries the vector the search box compares against, so "which folder does this belong in" is arithmetic, not a model call.

Folder talk #

Change the proposal by saying so:

drop nature, I want buildings, split into modern and classic

The instruction, the conversation so far, your folder names with their parents and counts, and what the AI wrote about your pictures go to the service, which returns a revised folder plan. No pictures are sent.

Applying is bound to the plan you were shown, for fifteen minutes, once. You read the difference before anything changes, and the thing you approved is the thing that happens.

Undo #

A fill can be undone from the Fill step, for a day. Undoing removes what the fill did and nothing else, and a file you moved yourself since then stays where you put it.

Nothing that cannot be interrupted #

Filling works in slices, and a job larger than one pass finishes in the background and remembers where it got to. Close the tab and pick it up.

Nothing here deletes a picture. A folder that goes away is a term that goes away; the files in it are re-filed, not removed.

Auto-file on upload #

A described file has an embedding. A folder full of described files has a middle. So "which folder does this belong in" is arithmetic, not a model call — and it is free.

Suggesting is the default. A newly uploaded file gets a suggestion you accept or dismiss.

Filing itself is earned, per folder. A folder may only file on its own after five accepted suggestions, and one dismissal takes the permission away again. Five rather than three because the two errors do not cost the same: a suggestion nobody wanted is a click, and a file that moved itself into the wrong folder is somebody hunting for it.

Two more guards:

• A margin. The nearest folder has to be meaningfully nearer than the one behind it (1.25×). "Two of your folders would both do" is a real answer, and the right thing to do with it is nothing.
• A reach. A file too far from every folder centre gets no suggestion at all.

The per-folder ledger lives in term meta (_vergeml_autonomy); the centroid lives beside it (_vergeml_centroid).

Say what you want, in words #

Move the screenshots into Products.

Typed into a box, doing what it says. Four rules govern it, and none is negotiable.

1. An allowlist of four verbs — move, tag, rename, create. Delete is not on it, and there is no delete in the file to reach. "Delete the unused ones" is answered with a refusal naming the four verbs, not with an apology and certainly not with a deletion.

2. Nothing runs from the sentence. Parsing produces a plan; the plan is shown with the actual files it would touch and a count; running takes the plan, never the text. A sentence that resolved to four thousand files says four thousand before it says anything else.

3. The text stays data. It is matched against a vocabulary built from your own folders and smart folders. It is never evaluated, never interpolated into SQL, never used as a callback name. What the parser cannot match, it refuses.

4. Hand-written fields are never overwritten. Renaming applies to folders. A file's own title, caption and alt are somebody's writing, and nothing here writes to them.

The parser is deterministic, small, and local — it makes no outbound request. It is filterable via vergeml_nl_parse, so a model can be put in front of it without any of the four rules moving: whatever produces the intent still has to name a verb from the allowlist and a selection the plugin can resolve, and it still cannot run anything.

Folders built from what was found #

Separately from all of the above, the tree grows a group of folders drawn from the index rather than from anything you filed — Photos, Screenshots, Documents, Logos, pictures with people in them, pictures with text in them. Empty ones are hidden, and the group says how much of your library it covers. See Smart folders.