Lineage
Lineage shows how baseline state evolved through promotions and snapshot restores.
Use it to answer: what became baseline, from where, and with what measurable delta?
Where to view lineage
- Baseline lineage page:
/live/lineage
The page supports timeline and table views and links to related scenarios/snapshots.
What each lineage entry shows
- type (
Scenario PromotionorSnapshot Restore) - from state
- to state
- applied timestamp
- actor who performed action
- summary deltas (headcount, FTE, cost, velocity)
This gives a compact historical chain of baseline transitions.
Why lineage is different from activity log
- Activity log: event-level detail of individual modeling changes
- Lineage: baseline transition milestones and outcomes
Use both together:
- lineage for high-level transition history
- activity for exact change-level forensics
Typical decision workflow
- Compare candidate scenarios via deltas.
- Promote chosen scenario.
- Confirm promotion appears in lineage.
- Reference lineage in release/change notes.
If needed later, restore a previous snapshot and observe that restore as a new lineage entry.
Best practices
- keep scenario names explicit and time-scoped
- avoid overlapping promotions without review checkpoints
- treat lineage as authoritative record in stakeholder retrospectives