Skip to content

v0.2.6 — Document RAG Foundation

Choose a tag to compare

View all tags
@Rcloudso Rcloudso released this 19 Jul 07:24
v0.2.6
950c4b2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Product impact

v0.2.6 turns the FAQ-first MVP into a small but complete document-grounded support workflow. Administrators can upload, inspect, retry, enable, disable, and delete enterprise documents; customer answers can cite the document and chunk used as evidence.

Highlights

  • TXT, Markdown, text-layer PDF, and DOCX ingestion.
  • Semantic chunking and FAQ/document hybrid retrieval.
  • Source-aware recall so one knowledge type does not crowd out the other.
  • Compact document, chunk, and page provenance in chat and knowledge-review snapshots.
  • Deterministic no-key fallback to the best original source excerpt.
  • Environment-only model credentials and atomic non-secret configuration writeback.
  • Compatible intent output negotiation across json_schema, json_object, validated text JSON, and keyword fallback.
  • Bilingual, light/dark, desktop/mobile admin workflows.

Verification

  • FAQ eval: 11 cases; Top1 100%, Top3 100%, no-match 100%.
  • Document eval: 12 real-format cases; Top3 100%, semantic-v1 MRR 1.000.
  • Playwright: 32 API and Chromium workflows passed.
  • Regression, TypeScript, production build, fresh-archive install/build, and diff checks passed.

See the full evidence package.

Demo and build story

  • The attached smart-customer-service-v0.2.6-demo.mp4 is a 2m57s Mandarin walkthrough recorded against the real local application.
  • The AI-assisted development case study explains what Codex accelerated, which decisions remained human, what failures were caught, and why the project did not add speculative multi-agent or vector-database infrastructure.

Known limits

  • Parsing and embedding are synchronous and bounded inside the Express process.
  • PDF requires a text layer; OCR and image understanding are not included.
  • Formal citations/page jumps, reranking, and no-evidence refusal are planned next.
  • SQLite plus the in-memory vector index remains the intended small-deployment path.
  • Existing dependency findings through bcrypt/tar, uuid, and xlsx remain documented; xlsx currently has no upstream fix.

This project remains pre-1.0. APIs and persisted data may change before a stability review.

Assets 3
Loading