Weekly context · causal chart reading

Analyze 6B Weekly Trends and Swings Without Predicting From a Label

A usable Sunday record names the dated 6B contract and chart construction, freezes the cutoff at the last completed session, marks only confirmed pivots, and places known catalysts inside the coming holding window. Its output is a small set of conditional paths and invalidation levels for the intraday plan.

Sunday preparationCONTEXT, NOT SIGNAL
1 · Audit the seriesDated contract, adjustment, session boundary.
2 · Confirm swingsOnly information available as of the cutoff.
3 · Write branchesIf/then paths with invalidation.
4 · Hand offIntraday team receives levels and conditions.

Top-down preparation

A Weekly Map Produces Four Decision Fields

Weekly context should change a specific downstream decision: which side needs more evidence, where a thesis becomes structurally wrong, whether the planned holding window crosses a known catalyst, or whether conditions are too ambiguous to use a directional filter.

Input

Freeze the cutoff

Record the last completed session available to the analysis.

Structure

Run one swing rule

Mark only pivots that were confirmed by the cutoff.

Context

Add non-price evidence

Roll, calendar and dated positioning data keep their own timestamps.

Output

Write conditional paths

No unconditional target or "this week should" statement.

A chart classification is descriptive

"Up-structure" means the chosen rule has confirmed higher pivots. It does not mean price is more likely to rise next week. That probability question requires a separate, dated and cost-aware study.

Confirmation timeline

A 2-and-2 Pivot Becomes Available After the Second Following Session

Here is one auditable example, not a recommended parameter: a daily pivot high exceeds the highs of the two completed sessions before it and is at least as high as the two completed sessions after it. A pivot low uses the inverse rule. The pivot becomes knowable only after the second following session closes.

Why the delay matters

If Wednesday is the candidate pivot, its label cannot enter a causal Friday-morning decision until Friday's comparison session is complete under the selected session clock. Backtests that place the pivot on Wednesday without delaying availability by two sessions leak future information.

Left window
2 completed sessions
Right window
2 completed sessions
Availability
After right window closes
Ties
Rule fixed in advance
Definition itemExample choiceWhy it must be frozen
Bar sourceCME dated-contract trade dataVendor, session and settlement conventions can change high/low/close
Session boundaryCME trade date in Chicago timeA London-midnight bar is not the same daily sample
Lookback/look-forward2 left, 2 rightChanging windows after outcomes changes event identity
Tie handlingFirst occurrence owns an equal extremeEqual highs otherwise create inconsistent duplicate pivots
Minimum separationAt least 3 completed sessionsPrevents rapid alternating labels under one implementation only
Availability timestampEnd of second right-hand sessionPrevents a visually obvious but unavailable pivot from entering decisions

Other rules can be valid research definitions. The requirement is deterministic implementation, not this particular 2-and-2 setting.

The chart is constructed

Map Continuous-Chart Levels Back to the Dated Contract

Standard 6B is an expiring, physically settled contract. CME expanded the standard listing cycle for trade date May 11, 2026 to 20 quarterly contracts plus 16 serial months, but actual liquidity is not uniform across that strip. A continuous series stitches dated contracts and can alter the weekly picture.

SeriesAdvantageDistortion riskExecution rule
Actual dated contractPrices correspond to a tradeable instrumentHistory becomes short and liquidity migratesUse for order levels and current risk
Unadjusted continuousPreserves each contract's historical priceRoll gaps can create false weekly breaks and rangesFlag every stitch; do not treat roll jump as market return
Back-adjusted continuousSmoother return-like visual historyPast absolute price levels shift when new rolls are appliedNever place an order from an old adjusted number without remapping
Ratio-adjusted continuousPreserves proportional moves betterStill transforms historical levels and depends on roll ruleUse only with versioned construction metadata
Record the roll rule

Calendar date, volume switch or open-interest switch can select different history.

Inspect both legs

Compare outgoing and incoming dated prices at the stitch.

Remap absolute levels

A continuous 1.2800 is not automatically an executable 1.2800.

Check delivery proximity

Use exchange and broker cutoffs, not a generic rollover date.

Separate returns from levels

A series suitable for return research may be unsuitable for order placement.

Version the data

Vendor corrections or roll-method changes can alter old swing labels.

Descriptive state machine

Classify Structure, Transition and Balance Separately

