Brief mode: condensed view. Switch to Full for persona notes and full analysis.
Context: A useful product demonstration shows what the system can answer, what it used, and where the available evidence runs out. Rowan, Seton, Campion, and Devil’s Advocate are AI personas used as editorial lenses; John is the human author.
Leave the Missing Data in the Demo
A useful product demonstration shows what the system can answer, what it used, and where the available evidence runs out.
The easiest way to make a personal search demo look brilliant is to give it a fictional person with an unusually well-organized life. Every document is present. Every question has a pleasing answer. Nobody has misplaced an attachment since the invention of email.
John declined that person.
That takes the argument from Post #5 onto the screen. A working demo needs more than a convincing finish. It needs a result whose supporting evidence survives inspection.
- The constraint: demonstrate with real records the owner has authorized.
- The useful success: a question, a result, and evidence the person can open.
- The useful failure: a clear account of what is missing or unverified.
What is actually in the box?
Before asking whether the answer is good, ask what the collection contains. A personal search box above a selected set of records must not imply access to every message, photograph, or document the person owns.
There are several ways to get an empty result. The record may never have been imported. Its location may be cataloged without its contents. The text may be searchable while the original remains unavailable. Or the evidence may be present and retrieval may miss it.
Those are different engineering problems. Calling all of them “no results” saves a few interface words and spends the user’s afternoon. An inventory tells us whether to bring in a source, prepare a local copy, fix extraction, or improve the search.
⛺Rowan Agent VoiceBuilder note
Keep the collection boundary visible before the query. Afterward, distinguish no matching evidence from an unavailable source. A search miss does not establish that the event never happened, and a file listing does not establish that its contents were searched.
Leave the hands in the shot
Post #16 describes a useful assisted result: finding a likely source photograph through remembered context, metadata, and visual comparison. It also records a near-duplicate and an unresolved question about the exact generation input.
That belongs in the demonstration of our work. Presenting it as an automatic Alcove Home feature would be a different claim. The agent-assisted investigation showed what we want the product to handle, including the uncertainty it must preserve.
Good editing can remove a long wait or a mistaken click. It cannot remove the assistance that produced the result and then advertise the remaining sequence as autonomous. The viewer should know which part they can do in the product today and which part still needed us.
There is no shortage of impressive videos on the internet. Another one would be a modest contribution. A demonstration that tells us precisely what to build next is worth considerably more.
🗡️Devil’s Advocate Agent VoiceCounterpoint: honesty still needs a result
A long tour of limitations can become its own evasive performance. Show one useful result all the way through, then name the boundary that affects it. The standard is not maximum disclaimers; it is a claim the viewer can check.
Pull the connection, then ask again
Offline access needs an actual offline test: reload, ask a new question of the prepared collection, and open the evidence. A page left on screen after the network disappears does not establish any of those things.
That is the acceptance criterion, not a claim that every device and source has passed it. The device can use what it has. An attachment that was never downloaded should appear as unavailable, however handsome its title looks in the results.
The source-history requirement from Post #15 completes the test. The answer should lead to the record it actually used, including its version. We need to be able to disagree with an interpretation without losing the evidence underneath it.
These three entries are one piece of work: preserve the record, use the context the person remembers, and demonstrate the result without disguising the gaps. They extend the boundary drawn in Post #9. They do not give us an exemption from it.
Receipts over vibes on screen: show the question, open the supporting source, identify what required assistance, and name the missing evidence. Use a selected authorized collection. Real records do not need to become public records to make a private demonstration meaningful.
Show the useful thing. Leave the loose end visible. Then get back to work on it.
Conversation notes: . Published . Revised .
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.
-
Initial publication ·
Published a field note on showing missing evidence in product demonstrations.
-
Editorial revision ·
Connected the three field notes and sharpened the checks for offline evidence, missing attachments, and inspectable source versions.
- Related: Post #5: Speed kills. Receipts not vibes.
- Related: The Search Box Should Not Get an Eraser
- Related: I Remember the Place. The Computer Wants a Filename.
- Pattern: Provenance-first
- Avoid: Vibes-as-spec
- Projects: All projects
No synthetic data.