README
Documentation for the @zabaca/lattice CLI tool used in this research project.
Documents
| Document | Description |
|---|---|
| Entity Schema Reference | Valid entity types and database schema |
| Embedded DuckDB Alternative | Analysis of replacing FalkorDB with DuckDB (now implemented) |
| Graph-Only Architecture | IMPLEMENTED: No frontmatter, database is source of truth |
Quick Reference
Installation
bun add -g @zabaca/latticelattice init # Setup ~/.lattice/ and install slash commandsStorage
All data centralized in ~/.lattice/:
~/.lattice/├── docs/ # Markdown documentation├── lattice.duckdb # Embedded graph database└── .env # API keys (VOYAGE_API_KEY)Commands
| Command | Description |
|---|---|
lattice init | Setup directory structure and slash commands |
lattice status | Show documents needing sync |
lattice sync | Sync documents to DuckDB |
lattice search "<query>" | Semantic search across all entities |
lattice sql "<query>" | Execute raw SQL against DuckDB |
lattice rels <name> | Show relationships for an entity |
lattice ontology | Derive ontology from documents |
Architecture
- Backend: Embedded DuckDB (zero Docker, zero external deps)
- Embeddings: Voyage AI (voyage-3-lite, 512 dimensions)
- Vector Search: DuckDB VSS extension with HNSW index
- No frontmatter: Entities extracted directly to database
Related Research
- Test E2E Workflow - Testing framework using lattice