Skip to main content
These documents record what was decided, measured or researched on a given date. They do not describe current behaviour, which is defined by the code, the OpenAPI contract, the domain language and the living pages in docs/inventory.toml. Each dated document carries a Date: and a Status: line under its title and is frozen: make docs fails when a branch edits or removes one (compared with where the branch forked from origin/main). To change a past decision, add a new document or ADR (docs/adr/) that supersedes it and links to it. Only a document whose status is proposed may still be edited. The rules and their trade-offs are recorded in ADR 0004 (docs/adr/0004-documentation-rules-are-enforced-by-ci-only.md). Dated documents keep their original language.

​
Adding one

  1. Put it in the folder for its kind below. Give it a stable file name.
  2. Start it with its title, then Date: YYYY-MM-DD and Status: <status> lines (for example proposed, accepted, final or historical).
  3. Add it to the list here.
Architecture decisions go in docs/adr/ with the next number.

​
Design records

Specifications and decision records from the design phase. Contract facts in them may since have changed; the contract and the code are authoritative.
  • Project and architecture overview (docs/dated/design/quivr-v2-architecture-overview.md) (French)
  • Backend MVP scope (docs/dated/design/quivr-v2-backend-mvp-scope.md) (French)
  • Canonical data model and lifecycle invariants (docs/dated/design/quivr-v2-canonical-data-model.md)
  • Module ownership and repository design (docs/dated/design/quivr-v2-module-boundaries.md)
  • Public ingestion contracts (docs/dated/design/quivr-v2-ingestion-contracts.md)
  • Public text search and projection rebuild (docs/dated/design/quivr-v2-search-contracts.md)
  • Thin monitoring tracer and public change feed (docs/dated/design/quivr-v2-monitoring-tracer.md)

​
Evidence

Measurements and verification reports tied to a commit.
  • THE-661: text retrieval baseline (docs/dated/evidence/the-661-retrieval-baseline.md)
  • THE-662: Spec 1 obligation map (docs/dated/evidence/the-662-spec1-closure.md)
  • THE-663: demo interface evidence (docs/dated/evidence/the-663-ui.md)
  • THE-664: deployment evidence (docs/dated/evidence/the-664-deployment.md)
  • THE-675: removing the per-query floor from public search (docs/dated/evidence/the-675-query-floor.md)

​
Research

Technology comparisons behind the stack.
  • Cloudflare Forge as the generation pipeline (docs/dated/research/forge-generation-pipeline.md)
  • DeepSeek Harness plugin architecture (docs/dated/research/deepseek-harness-plugin-architecture.md) (French)
  • Event runtime developer experience (docs/dated/research/event-runtime-devx.md) (French)
  • Herdr plugin model (docs/dated/research/herd-plugin-architecture.md) (French)
  • Meilisearch (docs/dated/research/meilisearch-for-quivr.md) (French)
  • Modern search developer experience (docs/dated/research/modern-search-devx.md) (French)
  • Recent durable runtimes (docs/dated/research/new-durable-runtime-systems.md) (French)
  • Open-source vector engines (docs/dated/research/new-oss-vector-systems.md) (French)
  • Pi extensions and Chord (docs/dated/research/pi-plugin-architecture.md) (French)
  • Isolated plugin runtime (docs/dated/research/plugin-isolation-runtime.md) (French)
  • Storage and search stack (docs/dated/research/storage-search-stack.md) (French)
  • Windmill as ingestion and plugin runtime (docs/dated/research/windmill-for-quivr.md) (French)