Scatter Into the Past, Scatter Into the Future

"Backdating and pre-dating are first-class capabilities, not repair mechanisms."

The Axis Bends Both Ways

Because there's no container above the date, the date can be anything. You can file a crumb to today, to a day three weeks behind, or to a day next month — and none of these is a workaround. This is the practical payoff of the open timeline, and it splits into two distinct, first-class acts.

Past scatter is retrospective capture. A memory surfaces today that belongs to last Tuesday — the light in a room, a thing someone said, a feeling you didn't have words for at the time. You file it to last Tuesday. You are not correcting a mistake or backfilling a missed day; you are placing a real fragment on the day it belongs to, now that you finally have it.

Future scatter is intent capture. A note to a future self. An event you're anticipating. A question you want to ask yourself when a certain date arrives. You file it forward. It's not a reminder and not a todo — it's a thought planted on the day it's about, waiting there for when that day becomes today.

Direction is meaning, not error. A backward crumb and a forward crumb are two different kinds of intention — remembering and anticipating — and the timeline treats both as normal. The instant you frame backdating as 'fixing' a missed entry, you've smuggled the guilt-journal back in. There is nothing to fix; there is only a day the fragment belongs to.

Filing Is Not Faking

Here's the subtlety that makes scatter honest: filing a crumb to another date never pretends it was written then. The day you assign it (its target_date) and the moment you actually wrote it (its captured_at) stay separate and both true. A memory filed to last Tuesday still records that you captured it today. A note placed on a date next month still records that you wrote it now. The timeline bends; the truth of when you wrote doesn't. That two-truth rule is important enough to get its own track next — but you can already feel why the open timeline needs it. Without it, every backdated crumb would be a small lie about the past.

Code

Three crumbs, three directions, one honest capture time·json

// captured today, about today
{ "text": "first tomatoes of the year", "captured_at": "2026-07-24T09:12Z", "target_date": "2026-07-24" }

// PAST scatter — a memory that belongs to last week, captured now
{ "text": "the quiet after everyone left", "captured_at": "2026-07-24T09:15Z", "target_date": "2026-07-18" }

// FUTURE scatter — an intent placed on a day next month
{ "text": "ask myself if the move was worth it", "captured_at": "2026-07-24T09:16Z", "target_date": "2026-08-31" }

// note: target_date moves freely; captured_at is always the real moment of writing

Exercise

Write two crumbs of your own from this exact moment. One is past scatter: a real memory that belongs to a specific earlier day. One is future scatter: a genuine note to yourself placed on a specific future day. For each, write down both dates it carries — the day it's about, and today (when you actually wrote it). Notice that neither of those numbers is wrong.

Hint

If you catch yourself wanting to change the 'written' date to match the 'about' date, stop — that instinct is the lie the two-truth rule exists to prevent. Let the two dates disagree. The disagreement is the honest part.

Scatter Into the Past, Scatter Into the Future

The Axis Bends Both Ways

Filing Is Not Faking

Code

External links

Exercise

Progress

Comments 0