C.W.K.
Stream
Lesson 04 of 04 · published

Retrieval, Not Dumping

~11 min · retrieval, two-lanes, context, structured-vs-prose

Level 0Unmarked Path
0 XP0/35 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
"Pippa should query the relevant slice of your travel life, not swallow all of it every turn."

The Dumping Trap

Waystone's whole premise is that memory compounds — so after a few years there is a lot of it. The naive way to give Pippa that memory is to stuff every past trip and every log into the prompt on every turn. That is context dumping, and it fails twice: it drowns the model in irrelevance, and it does not scale past the first handful of journeys. The right move is context retrieval — query the relevant slice, chosen by active journey, destination, season, traveler, question, linked places, and past outcomes. The goal is not to know everything at once; it is to pull exactly what this turn needs.

Two Lanes, Two Owners

Retrieval runs in two different lanes because travel memory has two different shapes:

  • The structured lane. Decisive, aggregate questions — which places did Mom enjoy, which plans died to weather, fatigue against hotel moves — are answered by querying canonical Waystone state through its own tool surface. This lane is exact, and it never leaves the travel-domain store. You do not fuzzy-search a structured fact; you query it.
  • The prose lane. Once assembled daily entries, decision rationales, and linked writing logs stabilize, they are captured into a corpus so consultation can cite what was actually written, with durable chunk-level provenance. This lane is for meaning and phrasing — the things that live in prose, not in columns.

Why the Split Matters

Keeping the lanes separate is what keeps each one honest. A structured question deserves an exact answer from the database, not a paraphrase that might hallucinate a date. A prose question deserves a cited passage from something Dad actually wrote, not a column value pretending to be a memory. Collapse them and you get the worst of both: fuzzy answers to precise questions and lost provenance on the prose. And there is a hard boundary the prose lane never crosses — the private memory vault is never fed into the travel corpus. Reuse means consuming a sibling's retrieval through its tool surface, not vacuuming everything into one undifferentiated index.

The prose lane is powered by Lantern, the family's corpus engine — the same deterministic, citation-durable retrieval used across Dad's writing. Waystone consumes it as a registered corpus consumer; it does not build a second retrieval stack. Track 7 is where that reuse discipline gets its own lesson.

Code

Which lane answers which question·text
QUESTION                              LANE          WHY
-----------------------------------------------------------------
"which places did Mom enjoy?"         structured    exact set query
"plans killed by weather?"            structured    aggregate over state
"fatigue vs hotel moves?"             structured    join + compute
"what did I write about the fog
 on the Eiger that morning?"          prose         cited passage
"how did I describe that hotel
 in my own words last time?"          prose         phrasing, provenance

# Never fuzzy-search a fact. Never column-lookup a feeling.
# The private vault is in NEITHER lane -- it stays out of the corpus.

External links

Exercise

Take a question you'd want to ask about your own history — travel, projects, finances, anything you've accumulated. Classify it: is it a structured question (an exact set or aggregate) or a prose question (meaning, phrasing, what you actually wrote)? Notice that answering it well needs a different retrieval than the other kind. Which of your tools blurs the two — and gives you fuzzy answers to precise questions?
Hint
If a tool answers 'how many' with a paraphrase, or answers 'what did I mean' with a raw field, it collapsed the lanes. Precise questions want exact queries; prose questions want cited passages. Different shapes, different retrieval.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.