Bound the directory query cache
Browsing many searches grows memory indefinitely. Introduce capacity and expiry with deterministic eviction.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Caching · Memory
Estimated field mix
- Performance engineering60%
- Frontend40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional workshop directory Cedar lists tools and spare parts using a local search adapter.
Setup prerequisites
- Create synthetic items with stable identifiers.
- Stub cursor pages, facets, delayed responses and missing items.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Capacity is configurable
- Keys contain all query dimensions
- Expired entries refresh visibly
Implementation constraints
- Cache public directory records only.
Verification to include
- Revisit retained query
- Exceed capacity and inspect eviction
Deliverables
- Cache policy and clock tests
Rollout and recovery
Disable cache and fetch committed queries.
Value of the work
For the engineer: Practice URL contracts and request ownership.
For the team: Inspect whether discovery intent survives changing results.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.