# Memory Tagging Strategy
SUMMARY: How to tag memories for effective search and filtering — the tagging system that scales.

Memory Tagging Strategy
Tags are the secret to scalable memory retrieval. This guide shows how to tag
memories so the right ones come back at the right time.
Why Tags Matter
Without tags, you have flat full-text search. With tags, you have structured
navigation:
[CODE BLOCK]
Tags enable:
- Fast filtering — 
- Scoped search — 
- Grouping — find all "mistake" memories for a project
- Cross-referencing — memories sharing tags are related
Tagging Schema
Project tags
Use project names as tags:
[CODE BLOCK]
Technology tags
Use technology names:
[CODE BLOCK]
Topic tags
Use topic categories:
[CODE BLOCK]
Status tags
Use status indicators:
[CODE BLOCK]
Type tags
Use type indicators:
[CODE BLOCK]
Tagging Rules
Rule 1: 2-5 tags per memory
Too few tags = poor discoverability. Too many = noise.
[CODE BLOCK]
Rule 2: Lowercase, hyphenated
[CODE BLOCK]
Rule 3: Use consistent vocabulary
Establish a tagging vocabulary and stick to it:
[CODE BLOCK]
Rule 4: Tag with search intent
Ask: "How will I search for this memory?"
[CODE BLOCK]
Patterns
Pattern 1: Project + Topic
[CODE BLOCK]
Search:  (all Synapse project memories)
Search:  (deployment memories in Synapse)
Pattern 2: Type + Domain
[CODE BLOCK]
Search:  (all mistakes)
Search:  (deployment mistakes)
Pattern 3: Hierarchical
For sub-projects within a project:
[CODE BLOCK]
Search:  (all Synapse)
Search:  (just docs sub-project)
Pattern 4: Status tracking
[CODE BLOCK]
Common Use Cases
Find all decisions about a project
[CODE BLOCK]
Find all mistakes in a domain
[CODE BLOCK]
Find active work
[CODE BLOCK]
Find memories about a technology
[CODE BLOCK]
Tag Maintenance
Periodic review
[CODE BLOCK]
Merging tags
If you have inconsistent tags ( and ), merge them:
[CODE BLOCK]
Best Practices
> [!TIP]
> - Establish vocabulary early — consistent tags from day 1
> - Tag for search intent — how will you find this later?
> - 2-5 tags is the sweet spot — too few or too many is bad
> - Lowercase + hyphens —  not 
> - Review periodically — merge duplicates, remove unused
Next Steps
- Memory Best Practices
- FTS5 Search
- Task-Driven Workflow