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

data/README.md

@@ -0,0 +1,11 @@
+# Data directory policy
+
+本目录只保存数据格式说明、公开许可的小样例、清单和校验和。以下内容不得提交：
+
+- 未取得许可的报告、论文、教材和扫描件；
+- 涉密或分级不明确的地质资料；
+- 精确坐标、商业秘密和个人信息；
+- 私有验证问题、答案或人工标注工作副本；
+- 向量索引、上传文件、运行缓存和数据库备份。
+
+真实语料通过部署环境挂载或对象存储提供，不作为代码仓库内容。