corrected

Summary

The result wearing a different provenance: the dish the user named, not the one the photo suggested.

Raw wireframe

• .context/designs/mobile/scan/corrected.html

Why it is drawn this way

Its own file, not a state of result. corrected is not a word the closed state set can name — it is not empty, loading, error, offline or locked.

The badge is on the dish and never on a row. A whole-dish correction is about what the dish is. Each row was still re-derived by the model and keeps its own honest mark — the butter is something the camera could not see whatever the plate is called. See confidence.

The rows really are different rows. Naming the dish re-derives every component, which is the whole value of the correction and the thing correct-dish warns about before the button rather than after it.

It cost nothing, and the card says so. No image is re-sent, so this is the same shape of call as answering a question. A correction that spends a scan is a correction nobody makes — and then the log is wrong and the user is out of pocket.

A correction is not a dead end. The dish name is an editable field and "Still wrong? Re-estimate" goes back to correct-dish.

No scan meter at the foot. billing-transparency puts the meter on every screen that can take money; this one cannot, because the scan was spent before it rendered.

Related

• result
• correct-dish
• confidence
• billing-transparency

Sources

• .context/designs/mobile/scan/corrected.html