Contents · 6 / 12
OHLCV invariants and ordered unique dates
Updated 4 August 2026 · 4 min read · 16 Contents
Plain-language meaning
OHLCV invariants and ordered unique dates means examining the provenance, timestamps, identity, units, missingness and reproducibility of every market or research observation with the identity, period, unit, source and limitations kept visible. It is a disciplined way to describe evidence, not a shortcut to an investment conclusion.
Learning objectives #
After this chapter you should be able to define ohlcv invariants and ordered unique dates, identify the evidence needed to use it, distinguish a reported zero from unavailable evidence, and explain why unlike instruments or periods may not be comparable.
Prerequisites #
Read “Currency, unit, scale and decimal precision” first. Be comfortable checking an exact listing or instrument, its source, observation date, native currency and unit. When any one of those is unknown, pause the comparison and record the gap.
Core concept #
Valid OHLCV has one ordered bar per key/date with low ≤ open/close ≤ high and nonnegative volume. Preserve raw facts separately from interpretation, and retain the denominator, time window, classification rule and provenance that make the evidence reproducible.
Method #
For ohlcv invariants and ordered unique dates, first identify the exact evidence named in this chapter: Valid OHLCV has one ordered bar per key/date with low ≤ open/close ≤ high and nonnegative volume. Then freeze identity and period, collect source-backed inputs with units, calculate or classify only compatible evidence, and record contrary facts and unavailable fields.
Where it appears in XMarketRadar #
Source, retrieved-at, as-of and unavailable labels appear across XMarketRadar. The Help catalogue itself is checked-in editorial data and has no live dependency. A displayed field is useful only with its source and as-of context. If XMarketRadar does not calculate this chapter’s concept directly, use the chapter as an educational checklist and retain the supporting primary document or screen URL in the research workspace.
Worked example #
O=100,H=105,L=98,C=102,V=1,000 passes; H=99 fails because open 100 exceeds high. Module context: Illustrative verified close is CU 100 at 16:00 on 3-Aug-2026, retrieved 16:08; a failed 4-Aug fetch retains CU 100 labelled 3-Aug stale or shows —, never a fabricated CU 101. This is an illustrative audit trail, not live data, a target or an expected outcome.
Interpretation #
Interpret the result in the direction defined by the field, not by an assumed desirable outcome. Higher, lower, positive and negative can each have different meanings by context. Compare the observation with its own history or a compatible benchmark, and label conclusions as observations, interpretations or user decisions.
Limitations and common mistakes #
Sorting text dates or retaining duplicate session rows. Providers can revise history, disagree on adjustments, return duplicate dates, omit fields or use timestamps that represent retrieval rather than observation. A precise calculation can still mislead when the source is stale, the denominator changed, or a classification hides important detail.
Market and jurisdiction differences #
Sessions, holidays, symbol systems, licensed fields, decimal scales and corporate-action sources vary. An empty international universe never falls back to another exchange. Exchange rules, accounting conventions, calendars, taxes, disclosure timing, quote scale and licensed coverage can differ. Verify the current primary source for the relevant venue; registry support alone does not prove that every field is available.
Key takeaways #
For ohlcv invariants and ordered unique dates, remember this boundary: Sorting text dates or retaining duplicate session rows. Keep the evidence exact, dated and source-backed; publish missing information as unavailable rather than manufacturing a value.
Practice #
Reproduce this historical scenario from source-labelled inputs: O=100,H=105,L=98,C=102,V=1,000 passes; H=99 fails because open 100 exceeds high. Then change one input, preserve the original period and unit, and explain whether the result changes or becomes unavailable. Write the identity, source, date, unit and failure condition, then state exactly what would display as —.
Knowledge check #
Reveal answer and explanation
Question: which mistake would invalidate a review of ohlcv invariants and ordered unique dates? Answer: Sorting text dates or retaining duplicate session rows. Explanation: the chapter requires the stated identity, period, unit and compatible evidence; a missing required input remains — rather than 0.
Educational use only #
This chapter is descriptive education, not investment advice, a forecast, a recommendation, a suitability assessment or an instruction to buy, sell, rebalance, trade or place an order. XMarketRadar’s broker connections remain read-only.