The Strategy editor

Tabs, toolbar, saving, committing, and history.

Tabs and toolbar

The Strategy editor is organized as tabs across the top: Overview, Targets, Rules, Vows, Checkins, Process, Accountability, Setup, and Properties. The Process tab has two sub-tabs, Daily process and Subroutine.

The toolbar is the same on every tab:

ControlWhat it does
Guided setupOpens the setup wizard, which builds entities from your answers
AssistantOpens the assistant in strategy mode so it can suggest and add pieces
RestoreRecovers an earlier backup of the whole strategy
SaveStores your work in progress
Commit / Already CommittedPublishes the version that scoring will use

Overview is a dashboard of cards, one per area, showing what exists and what is still empty. It is the fastest way to see the shape of your plan. If a deep review created an improvement plan, an Active plan card appears here too.

The Strategy entry in the sidebar shows a small dot when you have uncommitted changes.

The Strategy editor with the tab row and the toolbar buttons visible

Starting from empty

With no strategy yet, Overview shows Build your trading strategy and four ways in:

  • Browse catalogs starts from curated presets for rules, targets, setups, check-ins, and process steps.
  • Ask assistant opens the assistant, which can propose a starter set and add the pieces you approve.
  • Guided setup walks you through a structured questionnaire.
  • Set name, description, and experience opens Properties.

All four write to the same document, so you can mix them freely. A common approach is Guided setup for the skeleton, catalogs for the rules you had not thought of, and manual editing for everything specific to you.

The empty Strategy Overview showing Build your trading strategy and the start buttons

Save versus Commit

These are two different actions and confusing them causes most strategy questions.

Save writes your edits. Your changes persist, the editor shows them, and Rigor picks them up. Editing is also saved automatically shortly after you stop typing, so Save is mostly for reassurance.

Commit publishes the version that scoring uses. Rule verdicts, discipline scores, target progress, and Gravitas all read the strategy as it was at the most recent commit at or before the moment being scored.

Why it works that way: if drafts were scored, every experiment you typed at midnight would rewrite the history of trades you already took. Committing makes your plan versioned, so adherence can be measured against the plan you actually had at the time.

Practical consequences:

  • Add a rule and do not commit, and yesterday's trades are still judged without it. That is correct.
  • Change a threshold and commit, and only trades from that point forward use the new threshold.
  • The button reads Already Committed when nothing has changed since the last commit.

Commit when the plan is ready to be judged against, not every time you fix a typo.

Change history

Your strategy is stored as an append-only log of changes rather than a series of overwrites. Every edit you make records what happened: a rule added, a target updated, a process step deleted, accountability changed, and so on.

That gives you two useful things.

A timeline. The commit list shows each commit in order, with markers you can step through using the previous and next commit controls. You can see the plan as it stood at any commit, which is what makes adherence by strategy revision possible in Insights.

An honest record of drift. If your rules quietly loosened over three months, the history says so.

The log is also why deletion is safe. Removing a rule records a deletion event; it does not erase the fact that the rule existed while you were being scored against it.

The strategy commit history timeline with commit markers

Restore from backup

Restore, on the toolbar and also as Restore Strategy from Backup in Properties, brings back an earlier copy of the whole strategy document.

Use it when a series of edits went wrong and stepping back individually is not practical: a bad import of presets, an accidental bulk delete, or an experiment you want to abandon completely.

Restoring replaces the current working document. If you have unsaved work you want to keep, save it under a different shape first, or copy the text of anything you wrote by hand.