Fair Value Tracker: Use Scanner To Prioritize Monitoring, Not Execution
A practical Fair Value Tracker lesson for reading scanner rows as a triage queue into Overview, History, or Alerts instead of an execution list.
Lesson promise
Frame the question
Which asset and contract pair deserves my attention first?
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
Read scanner rank as a priority queue
Trader question
Which asset and contract pair deserves my attention first?
Scanner rank is a workflow sorter. It helps the learner decide which row to inspect first, but rank is not a recommendation and should never skip source, contract, confidence, and history checks.
Desk checklist
- Read rank as attention priority.
- Name the row's asset and contract pair.
- Keep the row inside a checklist, not an execution path.
Interactive proof
Scanner tab, rank column, asset, contract pair, and row order
Use the scanner triage game to route rows into inspect now, compare history, set alert, or ignore.
Scanner is an attention router. A row earns the next workflow only after confidence, regime, source freshness, and contract lane pass the quality gate.
Interactive desk lab
Scanner Triage Game
A practical Fair Value Tracker scanner triage game for sorting rows into inspect now, compare history, set alert, or ignore for data quality before treating rank as monitoring priority.
A practical Fair Value Tracker scanner triage game for sorting rows into inspect now, compare history, set alert, or ignore for data quality before treating rank as monitoring priority.
Rank is a priority queue
A rank badge moves beside the checklist while execution language stays blocked.
A rank one row enters the scanner.
The rank badge attaches to a checklist, not an order ticket.
A blocked execution label fades out.
The final frame says inspect first.
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
Read scanner rank as a priority queue
Which asset and contract pair deserves my attention first?
Scanner rank is a workflow sorter. It helps the learner decide which row to inspect first, but rank is not a recommendation and should never skip source, contract, confidence, and history checks.
Scanner tab, rank column, asset, contract pair, and row order
- Read rank as attention priority.
- Name the row's asset and contract pair.
- Keep the row inside a checklist, not an execution path.
Chapter 02
Check confidence and regime before basis size
Is the row good enough to study before the gap size impresses me?
Confidence and regime decide whether a scanner row is usable. A large basis with stale, estimated, or low-confidence source state should move behind cleaner rows or out of the queue.
Scanner confidence, regime tag, signal state, and z-score columns
- Check confidence before basis size.
- Check regime and signal state before ranking the row.
- Downgrade stale or estimated rows even when the basis is large.
Chapter 03
Separate best watch from largest basis
Is the best monitoring candidate the same as the biggest number?
The best watch row can be the one with clean sources, useful z-score context, and high confidence. The largest basis row can still be weaker if the source state, contract lane, or regime is poor.
Best watch, highest confidence, largest basis insight cards
- Compare highest confidence with largest basis.
- Explain why a smaller gap can deserve attention first.
- Keep large-basis rows caveated until data quality is clear.
Chapter 04
Use row actions as study paths
What should I do with a scanner row after it earns attention?
Scanner actions should route the learner into Overview, Spread Monitor, or Alerts. View means inspect the current read, compare means check pattern context, and alert means create an attention rule with filters.
Scanner row actions: view, compare, alert
- Use view when the row needs a first-read check.
- Use compare when the row needs historical context.
- Use alert only as monitoring hygiene, not execution automation.
Chapter 05
Ignore rows that fail data quality
Which scanner row would I ignore even if the basis is large?
The learner should practice rejecting noisy temptation. A row with large basis but low confidence, stale source state, estimated local leg, or contract mismatch should be ignored or paused before it becomes a story.
Scanner row, confidence, regime, estimated state, and contract selector
- Spot the largest basis row.
- Check whether confidence and regime support it.
- Ignore or pause when the quality gate fails.
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.