Embedding Pipeline Service  ·  View 04 of 22  ·  People and journeys

Journey — Find What I Just Wrote

The journey the platform runs millions of times a day, and the moment in it that is a structural problem wearing a UX costume.

Editable source SVG draw.io All views
Knowledge worker 3 M monthly active Goal — Get back to the page I edited an hour ago, by searching for what I remember writing in it Trigger — A half-remembered phrase, and no memory of which space the page is in Done when — The page appears with today's wording, and the citation opens at the paragraph that matched 1 · Edit in the editor 2 · Wait unknowingly 3 · Search ◆ moment of truth 4 · Judge ◆ moment of truth 5 · Open What they do Rewrites a section Closes the tab Types the phrase Scans the snippets Clicks a citation What the platform does Change event accepted Interactive lane Chunk diff: 3 of 41 Embed + index Query embedded Hybrid top-50 ACL filter applied Staleness returned Offset resolved How it feels Trusts it Unsure Gives up Where it hurts No signal it is indexing Old wording still matches Snippet is a fragment with no context What answers it 30 s p50 interactive lane Atomic version visibility Content-hash diff: only 3 chunks re-embedded Heading path carried on the chunk Offsets retained at extraction Journey — Find What I Just Wrote The trough is phase 4: a correct result the reader cannot interpret. Both answers to it are structural, decided at extraction and chunking. v 1.0 · owner Data & AI Platform Architecture · date 2026-10

The trough, and what answers it

  • The dip is at phase 4: the result is correct and the reader cannot interpret it. A snippet that is one paragraph with no heading above it looks like the wrong document.
  • Both answers are structural and both are decided before any retrieval happens — offsets preserved at extraction, and the heading path carried on the chunk.
  • The second pain, old wording still matching, is the atomic-visibility requirement: a half-reindexed document is worse than a stale one.

What the platform promises here

  • Interactive lane: the edit is retrievable at p50 30 s, p95 2 min, p99 10 min (stated assumption).
  • Retrieval p50 45 ms, p99 180 ms in-region for a hybrid top-50 over a tenant partition.
  • Every response carries the document version and a staleness indication, so the surface can tell the reader when it is behind.

What it does not promise

  • Nothing in the editor tells the user that indexing is in progress. That is a product gap this architecture enables an answer to and does not supply.
  • Phase 2 assumes the user does not watch. If a product adds a "search as you type in the same session" surface, the freshness budget it needs is a different conversation.
◀  Actors and Their Core Journeys All views Journey — Ship a New Corpus  ▶
Solution Architecture v1.0 · open source, self-hosted on Kubernetes · Data & AI Platform Architecture · 2026-10 · 22 views · 17 architecture decision records04-journey-find-what-i-wrote