Scope and best use
Start with the four questions the workspace is designed to answer before each decision.
The four questions
- Which side currently has the stronger case?
- Has that advantage already been priced into UP or DOWN?
- Can it survive the real cost of entering at the intended size?
- What evidence would weaken or invalidate the read?
BTC 5-min organizes information for these decisions. It does not execute a trade or guarantee an outcome.
Current round and recent rounds
Keep every observation attached to the correct BTC 5-min round and phase.
Start in Current Round
Confirm the market title, start and end time, remaining time and LIVE status before reading any signal. The Current Round keeps live observations together; Recent Rounds lets you open a completed round, inspect its evidence and return to live mode without mixing the two.
Settlement baseline and round prices
Read the target, BTC distance, contract prices and remaining time on one clock.
Read the shared baseline
Round Prices places Price to Beat, Reference Now, BTC Distance, UP and DOWN prices and the remaining clock in one view. BTC Distance shows where the reference price is relative to the settlement target; contract prices show how the market is currently pricing each outcome.
Read these fields together and on the same timestamp. A favorable BTC distance can already be reflected in an expensive contract.
Round snapshot and decision engines
Use the snapshot for the current read, then inspect which engines agree or conflict.
Read the conclusion, then its support
Round Snapshot summarizes the current directional read and engine agreement. Decision Intelligence exposes the four components behind it: settlement tendency, odds value, capital confirmation and reversal risk. Agreement may strengthen the case; a conflict should lower confidence and remain visible.
An alignment such as 3 / 4 or 4 / 4 is the number of engines agreeing, not a win probability.
Buy cost and executable depth
Test whether a visible advantage survives the real cost of entering at your order size.
Test the intended order size
Buy Cost supports a custom amount and 10U, 50U, 100U and 200U presets. Compare Est Avg with Best Ask, then inspect price impact, estimated fee, fill and expected profit. Show Depth reveals whether enough liquidity is visible behind the estimate.
VWAP(Q) = Σ(priceᵢ × filledᵢ) / Σ(filledᵢ)
If displayed depth cannot fill the selected amount, the workspace does not invent the missing liquidity.
Polymarket market flow
Compare observable buying and selling pressure over short, synchronized windows.
Compare pressure, not just totals
Market Flow separates observable BUY and SELL activity for UP and DOWN over 10, 30 and 60-second windows. Use directional net and the change between windows to judge whether capital is confirming, weakening or contradicting the current read.
Unknown-direction trades remain excluded. Flow is confirmation evidence, not a standalone instruction.
Round events
Use the event timeline to see what changed before price or direction changed.
Follow the sequence
Round Events records changes such as baseline crossings, flow bursts, spread widening, depth drops, large trades and data-status changes. Alert settings let you control which events deserve attention.
The timeline helps answer what changed first. Event timing provides chronology, not a trade instruction.
Large trades and wallet context
Separate meaningful large-trade activity from ordinary market noise, with wallet history as context.
Use large trades as context
Large Trades groups observable activity reaching 100U into Buy UP, Buy DOWN, Sell UP and Sell DOWN. For a visible wallet, the 72-hour settled history, win rate and sample size add context to the event.
Historical wallet performance describes prior observations; it is not a prediction of the current round.
Binance and major-coin context
Check whether external spot, order-book and major-coin behavior confirms or challenges the read.
Check external confirmation
Binance Market shows BTC/USDT price, volume and active buying or selling across selectable intervals and ranges. Major-coin Direction compares BTC, ETH, SOL and BNB over 30 seconds, 60 seconds and five minutes. Binance Order Book adds near-book depth and executed pressure.
Broad confirmation can strengthen a read; divergence or opposing book pressure should remain visible as a challenge.
Recent rounds, replay and audit
Review resolved rounds to understand the evidence sequence, not just the final result.
Review evidence, not only outcomes
Recent Rounds opens resolved observations with the same decision modules used during the live round. Replay restores the evidence sequence; Audit exposes the recorded state used by the workspace.
Use the review to improve process discipline. A resolved result does not make every earlier signal correct, and historical behavior does not guarantee the next round.
Data status and fallback
Treat freshness, conflicts and missing fields as part of the decision, not as invisible technical details.
Read status before direction
- VERIFIED
- Normal use with verified source context.
- PROVISIONAL
- Use as reference with lower weight.
- STALE
- Do not treat an old value as current.
- CONFLICT
- Sources disagree; keep the disagreement visible.
- UNAVAILABLE
- Omit the field from the directional case.
A blank, dash or waiting state is not zero and is not neutral. Last-known data is useful only when its age and degraded state remain visible.
Versioning and a repeatable routine
Finish with a consistent seven-step routine that can be repeated in every round.
Seven-step routine
- Confirm the settlement baseline, BTC distance and remaining time.
- Read Round Snapshot and the four decision engines.
- Check whether the stronger side is already priced in.
- Test the intended amount in Buy Cost and visible depth.
- Confirm with flow, large trades and Binance context.
- Define which change would weaken or invalidate the read.
- Review the evidence sequence after resolution before the next round.
- Method version
- btc5m-v1.0.0
- Review rule
- A material source, calculation, threshold, exclusion or quality-state change requires a dated review and, when needed, a new method version.