Documentation Index
Fetch the complete documentation index at: https://docs.memanto.ai/llms.txt
Use this file to discover all available pages before exploring further.
Memory Types Reference
Complete reference for all 13 semantic memory types in Memanto.Why Memory Types?
Memory types serve two purposes:- Organization - Group related memories instead of throwing everything into a generic “notes” bucket.
- Filtering - Query specific types (e.g., retrieving only “commitments” or “preferences”).
Quick Reference
| Type | Use Case | Example |
|---|---|---|
| fact | Objective information | ”User is in Finance dept” |
| preference | Likes/dislikes | ”Prefers email contact” |
| decision | Choices made | ”Chose PostgreSQL” |
| commitment | Promises/obligations | ”Will deliver Friday” |
| goal | Objectives | ”Reach 10K users” |
| event | Things that happened | ”Meeting at 2pm” |
| instruction | Rules/procedures | ”Validate input always” |
| relationship | Connections | ”Alice manages Bob” |
| context | Situational info | ”In Q1 planning” |
| learning | Lessons learned | ”Users need help” |
| observation | Patterns noticed | ”Traffic peaks Fridays” |
| error | Mistakes to avoid | ”Skip validation=bug” |
| artifact | Documents/files | ”Q3 budget.xlsx” |
Detailed Definitions
fact
Objective, verifiable information about the world or domain.- Static information
- Not opinions or preferences
- Verifiable claims
- Core knowledge
- “Paris is the capital of France”
- “Database uses PostgreSQL”
- “Team has 5 engineers”
preference
User or system likes, dislikes, or preferences.- Opinions about preferences
- User/system choices
- Style choices
- Communication preferences
- “Prefers dark mode”
- “Email over phone”
- “Concise responses”
decision
Important choices made that affect future behavior.- Technology choices
- Process decisions
- Strategic choices
- Why decisions
- “Chose TypeScript for codebase”
- “Decided to use AWS”
- “Selected Agile methodology”
commitment
Promises or obligations made.- Deliverables
- Promises to keep
- Obligations
- Accountability
- “Will deliver report by Friday”
- “Committed to 10% growth”
- “Promised 24/7 support”
goal
Objectives to achieve.- Future targets
- KPIs
- Milestones
- Aspirations
- “Reach 1M users”
- “Improve performance by 50%”
- “Launch MVP by Q2”
event
Something that happened or will happen.- Historical events
- Meetings
- Incidents
- Milestones
- “Had meeting with CEO”
- “System outage on March 20”
- “Project launched successfully”
instruction
Rules, guidelines, or procedures to follow.- Policies
- Best practices
- Procedures
- Constraints
- “Always validate input”
- “Follow REST conventions”
- “Require code review”
relationship
Connections or relationships between entities.- People relationships
- System dependencies
- Business relationships
- Hierarchies
- “Alice manages Bob”
- “Project X depends on API Y”
- “Customer referred by John”
context
Contextual information about the current situation.- Seasonal context
- Business phases
- System states
- Environmental factors
- “In Q1 planning phase”
- “Budget season is active”
- “System in maintenance”
learning
Lessons learned from experience.- Insights
- Lessons
- Patterns recognized
- Knowledge gained
- “Users need better onboarding”
- “Mobile-first is essential”
- “Documentation must be clear”
observation
Something noticed or perceived.- Patterns observed
- Trends noticed
- Data observations
- Field observations
- “Traffic peaks on Fridays”
- “Users skip step 2”
- “Support tickets spike after releases”
error
Mistakes to avoid in the future.- Warnings
- Lessons from failures
- Anti-patterns
- Known issues
- “Avoid deprecated API”
- “Skip validation=bug”
- “Don’t hardcode secrets”
artifact
Important documents, files, or references.- Documents
- Code files
- Resources
- References
- “Q3 budget spreadsheet”
- “API documentation file”
- “Customer contract”
Selection Guide
Best Practices
DO
- Use specific types for better organization
- Choose the most specific type available
- Be consistent in your selections
- Filter queries by type when appropriate
DON’T
- Overuse generic “fact” type
- Store everything as one type
- Mix unrelated information in one memory
- Ignore type distinctions
- Use wrong type for convenience
- Skip commitment type for promises
- Forget about error type for lessons