Chapter 11: The Weekly Operating Framework

Question answered

Can the reader form a disciplined weekly regime read from dated evidence before seeing the deterministic classifications and separate Score output?

Why it matters

Recording the three dials, dominant-driver hypothesis and conditional explanation before comparison reduces anchoring and turns Chapter 11 into a repeatable practice routine.

Inputs

• Dated DXY and broad-dollar observations
• Dated real-yield and nominal-rate context
• Dated credit, volatility and funding-stress evidence, plus a browser-local driver hypothesis and conditional written reading

Data cadence and timestamp

Latest repository-published completed-week Three-Dials snapshot with an exact-week Score bridge. No market data is retrieved in the browser.

Show the snapshot week and every source observation date. Keep the normal Monday/Tuesday publication window explicit, and disable deterministic comparison if the snapshot is outside the approved cadence.

Use it in three steps

1. Read the dated facts and record the three dials plus an unscored dominant-driver hypothesis.
2. Write what supports the reading and what would challenge it before seeing any deterministic labels.
3. Submit the browser-local reading, compare only the three deterministic dials, then inspect the separate exact-week Score output and return to the relevant chapter or Weekly report.

When the evidence agrees

• Use aligned, partly aligned or materially different for the three deterministic dials rather than correct or incorrect.
• Agreement shows process coherence, not predictive accuracy; the dominant-driver hypothesis remains unscored.

When the evidence diverges

• A dollar disagreement points back to Chapter 3.
• A real-rate or liquidity disagreement points back to Chapter 11 and the relevant primary evidence.
• A driver disagreement is not machine-scored; compare the hypothesis qualitatively with the Weekly report and transmission framework.