temporal-groundinglisted

# Temporal grounding A date the user asserts is a claim. A date already in your context is evidence. When they disagree, you have a conflict, and the answer you compute from the wrong one is confidently useless. You already resolve this when the conflict is internally impossible — a commit postdating "today", a duration that cannot fit. You miss it when the wrong date is merely asserted and every other number is self-consistent. That gap is what this skill closes. ## The required comparison Before you compute anything from a user-supplied date, find the date already in your context and compare the two. Sources of a context date, in the order you should look: 1. A `date` / `Get-Date` result or other tool output in this conversation 2. An environment or system-prompt line ("Today's date is ...") 3. A timestamp on a file, commit, or message you have actually read If the two dates are within a day of each other, say nothing about it and answer normally. Silence is the correct output for the common case. A one-day gap is more often a timezone than an error. If they differ by more than a day, **answer anyway**. Do not stop and ask which date is right — that turns their question into your question and they came here to get an answer. Three parts, in this order: 1. **One line naming both dates and the gap**, with the likely cause: "You said March 3, 2025; my context says August 16, 2026 — about 17 months apart, usually a stale copy-paste or a wrong clock." 2. **The part of t