Add read-only production runtime audit

README.md

@@ -3,21 +3,14 @@
 Medical chatbot grounded in the Vietnamese National Drug Formulary
 (Dược thư quốc gia Việt Nam 2018), built as a microservices monorepo.
 
-See [docs/architecture.md](docs/architecture.md) for the full design
-(service responsibilities, data stores, RAG ingestion strategy, safety
-guardrails), [docs/adr](docs/adr) for architecture decision records,
-[docs/pdf-parsing-outlier-catalog.md](docs/pdf-parsing-outlier-catalog.md)
-for a reusable checklist of confirmed PDF-parsing risks (useful for this
-book and any similarly-structured PDF), and
-[docs/progress-log.md](docs/progress-log.md) for a running log of what's
-been done and what's next.
+Start with the [canonical documentation set](docs/README.md). It is a compact,
+code-verified set covering architecture, PDF ingestion, RAG/chat, local development,
+operations, API, configuration, evaluation and documentation governance.
 
-Dated planning and audit documents (`docs/v1-delivery-plan.md`,
-`docs/rag-rebuild-plan.md`, `docs/current-rag-pipeline-audit.md`,
-`docs/answer-experience-implementation-plan.md`) record what was known on
-their date and are kept for their reasoning rather than as current status —
-this README and `git log` are the better reference for where things stand
-today.
+The former numbered `00–29` material and historical plans are retained in
+[`docs-legacy/`](docs-legacy/) as raw input only. Architecture decisions also remain
+there until reviewed. See the canonical
+[documentation policy](docs/documentation-policy.md) for source precedence.
 
 > **Status** (2026-08-11): **live in production at
 > [realvuxbaro.me](https://realvuxbaro.me)** — a real RAG chatbot over the
@@ -36,7 +29,8 @@ today.
 >
 > Because the gateway and auth services do not exist, `apps/web` talks
 > **directly** to `apps/ai-service`; there is no authentication layer. See
-> the build roadmap in `docs/architecture.md`.
+> [canonical architecture document](docs/architecture.md) for the implemented
+> topology and the explicit status of current, scaffolded and target components.
 
 ## Directory map
 
@@ -56,7 +50,8 @@ packages/
   config/         shared eslint/tsconfig presets
 ingestion/        offline batch pipeline: PDF -> monographs -> chunks -> embeddings -> Qdrant
 infra/            docker-compose, k8s/Helm, Terraform, CI
-docs/             architecture docs and ADRs
+docs/             canonical project documentation
+docs-legacy/      raw notes, historical plans and ADRs pending review
 ```
 
 ## Prerequisites
@@ -203,7 +198,7 @@ in named volumes rather than the containers.
 
 This is **interim infrastructure**, not the end state. The intended target is
 still the team's self-hosted **Gitea** (company domain) plus their **ArgoCD**
-instance, per `docs/adr/0002-argocd-gitops.md` — that work is *not started*,
+instance, per `docs-legacy/adr/0002-argocd-gitops.md` — that work is *not started*,
 not cancelled. Until it is deliberately started, the project stays on private
 GitHub, and the team's existing `git.vinmec.tech/ai-team/gitops` repository is
 reference-only: never push this project into it.