Information hierarchy · frozen states · explicit no-trade
6N Multi-Timeframe Framework: Rules You Can Replay
A weekly 6N chart can be labeled up, a four-hour chart down and a five-minute chart sideways at the same instant. Calling that “mixed” merely renames the contradiction. A usable framework assigns each chart one job and specifies which state controls the decision.
- Higher frame
- Permission
- Setup frame
- Location
- Execution frame
- Trigger
- Default
- No trade
No duplicate votes
Give Each Timeframe One Non-Overlapping Responsibility
Three charts should not be three versions of the same moving-average opinion. The higher timeframe determines permission, the setup timeframe identifies a testable location, and the execution timeframe determines whether and when an order may be submitted.
Higher timeframe: permission
Classify a frozen structural state and prohibit sides that the registered strategy does not allow in that state.
Setup timeframe: location
Define a price zone, pullback, compression or other setup with boundaries known before the trigger.
Execution timeframe: trigger
Translate the allowed setup into an objective event and an earliest order timestamp.
Risk layer: veto
Event, liquidity, expiry, loss-budget and data-integrity gates can cancel any apparent alignment.
Hypothesis—not a finding
A non-duplicative hierarchy may reduce discretionary relabeling compared with an otherwise similar rule that gives every chart an equal vote. That proposition requires a chronological replay and costed baseline.
- Fact
- Bars are transformations
- Mechanism
- Higher frames aggregate more time
- Result here
- None
Define the information set
Freeze Bar Clocks Before Reading Structure
A “daily” bar can end at a venue settlement, a broker-defined cutoff, midnight UTC or another boundary. Each version can move highs, lows and indicator values. Preserve dated 6N contracts and declare the exact bar construction.
| Field | Required declaration | Fail-closed condition |
|---|---|---|
| Instrument | CME product, delivery month and roll mapping | Generic symbol cannot be traced to an expiry |
| Boundary | Timezone, start/end, included endpoints and CME trade-date treatment | Vendor defaults are unknown |
| Prices | Trade-based or quote-based OHLC, correction policy and missing-interval rule | Stale quote becomes a valid close |
| Availability | Bar completion time plus computation and order delay | Trigger uses an unfinished bar |
| Calendar | Holiday, pause, early close and daylight-saving versions | Normal schedule is imposed on exceptions |
CME Rulebook Chapter 258 identifies 6N as a dated New Zealand dollar/U.S. dollar futures contract, while CME trading-hours and holiday notices provide schedule controls. The canonical 6N specification guide owns current contract mechanics.
Structure must be computable
Replace “Looks Like a Trend” With Frozen Swing Rules
The rule should map the same completed bars to the same state without knowing what followed. Pivots that require future bars are permitted only after their confirmation delay, never backdated to the visual turning point.
Pivot definition
Known only when confirmed
Declare left/right lookback, tie handling and the timestamp at which a swing becomes available.
Break definition
Close, trade or buffer
Specify the price field, comparison operator, tolerance and whether the level must persist through bar close.
Neutral definition
Conflict is a state
When required highs/lows disagree or warm-up is incomplete, classify neutral or ineligible instead of improvising.
structure state at t=f(completed bars available by t)Swing counts, moving averages, channels and volatility filters are candidate definitions. Their lookbacks and thresholds require independent testing; this article does not select a profitable version.
Alignment is a truth table
Enumerate Every Combination, Including No-Trade States
A strategy cannot say “wait for alignment” unless alignment and conflict are fully specified. Build the state table before replay so that every completed bar maps to one permissible action.
| Higher-frame permission | Setup state | Execution state | Permitted action |
|---|---|---|---|
| Long only | Inside declared long zone | Trigger absent | Observe; no order |
| Long only | Inside declared long zone | Long trigger confirmed | Evaluate risk and market-quality gates |
| Long only | Outside zone | Any | No trade; lower-frame signal has no authority |
| Short only | Inside declared short zone | Short trigger confirmed | Evaluate risk and market-quality gates |
| Neutral/conflict | Any | Any | No trade |
| Ineligible data/event | Any | Any | No trade and log reason |
Trading application: the table is only an example of rule completeness. It is not evidence that long-only, short-only or any named chart state predicts 6N returns.
From observation to order
Separate Trigger, Entry, Invalidation and Exit
A bar can confirm a trigger without offering an executable entry at its close. Define the earliest submission time, order type, maximum chase or limit lifetime, initial invalidation and position-management logic as separate fields.
Eligible
Contract, data, event and liquidity gates pass.
Aligned
Higher permission and setup location agree.
Triggered
Execution rule confirms on available data.
Submitted
Order arrives after declared processing and network delay.
Resolved
Fill, partial, cancel, exit and residual risk are logged.
Price invalidation
The structural premise is false
Use a level derivable at the decision time. If it is too distant for the independent loss budget, the correct action is no trade.
Time invalidation
The setup has expired
Cancel after a declared number of bars, session boundary, event cutoff or state transition. Do not keep a stale trigger alive.
Replay the information available then
Run a Bar-by-Bar State Ledger
At each decision timestamp, store the three frame states, the source bars that created them, eligibility flags, allowed actions and later order outcomes. Recompute forward; never annotate historical charts with final pivots or revised states.
Warm up
No state until every required lookback exists. Shortening the lookback silently is prohibited.
Snapshot
Hash the completed bars and record the exact higher, setup and execution states.
Transition
Apply only transitions permitted by the frozen truth table and risk vetoes.
Compare
Evaluate later outcomes against simpler baselines after realistic non-overlapping costs.
- Store state duration. Consecutive bars in one setup are not independent new setups unless defined that way.
- Deduplicate signals. Specify re-entry and cooldown rules before a repeated trigger appears.
- Model collisions. Define what happens when trigger, stop and target can all occur inside one unresolved bar.
- Open holdout once. A change after review retires that holdout for the modified system.
Common framework breakpoints
Treat Ambiguity as a Test Failure, Not Discretion
Most apparent precision disappears when timestamps, unfinished bars, overlapping indicators and order assumptions are made explicit. These failures must be counted, not edited out.
Information
Future leakage
- Backdated pivots
- Incomplete higher-frame bars
- Revised inputs
- Same-bar impossible fills
Architecture
Duplicate evidence
- Same indicator on all frames
- Majority vote without authority
- Threshold changed by chart
- No neutral state
Execution
Unpriced implementation
- Close assumed fillable
- No latency or spread
- Missing partial fills
- No event or roll veto
NIST/SEMATECH time-series guidance emphasizes time dependence, while the CFTC advisory on trading systems explains why hypothetical fills and hindsight differ from live results.
Operator handoff
One-Page State Handoff
A different operator should reach the same permitted action from this record. If any required entry is unknown, the handoff resolves to no trade.
6N decision state at a declared timestamp
- Instrument
- Dated contract, roll state, data version and bar-clock definitions.
- Higher frame
- State, confirmation time, source bars and allowed direction.
- Setup frame
- Zone boundaries, creation time, expiry and state.
- Execution frame
- Trigger definition, confirmation time, earliest order and order type.
- Invalidation
- Price, time, event and structural conditions plus independent risk limit.
- Action
- Submit, observe, cancel or no trade—with one machine-readable reason.
No original 6N multi-timeframe replay, setup frequency, win rate, expectancy, parameter selection or trading result is reported. The framework is a protocol for making rules testable. Its default conclusion remains no trade until a separately sealed study passes.
Sources, methods and editorial disclosure — reviewed August 20, 2026
- CME Rulebook Chapter 258: New Zealand Dollar/U.S. Dollar futures for dated-contract identity and rule context.
- CME Group trading-hours and holiday schedules for schedule-version controls.
- CME DataMine historical-data catalog for trade, settlement and order-book data distinctions. No dataset was purchased or analyzed for this page.
- NIST/SEMATECH time-series analysis guidance for chronological dependence.
- CFTC advisory on commodity trading systems and hypothetical results for hindsight and simulated-execution limitations.
Sources and methods were reviewed August 20, 2026. This unsponsored article separates instrument facts, information-aggregation mechanisms, testable rule hypotheses, inferences that would require a replay and any later trading application. It reports no original result.