The Rigor subroutine
The in-session flow you follow while the market is open.
What a subroutine is
The daily process gets you to the open. The subroutine is what you do repeatedly once you are there.
It lives under Process, sub-tab Subroutine, and unlike the daily process it is not a straight line. It is a small graph, because a live session is not a checklist you complete once. You cycle: scan, focus on a symbol, build a case, act or pass, return to scanning.
A subroutine is optional. It becomes worth building once you have rules on your checklist and a few check-ins, because that is when the question changes from what should I check to in what order and how often.
The assistant can draft a starter subroutine from your existing rules and check-ins. On the Strategy and Rigor screens, the prompt Draft a starter subroutine does exactly that, and shows which checklist rules it would put on the flow before you apply it.
Node types
The flow is built from nodes.
| Node | What it does |
|---|---|
| Step | A plain instruction to perform |
| Branch | Splits the flow based on a condition |
| Loop | Repeats a section. A loop can be marked as a symbol focus loop, so it runs once per symbol you are watching |
| Checklist | Points at checklist items from your rules, so the flow asks for specific checks rather than all of them |
| Check-in | Runs one of your check-in forms inside the flow |
| Situations | Handles distinct situations you have defined |
| Switch | Chooses between several paths |
A symbol focus loop can be tied to a specific check, so a red verdict on that check exits the loop instead of letting you keep working on a symbol that already failed. That is the structural version of walking away, and it is the most useful thing in the editor.
Keep the graph small enough to follow at speed. If you cannot describe your subroutine out loud in thirty seconds, it will not survive a fast open.