Rename the project spec and update every reference to it
The charter file carried a tool-specific name while being the repository's own document: mission, non-negotiable constraints, the pinned stack, repo conventions and phase status, cited as authority by thirty files across the agent, api, deploy, docs, search and terraform trees. PROJECT-SPEC.md says what it is. All 42 references are updated in the same commit, including the relative link in docs/status.md, so nothing points at a filename that no longer exists.
This commit is contained in:
+2
-2
@@ -1,7 +1,7 @@
|
||||
# deploy
|
||||
|
||||
Kubernetes deployment for Cairn OBS, added in Phase 4 (`/deploy` was
|
||||
deliberately stubbed through Phase 3 -- see `/CLAUDE.md`'s Phase 3
|
||||
deliberately stubbed through Phase 3 -- see `/PROJECT-SPEC.md`'s Phase 3
|
||||
non-goals). Two pieces:
|
||||
|
||||
- `operator/` -- a small Go controller-runtime Operator managing one CRD
|
||||
@@ -18,7 +18,7 @@ map of per-tenant ClickHouse connection pools via `internal/chrunner`;
|
||||
`search` holds a map of per-tenant Tantivy indices via
|
||||
`src/registry.rs`) -- not at the Kubernetes layer. This directory is
|
||||
**not** "one Deployment per tenant" or a general multi-cluster system;
|
||||
that's an explicit Phase 4 non-goal (see `/CLAUDE.md`). What it *does*
|
||||
that's an explicit Phase 4 non-goal (see `/PROJECT-SPEC.md`). What it *does*
|
||||
add:
|
||||
|
||||
- A `Tenant` CRD + controller (`operator/internal/controller`) that
|
||||
|
||||
Reference in New Issue
Block a user