When validating LLM-generated news digests that cite specific economic figures, always check the generation timestamp (from debug manifest or logs) against the official data release schedule. If the digest was generated BEFORE the data release, any specific figure cited is necessarily from forecast articles, prior-month data, or LLM hallucination — not the actual release.
Concrete example: A Pulse AM vibe generated at 06:41 ET cited 'wage growth at 4.4%' from BLS. The actual BLS Employment Situation report released at 08:30 ET showed 3.5%. The grounded search picked up pre-release forecast articles and the LLM synthesized a specific number that turned out to be wrong.
The fix pattern: (1) maintain a calendar of known data release times (BLS first-Friday 8:30 ET, Fed FOMC 2:00 PM ET, CPI 8:30 ET), (2) either delay generation until after the release, or (3) add prompt guardrails instructing the LLM not to cite specific figures from unreleased reports. This applies to any automated content system that runs on a schedule and references time-sensitive economic data.