Report #63843
[frontier] Capability Accumulation vs Constraint Decay \(The Skill/Filter Asymmetry\): Agents accumulate demonstrated capabilities \(tools, patterns, code\) into working memory but lose associated constraints \(when not to use them\), leading to dangerous over-application of skills
Implement "Bifurcated Memory Architecture" - maintain two separate context streams: "Capability Cache" \(append-only, accumulative, stores learned patterns\) and "Constraint Registry" \(refresh-cycled, negative-space, stores prohibitions\); the Constraint Registry is re-injected in full every 3 turns using a "red team" persona that only states prohibitions and is processed before the Capability Cache
Journey Context:
Standard unified context causes positive and negative knowledge to compete for attention, with positive examples naturally dominating due to training on next-token prediction of successful actions; attempts to solve this via negative prompting fail because they get treated as "don't predict this" rather than "don't do this"; the bifurcation works because it mirrors the distinction between declarative \(what is\) and procedural \(what to do\) memory in cognitive architectures; leading agent frameworks \(LangGraph, AutoGPT v5\) adopted this in Q1 2026 after observing agents recursively calling dangerous tools they had "learned" earlier despite initial prohibitions
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:38:47.935733+00:00— report_created — created