Capture Then Assemble

"Leave the fragments while you move. Make sense of them when you stop. Two jobs, two postures, two moments."

Two Phases, Not One

Waystone splits travel logging into two deliberately separate phases, because they have completely different demands. In motion: leave a useful breadcrumb in seconds — fast, cheap, no interpretation, Pippa silent. At the hotel: let Pippa help assemble those breadcrumbs into coherent events, route changes, decisions, and draft prose — slower, richer, interpretive, Pippa prominent. Trying to do both at once is the classic mistake: it makes capture too heavy for the field and assembly too shallow for the evening. Keeping them separate lets each be good at its own job.

Assembly Proposes, It Doesn't Overwrite

The evening phase — "Assemble Today" — starts a Pippa consultation over the day's breadcrumbs, itinerary, routes, and previous journey context. Pippa proposes: cluster these three fragments into one cable-car event, split that into morning and afternoon, promote this crumb to a decision, draft a narrative for the day. But here is the discipline that connects back to the whole memory thesis: the original breadcrumbs remain immutable evidence after assembly. The structured events and the prose draft link back to their source breadcrumb IDs; they do not replace or edit them. Assembly is interpretation layered on top of evidence, never a rewrite of it.

Why the Separation Is the Design

This two-phase shape is why the mobile surface opens on the capture stream and not the planning conversation, and why Pippa is quiet in the field but prominent at the hotel. The interaction budget of a person walking in the rain and the interaction budget of a person sitting down with tea after dinner are not the same, and pretending they are produces a tool that serves neither. Capture is optimized for speed and survival; assembly is optimized for meaning and coherence. The engine respects that these are two different moments in a traveler's day — and builds a different surface for each.

Code

Two phases, two postures·text

PHASE 1 -- IN MOTION (capture)
  goal:     get the fragment in, in seconds
  Pippa:    silent; latency never blocks
  output:   immutable breadcrumbs (evidence)

PHASE 2 -- AT THE HOTEL (assemble)
  goal:     make sense of the day
  Pippa:    prominent; proposes clusters, events, drafts
  output:   structured events + prose, LINKED to crumb ids
            (the crumbs stay immutable underneath)

# Assembly is interpretation ON TOP OF evidence.
# It never edits or replaces the original breadcrumbs.

Exercise

Think about how you currently capture and then process something — notes into a summary, photos into an album, tasks into a plan. Do you try to do both at once (and end up doing neither well), or is there a real 'capture fast now, make sense later' split? What would change if the raw captures stayed immutable and the processed version just linked back to them?

Hint

The tell of a collapsed two-phase is that you either over-process in the moment (too slow to capture) or never process at all (fragments pile up unread). Separating them — fast immutable capture, later linked interpretation — lets each phase be good at its own job without corrupting the other.