Gold trading basics · Lesson 86 of 100

Gold Setup Rules: Translate Chart Language into Testable Predicates

Define strict and inclusive comparisons, missing-data handling and boundary tests before interpreting a chart setup.

Test The Equality Case: instructional diagram for lesson 86 — CYGURU GOLD · Original lesson schematic. Examples are illustrative.

Replace adjectives with observable comparisons

Words such as clean breakout and strong rejection allow a trader to reinterpret history after the result is known. A testable rule identifies an input, a comparison and the time that input became available. The purpose is reproducibility, not the elimination of judgment from every research question. Keep discretionary observations in a separate annotation field. If they affect eligibility, document their evaluation procedure as well. Two people applying the same published rule to the same recorded observations should produce the same eligible set, including rejected and ambiguous cases.

Construct a deliberately simple paper predicate

Consider an invented long-only experiment using completed fifteen-minute bars. Let H be the maximum high of the previous twenty completed bars, explicitly excluding the current signal bar. Eligibility requires current close C strictly greater than H and quoted spread S less than or equal to USD 0.50 per ounce. Other charter gates must also pass. These are demonstration parameters, not an endorsed trading recipe. Recording C, H and S is essential because the word breakout alone cannot show which comparison was evaluated or whether the boundary included equality.

Test the boundaries rather than only the obvious winner

With H equal to 2,000, a close of 2,000 fails the strict price test. A close of 2,000.10 with spread 0.50 passes these two predicates. The same close with spread 0.51 fails the spread gate. A missing spread is unknown, not a measured zero, so the example policy blocks the decision until valid information exists. Keep arithmetic precision consistent with the instrument tick and avoid comparing rounded chart labels when the underlying values differ. These small boundary cases often expose larger disagreements between a written plan and its code.

Predicate boundary tests
Close C	Prior high H	Spread S	Outcome
2000	2000	0.40	Fail price
2000.10	2000	0.50	Pass these two tests
2000.10	2000	0.51	Fail spread
2000.10	2000	Missing	Unknown; blocked

Prior twenty-bar high excludes current signal bar; other gates remain necessary.

Keep the signal clock consistent with the evidence

If the rule uses a completed close, it cannot be credited with an entry before that close was established. Record the bar end, calculation time, quote timestamp and order-submission time separately. A later data correction should create an audit record rather than quietly rewriting the original decision. Also define whether one qualifying bar can trigger several attempts. A repeatable trigger requires an identity and a rearming rule; otherwise a chart that stays above the threshold may create unintended repeated exposure on every evaluation.

Use adversarial examples before performance statistics

Create tests where the prior window is incomplete, the current high exceeds H but the close does not, or the spread update arrives late. Test market-session boundaries and a price exactly one valid tick above H. A performance report cannot establish that these cases were processed correctly. First verify that the implementation matches the specification, then study whether the specified process has useful behavior. Passing a software test only establishes agreement with the rule being tested; a precisely implemented losing rule remains a losing rule.

Workshop deliverable: a decision test sheet

Write at least eight input rows with expected pass, fail or unknown outcomes and a reason for each. Include equality, missing data and delayed availability. Have a second pass evaluate the rows without reading the expected answers. Any disagreement becomes a specification question, not a debate about which chart looks better. Retain this sheet alongside the rule version so future changes can be checked against known boundaries. The next lesson will show why an eligible setup still needs an order lifecycle before it becomes a position.

Gold Setup Rules: Translate Chart Language into Testable Predicates

Replace adjectives with observable comparisons

Construct a deliberately simple paper predicate

Test the boundaries rather than only the obvious winner

Keep the signal clock consistent with the evidence

Use adversarial examples before performance statistics

Workshop deliverable: a decision test sheet

Can you apply the idea?

Make this lesson part of your process.

Gold Trading Mastery

Continue the beginner course

Lesson sources and further study

Core course references

Connected reading