Discord bot narrates future-dated forecast rows in the past tense #67

New issue

Closed

opened 2026-07-24 22:54:53 +00:00 by admin_emi · 0 comments

admin_emi commented

2026-07-24 22:54:53 +00:00

Owner

This is forecast data presented to the user as observation. Likely related to (but a distinct symptom from) the date-gap/boundary-artifact issue tracked separately — this one is specifically about the narration/copy layer not distinguishing "this row is a forecast" from "this row already happened," regardless of the underlying data-window bug. Worth checking whether the grade-card builder has access to a forecast-vs-observed flag per row and whether the narration template (or whatever generates natural-language commentary) respects it.

Observed live in the community Discord: asked to "roast" a location's weather, the bot's grade-card narration described forecast days (27th, 29th, 30th of the month — still in the future relative to the query date) as though they had already happened: *"on the 29th it logged…"*, *"the 30th topped out at 69"*, *"it has been dry-and-gray or wet-and-gray every day since"*, *"peaked on a Tuesday and has been coasting on it for two weeks."* This is forecast data presented to the user as observation. Likely related to (but a distinct symptom from) the date-gap/boundary-artifact issue tracked separately — this one is specifically about the narration/copy layer not distinguishing "this row is a forecast" from "this row already happened," regardless of the underlying data-window bug. Worth checking whether the grade-card builder has access to a forecast-vs-observed flag per row and whether the narration template (or whatever generates natural-language commentary) respects it.