Give the model a date lookup table instead of date arithmetic
Told the rule twice, it still wrote 14 August for "next Friday" asked on a Sunday. So stop asking it to calculate: todaySection() now emits the next occurrence of every weekday, pre-computed, and says to read the table. Verified it rolls correctly when today is itself a Friday. Same run also pushed the estimate from 10 to 20 by adding the requested hours to the existing ones, and overwrote a due date the request never mentioned. Both fields now say so explicitly in the update schema: the estimate REPLACES rather than accumulates, and due_date must be omitted unless the current request asks for it to change.
| Repository | pdombkins/rose_lawyer |
|---|---|
| Author | Peter Dombkins <pdombkins@gmail.com> |
| Authored | |
| Parents | 52823910 |
| Stats | 3 files changed , +61 , -12 |
| Part of | Guardrails on AI-agent writes to K&S |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-5ad66527.md
from inside the repo you want the change in.