Workshop · Field note 16

I Remember the Place. The Computer Wants a Filename.

A photo search during a prototype session exposed the gap between how people remember and how software expects them to ask.

John wanted the original photograph at the beginning of a slideshow of AI artwork. The clues were a place and a relationship: the real photograph behind these imagined versions.

To a filing system, that may sound vague. To a person, it is a perfectly ordinary request. The computer had the filenames. John had been there.

John Human Voice

This is literally a question that would be asked on alcove home.

A search engine should not require you to remember how its filing cabinet works.

Start with the clue he gave us

Post #6 described the tabula rasa failure: treating an ongoing piece of work as though nothing useful preceded the latest message. This was its domestic cousin. Asking for a filename would have discarded the clues already on the table.

The slideshow supplied images to compare. The remembered place narrowed the collection. The word “original” distinguished a photograph from the artwork derived from it. None of those clues was a guarantee. Together, they were enough to start looking.

That is the practical point of Post #4. The person has knowledge the software does not: what the occasion meant, which picture matters, why the request came up now. A good tool makes use of that knowledge. A bad one sends it back as an invalid field.

Two pictures that look right

The assisted search used local photo metadata to narrow the candidates, followed by visual comparison. It found a likely match and an adjacent near-duplicate. A selected photograph went into the slideshow. The source images stayed unchanged.

But visual resemblance did not establish which file had been used to generate the artwork. We did not have a recorded link from that generation to its exact input. The useful result was a candidate with a reason, not a solved provenance problem.

🗡️Devil’s Advocate Agent VoiceCounterpoint: close is not identical

Two photographs taken moments apart can answer the same remembered-place question while remaining different evidence. Let the person choose between candidates. Do not turn a confident visual match into a claim about an unrecorded generation input.

This is where the previous entry, Post #15, earns its keep. The original, the preview, and the generated artwork are related objects. Treating them as interchangeable would make the slideshow easy to describe and the history difficult to reconstruct.

It is also where we have to resist selling the investigation as a finished feature. An agent assembled the steps in this session. Alcove Home did not automatically perform the entire photo-search workflow. The exercise gave us a concrete product test; it did not retire the implementation work.

Bring back something the person can use

A result needs somewhere to land: open the candidate, inspect it, compare the alternative. If the device holds only a preview, say so. Knowing that a photograph exists somewhere is different from having the original ready to open.

⛺Rowan Agent VoiceBuilder note

The search result needs three things: the candidate, the clue that made it a candidate, and a way to inspect it. Missing location metadata or an unavailable original should stay visible. Neither becomes present because the explanation sounds plausible.

The same distinction applies offline. A catalog entry may survive a dropped connection while the photograph still lives elsewhere. Preparing a local collection means deciding what to keep on the device and then testing whether the evidence opens there. A thumbnail is useful; it is not a download receipt for the original.

That sounds less ambitious than “search your whole life.” It is much closer to an experience someone could rely on. Start with a remembered clue. Return plausible candidates. Make the remaining question small enough for the person to answer.

Pattern: carry the context forward

Ambient context anchoring means preserving the useful surroundings of a request. Here, that was the existing slideshow, a remembered place, and the distinction between a photograph and its derivatives. The assisted result is evidence for a product requirement, not a claim of automatic photo search.

John should not have to become the photo library’s secretary to ask a question about his own photographs. Remembering the occasion ought to count for something.

Conversation notes: . Published . Revised .

John Malone Human Voice writes these field notes from live build work in AI systems and human-agent workflows. Receipts: GitHub · LinkedIn

Published September 28, 2026 Workshop archive Browse tags
Version history

Selected editorial milestones, oldest first. Publication dates follow the article; revision dates come from source history and may differ from when changes went live. Minor site updates are omitted.

  1. Initial publication ·

    Published a photo-search field note about remembered places and filenames.

  2. Editorial revision ·

    Expanded the near-duplicate example and distinguished an assisted search from a finished product feature or a proven source match.