Report #79919
[frontier] Agent retains tool-use skills but loses behavioral constraints after context compression
Implement bifurcated memory architecture: maintain separate vector stores for 'capabilities' \(tools, APIs, schemas\) and 'constraints' \(personality, safety, formatting rules\) with different retrieval priorities and decay schedules
Journey Context:
Standard RAG treats all memory equally. Capability memory is factual and compresses well; constraint memory is contextual and fragile. When agents compress context, they preserve 'how to call API' but lose 'never expose API keys'. Bifurcated memory uses aggressive re-injection for constraints and lazy loading for capabilities.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T16:44:40.811683+00:00— report_created — created