<ContextMap />

Every page on this platform exposes machine-readable context to coding agents in three ways right now:

1. **Pull feeds:** Append `.md` or send `Accept: text/markdown` on any URL, or fetch `/llms-full.mdx/<brand>` for a single-file brand bundle.
2. **Full-text search API:** Query `/api/search?q=<query>&brand=<brand>` against each brand's isolated Orama index.
3. **Streamable HTTP MCP server (`/api/mcp`):** Call `list_docs`, `search_docs`, and `get_doc` over JSON-RPC 2.0 to retrieve Markdown with verified frontmatter citations (`checked` date and `sources`).

## Two layers: local sovereign memory + cloud docs index [#two-layers-local-sovereign-memory--cloud-docs-index]

Rather than relying on a single external SaaS database, the estate separates **operator memory** from **public product documentation**:

| Layer | Substrate | Verified performance & scope (`2026-10-25`) |
|---|---|---|
| **Local sovereign memory (`Starlight-Intelligence-System`)** | Append-only JSONL vaults (Strategic, Technical, Creative, Operational, Wisdom, Horizon) indexed in SQLite FTS5 + vector embeddings via `SisGatewayDaemon` (`127.0.0.1:5200`) with Reciprocal Rank Fusion (RRF) | `1,106` compiled memory atoms, `400` knowledge-graph rows, `Eval-50` `Hit@10 = 1.000`, `Recall@5 = 1.000`, `MRR@10 = 1.000` (`p50 = 218.9ms`), `0d` vault staleness |
| **Public docs & MCP index (`docs-platform`)** | Build-time Fumadocs MDX compilation + brand-isolated Orama search + `/api/mcp` Streamable HTTP server | Zero external DB latency; every page carries build-enforced `status: verified`, `checked` date, and `sources` |
| **Cloud relational & vector store (when multi-source)** | Supabase Postgres + `pgvector` + Row Level Security (RLS) | Used when joining documentation chunks with dynamic cloud records (`DemandSignal`, gate receipts) |
| **Temporal knowledge graph (when edge queries earn it)** | Graphiti on FalkorDB (bi-temporal validity windows) | Reserved for cross-artifact lineage ("which receipt superseded which release") |

<DocLink text="See the MCP tools reference" href="/starlight/mcp-tools" />

## Why local FTS5 + RRF and build-time Orama come before external SaaS [#why-local-fts5--rrf-and-build-time-orama-come-before-external-saas]

1. **Zero drift from Git:** Documentation lives in version-controlled MDX with a Zod provenance gate in `lib/source.ts`. If a page's `status: verified` frontmatter lacks a `checked` date or `sources` list, `next build` fails immediately.
2. **Progressive disclosure over heavy RAG:** As recorded in `TRUTH.md` §3b (`arXiv 2607.17598`), single-level index-to-passage lookup (`llms.txt` → `.md` page or `search_docs` → `get_doc`) outperforms multi-hop vector routing at corpus scales under 2M words while preserving exact file citations.
3. **Sovereign privacy boundary:** Private operator notes stay in `starlight-private-memory` and local `SisGatewayDaemon` loopback (`127.0.0.1:5200` with privacy tag scrubbing), never leaking into public cloud indexes.