What Waystone Is

"It's not an itinerary app. It's the thing that remembers the trip after the trip is over."

The One-Sentence Version

Waystone is an engine that owns your structured travel state — journeys, plans, days, places, routes, recommendations, decisions, and the living record of what actually happened — while the brain that interprets all of it stays somewhere else entirely. Say that split out loud, because it is the whole design: Waystone owns the travel facts; cwkPippa owns the judgment. Everything else in this quest is a consequence of taking that one boundary seriously.

Notice what Waystone deliberately is not. It is not a second Pippa — no soul, no memory vault, no model router of its own. It is not a rich-text editor — long-form prose round-trips to Rekindle. It is not a media archive — binaries stay with their owning system. It is not a map app — the map draws canonical state and stores nothing itself. Strip away everything a sibling already owns, and what remains is the actual product: the travel domain, kept honestly.

The Three Defining Sentences

Waystone's architecture document opens with three sentences, and this whole quest is built to earn them:

Conversation is planning. Structured state is the durable memory of that conversation. Geography is a projection of the same travel state, from globe to footstep.

Each sentence becomes a track. Conversation is planning is Track 2 — you plan by talking to Pippa, not by filling a form. Structured state is durable memory is Tracks 4 and 5 — the plan, the revisions, and the actual journey are preserved separately and captured in the field before any network exists. Geography is a projection is Track 3 — the globe, the journey map, and the place lens are all views of one canonical state, never independent marker databases.

Why an Engine, Not an App

Calling Waystone an engine instead of an app is not vanity. An app is defined by its screens; an engine is defined by what it owns. Screens are replaceable — the mobile capture surface, the desktop plan editor, and the map are all clients of the same travel state. If you defined Waystone by its current UI, you would have to redraw the definition every time a screen changed. Defining it by ownership — trips, days, decisions, lineage — gives you a boundary that survives every redesign. That is the same lens that made Ember an image engine and Bonfire a music engine: the model is the product, the views are output.

Code

The ownership split, in one line each·text

cwkWaystone  ->  journeys, plans, days, places, routes, decisions,
                 planned-vs-actual, travel-log links, map projections
cwkPippa     ->  identity, brain sessions, conversation, model routing,
                 judgment, the Sidekick capability
cwkRekindle  ->  long-form prose bodies and their edit history
cwkRecall    ->  source media + transcript discovery
cwkLantern   ->  deterministic retrieval + citation durability

# Waystone integrates deeply with each sibling.
# Integration never transfers ownership.

Exercise

Take any tool you use for travel — Google Maps saved lists, a Notes app trip folder, a spreadsheet, TripIt. Write one sentence naming what it OWNS versus what it merely displays. Then ask the hard question: when a new trip starts, does last trip's knowledge come with you, or does it vanish into an archive you never reopen?

Hint

If the tool can't answer 'which places did I plan but skip, and why?' across trips, it's an app that displays, not an engine that remembers. That gap is exactly the one Waystone is built to close.

The One-Sentence Version

The Three Defining Sentences

Why an Engine, Not an App

Code

External links

Exercise

Progress

Comments 0