cleanup phases 6
This commit is contained in:
@@ -8,7 +8,7 @@ side of the stack lives in that project's own `CLAUDE.md`.
|
||||
> Working in `server/`? Read [server/CLAUDE.md](server/CLAUDE.md).
|
||||
> You almost never need both. A frontend change does not touch server files, and vice-versa.
|
||||
|
||||
> Last verified: 2026-07-30 against commit `d3ec723`.
|
||||
> Last verified: 2026-08-02 against commit `e2db973`.
|
||||
|
||||
---
|
||||
|
||||
@@ -52,7 +52,7 @@ package, or solution — each project is built, linted, and run on its own.
|
||||
| [`server/`](server/) | Backend API | ASP.NET Core (.NET 10) · Clean Architecture · CQRS · EF Core | [server/CLAUDE.md](server/CLAUDE.md) |
|
||||
| [`product/`](product/index.md) | **Business truth** — what to build and why | Markdown (+ generated HTML) | the table above |
|
||||
| [`docs/`](docs/README.md) | **Engineering truth** — rules, the client↔server contract, flows, status, roadmap | Markdown | [docs/README.md](docs/README.md) |
|
||||
| [`dev/`](dev/README.md) | The finished build-plan chain. **History, not a project** — nothing to build in it | Markdown | [dev/README.md](dev/README.md) |
|
||||
| [`archive/`](archive/README.md) | The executed build-chain (was `dev/`) and the cleanup plan that produced `docs/`. **History, not instruction** — nothing to build from it | Markdown | [archive/README.md](archive/README.md) |
|
||||
| [`telegram-otp-bot/`](telegram-otp-bot/) | OTP relay (standalone, the pre-launch demo rail) | Node 18+, zero deps | [telegram-otp-bot/README.md](telegram-otp-bot/README.md) |
|
||||
| [`deploy/`](deploy/) | Reverse-proxy config | Caddyfile | [DEPLOY.md](DEPLOY.md) |
|
||||
| [`.githooks/`](.githooks/README.md) | Repo-managed git hooks (the pre-commit secret scan) | shell | [docs/rules/shared/git-and-gates.md](docs/rules/shared/git-and-gates.md) |
|
||||
@@ -68,9 +68,8 @@ The two projects communicate over **HTTP/JSON** (optionally gRPC). The client re
|
||||
network, serving `balinyaar.ir` (client) and `api.balinyaar.ir` (server). The database is **not**
|
||||
containerised; it is a remote SQL Server. Full runbook: [DEPLOY.md](DEPLOY.md).
|
||||
|
||||
`archive/` does not exist yet. When it does, it will hold `dev/`'s history — and the rule will be that
|
||||
**anything in it is a record, not an instruction**, because it is written in the imperative from having once
|
||||
been a prompt.
|
||||
`archive/` holds `dev/`'s history now that the clarify chain has run. **Anything in it is a record, not
|
||||
an instruction** — it is written in the imperative from having once been a prompt.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user