Caching Boundary¶

Stable ID: component.caching
Kind: shared-component
Status: stable
Source: skill/references/shared-components/caching.md

Purpose¶

Make cache keys, freshness, invalidation, ownership, and failure behaviour explicit at a stable boundary.

Use when¶

• Repeated reads are expensive and staleness is acceptable.
• Cache identity and invalidation rules can be defined precisely.
• The system can measure hit rate and stale data risk.

Avoid when¶

• Correctness requires immediately current state.
• No evidence shows repeated work is a bottleneck.
• Invalidation ownership is unclear.

Applicability¶

• Languages: any, python, q-kdbplus, cpp, rust, dart-flutter, typescript
• Related entries: workflow.performance.measurement-first