47 lines
1.1 KiB
Markdown
47 lines
1.1 KiB
Markdown
# Project Lifecycle
|
|
|
|
## States
|
|
|
|
Use `status.md` to record the current state. Do not infer state from folder location.
|
|
|
|
Recommended states:
|
|
|
|
```text
|
|
outline_review_prep
|
|
blocked_waiting_capability
|
|
blocked_waiting_user_decision
|
|
review_round
|
|
outline_repair
|
|
drafting
|
|
revision
|
|
local_complete
|
|
archived_by_user
|
|
```
|
|
|
|
States may repeat. For example, after several review rounds the user may add new materials and return to `outline_review_prep`.
|
|
|
|
## Stage Folders
|
|
|
|
```text
|
|
00-intake/
|
|
01-materials/
|
|
audit/
|
|
02-outline-review/
|
|
03-outline-repair/
|
|
04-drafting/
|
|
05-revision/
|
|
publish/
|
|
```
|
|
|
|
These folders are working areas, not mandatory linear gates.
|
|
|
|
`audit/` is the authoritative folder for individual reviewer audit runs. `02-outline-review/` is for shared briefs, synthesis, and user-decision support.
|
|
|
|
Root-level `ccpe/` owns the CCPE registry and invocation policy. Project `audit/` folders contain run evidence only.
|
|
|
|
## Advancement Rule
|
|
|
|
The workspace may suggest next actions, but only the user advances the project.
|
|
|
|
Avoid language such as "passed review" or "ready to draft" unless it is quoting the user's decision.
|