diff --git a/.gitignore b/.gitignore
index 47d38baef..fac545714 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,15 +1,164 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist*/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
.ipynb_checkpoints
-__pycache__
-files
-index
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+Pipfile.lock
+
+# PEP 582
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# IDE / Editor
+.vscode/
+.vscode
+.idea/
+.idea
+*.swp
+*.swo
+*~
+.DS_Store
+
+# Project-specific ignores
+files/
+index/
temp/*
chroma-collections.parquet
chroma-embeddings.parquet
-.DS_Store
-.env*
-notebook
+notebook/
SDK/*
-log/*
+log/
logs/
-parts/*
-json_results/*
+json_results/
+archive/
+results/
+parts/
+docs
+
+# Temporary test/validation scripts
+check_ollama_gpu.py
+setup_gpu_and_validate.py
+validate_*.py
+quick_e2e_test.py
+test_e2e_ollama.py
+test_ollama_speed.py
+test_provider_routing.py
+verify_all_17_targets.py
+test_parallel_processing.py
+tests/results
+tests/reports/
+run_comprehensive_e2e.log
+records
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 48e73fb35..fdfa91137 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -14,3 +14,6 @@ All notable changes to this project will be documented in this file.
### Changed
- [x] Change "child_nodes" -> "nodes" to simplify the structure
+
+### Modified
+- Decoupled OpenAI SDK completely and coupled with Ollama instead
diff --git a/ENHANCEMENTS_REPORT.md b/ENHANCEMENTS_REPORT.md
new file mode 100644
index 000000000..b2e15285e
--- /dev/null
+++ b/ENHANCEMENTS_REPORT.md
@@ -0,0 +1,388 @@
+# Local-First Enhancements and OpenAI Decoupling Report
+
+## 1) Report Scope
+
+This report compares:
+- **Fork (local workspace):** `PageIndexOllama` (local-first/Ollama-oriented implementation)
+- **Original repository:** [VectifyAI/PageIndex](https://github.com/VectifyAI/PageIndex) (upstream baseline)
+
+Primary focus is **OpenAI decoupling** (provider-agnostic runtime and local Ollama support). Secondary sections cover related enhancements that materially enabled or stabilized decoupling outcomes (parallel processing, prompt/system reliability, testing hardening).
+
+---
+
+## 2) What Each README Says the Project Does
+
+### 2.1 [Upstream README.md](https://github.com/VectifyAI/PageIndex/blob/main/README.md) — Functional Intent
+
+The upstream repo presents PageIndex as a **vectorless, explainable reasoning-RAG framework** and broader product ecosystem. The README emphasizes:
+- Reasoning over full-document structure without vector DB dependence
+- Explainability and traceable traversal
+- OpenAI API key setup in local package workflow
+- CLI usage through `run_pageindex.py` with OpenAI-model-oriented defaults and examples
+
+Interpretation: upstream positioning is framework/platform oriented, with practical local usage examples largely aligned to OpenAI-backed execution.
+
+### 2.2 Fork [README.md](README.md) — Functional Intent
+
+The fork README reframes the project as **local-first and Ollama-first**, with explicit setup and operations for offline/local inference:
+- Local Ollama server setup instructions
+- No OpenAI key required for default path
+- Provider/environment variable controls (`LLM_PROVIDER`, `OLLAMA_URL`, `OLLAMA_MODEL`)
+- CLI usage through `cli.py`
+
+Interpretation: the fork is not just a provider swap; it is an operational reorientation toward local execution and reproducibility.
+
+### 2.3 README-Level Strategic Delta
+
+At documentation level, the fork changes the “center of gravity” from:
+- **Upstream:** framework + OpenAI-centric local usage
+- **Fork:** local-first runtime with OpenAI as optional compatibility
+
+This documentation shift is significant because it aligns user onboarding, defaults, and expected failure modes with local deployment rather than cloud API dependency.
+
+---
+
+## 3) Architectural Baseline vs Fork (High-Level)
+
+## 3.1 Upstream Baseline Characteristics
+
+- Core API wrappers are OpenAI-branded (`ChatGPT_API*` pattern)
+- Prompt logic often embedded in code as long inline strings
+- Tree/index generation path is mostly sequential in critical scanning stages
+- Minimal automated test surface in Python test modules
+
+## 3.2 Fork Architecture Characteristics
+
+- Provider-agnostic API wrapper layer (`Ollama_API*` family + provider switch)
+- Explicit response normalization for finish reason semantics
+- External prompt registry and loader system
+- Added model capability abstraction and chunking policy modules
+- Async/bounded concurrency in tree-generation substeps
+- Expanded e2e + integration/performance validation tooling
+
+---
+
+## 4) Detailed Enhancement Inventory (Decoupling-Centric)
+
+## 4.1 Runtime Provider Decoupling
+
+### Change Summary
+Upstream OpenAI-tied wrappers are replaced/augmented with provider-routed wrappers:
+- `Ollama_API_with_finish_reason`
+- `Ollama_API`
+- `Ollama_API_async`
+
+Each routes based on provider context (not hardcoded OpenAI runtime), with provider-specific internal call paths.
+
+### Why It Matters
+- Removes direct dependence on a single vendor runtime from call sites
+- Enables default local execution while preserving optional OpenAI compatibility
+- Centralizes provider branching, reducing invasive provider conditionals across indexing/search workflows
+
+### Evidence (fork vs upstream)
+- Fork: `pageindex/utils.py`
+- Upstream: [pageindex/utils.py](https://github.com/VectifyAI/PageIndex/blob/main/pageindex/utils.py)
+
+### Implementation Impact
+- Call-site behavior is now abstracted through common wrapper contracts
+- Provider selection becomes a configuration concern, not a business-logic concern
+
+### Caveats
+- The fork still includes OpenAI package dependencies in runtime metadata, so full dependency minimization is not yet complete
+- Some naming retains legacy traces that may confuse future maintainers (example: mixed historical terminology across docs/code)
+
+---
+
+## 4.2 Finish Reason Normalization Layer
+
+### Change Summary
+The fork introduces explicit response handling and normalization constructs:
+- `ResponseHandler`
+- `FinishReason` normalization logic
+
+These map provider-specific response semantics into standardized continuation decisions.
+
+### Why It Matters
+Continuation handling is one of the most brittle places in provider migration. Different providers expose stop/truncation semantics differently; normalization avoids leaking this variability into higher-level indexing/search flows.
+
+### Evidence
+- `pageindex/response_handlers.py`
+- `pageindex/utils.py` (provider-specific with-finish-reason paths)
+
+### Implementation Impact
+- Cross-provider continuation logic becomes deterministic at the interface boundary
+- Fewer hidden assumptions in downstream pipeline stages
+
+### Caveats
+- Ollama finish states may still rely on inference heuristics in some paths; behavior should be validated under long outputs and token limits across multiple models
+
+---
+
+## 4.3 Credentials and Environment Abstraction
+
+### Change Summary
+Fork introduces centralized credential/provider handling in:
+- `pageindex/credentials.py`
+
+This abstracts env var retrieval and provider-aware credential logic.
+
+### Why It Matters
+- Avoids scattered key/env handling logic
+- Reduces inconsistent provider setup behavior between CLI and internal modules
+- Supports cleaner future extension for additional providers
+
+### Evidence
+- `pageindex/credentials.py`
+- `pageindex/config.yaml`
+
+### Caveats
+- Legacy env key naming patterns appear in places and can create confusion during migration/ops documentation
+
+---
+
+## 4.4 Local Ollama Integration as First-Class Path
+
+### Change Summary
+Fork adds robust Ollama-specific runtime behaviors:
+- Explicit endpoint use for chat calls
+- Endpoint/model availability checks
+- Local setup scripts for PowerShell/Bash workflows
+
+### Why It Matters
+- Makes local inference operationally reliable for users without cloud API dependencies
+- Improves startup diagnostics compared to opaque runtime failures
+
+### Evidence
+- `pageindex/utils.py` (Ollama HTTP call paths and checks)
+- `scripts/setup_ollama.ps1`
+- `scripts/setup_ollama.sh`
+- `scripts/set_model_env.sh`
+
+### Caveats
+- Extra endpoint checks add overhead per call path if not cached
+- Local model behavior varies substantially by model size/hardware profile
+
+---
+
+## 5) Enhancements That Strengthen Decoupling Outcomes
+
+These are not strictly provider-switch code, but they materially improve success rates after decoupling.
+
+## 5.1 Prompt Externalization and Prompt Governance
+
+### Change Summary
+Fork introduces a prompt system:
+- Prompt loader (`pageindex/prompt_loader.py`)
+- Registry-driven prompt definitions (`pageindex/prompts/prompt_registry.json`)
+- Prompt text files under `pageindex/prompts/`
+
+Replacing major inline prompt blocks from upstream reduces code coupling to prompt text.
+
+### Why It Matters for Decoupling
+Different providers/models respond differently to prompt shape and schema strictness. Externalized prompts allow:
+- Faster tuning without deep code edits
+- Better reproducibility across providers
+- Easier test prompt variants for weaker/stronger local models
+
+### Evidence
+- Fork: `pageindex/prompt_loader.py`, `pageindex/prompts/*`
+- Upstream inline approach: [pageindex/page_index.py](https://github.com/VectifyAI/PageIndex/blob/main/pageindex/page_index.py)
+
+### Caveats
+- Some schema key naming appears inconsistent in places (`node_ids` vs `relevant_node_ids`) and should be standardized
+
+---
+
+## 5.2 Parallel Processing for Tree Generation Performance
+
+### Change Summary
+Fork introduces bounded async concurrency in document-structure stages:
+- Async TOC page detection with semaphore limits
+- Parallelized summary generation flows
+
+### Why It Matters for Decoupling
+Local models can be slower than API-hosted models. Concurrency helps recover practical throughput and keeps local-first UX viable for larger documents.
+
+### Evidence
+- `pageindex/page_index.py` (async TOC and bounded concurrency logic)
+- `pageindex/utils.py` (parallel summary generation helper paths)
+- `test_parallel_processing.py`
+
+### Caveats
+- Fixed concurrency defaults may underperform or overload depending on workstation resources
+- Local LLM contention may degrade quality if overly parallelized
+
+---
+
+## 5.3 Adaptive Chunking and Hierarchical Fallbacks
+
+### Change Summary
+Fork includes chunking policy and no-TOC fallback improvements:
+- `pageindex/chunking_config.py`
+- Enhanced no-TOC/hierarchical processing in `pageindex/page_index.py`
+
+### Why It Matters for Decoupling
+When model quality/performance varies by provider and local model size, robust fallback behavior prevents hard failures and improves completion rates.
+
+### Caveats
+- Increased control-flow complexity requires stronger regression coverage
+
+---
+
+## 5.4 Schema and Model Layer Expansion
+
+### Change Summary
+Fork adds typed schema definitions in:
+- `pageindex/models.py`
+
+### Why It Matters for Decoupling
+Provider variation often causes output-shape drift. A stronger schema layer improves validation and debuggability, especially in search/result flows.
+
+### Caveats
+- Integration depth appears partial; not all paths may uniformly enforce typed models
+
+---
+
+## 6) CLI, Defaults, and Configuration Drift
+
+## 6.1 Entrypoint Shift
+
+- Fork CLI: `cli.py`
+- Upstream CLI: `run_pageindex.py`
+
+The fork aligns command examples and defaults around local provider assumptions.
+
+## 6.2 Model Defaults
+
+Observed defaults are not fully uniform across all fork assets:
+- Some files/documentation indicate `mistral24b-16k`
+- Some e2e artifacts reference `mistral:7b`
+
+This inconsistency is not fatal but is important for reproducibility and support clarity.
+
+## 6.3 Configuration Surface Expansion
+
+Fork config exposes provider-facing fields beyond upstream baseline, which is necessary for provider-agnostic behavior but requires strict canonical default policy.
+
+---
+
+## 7) Testing and Validation Improvements
+
+## 7.1 Fork Test Surface Growth
+
+Fork adds significant validation tooling not present in upstream Python tests:
+- Comprehensive e2e workflows
+- Direct integration checks
+- Parallel-processing validation scripts
+
+Representative files:
+- `run_comprehensive_e2e_tests.py`
+- `tests/e2e/test_comprehensive.py`
+- `tests/e2e/test_direct_integration.py`
+- `test_parallel_processing.py`
+
+## 7.2 Why This Matters for Decoupling
+Provider decoupling introduces behavior permutations (provider, model, latency, output schema). Expanded tests are essential to avoid regressions that only appear outside OpenAI assumptions.
+
+## 7.3 Caveats
+Some test paths/settings appear environment-specific and may need portability normalization for cross-platform CI.
+
+---
+
+## 8) Side-by-Side Enhancement Matrix (Condensed)
+
+| Area | Upstream | Fork | Decoupling Value |
+|---|---|---|---|
+| Provider API wrappers | OpenAI-branded wrappers | Provider-routed `Ollama_API*` wrappers | High |
+| Finish reason semantics | Provider-specific assumptions | Normalized response handler | High |
+| Credentials/env handling | More distributed | Centralized provider-aware module | Medium-High |
+| Prompt management | Inline prompt strings | Registry + loader + prompt files | High (operational) |
+| TOC/summary processing | More sequential | Async bounded concurrency | Medium-High |
+| Fallback behavior | Simpler/no hardening in some paths | Hierarchical/adaptive fallback paths | Medium |
+| CLI defaults | OpenAI model default | Local model default path | High (UX/ops) |
+| Test coverage | Minimal Python tests | Expanded e2e/integration/perf checks | High (risk reduction) |
+
+---
+
+## 9) Risk Register and Remaining Gaps
+
+## 9.1 Key Risks
+
+1. **Default model inconsistency**
+ - Conflicting defaults across CLI/config/tests can produce hard-to-reproduce behavior.
+
+2. **Schema key inconsistency in search prompts/contracts**
+ - Mixed key naming (`node_ids` vs `relevant_node_ids`) can force compatibility shims and silent parser branching.
+
+3. **Naming drift in capability constants/legacy terminology**
+ - Misleading names (e.g., constant naming not matching actual model size) increase cognitive load for maintainers.
+
+4. **Dependency intent not fully minimal**
+ - OpenAI package remains in dependency surface despite local-first orientation; acceptable for compatibility, but should be intentional and documented.
+
+## 9.2 Recommended Standardization Actions
+
+1. Define and enforce one canonical default model policy across CLI, config, docs, and tests.
+2. Standardize one canonical output key for tree-search node selection.
+3. Align naming of capability constants and legacy compatibility aliases with current behavior.
+4. Explicitly document compatibility dependencies (what is required for default local path vs optional OpenAI path).
+5. Add a small compatibility matrix test set (provider × model family × key response contracts).
+
+---
+
+## 10) Final Assessment
+
+The fork’s enhancement set is a **substantial architectural decoupling**, not a superficial endpoint swap.
+
+The highest-value outcomes are:
+- Provider-agnostic runtime abstraction at API wrapper boundaries
+- Deterministic response normalization for continuation behavior
+- Local-first operational path with explicit Ollama support
+- Supporting reliability/performance upgrades (prompt governance, bounded async processing, broader validation)
+
+Remaining issues are mainly **standardization and consistency** (defaults, naming, schema contracts), not foundational blockers. In practical terms, the fork has moved PageIndex from an OpenAI-assumed execution model to a viable multi-provider local-first architecture with clear room for hardening.
+
+---
+
+## 11) File Evidence Index
+
+### Core decoupling
+- `pageindex/utils.py`
+- `pageindex/response_handlers.py`
+- `pageindex/credentials.py`
+- `pageindex/config.yaml`
+- [upstream pageindex/utils.py](https://github.com/VectifyAI/PageIndex/blob/main/pageindex/utils.py)
+
+### README and CLI comparison
+- `README.md`
+- [upstream README.md](https://github.com/VectifyAI/PageIndex/blob/main/README.md)
+- `cli.py`
+- [upstream run_pageindex.py](https://github.com/VectifyAI/PageIndex/blob/main/run_pageindex.py)
+
+### Prompt/governance and schema
+- `pageindex/prompt_loader.py`
+- `pageindex/prompts/prompt_registry.json`
+- `pageindex/prompts/*.txt`
+- `pageindex/models.py`
+- upstream [pageindex/page_index.py](https://github.com/VectifyAI/PageIndex/blob/main/pageindex/page_index.py)
+
+### Parallelization and robustness
+- `pageindex/page_index.py`
+- `pageindex/chunking_config.py`
+- `test_parallel_processing.py`
+
+### Validation surface
+- `run_comprehensive_e2e_tests.py`
+- `tests/e2e/test_comprehensive.py`
+- `tests/e2e/test_direct_integration.py`
+
+---
+
+## 12) Appendix: Practical Interpretation for PR #145
+
+For the active PR context (“Add local-first support with Ollama backend for PageIndex CLI and workflows”), this fork demonstrates a coherent implementation trajectory:
+- Documentation and defaults now align with local-first behavior
+- Runtime internals decouple provider assumptions from pipeline logic
+- Operational and testing scaffolding exists to sustain the new execution model
+
+The PR narrative is therefore best framed as: **“provider decoupling + local-first operationalization + reliability/performance hardening.”**
diff --git a/LICENSE b/LICENSE
index c9081e449..f07140f47 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,21 +1,681 @@
-MIT License
-
-Copyright (c) 2025 Vectify AI
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Copyright (C) 2026 Ashwin Gupta
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/README.md b/README.md
index 7180efd5a..249152980 100644
--- a/README.md
+++ b/README.md
@@ -1,270 +1,295 @@
-
-
- **🔥 Releases:**
-- [**PageIndex Chat**](https://chat.pageindex.ai): The first human-like document-analysis agent [platform](https://chat.pageindex.ai) built for professional long documents. Can also be integrated via [MCP](https://pageindex.ai/mcp) or [API](https://docs.pageindex.ai/quickstart) (beta).
-
-
-
- **📝 Articles:**
-- [**PageIndex Framework**](https://pageindex.ai/blog/pageindex-intro): Introduces the PageIndex framework — an *agentic, in-context* *tree index* that enables LLMs to perform *reasoning-based*, *human-like retrieval* over long documents, without vector DB or chunking.
-
-
- **🧪 Cookbooks:**
-- [Vectorless RAG](https://docs.pageindex.ai/cookbook/vectorless-rag-pageindex): A minimal, hands-on example of reasoning-based RAG using PageIndex. No vectors, no chunking, and human-like retrieval.
-- [Vision-based Vectorless RAG](https://docs.pageindex.ai/cookbook/vision-rag-pageindex): OCR-free, vision-only RAG with PageIndex's reasoning-native retrieval workflow that works directly over PDF page images.
-
+# 🌲 PageIndexOllama: Local-First Tree RAG for Long Documents
+
+**PageIndex-Ollama** is an independent fork of PageIndex focused on **fully local document indexing and reasoning** with **Ollama**.
+
+You point it to a PDF (or Markdown), it builds a **hierarchical tree index**, and then uses LLM reasoning over that tree to retrieve relevant sections.
+
+Run it on your own machine with **no API keys** and no required external inference service.
+
+Detailed technical delta report: [ENHANCEMENTS_REPORT.md](ENHANCEMENTS_REPORT.md)
---
-# 📑 Introduction to PageIndex
+## ✨ Why This Fork Exists
-Are you frustrated with vector database retrieval accuracy for long professional documents? Traditional vector-based RAG relies on semantic *similarity* rather than true *relevance*. But **similarity ≠ relevance** — what we truly need in retrieval is **relevance**, and that requires **reasoning**. When working with professional documents that demand domain expertise and multi-step reasoning, similarity search often falls short.
+The upstream project is broad. This fork is opinionated:
-Inspired by AlphaGo, we propose **[PageIndex](https://vectify.ai/pageindex)** — a **vectorless**, **reasoning-based RAG** system that builds a **hierarchical tree index** from long documents and uses LLMs to **reason** *over that index* for **agentic, context-aware retrieval**.
-It simulates how *human experts* navigate and extract knowledge from complex documents through *tree search*, enabling LLMs to *think* and *reason* their way to the most relevant document sections. PageIndex performs retrieval in two steps:
+- local-first workflows
+- Ollama as the default inference backend
+- minimal cloud assumptions in setup and usage docs
+- engineer-focused, reproducible CLI + test flow
-1. Generate a “Table-of-Contents” **tree structure index** of documents
-2. Perform reasoning-based retrieval through **tree search**
+This repo keeps the core PageIndex retrieval design while making local execution the default operating mode.
-
+---
-### 🎯 Core Features
+## 🔍 What’s Different From Upstream PageIndex
+
+- OpenAI SDK is not part of the documented local workflow for this fork.
+- Ollama is the default backend used in setup and examples.
+- Provider abstraction is retained so model-call logic stays isolated from pipeline logic.
+- Offline-capable after model download.
+- No external API dependency required for normal local operation.
+
+### Enhancement Highlights in This Fork
+
+- **Runtime decoupling:** provider-routed wrappers replace OpenAI-tied call assumptions.
+- **Response contract stability:** finish-reason and response-shape normalization reduce provider-specific branching downstream.
+- **Prompt governance:** registry + loader architecture replaces large inline prompts and improves reproducibility.
+- **Performance:** bounded async parallelism accelerates TOC/summarization stages for local inference.
+- **Robustness:** adaptive chunking and hierarchical fallbacks reduce failure rates on difficult PDFs.
+- **Validation:** expanded e2e/integration/performance coverage validates local-first behavior end-to-end.
+
+### Upstream vs Fork (Practical Delta)
+
+| Area | Upstream | Fork | Decoupling Value |
+|---|---|---|---|
+| Provider API wrappers | OpenAI-branded wrappers | Provider-routed `Ollama_API*` wrappers | High |
+| Finish reason semantics | Provider-specific assumptions | Normalized response handler | High |
+| Credentials/env handling | More distributed | Centralized provider-aware module | Medium-High |
+| Prompt management | Inline prompt strings | Registry + loader + prompt files | High (operational) |
+| TOC/summary processing | More sequential | Async bounded concurrency | Medium-High |
+| Fallback behavior | Simpler/no hardening in some paths | Hierarchical/adaptive fallback paths | Medium |
+| CLI defaults | OpenAI model default | Local model default path | High (UX/ops) |
+| Test coverage | Minimal Python tests | Expanded e2e/integration/perf checks | High (risk reduction) |
+---
-Compared to traditional vector-based RAG, **PageIndex** features:
-- **No Vector DB**: Uses document structure and LLM reasoning for retrieval, instead of vector similarity search.
-- **No Chunking**: Documents are organized into natural sections, not artificial chunks.
-- **Human-like Retrieval**: Simulates how human experts navigate and extract knowledge from complex documents.
-- **Better Explainability and Traceability**: Retrieval is based on reasoning — traceable and interpretable, with page and section references. No more opaque, approximate vector search (“vibe retrieval”).
+## 🧠 How It Works (Architecture)
-PageIndex powers a reasoning-based RAG system that achieved **state-of-the-art** [98.7% accuracy](https://github.com/VectifyAI/Mafin2.5-FinanceBench) on FinanceBench, demonstrating superior performance over vector-based RAG solutions in professional document analysis (see our [blog post](https://vectify.ai/blog/Mafin2.5) for details).
+PageIndex-Ollama keeps the same core pattern:
-### 📍 Explore PageIndex
+1. Build a structured tree from a document
+2. Run LLM-guided search over that tree
+3. Generate answers from selected node context
-To learn more, please see a detailed introduction of the [PageIndex framework](https://pageindex.ai/blog/pageindex-intro). Check out this GitHub repo for open-source code, and the [cookbooks](https://docs.pageindex.ai/cookbook), [tutorials](https://docs.pageindex.ai/tutorials), and [blog](https://pageindex.ai/blog) for additional usage guides and examples.
+Key implementation points:
-The PageIndex service is available as a ChatGPT-style [chat platform](https://chat.pageindex.ai), or can be integrated via [MCP](https://pageindex.ai/mcp) or [API](https://docs.pageindex.ai/quickstart).
+- `pageindex/page_index.py` contains the PDF pipeline (`page_index_main`) and tree construction flow.
+- `pageindex/page_index_md.py` provides the Markdown path (`md_to_tree`).
+- `pageindex/utils.py` contains model-call wrappers (`Ollama_API_with_finish_reason`, `Ollama_API`, `Ollama_API_async`) and env-driven provider/model resolution.
+- `pageindex/response_handlers.py` normalizes response shape (including finish reason handling) to keep downstream logic stable.
+- `pageindex/continuation.py` handles truncated outputs by generating continuation prompts and stitching responses.
+- `pageindex/credentials.py` centralizes provider-specific credential/environment resolution.
+- `pageindex/models.py` defines typed schemas for structured outputs and parsing stability.
+- `pageindex/chunking_config.py` provides adaptive chunking strategy used for large-document handling.
+- Prompt templates are loaded through `pageindex/prompt_loader.py` and `pageindex/prompts/`.
-### 🛠️ Deployment Options
-- Self-host — run locally with this open-source repo.
-- Cloud Service — try instantly with our [Chat Platform](https://chat.pageindex.ai/), or integrate with [MCP](https://pageindex.ai/mcp) or [API](https://docs.pageindex.ai/quickstart).
-- _Enterprise_ — private or on-prem deployment. [Contact us](https://ii2abc2jejf.typeform.com/to/tK3AXl8T) or [book a demo](https://calendly.com/pageindex/meet) for more details.
+### Provider-Decoupling Design
-### 🧪 Quick Hands-on
+This fork keeps provider-specific behavior at the runtime boundary:
-- Try the [**Vectorless RAG**](https://github.com/VectifyAI/PageIndex/blob/main/cookbook/pageindex_RAG_simple.ipynb) notebook — a *minimal*, hands-on example of reasoning-based RAG using PageIndex.
-- Experiment with [*Vision-based Vectorless RAG*](https://github.com/VectifyAI/PageIndex/blob/main/cookbook/vision_RAG_pageindex.ipynb) — no OCR; a minimal, reasoning-native RAG pipeline that works directly over page images.
-
-
+1. Resolve provider/model from environment and config.
+2. Dispatch to provider-specific call path.
+3. Normalize output/finish reason into a stable internal shape.
+4. Continue tree/search/answer logic with provider-agnostic contracts.
----
+This keeps indexing and retrieval flows isolated from vendor-specific response differences.
-# 🌲 PageIndex Tree Structure
-PageIndex can transform lengthy PDF documents into a semantic **tree structure**, similar to a _"table of contents"_ but optimized for use with Large Language Models (LLMs). It's ideal for: financial reports, regulatory filings, academic textbooks, legal or technical manuals, and any document that exceeds LLM context limits.
-
-Below is an example PageIndex tree structure. Also see more example [documents](https://github.com/VectifyAI/PageIndex/tree/main/tests/pdfs) and generated [tree structures](https://github.com/VectifyAI/PageIndex/tree/main/tests/results).
-
-```jsonc
-...
-{
- "title": "Financial Stability",
- "node_id": "0006",
- "start_index": 21,
- "end_index": 22,
- "summary": "The Federal Reserve ...",
- "nodes": [
- {
- "title": "Monitoring Financial Vulnerabilities",
- "node_id": "0007",
- "start_index": 22,
- "end_index": 28,
- "summary": "The Federal Reserve's monitoring ..."
- },
- {
- "title": "Domestic and International Cooperation and Coordination",
- "node_id": "0008",
- "start_index": 28,
- "end_index": 31,
- "summary": "In 2023, the Federal Reserve collaborated ..."
- }
- ]
-}
-...
-```
+This design allows the same indexing/search pipeline to operate across providers with minimal call-site change.
+
+Runtime controls:
-You can generate the PageIndex tree structure with this open-source repo, or use our [API](https://docs.pageindex.ai/quickstart)
+- `LLM_PROVIDER=ollama`
+- `OLLAMA_URL=http://localhost:11434`
+- `OLLAMA_MODEL=mistral24b-16k` (or any installed Ollama model)
---
-# ⚙️ Package Usage
+## 🤖 Supported Models
+
+Any Ollama-compatible model can be used, including:
+
+- mistral
+- llama
+- qwen
+- other locally available Ollama models
-You can follow these steps to generate a PageIndex tree from a PDF document.
+Default examples in this repo use `mistral24b-16k`.
-### 1. Install dependencies
+Model quality and speed depend on:
+
+- model family + parameter size
+- quantization
+- context length
+- local CPU/GPU/VRAM
+
+---
+
+## 🚀 Quick Start (Local Only)
+
+### 1) Install dependencies
```bash
-pip3 install --upgrade -r requirements.txt
+pip install -r requirements.txt
```
-### 2. Set your OpenAI API key
+### 2) Install Ollama
+
+Use one of the repo scripts if helpful:
+
+```bash
+# Linux/macOS
+bash scripts/setup_ollama.sh
+
+# Windows PowerShell
+powershell scripts/setup_ollama.ps1
+```
-Create a `.env` file in the root directory and add your API key:
+### 3) Pull a model
```bash
-CHATGPT_API_KEY=your_openai_key_here
+ollama pull mistral24b-16k
```
-### 3. Run PageIndex on your PDF
+If that tag is unavailable on your machine, use any installed Ollama model and set `OLLAMA_MODEL` accordingly.
+
+### 4) Set environment variables
```bash
-python3 run_pageindex.py --pdf_path /path/to/your/document.pdf
+# Linux/macOS
+export LLM_PROVIDER=ollama
+export OLLAMA_URL=http://localhost:11434
+export OLLAMA_MODEL=mistral24b-16k
+
+# Windows PowerShell
+$env:LLM_PROVIDER="ollama"
+$env:OLLAMA_URL="http://localhost:11434"
+$env:OLLAMA_MODEL="mistral24b-16k"
```
-
-Optional parameters
-
-You can customize the processing with additional optional arguments:
+### 5) Run the CLI
+
+PDF:
+```bash
+python cli.py --pdf_path /path/to/document.pdf --model mistral24b-16k
```
---model OpenAI model to use (default: gpt-4o-2024-11-20)
---toc-check-pages Pages to check for table of contents (default: 20)
---max-pages-per-node Max pages per node (default: 10)
---max-tokens-per-node Max tokens per node (default: 20000)
---if-add-node-id Add node ID (yes/no, default: yes)
---if-add-node-summary Add node summary (yes/no, default: yes)
---if-add-doc-description Add doc description (yes/no, default: yes)
+
+Markdown:
+
+```bash
+python cli.py --md_path /path/to/document.md --model mistral24b-16k
```
-
-
-Markdown support
-
-We also provide markdown support for PageIndex. You can use the `-md_path` flag to generate a tree structure for a markdown file.
+Outputs are written to `results/*_structure.json`.
+
+---
+
+## 🧪 Testing
+
+Main test surfaces:
+
+- `run_comprehensive_e2e_tests.py`
+- `tests/e2e/`
+- `tests/`
+- `test_parallel_processing.py`
+
+Run:
```bash
-python3 run_pageindex.py --md_path /path/to/your/document.md
+python run_comprehensive_e2e_tests.py
+python -m pytest tests
```
-> Note: in this function, we use "#" to determine node heading and their levels. For example, "##" is level 2, "###" is level 3, etc. Make sure your markdown file is formatted correctly. If your Markdown file was converted from a PDF or HTML, we don't recommend using this function, since most existing conversion tools cannot preserve the original hierarchy. Instead, use our [PageIndex OCR](https://pageindex.ai/blog/ocr), which is designed to preserve the original hierarchy, to convert the PDF to a markdown file and then use this function.
-
+What these validate (end-to-end):
+
+- tree generation
+- tree availability/structure checks
+- LLM-driven node selection over tree content
+- answer generation from extracted node context
+- provider-decoupled response handling (including continuation behavior)
+- concurrency paths used for local throughput improvements
-
+### Why These Enhancements Matter Locally
+
+Local-first systems face two practical constraints: variable model quality and slower inference throughput.
+These enhancements directly target those constraints by improving deterministic behavior under imperfect outputs
+and reducing total latency through bounded parallelism.
---
-# 📈 Case Study: PageIndex Leads Finance QA Benchmark
+## 📌 Current Standardization Gaps
-[Mafin 2.5](https://vectify.ai/mafin) is a reasoning-based RAG system for financial document analysis, powered by **PageIndex**. It achieved a state-of-the-art [**98.7% accuracy**](https://vectify.ai/blog/Mafin2.5) on the [FinanceBench](https://arxiv.org/abs/2311.11944) benchmark, significantly outperforming traditional vector-based RAG systems.
+The core architecture is stable, but a few consistency items remain:
-PageIndex's hierarchical indexing and reasoning-driven retrieval enable precise navigation and extraction of relevant context from complex financial reports, such as SEC filings and earnings disclosures.
+- Canonical default model should be unified across CLI, config, docs, and tests.
+- Tree-search output key naming should be standardized (`node_ids` vs `relevant_node_ids`).
+- Some legacy naming/constants should be aligned with current model/provider behavior.
-Explore the full [benchmark results](https://github.com/VectifyAI/Mafin2.5-FinanceBench) and our [blog post](https://vectify.ai/blog/Mafin2.5) for detailed comparisons and performance metrics.
+These are consistency and maintenance concerns, not blockers for local-first operation.
-
+For full technical analysis, see [ENHANCEMENTS_REPORT.md](ENHANCEMENTS_REPORT.md).
---
-# 🧭 Resources
+## ⚠️ Known Limitations
-* 🧪 [Cookbooks](https://docs.pageindex.ai/cookbook/vectorless-rag-pageindex): hands-on, runnable examples and advanced use cases.
-* 📖 [Tutorials](https://docs.pageindex.ai/doc-search): practical guides and strategies, including *Document Search* and *Tree Search*.
-* 📝 [Blog](https://pageindex.ai/blog): technical articles, research insights, and product updates.
-* 🔌 [MCP setup](https://pageindex.ai/mcp#quick-setup) & [API docs](https://docs.pageindex.ai/quickstart): integration details and configuration options.
+- Local model choice matters a lot; small models can struggle on deep reasoning.
+- ~3B class models are usually weaker than larger frontier-class systems on complex document QA.
+- Very large PDFs can pressure RAM/VRAM depending on model/context settings.
+- Inference throughput and latency are hardware-dependent.
+- Some scripts in the repo assume specific local paths/shell conventions and may need environment-specific adjustment.
---
-# ⭐ Support Us
-Please cite this work as:
-```
-Mingtian Zhang, Yu Tang and PageIndex Team,
-"PageIndex: Next-Generation Vectorless, Reasoning-based RAG",
-PageIndex Blog, Sep 2025.
+## 🗂️ Project Layout
+
+```text
+PageIndexOllama/
+├── cli.py
+├── run_comprehensive_e2e_tests.py
+├── pageindex/
+│ ├── page_index.py
+│ ├── page_index_md.py
+│ ├── utils.py
+│ ├── response_handlers.py
+│ ├── continuation.py
+│ ├── credentials.py
+│ ├── models.py
+│ ├── chunking_config.py
+│ ├── prompt_loader.py
+│ └── prompts/
+├── scripts/
+│ ├── setup_ollama.sh
+│ └── setup_ollama.ps1
+├── tests/
+│ ├── e2e/
+│ ├── pdfs/
+│ └── results/
+└── requirements.txt
```
-Or use the BibTeX citation:
+---
-```
-@article{zhang2025pageindex,
- author = {Mingtian Zhang and Yu Tang and PageIndex Team},
- title = {PageIndex: Next-Generation Vectorless, Reasoning-based RAG},
- journal = {PageIndex Blog},
- year = {2025},
- month = {September},
- note = {https://pageindex.ai/blog/pageindex-intro},
-}
-```
+## 🔗 Relationship to Official PageIndex
-Leave us a star 🌟 if you like our project. Thank you!
+This repository is an **independent fork**.
-