Exists now
- A local index built from git history.
- Recall for broader prior-work questions.
- Targeted checks before a file or decision is changed.
Pastlight
Pastlight retrieves the earlier decision, failure, or constraint that matters to the question in front of you. Its source is local repository history, where the reason usually survives even when nobody remembers where to look.
The problem
Git keeps the changes. The reason is harder to recover.
A constraint set six months ago still shapes the code today. The commit is somewhere in the history, along with failed approaches and the discussion that made the final choice sensible. Finding that thread by hand takes long enough that teams often reopen the decision instead.
Pastlight indexes that history and retrieves prior work before a new session repeats it.
Intended user
People maintaining codebases that have outlived the chat that changed them.
The useful case is a live question with history behind it: why a rule exists, whether a similar fix failed before, or which constraint an apparently simple change would violate.
Current boundary
What exists, and what the next gate still has to prove.
The page describes the application as it stands today. M1 may change the first public offer.
Still open
- The M1 exit and the evidence it produces.
- A supported public installation path.
- The exact boundary of the first public release.
Availability
In development. No public build or price.
M1 is the next evidence gate. Its result will decide what Pastlight can honestly offer first; the site will change status when that boundary exists.
Public receipts
No public product receipt yet.
The M1 result is the next receipt expected here. Until it is published, development status is the claim.
Writing
The work behind Pastlight
Longer development notes and release stories will be published on Sea Trials when they are ready.