What this is

The review screen: the photo itself, the names Recued matched in it, and the line it wrote — together, so a wrong name or a wrong sentence is something you can see rather than take on trust.

This is the only place a wrong attribution gets caught. Nothing else compares the names against the picture, and the next step after this sends the picture to the people named.

The photo is read live, never copied

The picture is read from where it sits each time you open this, and Recued keeps no copy. Move or rename it and this says so, rather than showing a thumbnail that is quietly out of date.

Correcting the line

The box opens with the line already in it, so fixing one word means fixing one word. Press Save and the correction is kept.

Saving an unchanged line changes nothing — not the wording, and not who is recorded as having written it. (Emptying the box keeps the line too; there is no way to leave a photo with no line at all.)

⚠ What actually protects a line you wrote is marking the photo ready. An approved photo is never rewritten. A photo you corrected but left unapproved still counts as waiting, so re-describing one of the people in it will discard your line and write a fresh one — deliberately, because the reason to re-describe somebody is that their name changed, and your line names them under the old one. If you have fixed the wording, mark it ready in the same visit.

Ready to send?

Three choices, not a tick box, and deliberately:

• leave as it is — the default, so opening this screen and pressing Save never

changes whether a photo is ready.

• yes, ready — the photo and its line are approved for everyone recognised in it.
• no, hold it back — returns it to the pile for another look.

A tick box could not tell "I did not touch this" from "no", so simply opening a photo would have quietly un-approved it.

Who was matched, and how closely

The table lists each person and their distance — lower is a closer match. Two names may be two people, or one face that resembled two people on your roster, and the picture above is how you tell which.

Leaving a photo out

Skipping releases everyone waiting on it and nothing is sent. The record stays, so a re-scan will not offer it again.

Not offered to an AI

This screen is kept out of the chat and MCP tool catalog. Approving a photo is the decision to send someone their picture, and it belongs to a person looking at the picture.

It used to share that job with two smaller recipes — one that approved a photo by id, one that rewrote its line. Both are retired: this screen does what they did, with the photo in front of you, and two ways to do one thing is how they drifted apart (one of them stamped when you decided; the other did not).

What that flag is, exactly: it means an AI is never handed this as a tool. It is not an authorisation boundary — a caller that already knows the recipe's name can still reach it through the generic runner. What actually stops an AI here is the approval gate: driven from an AI, every write this screen makes pauses for the owner first. Both together are the point; neither alone is the whole answer.

When you last decided

Marking a photo ready — or holding it back — records the moment you did. Editing the line alone does not: correcting a word is not the same as reaching a verdict, and the two are worth telling apart when you come back to a pile of photos weeks later.

How this photo got here

The dates say when it was scanned, when its line was written, and when you last decided about it — so a photo that has been sitting for weeks is distinguishable from one that arrived this morning. Matched at is the tolerance the scan ran with: a higher number lets more faces through, so a surprising name on a photo matched at a loose tolerance is worth a second look.

A photo you left out shows the reason you gave, so the decision is still legible later.