Establish a safe foundation before implementing the geology RAG system

The project begins with architecture, data governance, reproducible evaluation, deployment boundaries, and secret-handling contracts so later code has measurable acceptance criteria.

Constraint: Real provider credentials, workspace identities, and restricted geological data must never enter Git

Rejected: Add placeholder runnable services in the design commit | would imply unverified implementation readiness

Confidence: high

Scope-risk: narrow

Reversibility: clean

Directive: Run make verify before every commit and update ADRs when architecture boundaries change

Tested: Secret scan, Markdown links, YAML parse, shell syntax, and staged diff validation

Not-tested: Application runtime is intentionally deferred to the implementation stage

docs/adr/README.md

@@ -0,0 +1,9 @@
+# Architecture Decision Records
+
+ADR 用于记录会长期影响系统的技术决策。状态使用 `proposed`、`accepted`、`superseded` 或 `rejected`。
+
+当前记录：
+
+- [0001-use-pgvector.md](0001-use-pgvector.md)：选择 PostgreSQL + pgvector 作为第一版向量存储。
+- [0002-separate-bailian-protocols.md](0002-separate-bailian-protocols.md)：分离百炼 Chat/Embedding 与 Rerank 协议适配器。
+- [0003-text-first-scope.md](0003-text-first-scope.md)：第一版采用文本优先边界，不宣称地质图空间理解。