Travel Is Chronological, Video Is Narrative

"The calendar says what happened when. The edit says what the story is. Do not let either one pretend to be the other."

Two Orthogonal Truths

A trip produces two completely different kinds of truth. Travel is chronological: day 12 came before day 13, the cable car ran before lunch, this is simply what happened when. Video is narrative: the story about the mountains might combine two days and skip a third, because a story is built for meaning, not for the calendar. These two truths are orthogonal, and the most common modeling mistake in travel-to-content tooling is assuming one day equals one video. It does not, and building on that assumption quietly makes half of your real editing impossible.

Many-to-Many, Through Ordered Segments

So Waystone models Days and VideoStories as a many-to-many relationship ordered through StorySegments. One video may span several days; one day may produce several videos. July 12 and 13 become one story; July 14 splits into a morning video and an afternoon video; July 15 through 17 become a fourth. A VideoStory is an editorial grouping — it selects and orders travel truth for a narrative purpose, and it is explicitly independent of calendar-day boundaries. The segments carry the order the editor wants, while the days keep the order that actually happened. Neither overwrites the other.

Where This Ownership Stops

This is also a good place to see the reuse discipline hold under pressure. Waystone owns the travel-to-story lineage: which days, events, places, routes, and media a story draws from, and what got published where. It does not own the production timeline, the renders, or the edit itself — an editing tool owns those. It does not own source-media discovery — that is Recall's job. It does not own the script's prose — that goes to Rekindle. Waystone answers "what did we film in Grindelwald that never made it into a published video?" and then hands off. Lineage, not production.

Code

Calendar truth vs editorial truth·text

TRAVEL (chronological)        VIDEO (narrative)
  July 12  -----------\
  July 13  -----------+------>  Video A  (two days, one story)
  July 14 morning ----------->  Video B  (one day, two stories)
  July 14 afternoon --------->  Video C
  July 15..17 --------------->  Video D

# Day <-> VideoStory is MANY-TO-MANY, ordered via StorySegments.
# 'one day = one video' is the modeling mistake that makes
#   half of real editing impossible.

# Waystone owns: which days/places/media a story drew from (LINEAGE)
# Waystone does NOT own: the timeline, the renders, the prose, the
#   media originals -- those stay with their canonical owners.

Exercise

Think of source material you've turned into something published — photos into a post, notes into an article, footage into a video. Did the published piece map one-to-one onto the source's natural units (one day, one session, one file), or did it recombine them? Now check whether your tools could even represent that recombination, or whether you did the mapping in your head and lost it.

Hint

The recombination almost always happens — and it almost always lives only in the editor's head. If your tool can't record 'this story drew from these three days and skipped that one', the lineage between what you lived and what you published disappears the moment you finish editing.