mirror of
https://github.com/teamchong/pxpipe.git
synced 2026-07-22 02:02:51 +02:00
teamchong
50f3f1f86b
New docs/CACHING_AND_SAVINGS.md explains the two things that keep coming up: 1. How pxpipe stays aligned with Anthropic's prompt cache when it images the static prefix: split static/dynamic blocks first (keep drifting <env> etc. as cheap text, never imaged), then relocate (never add) the caller's cache_control onto the last image so the breakpoint anchors at the end of the stable slab. Covers the cache-friendly splice, the symmetric anti-flapping burn term, and the horizon-amortized history-collapse gate. 2. How savings are measured without double-counting the cache discount: both the real request and a count_tokens counterfactual of the original body are priced with identical cache rates at the same moment, so the discount cancels in the difference and only the token reduction survives. Also reconcile the priorWarmTokens JSDoc in transform.ts: the burn term is applied undivided, matching all three gate call sites and the symmetric priorWarmImageTokens doc. The '/ N' was stale (the per-turn gate has no horizon to divide by; the horizon scales the lifetime cost, not the burn).