Open-Source JitArchives Runs AI Archive Search on SQLite, Not a Vector Database
Compliance-sensitive teams can get AI-assisted archive search without standing up vector or graph databases: JitArchives shows that a single SQLite file plus a read-only, evidence-citing Agent is a workable trade-off, even though semantic depth and fine-grained ACL control are sacrificed.
JitArchives, built on the JitWord collaborative document SDK, targets organizations that have to manage credentials and audit trails: contracts, project files, administrative and financial records. It covers the full archival lifecycle, including cataloging, classification, filing review, borrowing approval, permission control and audit logging, then adds two AI features on top. An archive Agent answers natural-language questions by searching metadata and attachment text inside the user's permission scope, checks whether evidence is sufficient before responding, and attaches a source location to every conclusion. It has read-only access and no path to modify or delete records. A knowledge graph models categories, archives, attachments and text chunks as nodes, keeping structural relations trusted and text-similarity relations computed from CJK Bigram + TF-IDF cosine similarity, explicitly flagged as clues that need human verification.
Search and similarity run on SQLite's built-in FTS5 with BM25 ranking and application-layer TF-IDF, so there is no separate vector or graph database. Deployment shrinks to a single-file database, which drops the ops burden for small units without dedicated middleware staff. The trade-off is acknowledged: lexical retrieval lacks the semantic generalization of embedding-based vectors, and scanned image PDFs cannot be text-extracted, so they never enter Agent search. The stack is Vue3 + TypeScript, NestJS, SQLite by default, plus an OpenAI-compatible model API that receives only permission-filtered snippets, never direct database or file access. Indexes are derived data and can be rebuilt without touching original files; business changes and audit logs write in the same transaction.
Limitations are spelled out: no fine-grained ACL beyond role and access level, production HTTPS and security headers left to ops, and text-similarity edges are only clues. JitArchives is positioned as an open-source base for small and mid-size organizations, not as a substitute for commercial archive systems.
The design inverts the usual RAG priorities: it treats the LLM as a tool that must justify every sentence with a citation, not as a knowledge source, which is a direct answer to hallucination risk in archival settings.
Separating structural relations from text-similarity relations keeps the knowledge graph honest, but it shifts verification work onto users, so the graph accelerates discovery more than it automates judgement.
The SQLite-only stack makes AI archive search practical where dedicated middleware is not an option, but the admitted trade-offs mean the tool pays off mainly for born-digital records and queries that lexically match the source text.