Portolan
Lock the record. The number becomes a fact.
Portolan is the system of preserved positions. Snapshots seal the renewals, pipeline, and forecast together — versioned forever, reconstructable on demand. What you believed, and when.
Forecasts that can't be reconstructed can't be defended.
Every finance team carries the same problem. The forecast you showed the board in August is gone — overwritten by September's numbers, then October's, then November's. When variance gets questioned, the underlying belief is unreachable.
The spreadsheet captures the number. It doesn't capture the construction of belief — the renewal posture, the pipeline weights, the timing assumptions, the operator judgment that went into it. That context evaporates the moment someone hits Save.
A deliberate act. Sealed forever.
Snapshots aren't exports. They are commitments — versioned, immutable records of operational truth at a moment in time. The renewals, pipeline, and forecast are sealed together as one position.
Committing a snapshot is a weighted action. You're not saving a file. You're locking the record.
Every position, still navigable.
Past snapshots don't go away. They remain navigable, comparable, reconstructable. You can pull up V3 from August and see exactly what the team believed — the same numbers you took to the board, with the same underlying contracts and assumptions intact.
The logbook reads back as cleanly as it was written.
Movement, traced to the contract.
Every delta between snapshots traces back to specific contracts and specific assumption changes. When the board asks why the forecast moved, the answer is mechanical — not narrative.
Variance is reconstructable down to the field that changed.
2 assumption changes
The number is only as defensible as the record behind it. Portolan keeps the record.
Portolan seals the work. It is the system remembering.