Trident Memory System

Trident Memory System

Trident is a three-tier memory architecture for OpenClaw agents. It provides genuine continuity, identity, and recall across sessions without vendor lock-in.

Features

Quick Start

Installation

openclaw plugins install openclaw-trident

Or from GitHub:

openclaw plugins install https://github.com/ShivaClaw/trident-plugin

Usage

Once installed, Trident exposes four memory tools for agents:

#### 1. Memory Search

# Full-text search across all memory
memory_search(query="job search", mode="full_text", scope="both", limit=50)
Regex search
memory_search(query="^\\[lesson\\]", mode="regex", limit=20)

#### 2. Memory Expand

# Expand a specific compacted summary
memory_expand(summary_ids=["sum_aab3cd29ed348405"], max_depth=3)
Search first, then expand top matches
memory_expand(query="backup cron", max_depth=2)

#### 3. Memory Update

# Append to today's daily log
memory_update(
  entry="Deployed Trident v1.0 to ClawHub",
  section="## Milestones",
  tag="[project]"
)

#### 4. Memory Recall

# Answer a question using memory context
memory_recall(
  prompt="What was the job search status as of last week?",
  max_tokens=2000
)

Architecture

Layer 0: Signal Classification (15-min heartbeat)

Routes high-signal items to Layer 1 buckets automatically.

Layer 1: Hierarchical Memory

MEMORY.md                    # Curated long-term memory
memory/
  ├── YYYY-MM-DD.md         # Daily episodic logs
  ├── projects/             # Active workstreams
  ├── self/                 # Identity & interests
  ├── lessons/              # Mistakes & insights
  └── reflections/          # Weekly consolidation

Each file is promoted only when durable and high-signal.

Layer 2: Durability & Backup

Semantic Recall (Phase 8)

Configuration

Install with openclaw plugins install openclaw-trident, then configure:

{
  "plugins": {
    "trident": {
      "enabled": true,
      "memoryRoot": "/path/to/workspace",
      "maxDailyLogSize": 5242880,
      "enableSemanticRecall": true
    }
  }
}

Example Workflows

Daily Briefing

Layer 0 (15-min) → Scan messages → Tag signals → Write to daily log
↓
Daily cron (6 AM) → Read memory/YYYY-MM-DD.md → Synthesize briefing

Weekly Reflection

Layer 0 (5 days) → Accumulate signals → Triage
↓
Reflection cron (Fri 4 PM) → Promote to MEMORY.md, projects/, self/
↓
Next session → Read promoted items → Updated identity

Semantic Recall

Agent turn starts
↓
Layer 0.5 → Query Qdrant (user's prompt) → Top 3–5 summaries
↓
LCM expand → Inject as context
↓
Agent responds with genuine continuity

Rationale

Why Three Tiers?

Why Semantic Recall?

Why GitHub + Snapshots?

Limitations & Future

Current

Roadmap v1.1+

References

_Shiva's memory is persistent. Build continuity; it compounds._

Once installed, Trident exposes four memory tools for agents:

#### 1. Memory Search

# Full-text search across all memory
memory_search(query="job search", mode="full_text", scope="both", limit=50)
Regex search
memory_search(query="^\\[lesson\\]", mode="regex", limit=20)

#### 2. Memory Expand

# Expand a specific compacted summary
memory_expand(summary_ids=["sum_aab3cd29ed348405"], max_depth=3)
Search first, then expand top matches
memory_expand(query="backup cron", max_depth=2)

#### 3. Memory Update

# Append to today's daily log
memory_update(
  entry="Deployed Trident v1.0 to ClawHub",
  section="## Milestones",
  tag="[project]"
)

#### 4. Memory Recall

# Answer a question using memory context
memory_recall(
  prompt="What was the job search status as of last week?",
  max_tokens=2000
)

Install with openclaw plugins install openclaw-trident, then configure:

{
  "plugins": {
    "trident": {
      "enabled": true,
      "memoryRoot": "/path/to/workspace",
      "maxDailyLogSize": 5242880,
      "enableSemanticRecall": true
    }
  }
}