AI News Recaps
How cached topic summaries are generated and interpreted.
A recap summarizes recent signals for one topic. The app shows the 12-hour recap window. Use the News guide to select topics and open recaps.
Generation schedule
Recap scheduling starts at 00:02, 06:02, 12:02, and 18:02 UTC. Topic jobs start 45 seconds apart. Completion depends on the queue and provider.
RSS ingestion has separate topic schedules: every 30 minutes, two hours, or six hours. X ingestion runs weekly. A recap can therefore contain sources with different retrieval times.
Opening News or selecting Refresh reads the cache. It does not generate a new recap.
Recap contents
The app displays the main narrative. A structured recap can also contain:
| Content | Meaning |
|---|---|
| Executive summary | A short overview |
| Sentiment | Bullish, bearish, neutral, or unclassified |
| Key developments | Up to six findings with sources and entities |
| Subjects | Up to eight topic clusters |
| Open questions | Up to five questions grounded in the inputs |
| Item count | Number of input signals considered |
| Creation time | When the recap was generated |
The count does not measure total market activity. Sentiment does not predict an outcome.
Fallback output
Y2 can retain an existing recap or provide a summary assembled from cached signals while generation is pending. This fallback can contain different fields from a structured model response. API clients must handle both shapes.
Interpret recaps safely
Review the underlying evidence
Recaps use a limited set of cached signals. They can omit events or repeat source errors. Open the original sources in Live Feed before making a decision.
A missing card can mean no recap is cached for that topic. Quiet topics can display a neutral “no direct signals” message. Source IDs identify inputs. Use Live Feed links to inspect the original source.
Retrieve recaps with the API
The API accepts 12h, 24h, 3d, and 7d. The registry schedules only 12h.
Longer valid windows can return no recap.
Use List recaps for authentication, parameters, and the response schema.