35 lines
983 B
Markdown
35 lines
983 B
Markdown
# Drafting
|
|
|
|
Project:
|
|
|
|
Stage: drafting_prep
|
|
|
|
Lead writer:
|
|
|
|
Authoritative outline:
|
|
|
|
## Minimal Workflow
|
|
|
|
1. Create `drafting/sessions/<unit>.prompt-N.md` for the current writing unit.
|
|
2. Have the lead writer write directly to `drafting/sessions/<unit>.returned-N.md`.
|
|
3. Keep one prompt/returned pair per unit attempt.
|
|
4. Increment `N` for reruns; do not overwrite prior attempts.
|
|
5. Do not maintain a controller-side aggregate draft by default.
|
|
6. Put user feedback into the next prompt instead of creating a separate issue log.
|
|
|
|
## Writing Units
|
|
|
|
| Order | Unit | Outline Node | Status |
|
|
| --- | --- | --- | --- |
|
|
| 00 | `00-intro` | | pending |
|
|
|
|
## Current Unit
|
|
|
|
`00-intro`
|
|
|
|
## Notes
|
|
|
|
- This is a first-draft pipeline, not an audit system.
|
|
- Do not create per-unit `agent-invocation-packet.md`, `run-metadata.json`, extraction files, proofread logs, or aggregate draft files unless the user asks.
|
|
- Outside-reader review and polish belong to revision after first-draft completion.
|