History & Time-Travel
Specor is event-sourced: every change is an append-only event that is never silently overwritten. That gives you two things a document tool can’t — a complete, trustworthy history of how your product got here, and the ability to time-travel to view it exactly as it was at any past point.
Branch history
Open the History view to see the sealed commits on the active branch, newest first. For each commit you can see:
- Its name and description
- When it was sealed and by whom
- The set of changes it bundled
This is the durable record behind every version of your product — useful for status updates, for answering “when did we decide this?”, and for accountability reviews.
Time-travel
The Time Travel view reconstructs the entire product model as it existed at a chosen point. Pick how to travel:
| Tab | What it does |
|---|---|
| At Commit | View the model as it stood immediately after a specific commit was sealed |
| At Date | View the model as it stood on a specific date and time |
Time-travel is read-only — you’re inspecting a past state, not editing it. Nothing you view changes the current working state.
History, rollback, and diff
These three features work from the same immutable log:
- Diff compares any two points and shows what changed, in plain English
- Rollback reverses a past commit by creating a new inverse commit — it never erases history
- Time-travel simply views a past point without changing anything
Because history is append-only, none of these are destructive. You can always get back to any prior state.
Tips
- Name commits well. Clear commit names make the history — and time-travel — far easier to navigate months later.
- Use “At Date” for incident reviews. When you need to know what the product looked like at the moment something happened, travel to that timestamp.
- Reach for rollback, not manual undo. If a past change was wrong, roll it back so the correction is itself recorded in history.