Fair Value Tracker: Use Spread Monitor And History To Separate Print From Pattern
A practical Fair Value Tracker lesson for separating a single stretched basis print from a reviewable historical pattern without treating history as a prediction.
Lesson promise
Frame the question
Is this gap unusual, persistent, or just one noisy print?
Check the evidence
Use 5 guided chapters to read freshness, confidence, and caveats in order.
Move into the tool
Open Open Fair Value Tracker with a checklist instead of a blank screen.
Educational workflow only. No trade recommendations, personalized advice, leverage guidance, or guaranteed outcomes.
Chapter 01
Treat one spread print as weak evidence
Trader question
Is this gap unusual, persistent, or just one noisy print?
A single basis print is the beginning of the question, not the end. The learner should compare it with a recent spread path before describing it as stretched, routine, or event-sensitive.
Desk checklist
- Read the current spread after source and contract checks.
- Compare the current dot with nearby observations.
- Avoid writing pattern language from one print alone.
Interactive proof
Spread Monitor current spread, price chart, and basis chart
Use the spread pattern lab to keep the current print fixed while the surrounding history appears.
Spread Monitor turns one print into a reviewable context only after the lookback, history model, source state, and event caveats are visible.
Interactive desk lab
Spread Pattern Lab
A practical Fair Value Tracker spread-pattern lab for using lookback, history model, z-score, percentile, convergence, event, and source caveats before trusting a basis pattern.
A practical Fair Value Tracker spread-pattern lab for using lookback, history model, z-score, percentile, convergence, event, and source caveats before trusting a basis pattern.
One print is not a pattern
A single stretched print is held back until the surrounding basis series appears.
One basis dot appears with a warning label.
The rest of the spread series fades in.
Mean and sigma rails frame the current dot.
The learner sees pattern context before language is allowed.
Lesson notes
The full chapter walkthrough in reading form — use it to review the lesson or skim ahead before working through the interactive steps above.
Chapter 01
Treat one spread print as weak evidence
Is this gap unusual, persistent, or just one noisy print?
A single basis print is the beginning of the question, not the end. The learner should compare it with a recent spread path before describing it as stretched, routine, or event-sensitive.
Spread Monitor current spread, price chart, and basis chart
- Read the current spread after source and contract checks.
- Compare the current dot with nearby observations.
- Avoid writing pattern language from one print alone.
Chapter 02
Choose the lookback that answers the desk question
Am I asking a tactical question or a behavior question?
A 5D lookback can help with a short desk read, while 20D, 60D, and 1Y windows reveal different behavior context. The same basis can look routine or stretched depending on the sample.
Lookback selector: 5D, 20D, 60D, 1Y
- Use 5D for immediate context.
- Use 20D or 60D for a broader desk comparison.
- Use 1Y for behavior context with regime caveats.
Chapter 03
Read z-score and percentile without overconfidence
How unusual is the gap inside the selected history?
Z-score and percentile describe relative unusualness inside the chosen sample. They do not prove that the spread must converge, and they should always travel with lookback, history model, and source caveats.
Historical Analytics z-score, percentile, mean, and sigma rails
- Name the selected lookback.
- Name the history model: global or import.
- Say unusual, stretched, or routine without saying reversion is due.
Chapter 04
Use convergence and events as context
What could explain why this pattern behaves differently now?
Convergence statistics and event overlays can improve the note only when they are treated as context. A macro event, market closure, roll change, or regime break can make a clean-looking history comparison less useful.
Historical Analytics convergence, event overlays, and regime breakdown
- Read convergence as historical behavior, not a promise.
- Check whether an event marker sits near the current print.
- Add regime and event caveats before any monitoring note.
Chapter 05
Ask what weakens the historical comparison
What would make this historical comparison less trustworthy?
The learner should invalidate the history read before leaning on it. Stale sources, changed contract lanes, thin observations, event windows, and model mismatch should move the note from pattern language to caution-only context.
Spread Monitor, Historical Analytics, source state, contract selector, and history model
- Check whether source freshness still supports the history read.
- Check whether the contract selector stayed consistent.
- Downgrade history language when the comparison is weak.
Sources used for this tutorial
Next step
Open the tool with the checklist beside you.
Move from the lesson into the matching Bullion Brains tool, keep the checklist visible, and treat the output as evidence until the caveats are clear.