ed/manual_slop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(conductor): Add per-response metrics requirement to caching optimization track

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-03-08 13:55:32 -04:00
parent d7083fc73f
commit 235b369d15
2 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
conductor/tracks/caching_optimization_20260308/spec.md
View File

@@ -35,6 +35,7 @@ This track aims to verify and optimize the caching strategies across all support
- Add a "Force Cache Rebuild" button to invalidate existing caches and start fresh.
- Add a "Clear Provider Caches" button to explicitly delete server-side caches (primarily for Gemini).
- **Cache Awareness:** Display a visual indicator (e.g., a "Cached" badge) next to files in the Context Hub that are currently part of a cached prefix.
- **Per-Response Comms Metrics:** Ensure each response entry in the Comms Log displays its specific token usage (input, output, cached) directly in the list or detail view for immediate verification of caching efficacy.
## Non-Functional Requirements
- **Efficiency:** The caching logic itself must not introduce significant overhead or latency.