Repository navigation
Ask knows what day it is; pin the notebook's re-tag behaviour - #249
Merged
Merged
Conversation
Told 'runway is 8 months' on 9 Oct 2026, Finance dated the deadline 'June 2026': nothing in the Ask context said what today was. The context now opens with 'Today is 2026-10-09 (October 2026)', ISO for arithmetic and the month name so a deadline lands on a month the model can name. In the per-request context, not the cached system prompt, which must stay byte-identical across days for the prefix cache to hit. First in the context so the CONTEXT_CAP clip can never trim it. Store-level test pins that the request carries it (red with the store line removed). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An ordinary turn straight after a Finance turn records no department, and its re-record of the same topic takes it off Finance's desk. - A company-wide re-record clears the tag at merge level. - End to end: once Sales re-records Finance's price, Finance's desk no longer lists it and Sales' does. Characterisation tests: the behaviour was already right; these fail if it stops being so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two follow-ups from #248.
Ask knows what day it is
Told "runway is 8 months" on 9 Oct 2026, Finance dated the deadline "June 2026", because nothing in the Ask context said what today was.
The context now opens with
Today is 2026-10-09 (October 2026). Count any deadline or runway from this date.The date sits in the per-request context, not the cached system prompt, which has to stay byte-identical across days for the prefix cache to hit. It goes first so theCONTEXT_CAPclip can't trim it.Pinned the notebook's re-tag behaviour (the review minors from #248)
These are characterisation tests. The behaviour was already correct; they fail if it stops being.
On the remaining #248 minor (cap 60 and token cost): chat context is clipped at
CONTEXT_CAP(12,000 chars), so that cost is bounded.extractDecisionsstill sends every existing decision uncapped. It is unchanged here and noted for later.Verified
ChatContextTodayTests(3), which were red untilcomposetook a date.testTheChatRequestCarriesTodaysDate: red with the store'stoday: Date()removed, green with it.CompanyStoreChatTests,DepartmentNotebookTestsandDepartmentSpecialistReachesModelTestsall pass.🤖 Generated with Claude Code