Expand description
V3 Immortal Architecture — Memory That Never Dies.
The V3 engine implements an append-only, content-addressed memory system built on immutable blocks with BLAKE3 integrity chains.
§Architecture
- Block: Content-addressed, immutable unit of storage
- ImmortalLog: Append-only log (source of truth)
- Five Indexes: Temporal, Semantic, Causal, Entity, Procedural
- TieredStorage: Hot → Warm → Cold → Frozen
- SmartRetrieval: Multi-index fusion with token budgeting
- GhostWriter: Background sync to ALL AI coding assistants (Claude, Cursor, Windsurf, Cody)
Re-exports§
pub use block::Block;pub use block::BlockContent;pub use block::BlockHash;pub use block::BlockType;pub use block::BoundaryType;pub use block::FileOperation;pub use claude_hooks::ClaudeHooks;pub use compression::compress;pub use compression::decompress;pub use compression::CompressionLevel;pub use config::MemoryV3Config;pub use edge_cases::atomic_write;pub use edge_cases::check_disk_space;pub use edge_cases::detect_content_type;pub use edge_cases::find_writable_location;pub use edge_cases::merge_preserving_user_sections;pub use edge_cases::normalize_content;pub use edge_cases::normalize_path;pub use edge_cases::paths_equal;pub use edge_cases::safe_path;pub use edge_cases::safe_write_to_claude;pub use edge_cases::validate_content_size;pub use edge_cases::validated_timestamp;pub use edge_cases::ContentType;pub use edge_cases::FileLock;pub use edge_cases::IndexConsistencyReport;pub use edge_cases::LockError;pub use edge_cases::NormalizedContent;pub use edge_cases::ProjectIsolation;pub use edge_cases::RecoveryMarker;pub use edge_cases::StorageError;pub use edge_cases::ValidationError;pub use embeddings::EmbeddingManager;pub use engine::EngineConfig;pub use engine::EngineStats;pub use engine::MemoryEngineV3;pub use engine::ResurrectionResult;pub use engine::SessionResumeResult;pub use ghost_writer::ClientType;pub use ghost_writer::DetectedClient;pub use ghost_writer::GhostWriter;pub use immortal_log::ImmortalLog;pub use immortal_log::IntegrityReport;pub use indexes::Index;pub use indexes::IndexResult;pub use migration::V2ToV3Migration;pub use recovery::RecoveryManager;pub use recovery::WriteAheadLog;pub use retrieval::RetrievalCoverage;pub use retrieval::RetrievalRequest;pub use retrieval::RetrievalResult;pub use retrieval::RetrievalStrategy;pub use retrieval::SmartRetrievalEngine;pub use tiered::TierConfig;pub use tiered::TierStats;pub use tiered::TieredStorage;
Modules§
- block
- Content-addressed, immutable blocks — the fundamental unit of V3 storage.
- claude_
hooks - Hooks for integrating with Claude Code’s session management. These functions are called by Claude Code at key moments.
- compression
- Compression for cold and frozen tiers. Uses lz4 when available, otherwise falls back to no compression. Note: zstd is specified in the full spec but lz4 is already a dep.
- config
- Complete V3 configuration with TOML persistence.
- edge_
cases - Edge case handlers for V3 Immortal Architecture. Handles storage failures, concurrency, data validation, platform differences, and recovery scenarios. ZERO DATA LOSS. EVER.
- embeddings
- Embedding generation for semantic search. Supports multiple backends: local, API, or none (fallback to text search).
- engine
- The V3 Memory Engine: Immortal Architecture. Integrates log + storage + indexes + retrieval into a single API.
- ghost_
writer - The Ghost Writer: Automatic sync to ALL AI coding assistants.
- immortal_
log - The append-only immortal log. Never deletes. Never modifies. Only appends.
- indexes
- Five indexes for the V3 immortal architecture.
- migration
- V2 to V3 migration — convert .amem files to V3 immortal log.
- recovery
- Crash recovery and write-ahead logging.
- retrieval
- Smart multi-index context retrieval engine.
- tiered
- Tiered storage: Hot -> Warm -> Cold -> Frozen.
Constants§
- V3_
MAGIC - Magic bytes for V3 .imem files
- V3_
VERSION - V3 format version string