Concepts
Concepts are the generalized knowledge that emerges from consolidation. They're the persistent, meaningful output of Remind's memory system — what episodes become after the LLM "sleeps on" them.
Structure
Each concept has:
| Field | Description |
|---|---|
id | Unique identifier |
title | Short descriptive title |
summary | Natural language description of the generalized knowledge |
confidence | How certain (0.0–1.0), based on supporting evidence |
instance_count | How many episodes support this concept |
relations | Typed edges to other concepts |
conditions | When/where this concept applies |
exceptions | Known cases where it doesn't hold |
source_episodes | Episode IDs this was derived from |
embedding | Dense vector for similarity retrieval |
tags | Searchable tags |
decay_factor | Retrieval priority weight (affected by memory decay) |
How concepts differ from episodes
| Episodes | Concepts | |
|---|---|---|
| Nature | Specific, raw | Generalized, processed |
| Created by | remember() | Consolidation (LLM) |
| Lifespan | Temporary (consumed) | Persistent |
| Structure | Plain text + type | Text + confidence + relations + conditions |
| Retrieval | Not directly queried | Primary retrieval target |
Concept quality
Good concepts are:
- Generalized — Not just restating a single episode, but abstracting across multiple
- Conditional — Stating when they apply, not claiming universal truth
- Connected — Linked to related concepts via typed relations
- Grounded — Traceable back to source episodes
Managing concepts
bash
# List all concepts
remind inspect
# View a specific concept with details
remind inspect <concept-id>
# Update a concept's summary
remind update-concept <id> -s "Refined understanding"
# Update confidence
remind update-concept <id> --confidence 0.9
# Soft delete
remind delete-concept <id>
# Restore
remind restore-concept <id>TIP
Updating a concept's summary clears its embedding vector. The embedding is regenerated on the next recall query.