Create new knowledge files in the Maenifold memory system with automatic knowledge graph integration. This tool builds your persistent knowledge base through [[WikiLink]] concepts that automatically connect related information. REQUIRES at least one [[concept]] in double brackets to ensure knowledge graph connectivity.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| title | string | Yes | Human-readable title for the memory file | ”Machine Learning Fundamentals” |
| content | string | Yes | Main content with required [[concepts]] in brackets | ”Learning about [[Neural Networks]] and [[Deep Learning]] applications in [[Computer Vision]]“ |
| folder | string | No | Optional folder path for organization | ”research/ai” or “projects/2024” |
| tags | string[] | No | Optional tags for categorization | [“ai”, “research”, “fundamentals”] |
{
"title": "GraphRAG Implementation Notes",
"content": "Implementing [[GraphRAG]] requires understanding [[Vector Embeddings]] and [[Knowledge Graphs]]. Key insight: combine [[Semantic Search]] with [[Graph Traversal]] for enhanced context retrieval."
}
Creates a basic memory file with automatic concept extraction and graph integration.
{
"title": "Transformer Architecture Deep Dive",
"content": "The [[Transformer]] architecture revolutionized [[Natural Language Processing]] through [[Self-Attention]] mechanisms. Key components include [[Multi-Head Attention]], [[Positional Encoding]], and [[Layer Normalization]].\n\n## Key Insights\n- [[Attention]] allows parallel processing unlike [[RNN]] sequential approach\n- [[BERT]] and [[GPT]] are both [[Transformer]]-based but use different training objectives",
"folder": "research/deep-learning",
"tags": ["transformers", "nlp", "architecture", "research"]
}
Creates an organized research file with folder structure and comprehensive tagging.
{
"title": "Debugging Memory Leaks in C# Applications",
"content": "Encountered [[Memory Leak]] in [[C# Application]] during [[Performance Testing]]. Root cause: [[Event Handlers]] not properly unsubscribed in [[Observer Pattern]] implementation.\n\n## Solution\n- Use [[Weak References]] for event subscriptions\n- Implement [[IDisposable]] pattern properly\n- Apply [[RAII]] principles from [[Resource Management]]",
"folder": "solutions/performance",
"tags": ["debugging", "performance", "csharp", "memory-management"]
}
Documents a specific problem-solution pattern with technical concepts.
Use WriteMemory to capture learning insights with concept connections. Every new concept becomes searchable and linkable to future knowledge.
Create project-specific memory files in dedicated folders. Use consistent tagging schemes for project phases or components.
Document solutions to technical problems with [[concept]] links to technologies, patterns, and methodologies used.
WriteMemory works seamlessly with Sequential Thinking sessions - capture thinking results as persistent knowledge for future reference.
Each [[concept]] becomes a node. Related files sharing concepts automatically connect, building your knowledge graph organically.
research/ # Research notes and findings
projects/ # Project-specific documentation
solutions/ # Problem-solution pairs
methodologies/ # Process and methodology documentation
chain-of-thought/ # Automatic from thinking sessions
concepts/ # Pure concept definitions
research/ai/transformers for deep organizationprojects/2024/q4 for temporal organizationCause: Content lacks [[WikiLink]] concepts in double brackets
Solution: Add relevant concepts like [[Machine Learning]] or [[Software Architecture]] to connect your knowledge to the graph
Cause: File title or URI reference is incorrect
Solution: Use exact title from WriteMemory response or full memory:// URI format
Cause: Using very unique [[concepts]] that don’t connect to existing knowledge
Solution: Include some established concepts alongside new ones to maintain graph connectivity
Cause: Inconsistent folder naming or deep nesting
Solution: Use consistent folder patterns and avoid more than 3-4 levels of nesting
Cause: Single file exceeds 250 lines
Solution: Split into multiple focused files with shared [[concepts]] for connection
Every WriteMemory operation automatically:
The [[concept]] requirement ensures no orphaned knowledge - every file connects to your growing knowledge graph, making information discoverable and relationship-aware.
WriteMemory follows Maenifold’s Ma Protocol principles:
This tool creates the foundation for your Maenifold knowledge system - every file becomes part of your growing cognitive infrastructure.