joaoh82 / rust_sqlite / 24966819455
69%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 29
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.922%. Remained the same
24966819455

push

github

web-flow 
Phase 7 — AI-era extensions: proposal + plan (no code) (#41)

* docs: Phase 7 (AI-era extensions) proposal + plan

Drafts the design pass before any Phase 7 code lands. Replaces
the one-line "Phase 7 — AI-era extensions (research)" stub in
roadmap.md with a real proposal in docs/phase-7-plan.md and a
short pointer in roadmap.md.

The proposal answers, for the AI-era equivalent of "what's
SQLRite for and where does it stop":

  - WHAT: vector + JSON + NL→SQL + MCP server. The storage +
    query primitives modern AI workloads need, plus the
    surface LLM agents naturally drive.
  - WHAT NOT: hosting/training models, GPU, multi-modal,
    distributed indexing, vector quantization. We integrate;
    we don't compete with Pinecone.
  - HOW MUCH: ~2-3 kLOC new Rust across the wave, sub-phased
    7a-7h with a clean dependency chain so any can be a
    stopping point.
  - DEPENDENCIES: clean DAG. 7a (VECTOR) gates 7b (distances)
    gates 7c (KNN exec) gates 7d (HNSW). 7e (JSON), 7f (FTS),
    7g (.ask), 7h (MCP) are parallelizable.

The doc deliberately calls out 8 open design questions
(Q1-Q8) with options + recommendations, so the project owner
can answer them up front rather than discovering them mid-
implementation:

  Q1. Is FTS in or out of Phase 7? (rec: out → Phase 8)
  Q2. HNSW params fixed or configurable? (rec: fixed)
  Q3. JSON storage format? (rec: bincoded serde_json::Value)
  Q4. .ask LLM provider — one or several? (rec: Anthropic-first)
  Q5. MCP — roll our own or use a crate? (rec: roll our own)
  Q6. pgvector-style operators or function-only? (rec: operators)
  Q7. Vector literal syntax? (rec: bracket arrays [0.1, ...])
  Q8. File format version bump strategy (rec: bump to v4 in 7a)

Also captures release-pipeline implications (MCP becomes the
8th product line in lockstep versioning) and what each Phase 6
SDK gains from the Phase 7 features (vector + JSON cross every
SDK; .ask is REPL-only).

Wires the new doc into:
  - docs/_index.md —... (continued)

4012 of 5995 relevant lines covered (66.92%)

1.23 hits per line

Jobs
ID Job ID Ran Files Coverage
1 24966819455.1 29
66.92
 GitHub Action Run
Source Files on build 24966819455