Compare the two most recent confirmed pivot highs and lows. Keep an unconfirmed extreme in a separate pending field; do not let it silently overwrite the confirmed state.

Up-structure

Descriptive
HighsHigher
LowsHigher
UseContext
ForecastNone

Down-structure

Descriptive
HighsLower
LowsLower
UseContext
ForecastNone

Mixed transition

Ambiguous
HighsHigher/lower
LowsOpposite
UseBranches
BiasReduced

Contained balance

Range state
ExtremeInside
BreakUnconfirmed
UseBoundaries
DirectionOpen
Do not collapse mixed evidence into "trend"

A higher high with a lower low is expansion or transition under this taxonomy, not an uptrend or downtrend. Preserve the conflict because it changes the intraday plan.

If/then preparation

Write the Week as Branches, Not a Point Forecast

Each branch names evidence, a response and an invalidation. The levels below are hypothetical and exist only to show structure.

Observed pathWorking interpretationIntraday requirementContext invalidation
Holds above confirmed 1.3020 swing high after a causal retestPossible acceptance above the prior weekly boundaryLong candidates may receive priority only if local quality and trigger rules passSustained trade back inside the declared boundary or event-policy failure
Probes above 1.3020 and closes back belowFailed probe hypothesis, not automatic reversalRequire a separate short trigger; do not short merely because the break failedFresh acceptance above the boundary
Trades between 1.2680 and 1.3020 without confirmationContained weekly rangeAvoid middle-of-range directional bias; define local edges independentlyConfirmed break under the frozen rule
Breaks below 1.2680 during a scheduled macro eventTransition candidate with event riskApply the written news and spread gate before interpreting the printFeed failure, non-executable spread or recovery above the declared failure level
weekly range = 1.3020 - 1.2680 = 0.0340340 ticks × $6.25 = $2,125 per 6B

The full-swing dollar figure is scale context, not a suggested stop or expected move. A weekly boundary can be useful while being far too wide for the intended trade risk.

From weekly to executable

Hand Off Conditions, Not Conviction

The intraday plan needs a compact set of facts it can accept, reject or classify as irrelevant. It should not inherit a vague instruction to "buy dips because weekly is bullish."

Required handoff packet

  • Exact dated contract and continuous-series version.
  • Analysis cutoff and session timezone.
  • Last two confirmed pivot highs/lows and availability times.
  • Pending, unconfirmed extremes kept separate.
  • Scenario boundaries and what invalidates each context.
  • Scheduled BoE, Fed and official-data windows inside the plan.

Context modifiers, not triggers

  • CFTC positioning is Tuesday data generally released Friday; label that lag.
  • Open interest and volume help audit contract selection, not predict direction.
  • Relative rates can explain repricing but need synchronized timestamps.
  • Broad USD evidence must not double-count GBP/USD itself.
  • A weekly state never overrides spread, feed, size or event gates.

Weekly preparation worksheet

A Completed Map Should Be Reproducible Next Week

Store the worksheet even when the conclusion is "no directional filter." That result prevents hindsight from converting an ambiguous week into an obvious story.

BlockFields to completeFail-closed rule
Data identityVendor/feed, timezone, session, price type, dated contract, continuous symbol and adjustmentUnknown construction means no level transfer to orders
Roll auditOutgoing/incoming contracts, switch date, price gap, volume/open-interest context, delivery deadlineUnreconciled roll means affected swing is provisional
Confirmed structurePivot rule/version, four latest confirmed pivots, availability timestamps, state labelFuture-dependent pivot stays pending
Range and locationConfirmed boundaries, current price percentile, calculation timestampDo not call location cheap/expensive without a declared reference
Known calendarOfficial source, event time, timezone, revision risk, trade restrictionsUnresolved time conversion blocks the affected window
Scenario setAt least two competing paths, evidence required, invalidation and expiryA single path is an opinion, not a scenario plan
Intraday handoffPriority, prohibited zones, actionable boundaries, local trigger required, max riskWeekly conviction cannot waive local gates
ReviewWhat occurred, what was knowable, any rule change, data issue and decision impactNo moving pivots or boundaries after outcome
Sources, method and editorial disclosure

Sources and exchange terms were reviewed August 13, 2026. The pivot rule, prices and scenario matrix are explicit editorial examples, not findings. No study is reported and no weekly state is claimed to predict return. A predictive claim would require a frozen implementation, complete event history, roll treatment, realistic costs and untouched out-of-sample validation.