Methodology

Market Status Methodology

This page defines the public Market Status metrics used across ConfluenceMeter. The current version is built around a single primary score, regime as context, agreement across timeframes, and family-level explanations.

Use as context, not signalsHub updated ~5 minutes1h closes stored as historyPublic view is intentionally simplified
Reference links
Quick links for citing Market Status

If you want to reference Market Status in an article, report, or newsletter, use the hub link together with the visible timestamp. For reproducible references, link the CSV export you used.

Hub
https://confluencemeter.com/market-status
Rankings, summaries, and current market context.
CSV snapshot
https://confluencemeter.com/api/public-dashboard?format=csv
Latest hub snapshot for citations or audits.
CSV example (BTC 1h history)
https://confluencemeter.com/api/market-status/pair?pair=btc-usdt&format=csv&series=history_1h
Closed 1h history series export.
Definition
Score (0–100)

The Score is the main confluence output for a timeframe.

  • • Around 50 often means mixed evidence.
  • • Farther from 50 means clearer directional bias in that timeframe.
  • • The score is direct and authoritative. It is not blended with a second hidden trust score.
Neutral zone: ~40–60Clearer: <40 or >60
Definition
Regime (trend / range)

Regime classifies the current context as more trend-like or more range-like.

  • trend: directional continuation is more plausible.
  • range: rotation and mean-reversion matter more.
  • • Regime helps interpretation, but it does not suppress or cap the score.
In the current version, regime is context only — never a hidden gate.
Definition
Data Quality (0–1)

Data Quality measures how much of the expected evidence set was actually available in that snapshot.

  • • It is a technical completeness metric, not a market-opportunity metric.
  • • High data quality means more of the intended indicator set was present.
  • • Low data quality means the snapshot is less complete, even if a score is still available.
0.00–1.00 scaleSnapshot completeness
Definition
Family breakdowns

Market Status can group evidence into families such as trend, momentum, volatility, and volume.

  • • Each family can contribute in a different direction.
  • • Family readings are explanatory context, not separate signals.
  • • The public view may show simplified family summaries, while the app can show more detail.
Example reading: trend bullish, momentum neutral, volatility noisy, volume supportive.
Definition
Agreement (1h-led)

Agreement measures how consistent tracked timeframes are with the 1h stance.

  • • High agreement = fewer timeframe conflicts.
  • • Low agreement = mixed stack and higher noise risk.
  • • A neutral 1h stance is valid and means conditions are not clearly biased.
70%+ = highly consistent40–69% = mixed stack<40% = conflict-heavy
Data
Update cadence and history
  • Hub refresh: roughly every ~5 minutes.
  • History series: uses closed 1h candles, which are more stable than fast intrabar reads.
  • Data availability: new symbols may show limited history until enough 1h closes accumulate.
Practical rule: read Score + Regime + Agreement first, then use family context to understand why.
Architecture
What changed in the current version
  • • Hidden confidence blending was removed from the public framing.
  • • Regime no longer suppresses the score.
  • • Data Quality replaced older public coverage/confidence-style messaging.
  • • The product now exposes one main score plus context, instead of overlapping public trust metrics.
This makes the public explanation cleaner and closer to how the product is actually used.
What it is NOT
Not a signal service

Market Status is not “buy/sell.” It is a conditions filter.

  • • A high score does not mean “buy.”
  • • A low score does not mean “sell.”
  • • Family readings explain context, but do not replace execution rules.
Treating context metrics as direct signals is how people overtrade.
Limits
Limitations and edge cases
  • • Sudden news events can invalidate recent context fast.
  • • Low-liquidity assets can create noisier readings.
  • • During extreme volatility, score may move quickly while regime still warns of instability.
  • • If history is short, treat long-horizon comparisons cautiously.
Always interpret the numbers together with timestamps and broader market context.
Citable source
How to cite

Use the hub or a symbol page as the referenced page, together with the visible timestamp and access date. For reproducible references, prefer the CSV export used in your analysis.

Suggested citation
ConfluenceMeter — Market Status Methodology. Accessed 2026-04-21. https://confluencemeter.com/market-status/methodology
Exports (recommended)
  • • Hub snapshot CSV: https://confluencemeter.com/api/public-dashboard?format=csv
  • • Symbol 1h history CSV (example): https://confluencemeter.com/api/market-status/pair?pair=btc-usdt&format=csv&series=history_1h