Deep review
The periodic behavioral review, its letter, and its proposals.
What a deep review is
A deep review is the assistant going through your data properly rather than answering one question. It reads your trades, notes, todos, check-ins, and trade reviews, looks for patterns, forms a view about what is causing them, and proposes specific changes to your strategy.
Start it from the button in the assistant panel, labelled Run a deep review of my trading, or from the Review screen. You can also ask for it in words; phrases like run a review or review my trading start it rather than a normal chat turn.
It runs through phases, shown on the button as it works: briefing, probing, composing, proposing, and finally awaiting your review. Probing is the long part, because it is querying your data repeatedly rather than summarizing a single fetch.
When it finishes it takes you to the Review screen and closes the assistant.
The default cadence is about every thirty days, and the assistant will nudge you when one is due, saying how long ago the last one was, or noting bluntly that you have never had one and that this is how a plan gets made. Monthly is deliberate: reviewing behavioral patterns weekly mostly finds noise.
The review letter
The result is a letter, not a dashboard. It is written to be read once, properly.
Its structure:
- An opening that frames what it looked at.
- One section per pattern found, each with a severity badge: Worth watching, Costing you, or In the way.
- Inside each pattern, two parts. Here is what I noticed, with the evidence it used, and Here is what I think causes it, again with evidence.
- An Action plan in the sidebar, with a duration in days and a count of suggestions.
The separation between what it noticed and what it thinks causes it is the most important thing on the screen. The first part is data and you should check it. The second part is inference and you are allowed to disagree. An assistant that presented both with equal confidence would be teaching you to accept explanations you have not tested.
A Past reviews selector keeps previous letters, marked as archived, so you can compare what it said three months ago with what it says now. That comparison answers the only question that matters: did anything change.
The Review: Evidence screen holds the supporting charts and metrics for the findings, so you can check the claims rather than take them.
Accepting the action plan
The action plan is a list of concrete proposals, each tied to a finding. A proposal might be a new subroutine, a process step, a check-in, or a todo, and each card names the entity type, the change, and which finding it addresses.
For each one:
- Keep this accepts it.
- Not now declines it.
- Edit opens Edit suggestion, where you can change the Title and the Why this change text before accepting.
The footer tracks where you are: how many still need a yes or no, how many changes are ready to write, or that you turned everything down. You cannot start the plan while proposals are undecided, which is intentional. Skipping the decision is how a plan becomes something that was suggested to you rather than something you chose.
Then:
- Start this plan writes the accepted changes into your strategy.
- Discuss with assistant opens a conversation about the plan instead of accepting it.
- Discard throws it away.
Turning everything down is a legitimate outcome. If the findings are wrong, saying so is more useful than accepting changes you will not make. But be honest about which one is happening: declining every proposal in three consecutive reviews is usually not a sign that the reviews were wrong.
Once started, the plan appears as the active plan on your Strategy Overview, with a window and an outcome target. See the Strategy chapter under Improvement plans.
