The Substrate group is Dav1d's formal Merkle-AGI research that drove the design — valuable, but it sat third in the nav and read like required reading. IA-only fix (no content touched): - re-caption 'Substrate' -> 'Substrate theory (advanced)' + a preamble marking it optional (nothing in Getting started / API depends on it); - reorder it BELOW the practical sections (now: Summary -> Getting started -> API -> Substrate theory -> Project); - pull 'bench' out of Substrate into Getting started (it's the practical benchmark surface, not theory). Practitioner path comes first; theory stays intact + credited, just last. |
||
|---|---|---|
| .. | ||
| _ext | ||
| _static | ||
| api | ||
| arborist-one-pager.rst | ||
| arborist-two-pager.rst | ||
| bench.rst | ||
| concepts.rst | ||
| conf.py | ||
| cookbook.rst | ||
| diagrams | ||
| google-l5-rag-10m.rst | ||
| index.rst | ||
| license.rst | ||
| Makefile | ||
| merkle-agi-dag-v7.rst | ||
| merkle-agi-v7w-spatial-temporal.rst | ||
| merkle-agi-v8-consensus.rst | ||
| pi-star.rst | ||
| quickstart.rst | ||
| README.md | ||
| requirements.txt | ||
| v8-fork-score.rst | ||
Arborist API Reference (Sphinx)
This directory contains Sphinx configuration to generate API documentation from docstrings.
Build
cd docs/_source
make html # Generate HTML (output: _build/html/)
make text # Generate text (output: _build/text/)
make clean # Remove build artifacts
Or directly:
sphinx-build -b html . _build/html
View
After building, open _build/html/index.html in a browser.
Structure
conf.py— Sphinx configurationindex.rst— Main table of contentsapi/— Module documentation (one .rst per module category)substrate.rst— Core data structures (merkle, document, wikitext)storage.rst— SQLite schema (store, ingest, evict)retrieval.rst— FTS5 search (search, sources, concepts)qa.rst— Q&A pipeline (runner, query, verify, evidence, etc.)distill.rst— Distillation (surface→core)mesh.rst— Federation (gossip-based sync)cli.rst— Command-line interface
What it replaces
This generated documentation replaces docs/modules.md (1200+ lines of static API reference). The docstrings in code are the source of truth; Sphinx extracts them automatically.
Adding new modules
- Add a docstring to the module (module-level docstring at the top of
module.py) - Add an
.rstfile inapi/that includes the module withautomoduledirective - Reference it in
index.rst - Rebuild with
make html
Theme
Uses furo theme (modern, responsive, search-enabled).
Autodoc directives
The .rst files use Sphinx automodule to extract:
- Module docstrings
- Class docstrings + members
- Function signatures + docstrings
- Source code links (
:viewcode:extension)
See Sphinx autodoc docs.