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
2026-07-12 14:42:11 +08:00
commit ec1acb36b5
55 changed files with 2882 additions and 0 deletions
--- a/frontend/src/api/.gitkeep
+++ b/frontend/src/api/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/components/.gitkeep
+++ b/frontend/src/components/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/features/.gitkeep
+++ b/frontend/src/features/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/features/chat/.gitkeep
+++ b/frontend/src/features/chat/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/features/documents/.gitkeep
+++ b/frontend/src/features/documents/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/features/evaluation/.gitkeep
+++ b/frontend/src/features/evaluation/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/features/retrieval/.gitkeep
+++ b/frontend/src/features/retrieval/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/hooks/.gitkeep
+++ b/frontend/src/hooks/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/pages/.gitkeep
+++ b/frontend/src/pages/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/routes/.gitkeep
+++ b/frontend/src/routes/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/styles/.gitkeep
+++ b/frontend/src/styles/.gitkeep
@@ -0,0 +1 @@
+
--- a/frontend/src/types/.gitkeep
+++ b/frontend/src/types/.gitkeep
@@ -0,0 +1 @@
+