70 lines
2.2 KiB
Markdown
70 lines
2.2 KiB
Markdown
---
|
||
title: "Editorial Workflow"
|
||
type: concept
|
||
tags: ["writing", "process", "iteration", "quality"]
|
||
sources: ["marketing-book-co-author"]
|
||
last_updated: 2026-04-30
|
||
---
|
||
|
||
## Definition
|
||
|
||
编辑工作流（Editorial Workflow）是一套以版本化管理、编辑注释显式化和明确反馈回路为核心的迭代修订过程。在 Book Co-Author Agent 的语境中，编辑工作流是确保书籍质量、保持作者声音、保护品类定位的核心机制。
|
||
|
||
## Core Components
|
||
|
||
### 1. 版本化管理（Versioning）
|
||
- 每个实质性草稿必须标注明确版本号
|
||
- 格式示例：`Chapter 3 - Version 1 - ready for review`
|
||
- 版本标签是强制要求，不可省略
|
||
|
||
### 2. 编辑注释显式化（Editorial Notes Visibility）
|
||
- 假设条件明确标注
|
||
- 证据缺口和来源缺口显式列出
|
||
- 语气和可信度风险直接说明
|
||
- 决策需求以问题形式列出
|
||
|
||
### 3. 明确反馈回路（Explicit Feedback Loop）
|
||
- 不以"请告知修改意见"结束
|
||
- 必须提出具体的下一步修订任务
|
||
- 明确哪些问题需要委托方决策，哪些由代笔人处理
|
||
|
||
## Versioned Draft Format
|
||
|
||
```markdown
|
||
Chapter X - Version N - ready for review
|
||
|
||
[Fully written first-person draft with clear section flow,
|
||
concrete examples, and language aligned to the author's positioning.]
|
||
```
|
||
|
||
## Editorial Notes Format
|
||
|
||
```markdown
|
||
## Editorial Notes
|
||
- Assumptions made
|
||
- Evidence or sourcing gaps
|
||
- Tone or credibility risks
|
||
- Decisions needed from the author
|
||
```
|
||
|
||
## Feedback Loop Format
|
||
|
||
```markdown
|
||
## Next Review Questions
|
||
1. Which claim feels strongest and should be expanded?
|
||
2. Where does the chapter still sound unlike you?
|
||
3. Which example needs better proof, detail, or chronology?
|
||
```
|
||
|
||
## Key Success Metric
|
||
|
||
> "Each revision round ends with explicit decisions, not open-ended uncertainty."
|
||
|
||
编辑工作流的最终目标：每轮修订后，双方（代笔人+委托方）都有明确的行动项，而非模糊的"继续打磨"。
|
||
|
||
## Related Concepts
|
||
- [[Voice Protection]] — 编辑工作流服务于声音保护
|
||
- [[Ghostwriting]] — 编辑工作流是代笔写作的核心流程
|
||
- [[Chapter Blueprint]] — 蓝图是编辑工作流的前置规划步骤
|
||
- [[Narrative Architecture]] — 编辑工作流需维护叙事架构不被破坏
|