cleanup phases 6
This commit is contained in:
+9
-8
@@ -2,9 +2,10 @@
|
||||
|
||||
The entry point. Start here, follow one link, stop reading.
|
||||
|
||||
> **Being built.** This tree is the output of [the clarify chain](_plan/README.md). Sections marked
|
||||
> _not yet written_ are scaffolded but empty — the doc that currently holds that knowledge is named
|
||||
> beside each one so nothing is unreachable in the meantime.
|
||||
> **Built by the clarify chain**, phases 0–6, 2026-07-29 → 2026-08-02. The chain's own plan — inventory,
|
||||
> contradiction log, phase files, and their progress table — is now history, kept at
|
||||
> [`archive/clarify-chain/`](../archive/clarify-chain/README.md). Phase 7 (skills & guardrails) is still
|
||||
> open.
|
||||
|
||||
---
|
||||
|
||||
@@ -19,7 +20,8 @@ The entry point. Start here, follow one link, stop reading.
|
||||
**A file belongs in exactly one.** If you are about to write a business rule into `docs/`, it belongs in
|
||||
`product/`. If you are about to obey something in `archive/`, stop — it is a record, not an instruction.
|
||||
|
||||
`archive/` does not exist yet; Phase 6 creates it from today's [`dev/`](../dev/README.md).
|
||||
`archive/` holds the executed build-chain prompts, reports, and the pre-cleanup `docs/_plan/`. Start at
|
||||
[`archive/README.md`](../archive/README.md).
|
||||
|
||||
---
|
||||
|
||||
@@ -30,9 +32,8 @@ The entry point. Start here, follow one link, stop reading.
|
||||
| [rules/](rules/index.md) | What must never be broken — the tiered rule set behind the `CLAUDE.md` files | **written** · phase 1 |
|
||||
| [integration/](integration/index.md) | The client↔server seam in one place: contract, config, topology, OpenAPI | **written** · phase 2 |
|
||||
| [flows/](flows/index.md) | What is implemented, and how to test it — one file per user journey | **written** · phase 3 |
|
||||
| [status/](status/index.md) | Where the project actually is: implemented, backlog, decisions | not yet written · phase 4 |
|
||||
| [roadmap/](roadmap/index.md) | Where it goes next, and what gates a launch | not yet written · phase 5 |
|
||||
| [_plan/](_plan/README.md) | The chain that builds this tree. **Temporary** — moves to `archive/` when done | in progress |
|
||||
| [status/](status/index.md) | Where the project actually is: implemented, backlog, decisions | **written** · phase 4 |
|
||||
| [roadmap/](roadmap/index.md) | Where it goes next, and what gates a launch | **written** · phase 5 |
|
||||
|
||||
## Still elsewhere
|
||||
|
||||
@@ -40,7 +41,7 @@ Two documents stay outside this tree on purpose:
|
||||
|
||||
- [`DEPLOY.md`](../DEPLOY.md) — the deploy *procedure*, at the repo root where an operator will look for
|
||||
it. The runtime *topology* it implies moves to `docs/integration/topology.md`.
|
||||
- [`product/`](../product/index.md) — untouched by this chain. `docs/status/implemented.md` will overlay
|
||||
- [`product/`](../product/index.md) — untouched by this chain. `docs/status/implemented.md` overlays
|
||||
build state onto its 14 business areas rather than restating them.
|
||||
|
||||
## Conventions
|
||||
|
||||
Reference in New Issue
Block a user