1.5 KiB
Raw Blame History

Architecture Decision Records

  • ADR-001: API First + Admin Console — Accepted
  • ADR-002: Modular monolith + workers + MCP gateway for V1 — Accepted
  • ADR-003: PostgreSQL + object storage are canonical — Accepted
  • ADR-004: Mochow is initial retrieval backend but replaceable — Superseded by ADR-010
  • ADR-005: Provider abstraction for embedding/reranker/parser/LLM — Accepted
  • ADR-006: RAG + Knowledge Compilation — Accepted
  • ADR-007: ACL before/during retrieval — Accepted
  • ADR-008: MCP hides infrastructure details — Accepted
  • ADR-009: Baidu BOS is the primary object-storage provider; local storage remains for tests and local development — Accepted
  • ADR-010: OceanBase Vector is the primary rebuildable retrieval index behind VectorStore; PostgreSQL remains canonical — Accepted
  • ADR-011: Qianfan bge-large-zh plus bce-reranker-base is the initial Demo model baseline — Accepted

Architecture migration boundary

ADR-009~011 adopt the verified internal platform provider baseline without copying its canonical-database design. ADR-003 remains binding: OceanBase Vector stores only rebuildable retrieval rows, while PostgreSQL and object storage retain canonical metadata and immutable source data.

The migration retains the Demo's Dense Top20 → Reranker Top5 behavior and current lightweight Parser scope. Top50 retrieval, distance thresholds, dual-query RRF, Marker/Pandoc and LLM-derived index content require separate product and evaluation decisions.