Applied ArtifactApril 2026Foundation Stage

Sample Market
Observation Record

A demonstration of how the Market Observation Record Standard is applied in practice. This is a fictional, generalized example—not a live security recommendation or trading signal.

Observation record

A complete market observation record for a stale, disputed liquidity signal.

Observation ID
MO-2026-0413-001
Timestamp Observed
2026-04-13T09:47:00Z
Source Type
Alternative data
Source Attribution
VendorX Liquidity Monitor (institutional data feed)
Instrument / Entity
Generic broad-market equity index futures (unnamed benchmark)
Market Domain
Equity derivatives
Observation Type
Liquidity observation
Raw Claim
"Bid-ask spreads in the front-month contract widened 18% versus the 30-day rolling average during the opening auction. Depth at the top three price levels declined 31%."
Structured Summary
Front-month equity index futures: bid-ask spread +18% vs 30D MA; top-3-level depth -31%. Measured during opening auction (09:30–09:35).
Truth-State
Stale
Freshness Window
15 minutes for intraday liquidity signals
Confidence Posture
Medium. Vendor methodology is transparent, but the observation was captured 12 minutes past the freshness window and has not been validated by a second source.
Context Tags
Opening auction, options expiration week, macro release window (CPI scheduled 08:30 same day)
Conflicts Detected
Yes. Exchange-reported opening auction data shows spread widening of 9% (not 18%) and depth decline of 14% (not 31%).
Missing Dimensions
No futures-options delta-hedging flow estimate available. No cross-asset (fixed income / FX) liquidity comparison available.
Operator Notes
Discrepancy between vendor and exchange data requires resolution before this signal can influence any downstream reasoning. Do not proceed until secondary source confirms magnitude or explains variance.
Escalation Flag
True. Disputed magnitude + stale window = automatic block from reasoning pipeline pending review.

Truth-state rationale

This observation is labeled Stale because it was captured at 09:47Z, twelve minutes past the defined 15-minute freshness window for intraday liquidity signals. By the time the record reached the classification layer, the market microstructure conditions it described may have already shifted.

It is also flagged Disputedbecause the exchange-reported opening auction data conflicts materially with the vendor's estimate. The vendor reports 18% spread widening; the exchange reports 9%. The vendor reports 31% depth decline; the exchange reports 14%. Without resolution, neither figure can be treated as reliable.

The combination of stale + disputed triggers an automatic escalation. The observation cannot enter the reasoning pipeline until an operator resolves the conflict or explicitly overrides the block.

Allowed downstream uses

  • Log the record in the audit ledger with full attribution and conflict flags.
  • Trigger a source-reconciliation workflow to resolve the vendor/exchange discrepancy.
  • Notify the operator that a stale, disputed liquidity signal requires review.
  • Use the record as a case study for calibration of vendor data quality scoring.
  • Include the observation in a post-mortem analysis of auction-period data variance.

Prohibited downstream uses

  • Feed into real-time risk models without explicit operator override and re-validation.
  • Use as a sole justification for any allocation or positioning decision.
  • Blend with live observations without clear labeling of stale and disputed status.
  • Present to any external party as a verified market fact.
  • Trigger automated alerts implying immediate action is required.

Operator review notes

Review timestamp2026-04-13T10:15:00Z

Operator judgmentThe magnitude discrepancy between VendorX and the exchange is too large to ignore. Possible explanations include: (a) different measurement windows within the auction, (b) different depth aggregation methodologies, or (c) a vendor calibration error. I am requesting vendor clarification before this signal is released from escalation.

DecisionDefer / Block

Conditions for releaseVendor must provide auction-subsecond methodology documentation, or a second independent source must confirm the 18% / 31% figures, or the observation must be downgraded to an unverified alternative-data flag with no downstream weighting.

Audit trail stub

09:47:00ZObservation captured
09:48:12ZClassification complete — truth-state: Stale
09:48:15ZConflict detected — exchange data mismatch
09:48:16ZEscalation flag set — automatic block
10:15:00ZOperator review — decision: Defer / Block
PendingVendor clarification requested

Disclaimer

This artifact is for research, educational, and product-development purposes only. It is not investment advice, not a recommendation to buy or sell any financial instrument, and not an offer to manage capital.

Veldarium Capital is a research and software initiative of Veldarium Technology Systems LLC. It does not manage outside capital, provide personalized investment advice, or offer trade recommendations.