Troubleshooting, System Delays, and Compliance FAQ

Why didn't an asset generate a summary?

You may occasionally see "empty cards" for an asset that has experienced a large price swing. This typically occurs for a few specific reasons:

• Insufficient Corroboration: There was a large price move, but the system found insufficient source corroboration or story context to confidently explain it. Market Reader prioritizes accuracy over volume and will not publish a summary if it lacks a high enough Information Score.
• Illiquidity: The asset may be highly illiquid or an obscure derivative (like a levered ETF) where there is no active news or trading volume driving the anomaly.
• Intraday Mean Reversions: Sometimes an asset experiences unusual volatility within a specific 10-minute window, triggering the system, but the price quickly reverts to zero. The system will still record the analysis for that 10-minute spike, but the net daily move may appear flat.
• Pipeline Failure: If there is a failure point in the underlying data flow or models for a specific stock, the system will intentionally withhold publication rather than push an incomplete analysis.

Why is there a delay between a news headline and the summary?

Market Reader utilizes an intentional 10-minute analysis window, meaning there is typically a 5-to-15 minute delay after a headline breaks before an explanation is published.

• Analytical Delay (Intentional): This delay is a feature, not a bug. It prevents the system from blindly reacting to split-second headlines. The 10-minute window allows the system to verify the actual price reaction, wait for corroborating chatter to propagate on social media, and weed out false rumors before generating a high-confidence explanation.
• Visual UI Delay (NASDAQ Licensing): If you are using the web platform's visual UI, you will experience a strict 15-minute delay on real-time pricing and visual triggers. This is a legal requirement to comply with NASDAQ exchange licensing restrictions. To receive true real-time analysis the moment the 10-minute analytical window concludes, clients must use the WebSockets API.

How does Market Reader handle conflicting news sources?

Market Reader operates a rigorous "Layer B" inline Quality Assurance (QA) evaluator that checks every generated output before it is committed.

• The evaluator explicitly compares the AI-generated outputs against the original source inputs.
• If the generated summary materially misrepresents the source material—such as changing a number, contradicting supplied context, or omitting a salient point—the system fails the output.
• Instead of publishing conflicting information, the system forces a stateless rerun of the summarizer with the same inputs. It will attempt this up to three times; if it persistently fails, the row is excluded from user-facing surfaces entirely.

Does Market Reader provide forward-looking investment advice?

No. Market Reader operates under a strict compliance boundary as an "objective scientist" explaining what has already happened in the market. It does not forecast future prices, offer buy/sell ratings, or provide investment advice.

• Hard-Check Constraints: The QA evaluator features non-negotiable "hard checks". It will automatically fail and block any output that contains a forward-looking statement or prediction in Market Reader's own voice.
• Investment Advice Ban: Any summary that attempts to recommend buying, holding, allocating, or sizing positions will trigger a critical failure and be blocked from publication.
• Note on third-party sources: The system is permitted to report on forward-looking statements if they are explicitly attributed to a third party (e.g., "Company X issued forward earnings guidance" or "A social media user predicted X"), but it will never assert these claims as Market Reader's own expectation.