01 / DECISION
When this primitive earns a place
Cache responses only when users can safely reuse the same representation under a known cache key.
02 / ARCHITECTURE
Build the smallest defensible path
Classify public and personalized routes, define Cache-Control and key inputs, then document bypass and purge paths before increasing TTL.
- 01Name the contract
Cache responses only when users can safely reuse the same representation under a known cache key.
- 02Add one primitive
Classify public and personalized routes, define Cache-Control and key inputs, then document bypass and purge paths before increasing TTL.
- 03Capture failure evidence
Record cache status, age, vary inputs, and origin load before and after the rule; test purge and bypass explicitly.
03 / REPRODUCE
Evidence before confidence
Record cache status, age, vary inputs, and origin load before and after the rule; test purge and bypass explicitly.
curl -sI https://example.com/ | rg "cf-cache-status|cache-control|age"04 / BOUNDARY
The production boundary
Caching authenticated or user-specific content under an incomplete key can leak data. Cache misses can also hide origin capacity problems.
05 / FIRST-PARTY SOURCES
Keep first-party sources authoritative
Product behavior, limits, pricing, and availability can change. Re-check these sources before acting.