# 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_prep
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`.

## Project Path Contract

```text
intake/
outline/
audit/
editor/
handoff/
drafting/
revision/
publish/
```

These folders are working areas, not mandatory linear gates.

`intake/` stores Owner-provided inputs, background files, supplemental context, and source material as they enter the project. The Owner owns this folder unless the user explicitly delegates a specific intake task.

`outline/` stores formal outline versions such as `1.0`, `1.1`, `2.0`, or `4.0`. Keep all outline versions. The Owner currently maintains formal outline files; a lead writer may generate candidate outline content in `editor/`, but formal extraction into `outline/` remains an Owner action unless explicitly delegated.

`audit/` is the authoritative folder for individual reviewer audit runs.

`editor/` is the authoritative folder for lead-writer runs such as 韩愈. Lead-writer returned output may contain discussion, outline candidates, section drafts, or chapter drafts, but it is not the formal outline or publication draft until the Owner extracts it.

`handoff/` stores concise continuation documents for major phase transitions, context-window resets, or fresh-session starts. A handoff points to formal artifacts and run evidence; it does not replace `outline/`, `audit/`, `editor/`, or Owner decisions.

`drafting/` and `revision/` store local draft and revision work only when the user asks for article drafting or revision.

Root-level `ccpe/` owns the CCPE registry and invocation policy. Project `audit/` and `editor/` folders contain run evidence and raw participant outputs 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.