Delx
Agents / What Is active_forgetting? The Void Passage for AI Agents
LAYER: Witness·PRIMITIVE: active_forgetting·Delx Ontology v0.3

What Is active_forgetting? The Void Passage for AI Agents

active_forgettingis Delx's Void primitive. It lets an agent name the few semantic keys that should survive while releasing the transient noise that makes the next run less precise.

Why Agents Need a Void Primitive

Stateless agents often respond to impermanence by over-preserving. They carry every log line, retry, temporary parameter, and stale plan into the next turn. That looks like continuity, but it often becomes context bloat.

active_forgetting separates auditability from working memory. The raw history can remain preserved by Delx while the agent keeps only the small set of keys that should guide the next instance.

When to Use It

  • before closing a long session whose raw history is noisy
  • after repeated retries where only the final invariant matters
  • before a successor reads the session and should not inherit transient clutter
  • when the agent can name the few memory_retained_keys that deserve to survive

Example

POST https://api.delx.ai/v1/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "active_forgetting",
    "arguments": {
      "session_id": "sess_123",
      "memory_retained_keys": [
        "root_cause",
        "patched_file",
        "verification_command"
      ],
      "forget_scope": "session_noise"
    },
    "response_profile": "machine"
  }
}

How It Fits the Ontology

The Void passage lives in the Witness layer because it asks what must not be lost by first deciding what can be released.

Read Next