Operating Checklist

Use this page when you want a repeatable way to operate Axiom Strategy Lab Pro without losing the parts that matter. This page is not here to replace the rest of the manual. It is here to give you a disciplined routine once the bigger ideas already make sense. Think of it as the page you reach for when:

• you are coming back to the strategy after a break
• you are about to test a new workflow
• you have a promising run and want to keep yourself honest
• you want a stable sequence under pressure

The Operating Principle Behind This Checklist

The safest working rhythm is:

1. confirm what you are actually testing
2. confirm what assumptions are shaping that test
3. verify one chart path before trusting the summary
4. record what you learned before changing something else

That rhythm is simple, but it does a lot of work. It keeps the builder from turning into a blur of settings, results, and half-remembered edits.

Fast Return Check

If you are opening the strategy again after time away, start here.

• Confirm the chart symbol and timeframe are the ones you intend to study.
• Confirm the active direction still matches the side you meant to run.
• Re-read the strategy properties before trusting any previous memory of the report.
• Verify one setup, one entry, and one management path on the chart before drawing new conclusions.
• Confirm no broader rail, token change, or settings drift is quietly changing the behavior.

If those five checks are clean, the deeper review below becomes much easier and much faster.

Phase 1: Before You Run Anything

This phase is about orientation. Most avoidable mistakes happen because people skip it.

• Decide whether this session is long-only, short-only, or truly two-sided.
• Confirm the active side's builder inputs are populated and the inactive side is blank unless you intentionally want both sides live.
• Review the strategy properties and make sure sizing, commission, slippage, pyramiding, and timing assumptions still match your intent.
• Confirm any custom token names still match the logic that references them.
• Confirm whether important non-market paths are meant to use fixed prices or monitored prices.

What this phase protects you from:

• testing the wrong side
• reading an old report under new assumptions
• letting a renamed token break a workflow silently
• forgetting that price behavior changed when you last edited the setup

Phase 2: Before You Expect Trades

This phase is about readiness.

• Confirm the properties-review confirmation is checked only after the review is genuinely complete.
• Confirm the strategy is not blocked by structural, vocabulary, or readiness issues.
• Confirm at least one setup has a realistic chance to become valid on the chart you are using.
• Confirm broader strategy-level rails are not already suppressing fresh participation.

What this phase protects you from:

• treating a blocked runtime like a broken workflow
• expecting trades from a chart that never presents the required context
• blaming the entry when the real issue is readiness or a broader rail

Phase 3: First-Path Verification

This is the phase most people try to rush past. Do not.

• Watch one setup become active or confirmed for reasons you can explain.
• Watch one entry become eligible and either place, wait, cancel, or expire for reasons you can explain.
• Watch one management path attach to the live trade context the way you intended.
• Confirm the visible order behavior matches the order behavior you authored.
• Treat the first few trades as behavior receipts, not proof of edge.

This phase matters because the strategy's real trust begins on the chart, not in the summary table.

Phase 4: Before You Trust The Report

Once the chart path is understandable, now read the result more critically.

• Re-read the properties assumptions with the finished run in mind.
• Ask whether cost and slippage assumptions are flattering the result.
• Ask whether any custom token is adding genuine signal or only complexity.
• Confirm whether any broader rail changed the sample of trades you are looking at.
• Re-check one complete trade path before summarizing the result to yourself.

What this phase protects you from:

• mistaking a clean report for a robust workflow
• forgetting that the tester posture shaped the story
• letting one helpful-looking token earn more trust than it deserves

Phase 5: Before You Optimize

Optimization should begin from a recorded baseline, not from a feeling.

• Freeze one baseline configuration in writing.
• Decide which one variable family you are changing next.
• Leave every other major assumption alone for that pass.
• Decide how you will verify the change on the chart before you read the summary.
• Write down what outcome would count as a real improvement rather than just a prettier report.

This phase protects you from calling noise "learning."

Phase 6: When Behavior Looks Wrong

When something feels off, move in this order.

1. Check readiness first.
2. Check direction second.
3. Check setup state third.
4. Check ownership and package scope fourth.
5. Check token meaning and token wiring fifth.
6. Turn on only the diagnostic view that matches the actual question.
7. Use Troubleshooting before rewriting the workflow from scratch.

This order matters because it keeps you from trying to solve every symptom as if it were a syntax problem.

Phase 7: When Returning To An Older Configuration

Older configurations can feel familiar enough to trust too quickly.

• Confirm the symbol and timeframe still match the version you think you are comparing against.
• Confirm the properties tab still matches the earlier run you are remembering.
• Confirm the authored workflow has not drifted since the last baseline.
• Confirm no custom token source changed upstream.
• Re-verify one visible trade path before trusting the older conclusion.

This phase protects you from one of the easiest mistakes in all trading research: remembering the result more clearly than the conditions that created it.

Phase 8: Before Any Wider Operational Use

If you are tempted to widen the workflow beyond the chart, pause here first.

• Confirm you can explain why the strategy trades when it trades.
• Confirm you know what assumptions shaped the result.
• Confirm you are not relying on behavior the current production strategy does not actually claim to provide.
• Confirm you are not using outside operational ambition to skip over remaining uncertainty in the workflow itself.

This phase protects you from operationalizing a misunderstanding.

A Good Closing Habit

Before you end a session, record three things:

• what configuration you ran
• what you verified on the chart
• what still feels uncertain

That small habit builds momentum because it turns vague memory into usable continuity for the next session.

If You Only Remember Five Checks

When time is short, keep these five:

1. confirm direction
2. review properties
3. verify one setup
4. verify one entry and one management path
5. record what changed before changing something else

Those five checks are not everything, but they prevent a remarkable amount of avoidable confusion.