ORGONAUT
Login Signup
Docs
Scenarios
Lineage

Lineage

Lineage shows how the Live View state evolved through promotions and snapshot restores.

Use it to answer: what became Live, from where, and with what measurable delta?

Where to view lineage

  • Live View Lineage page: /live/lineage

The page supports timeline and table views and links to related scenarios and snapshots.

What each lineage entry shows

Every entry in the lineage provides a durable record of a state transition:

  • Type: Either Scenario Promotion or Snapshot Restore.
  • From: The historical state that was replaced (a Live View Snapshot).
  • To: The resulting state (either an Applied Scenario or the snapshot that was restored).
  • Metadata: Applied timestamp and the actor who performed the action.
  • Summary deltas: Quantified impact on headcount, FTE, monthly cost, and velocity.

Scenario Promotion

When you promote a scenario, Orgonaut archives the current Live View into a new Live View Snapshot and converts the planning scenario into an Applied Scenario. The lineage entry links these two artifacts, showing exactly what was replaced and what was applied.

Snapshot Restore

When you restore a historical snapshot, Orgonaut archives the current Live View as a new snapshot before replacing it with the values from your chosen historical snapshot. This creates a new lineage entry for traceability, even when returning to a previous state.

This gives a compact, auditable chain of all canonical state transitions.

Why lineage is different from activity log

  • Activity log: Event-level detail of individual modeling changes within a specific scenario or Live View.
  • Lineage: High-level milestones and outcomes of Live View transitions.

Use both together:

  1. Lineage for the "big picture" history of what became Live.
  2. Activity log for the exact change-level forensics within a specific window of time.

Typical decision workflow

  1. Compare candidate scenarios via deltas.
  2. Promote the chosen scenario to Live.
  3. Confirm the promotion appears in the lineage.
  4. Reference the lineage entry in release or change notes.

If needed later, you can restore a previous snapshot; that restore will be recorded as a new lineage entry, preserving the complete history of your organization's structure.

Best practices

  • keep scenario names explicit and time-scoped
  • avoid overlapping promotions without review checkpoints
  • treat lineage as authoritative record in stakeholder retrospectives