You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Replace "reasoning-native" and "reasoning-based" with "document
understanding" throughout documentation
- Update README.md to clarify that Vectorless compiles documents
into structured trees and provides reasoning acts, not retrieval
results
- Change "Fusion" to "Synthesis" in architecture diagram
- Update blog post tags from [vectorless, rag, llm, announcement]
to [vectorless, document-understanding, llm, ai, announcement]
- Modify docusaurus config and homepage header/description to
reflect new positioning as "Document Understanding Engine for AI"
- Streamline feature descriptions and remove redundant phrases
**Vectorless** is a document understanding engine for AI. It reads documents as structured trees of meaning, then dispatches multiple agents to reason through headings, sections, and paragraphs — understanding how each part relates to the whole. The problem it solves is not "where to look", but "what does this mean in context". Every understanding is a **reasoning** act.
17
+
**Vectorless** is a document understanding engine for AI. It compiles documents into structured trees of meaning, then dispatches multiple agents to reason through headings, sections, and paragraphs — evaluating how each part relates to the whole. The problem it solves is not "where to look", but "what does this mean in context". Every answer is a reasoning act, not a retrieval result.
18
18
19
19
Light up a star and shine with us! ⭐
20
20
@@ -60,7 +60,7 @@ Engine.query("What drove the revenue decline?")
Vectorless is a reasoning-native document intelligence engine written in Rust — **no vector database, no embeddings, no similarity search**.
8
+
Vectorless is a document understanding engine for AI. It compiles documents into structured trees of meaning, then dispatches multiple agents to reason through headings, sections, and paragraphs — evaluating how each part relates to the whole. The problem it solves is not "where to look", but "what does this mean in context". Every answer is a reasoning act, not a retrieval result.
9
9
10
10
{/* truncate */}
11
11
12
12
## Why Vectorless?
13
13
14
-
Traditional RAG systems rely on vector embeddings and similarity search. This approach loses document structure, requires a vector database, and often returns chunks that lack context.
14
+
Understanding a document requires more than finding keywords — it requires navigating structure, cross-referencing sections, and evaluating whether the evidence is sufficient. Vectorless agents do exactly this: they reason through documents the way a human expert would.
15
15
16
-
Vectorless takes a different path:
16
+
Key capabilities:
17
17
18
18
-**Hierarchical Semantic Trees** — Documents are parsed into a tree of sections, preserving structure and relationships.
19
19
-**LLM Agent Navigation** — Queries are resolved by agents that navigate the tree using commands (ls, cd, cat, find, grep), making every decision through LLM reasoning.
20
-
-**Zero Infrastructure** — No vector DB, no embedding models, no similarity search. Just an LLM API key.
20
+
-**Zero Infrastructure** — Just an LLM API key, nothing else to deploy.
Copy file name to clipboardExpand all lines: docs/docs/intro.mdx
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ sidebar_position: 1
4
4
5
5
# Introduction
6
6
7
-
**Vectorless** is a reasoning-native document intelligence engine written in Rust — **no vector database, no embeddings, no similarity search**.
8
-
9
-
It transforms documents into hierarchical semantic trees and uses LLMs to navigate the structure, retrieving the most relevant content through deep contextual understanding instead of vector math.
7
+
**Vectorless** is a document understanding engine for AI. It compiles documents into structured trees of meaning, then dispatches multiple agents to reason through headings, sections, and paragraphs — evaluating how each part relates to the whole. The problem it solves is not "where to look", but "what does this mean in context". Every answer is a reasoning act, not a retrieval result.
-**Hierarchical Semantic Trees** — Preserves document structure, not flat chunks
79
-
-**LLM-Powered Agent Navigation** — Worker agents navigate the tree using commands (ls, cd, cat, find, grep), making every retrieval decision through LLM reasoning
77
+
-**LLM-Powered Agent Navigation** — Worker agents navigate the tree using commands (ls, cd, cat, find, grep), making every decision through LLM reasoning
80
78
-**Cross-Reference Resolution** — Automatically resolves "see Section 2.1", "Appendix G" references during indexing
81
79
-**Synonym Expansion** — LLM-generated synonyms for indexed keywords improve recall for differently-worded queries
82
80
-**Orchestrator Supervisor Loop** — Multi-document queries are coordinated by an LLM supervisor that dispatches Workers, evaluates evidence, and replans when needed
83
81
-**Cross-Document Graph** — Automatic relationship discovery between documents via shared keywords
<pclassName={styles.subTitle}>Document Understanding Engine for AI</p>
46
46
47
47
<divclassName={styles.featureList}>
48
48
<divclassName={styles.featureItem}>
@@ -119,7 +119,7 @@ export default function Home(): ReactNode {
119
119
return(
120
120
<Layout
121
121
title={`${siteConfig.title}`}
122
-
description="Reasoning-based document engine. No embeddings, no chunking. Multiple agents navigate your documents to find exactly what's relevant.">
122
+
description="Document understanding engine for AI. Agents reason through your documents — navigating structure, reading passages, cross-referencing across sections.">
0 commit comments