Implement cache strategy with keys/TTLs/metrics

[JoshuaAFerguson]

Summary

Redis cache exists but usage is ad hoc. Need standard keys/TTLs, invalidation, metrics, and fail-open behavior per design/ADR.

Scope

• Services using cache (templates, org settings, session summaries, user roles, feature flags)
• Cache metrics and error handling

Acceptance Criteria

• Implement keys/TTLs per cache strategy; cache disabled mode remains functional.
• Invalidation on writes; no side-effect caching from non-canonical paths.
• Metrics for hit/miss/error and latency; short timeouts and fail-open behavior.
• Tests: hit/miss/error, invalidation, disabled cache mode.

References

• ../streamspace-design-and-governance/03-system-design/cache-strategy.md
• ../streamspace-design-and-governance/02-architecture/adr-002-cache-layer.md

---

Priority: P2 - Medium (v2.0-beta.2)
Milestone: v2.0-beta.2
Documentation: See ADR-002 for architecture

[JoshuaAFerguson]

📚 Architecture Documented

Cache layer strategy is documented in ADR-002: Redis Cache Layer for Session Metadata

Location: docs/design/architecture/adr-002-cache-layer.md

Status: Accepted (implementation tracked in this issue)

Key Details:

• Redis caching strategy for session metadata
• Cache-aside pattern with TTL management
• Performance improvement targets (10ms → 2ms for reads)
• Cache invalidation on updates

Refer to ADR-002 for the complete architectural rationale and implementation guidance.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.

Action Required:

• If this issue is still relevant, please add a comment to keep it open
• If this is blocked, add the status:blocked label
• If this is no longer needed, it will be closed in 7 days

[github-actions]

This issue was automatically closed due to inactivity.

If you believe this was closed in error, please reopen it with a comment explaining why it should remain open.