Gold trading basics · Lesson 87 of 100

Gold System States: Separate Eligibility, Submission, Exposure and Rearming

Build a state-transition specification that prevents duplicate entries and distinguishes local intent from confirmed broker exposure.

Intent Is Not Exposure: instructional diagram for lesson 87 — CYGURU GOLD · Original lesson schematic. Examples are illustrative.

An eligible signal is not an open position

An indicator can identify a condition while an execution process is disconnected, rejected or still waiting. Treating all of those events as an entry obscures both operational failures and economic results. Begin with a small state vocabulary: idle, eligible, submitted, partially filled, open, exit pending, closed and reconciliation required. A blocked decision can remain idle with a rejection reason. These labels are useful only when their transition conditions are explicit. The same market observation should not become several independent orders simply because several components received it.

Give each intention one durable identity

Construct a stable program identifier from the rule version, instrument, decision timestamp and direction. A retry carries the same identifier rather than creating a fresh economic intention. Store event sequence and broker identifiers separately, because one program can contain several orders and fills. An acknowledgement confirms receipt under that system's protocol; it does not necessarily confirm the full requested execution. If the response is missing, reconcile the broker state before retrying an order. Uncertainty about whether an order exists is a reason to investigate, not evidence that no order exists.

Reconcile a partial-fill example

Suppose a paper intention requests six ounces and the execution record confirms two ounces followed by one ounce. Exposure is three ounces, while three requested ounces remain unfilled or otherwise unresolved. A duplicate notification of the one-ounce fill does not increase exposure if it has the same unique execution identifier. If the unfilled remainder is canceled and that cancellation is confirmed, requested size remains six for historical intent, executed size remains three and working remainder becomes zero. Retaining all three quantities explains what happened without rewriting the original request.

Program quantity reconciliation
Event	Unique filled oz	Working oz
Submit six	0	6
Fill two	2	4
Fill one	3	3
Duplicate same fill ID	3	3
Confirmed remainder cancel	3	0

Illustrative program; a request or acknowledgement is not a confirmed fill.

Define what can legitimately move the system

Only confirmed new executions alter the fill ledger. A cancellation request moves an order toward a pending-cancel state until its outcome is known. An exit request similarly does not make the position flat. If observations conflict, transition to reconciliation required and block new exposure under the example policy. The process must also account for a fill arriving during cancellation. Write that race explicitly rather than assuming that a button press removes an order instantly. State transitions should be traceable to evidence and should not depend on the color of an indicator label.

Rearm only after the chosen reset condition

Closure of a position and permission for a new attempt are different decisions. A construction exercise might require price to return below the prior threshold and a later completed qualifying bar before another long program is allowed. That is one testable reset policy, not a universal trading rule. Alternative reset choices create different opportunity populations and must be compared as separate versions. Do not reset automatically on a browser refresh, alert retry or chart timeframe change. Technical restarts should recover the durable state rather than silently grant a fresh trade allowance.

Workshop deliverable: a transition and recovery ledger

List each current state, allowed incoming event, resulting state and quantities that change. Include one partial fill, one duplicate, one cancel-fill race and one lost response. Verify that every path ends with reconciled exposure or a visible unresolved state. Keep program accounting distinct from notification counts and from completed-trade statistics. This specification connects earlier webhook and bracket-order lessons into a complete operating process. It also gives the sizing engine a reliable answer to a necessary question: how much exposure is already committed before another intention can be accepted?

Gold System States: Separate Eligibility, Submission, Exposure and Rearming

An eligible signal is not an open position

Give each intention one durable identity

Reconcile a partial-fill example

Define what can legitimately move the system

Rearm only after the chosen reset condition

Workshop deliverable: a transition and recovery ledger

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