A strategy is rule-based when every decision it makes can be written down precisely enough that two people, given the same chart and the same rules, would take the same trade. Before you connect it to automation, identify which decisions already meet that test, which need a rule written and tested, and which will stay with you.
The checklist below reveals where judgment may still be hiding. Automation executes rules; it does not create a profitable strategy.
Part 2 of 8 in From discretionary to automated trading. Previous: who decides and who executes. Next: turn a setup into measurable conditions.
Why Does This Matter Before You Automate?
If a rule is vague or missing, the implemented version may behave differently from the process you follow manually. You may apply judgment to the entries you take and the ones you skip without recording that filter. Software cannot apply an unwritten judgment on your behalf.
PineConnector processes received alert messages using the configured setup and broker rules. A message can be received without a broker trade occurring, so a complete rule and a verified execution path are separate requirements.[1]
The gap between a discretionary strategy and a rule-based one is not always large. Sometimes it is one missing condition. Finding it before live execution lets you define and test the intended behaviour first.
Which decisions are ready, and which stay with you?
Copy the ten items below into your journal. For each, write the current rule, its inputs, one example that should qualify and one that should not. Then choose one status:
- Automate now: the decision has an explicit rule and evidence that its inputs can be observed at the required time. “Now” means ready to implement and verify on demo, not permission to trade live.
- Write and test first: the wording, data availability or exception is still uncertain.
- Keep with a logged veto: a human retains the decision, with a stated scope and a record of every intervention.
-
Market and instrument: which exact instrument and data source may the process use?
Record: allowed list ___; exclusions ___; status ___. -
Setup: what observable conditions identify the opportunity?
Record: inputs ___; comparisons ___; lookback ___; status ___. -
Entry trigger: what event turns an eligible setup into an instruction, and when is it evaluated?
Record: event ___; timeframe ___; bar-close or intrabar ___; repeat handling ___; status ___. -
Session, news and other filters: what blocks a new entry, and which clock or outside information does the decision use?
Record: entry window ___; timezone ___; information source ___; manual veto ___; status ___. -
Position size: what formula and units determine the request?
Record: formula ___; input source ___; planned loss versus actual-loss limitation ___; status ___. -
Initial stop and target: how are the levels found, and what happens if a level is invalid?
Record: stop rule ___; target rule ___; missing-level action ___; status ___. -
Trade management: when may stops, targets or volume change after entry?
Record: permitted changes ___; decision owner ___; manual/automated handoff ___; status ___. -
Exit: what requests closure, and how do you confirm that exposure actually changed?
Record: exit condition ___; request time ___; broker verification ___; status ___. -
Position and account limits: what limits apply, what do they count, and where is actual exposure checked?
Record: intended scope ___; open-position check ___; daily count/reset ___; breach action ___; status ___. -
Run, pause and resume: who may intervene, for what reason, and what must be checked before restart?
Record: pause condition ___; owner ___; open-position treatment ___; resume evidence ___; status ___.
Illustrative example, not a recommendation: “the hourly trend is up” belongs in write and test first until “up” is measurable. A defined cash-loss sizing rule can be ready to implement once its stop, currency and units are explicit. “Stay out around big news” remains a logged human veto if the strategy has no defined event source and rule.
No news-event filter is documented in the PineConnector Syntax and EA references cited here. That is a documentation limit, not proof about every possible implementation; do not treat a spread filter or a clock window as an event-aware news decision.[2][3]
Does Your Strategy Pass the Rule-Based Test?
Work through the table below. For any row where your honest answer is “it depends” or “I would have to judge the chart”, mark it as a gap. Gaps are the specific things to resolve before you automate that decision.
| Area | Ask Yourself | Sign of a Gap |
|---|---|---|
| Entry | Can every condition be written without an extra judgment? | You skip qualifying signals by feel |
| Entry vs tester | Do intended signals match the rules on the same bars? | You would reject some qualifying signals |
| Exit | Is every exit defined, including stops, targets and early closes? | You move stops or close early by feel |
| Position sizing | Is size set by a fixed value or explicit formula? | Size changes with confidence |
| Filters | Are session and news decisions explicit or logged as manual? | You avoid conditions without a recorded rule |
| Override history | Did the last 20 reviewed trades follow the written rules? | A trade was taken or skipped outside them |
The 20-trade lookback is a practical inventory window, not proof of reliability or profitability. Record qualifying signals skipped during the same period too. For “Entry vs tester”, compare the decision rule and bar first: TradingView simulates fills using a broker emulator, so identical broker fill prices are not the pass condition.[4]
Use the checklist with the inventory. For example, an explicit exit rule can still need broker verification, and a written “one position” rule needs a defined account scope. Pine’s simulated strategy state cannot establish that the receiving MT5 account has no open position.[4]
What to Do With the Gaps
A gap is not a problem to ignore. It is a decision to make before you automate.
For each gap, you have three options. You can write the rule explicitly and add it to your implementation. You can decide the condition is not important enough to include and accept that the automated version will behave differently in those cases. Or you can decide the strategy is not ready to automate yet and continue observing the decision before committing it to code.
Treat the second option as a changed strategy and test it separately. The first option needs a measurable definition; Part 3 provides the worksheet. The third option can leave a selected decision with you while you gather evidence, provided the handoff is explicit.
A logged veto records the time, qualifying signal, information available then, decision and affected scope. Define how the intervention affects new entries, exits and existing positions before using it. Pausing a signal path is not the same as closing a position; use Part 8 for the control-specific checks.
A Useful Test Before You Connect Anything
First observe the strategy’s signals without routing order instructions. For each qualifying signal, record whether you would take it under the written rules and, if not, why. Log that decision before seeing the later outcome.
- Signal record: timestamp and timezone ___; instrument/data source ___; rule version ___; condition and bar ___.
- Your decision: take, skip or change ___; reason known then ___; written rule or discretionary veto ___.
- Follow-up: repeatable missing condition ___; proposed rule ___; data reserved for a separate test ___.
If the same reason appears repeatedly, it is a candidate rule to define and test on data you did not use to invent it. Whether a handful of skipped trades later won or lost does not establish the filter’s value. Repeatedly changing the rule to fit those outcomes can overfit the observed sample.[4]
Choose observation coverage that includes the conditions your rules handle, including skips and exceptions. A fixed number of weeks alone cannot establish readiness. After defining the rules, use Part 7’s connection check and separate demo-trade verification.[5]
What Happens After the Checklist?
A strategy that passes the checklist is ready for a detailed implementation specification and tests. It may use existing alert conditions, editable Pine Script or an MT5 Expert Advisor; Part 5 compares those paths.
For a TradingView-to-PineConnector path, the PineConnector Syntax reference defines entry, exit and sizing messages. Each received instruction remains subject to EA settings, filters and broker processing. A receipt or accepted order is not proof of the intended fill or position.[2]
The value of writing the rules is that you can compare intention with observed behaviour. It does not remove the need to verify what happened.
FAQ
What if my strategy uses market feel or pattern recognition?
Those elements remain discretionary until you can define a repeatable decision procedure. You can still automate the rule-based parts and retain judgment for the rest, with a clear handoff and intervention record.
Can I automate a strategy that is mostly rule-based but has one discretionary filter?
You can define the filter, test a version that omits it, or retain it as a logged human decision. Omitting it changes the strategy. Do not quietly compare that changed version with the original as if they were the same process.
Does PineConnector work with any Pine Script strategy?
Check the alert events and their meanings. The Connect your strategy guide explains the existing-alert path, while the Add alerts to your script guide covers editable scripts. A chart marker alone is insufficient, and an exit fill must not be mapped blindly to a new entry. Exits may use separate closing messages or broker stop/target instructions, depending on the specification.[6][7]
Which gap should I check first?
Start with the earliest decision you cannot reproduce from the written rule, including qualifying signals you skipped. Entry filters are one example; your own record determines the priority.
How do I know when a strategy is ready to connect to demo?
Every intended action, exception and retained human decision should have a written meaning and acceptance check. Then verify the separate connection and demo-order steps. Passing this checklist alone is not a decision to trade real money.[5]
What does this checklist leave unproven?
- Data timing: a condition visible later may not have been known at the decision time. Define that timing in Part 3.
- Enforcement: a documented rule still needs an implementation layer. A stop in a backtest is not automatically a broker-side stop; assign and verify it using Part 4.
- Hosted settings: PineConnector Edge hosts MT5 with the PineConnector EA, whose settings currently use fixed defaults. A checklist entry that depends on changing those settings is not yet resolved for that path.[8]
- Future outcomes: complete rules and a functioning delivery path do not establish future profitability.
What should you do next?
Complete the ten-decision inventory, then take the first “write and test” item to Part 3: measurable conditions. Keep the original wording alongside the new definition so the change can be checked.
Reviewed 23 September 2026 against the linked primary documentation. Nothing was tested on a trading account, and no Pine Script or MQL5 code was compiled.
Related reading
- Series guide: from discretionary to automated trading
- Part 1: who decides and who executes
- Part 3: measurable conditions
- Part 4: the complete strategy specification
- Part 7: demo verification
Sources
- PineConnector – Frequently Asked Questions, accessed 23 September 2026.
- PineConnector – PineConnector Syntax, accessed 23 September 2026.
- PineConnector – EA settings reference, accessed 23 September 2026.
- TradingView – Strategies, accessed 23 September 2026.
- PineConnector – Test your setup, accessed 23 September 2026.
- PineConnector – Connect your strategy, accessed 23 September 2026.
- PineConnector – Add alerts to your script, accessed 23 September 2026.
- PineConnector – Connect your MT5 account, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
