-
Notifications
You must be signed in to change notification settings - Fork 323
feat: Tiered history retrieval (hot/cold layer pattern) #595
Copy link
Copy link
Open
Labels
go:needs-researchNeeds investigationNeeds investigationpriority:p2Next sprintNext sprintsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:dskyAssigned to DSKY (TUI Engineer)Assigned to DSKY (TUI Engineer)squad:proceduresAssigned to Procedures (Prompt Engineer)Assigned to Procedures (Prompt Engineer)type:featureNew capabilityNew capability
Metadata
Metadata
Assignees
Labels
go:needs-researchNeeds investigationNeeds investigationpriority:p2Next sprintNext sprintsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:dskyAssigned to DSKY (TUI Engineer)Assigned to DSKY (TUI Engineer)squad:proceduresAssigned to Procedures (Prompt Engineer)Assigned to Procedures (Prompt Engineer)type:featureNew capabilityNew capability
Feature Proposal: Tiered History Retrieval
Problem
Agent history.md files grow unbounded. Currently Scribe summarizes at 12KB, but agents read everything — no distinction between recent context and archived knowledge. This wastes context window tokens and slows agent startup.
Proposed Solution
Formalize a two-tier retrieval pattern inspired by ClawMongo's tiered projection model:
Hot layer (history.md): Last ~20 entries. Always read at spawn time. Fresh, actionable context.
Cold layer (history-archive.md): Summarized older entries. Read only when agent explicitly needs historical context.
Implementation
Benefits
Prior Art
Inspired by ClawMongo's tiered retrieval model (https://clawmongo.site) which uses ID-only projections for 10x context reduction. Adapted for Squad's file-based architecture.