Repository navigation
docs(agents): a cache never changes what a subscription delivers - #9211
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Merge pick (2026-11-19, maintainer): ✅ /quest-merge; the maintainer asked for this rule. (Written by Claude Opus 5.5 with high) |
There was a problem hiding this comment.
✅ No new issues found.
Approach: sound — records the maintainer's stated cache rule in AGENTS.md under Required.
Reviewed changes
AGENTS.mdcache rule: adds one Required bullet saying a cache never changes what a subscription delivers, and a copy answers from cache only what it can prove upstream would answer.
claude-sonnet-5-5 | 𝕏
|
No actionable comments were generated in the recent review. WalkthroughAGENTS.md adds a rule for subscription caches. A copy may answer from its cache only when it can prove the upstream answer. Otherwise, it must update the upstream subscription and wait for the upstream answer. Merge Risk:
|

Summary
Adds a Required rule to
AGENTS.md: a cache only makes things faster. What a subscription delivers never depends on what a copy happens to hold. A copy answers from its cache only what it can prove upstream would answer, and anything else updates the upstream subscription and waits for its answer.Decisions
Maintainer, 2026-11-19 (/quest-complete), while reviewing #9198 and #9172: ✅ "subscriptions MUST NOT change behavior based on cache state" and "The cache is a performance optimization that should not change user behavior. Similar concept to HTTP." A provable answer, such as #8638's time placement between held groups linked by Previous Start, is allowed. The maintainer asked for this rule in AGENTS.md.
Impact
Agent instructions only. Public API: none. Wire: none.
Models
Size: XS
Implementer: Claude Code, claude-opus-5-5, high effort
Review
Skipped: one maintainer-dictated rule, worded from the maintainer's own statements.
(Written by Claude Opus 5.5 with high)
🤖 Generated with Claude Code