← All case studies
AUD/CAD2026-09-28 → 2026-10-02No confirmation

AUDCAD: Conditions Never Reached Confirmation

A retrospective review of an included pair that remained in observation.

AUDCAD entered the weekly universe, but its starting record was UNMAPPED because major-event coverage was incomplete. Subsequent event-risk phases passed into observation, yet higher-timeframe structure remained TRANSITIONAL and confirmation never occurred.

01 / Starting context

What PairPilotFX knew at the time

At the 2026-09-28 decision cutoff, AUDCAD showed moderate relative-strength separation with CAD stronger than AUD, while D1 and H1 structure were in transition and H4 was bullish. Price was bracketed between untested H4 support at 0.99079 and H1 resistance at 0.99578. Macro coverage was incomplete, so execution was BLOCKED; this was not a trade signal.

02 / Selection

Why this pair was included or filtered

AUDCAD was included in the weekly universe. The deterministic execution gate remained blocked because complete major-event coverage was required before execution conditions could be evaluated.

03 / Lifecycle

What changed during the observation window

The persisted sequence was UNMAPPED at the starting snapshot; BLOCKED during EVENT_RISK; BLOCKED during MIXED event risk; then MONITOR during the POST_EVENT observation phase; and MONITOR after macro state became CLEAR. The monitor state during POST_EVENT still required the post-event risk window to clear. After macro became CLEAR, the outstanding condition was higher-timeframe structure resolving out of transition. Confirmation never occurred.

04 / Outcome

What price did afterward

This outcome was observed after the decision cutoff. Across 115 H1 bars, price ranged from 0.98394 to 0.99696 and ended at 0.99144 versus a 0.99321 anchor. Direction was UNRESOLVED, so no favourable or adverse scenario excursion was evaluated. Starting resistance at 0.99578 was touched and crossed beyond without a close beyond; starting support at 0.99079 was touched, crossed beyond, and had a close beyond. The observed endpoint displacement was small relative to the observed range, and no meaningful move was recorded.

05 / Accountability

What the process got right

Radar preserved the distinction between screening context and confirmation. It blocked evaluation while macro coverage was incomplete and through event-risk windows, then retained an observation posture when macro conditions improved because higher-timeframe structure remained TRANSITIONAL. The final evaluation supports this: the pair was included, but the required condition was not observed.

06 / Limitations

What remained weak, incomplete, or missed

The real limitation was unresolved higher-timeframe structure, alongside changing relative-strength states and event-risk conditions; these prevented a confirmed scenario. This is not a deterministic Radar miss: the supplied evaluation is NO_CONFIRMATION and assesses Radar as supported. No invalidation was observed, but neither was confirmation.

  • The starting macro record was UNMAPPED because major-event coverage was incomplete.
  • Direction remained UNRESOLVED, so scenario-relative excursion and support could not be evaluated.
  • The review records observed market behaviour, not an executed trade or performance result.

07 / Lesson

In an unresolved market, strength separation and nearby liquidity are context rather than sufficient confirmation. A disciplined process should preserve observation status until macro conditions and higher-timeframe structure jointly permit confirmation.

Continue the process

Use the case study as research, not as a signal.

Move from retrospective accountability back into the current PairPilotFX preparation workflow: weekly context first, then Radar when a pair deserves attention.

Risk note

This retrospective material is for educational and review purposes only and is not financial advice. PairPilotFX provides decision support, not trade execution or a guarantee of market outcomes.