VECTORDocs
Open Dashboard

History

History records every change you make to the portfolio during a session and shows, next to each one, the metrics that change produced. It is your working bench: try things freely, watch the numbers, then step back to a version that stood out and recall it.

You'll find it at the bottom of the Tools section in the sidebar, right after Variants.

Risk Sizing has its own history

The Risk Sizing module keeps a separate history of its runs. Open it from the Risk Sizing history button on this page. It's independent of the analysis session and stored locally in your browser, so it behaves a little differently from the session history described here.

What it records

Each row is the state of your recipe after one change, with:

  • When — date and time of the change.
  • Action — what changed (a weight, capital, the mode, a weekday filter, a strategy added or removed).
  • PnL, CAGR, Max DD, MAR, Sharpe — the portfolio metrics at that moment, computed exactly like the Metrics panel.
  • a small equity sparkline for a glance at the shape.

The current version is marked with a dot; steps you've moved past (and abandoned branches) are dimmed.

Undo, redo and recall

  • Undo — Cmd/Ctrl + Z — go back one change.
  • Redo — Shift + Cmd/Ctrl + Z — go forward again.
  • Recall — jump straight to any row with its Recall button, however far back it is.

Undo, redo and recall all rewrite your live session, so the charts, metrics and every other page follow along. The keyboard shortcuts are global, except while you're typing in a field — there, the shortcut keeps the browser's normal text undo.

A scrubber at the top shows the active path as a row of dots — the filled one is where you are. Click any dot to jump to that step, or use the arrows. On a long history the dots scroll sideways.

No spurious rows while dragging

Dragging a weight slider doesn't fill the list with noise. Rapid changes to the same thing within a couple of seconds collapse into one row, and a change that ends up back where it started leaves no trace — the record follows what actually changed.

Branches

History is append-only: nothing is ever thrown away when you go back. If you undo a few steps and then change something, you start a new branch — the steps you'd undone are kept as an abandoned branch rather than being overwritten. Undo and redo always follow the most recent path; the abandoned steps show up dimmed under Show abandoned branches, and you can recall any of them at any time. This means you can explore one idea, back out, try another, and still return to the first.

Reading it with the AI

The AI analyst sees a ranked summary of your history (and your saved variants) for the current session. So you can ask, in the Ask Vector drawer, things like "which combination this session had the best risk/reward?" — it will point you to the version by its number, cite its Calmar/Sharpe, and can offer a one-click recall of that state. It describes the numbers; the decision stays yours.

For the standout versions (the ones with the best Calmar, Sharpe, CAGR or the smallest drawdown) the analyst also sees how that version differs from your current configuration — which strategies were on or off, how a weight changed, which weekday filters moved. So it can answer "what's different about that version?" directly, e.g. "there, two strategies were off and one carried a higher weight." Each difference is read in the direction version → current.

Weight is a P&L multiplier, not contracts

When the analyst mentions a weight change it means the strategy's P&L multiplier (×N) in the backtest, not the number of contracts or lots — position sizing lives in Risk Sizing, a separate module. A weekday change names the days that flip on or off relative to your current configuration; days no longer present in a strategy's data are not counted as a change.

History vs. Variants

They solve different problems and work together.

  • History is the volatile bench of the current session. It lives only as long as the session (24h of inactivity, and it does not survive a server restart). You don't create its entries — they appear automatically as you work.
  • A Variant is a persisted snapshot you create on purpose, to overlay and compare, and it survives restarts.

Found a version you like?

When a row in History catches your eye, recall it and then save it as a Variant to keep it for good. History is where you explore; Variants are where you keep the keepers.

Limits

History keeps the most recent changes of the session (older entries fall off once the list gets long). Because it is in-memory, it is not part of the GDPR data export — only saved portfolios and variants are.