writing-workbench/docs/operating-playbook.md

Operating Playbook

1. Start A Project

Start a project only when the user has a Web-generated initial outline.

Minimum inputs:

• lead writer identity;
• initial outline path or pasted outline;
• source material paths;
• working slug;
• the user's instruction to create the project.

If the user only has source materials or open discussion, stop and keep the work in knowledge-vault.

2. Create The Folder

Use:

projects/YYYY-MM-DD-short-slug/

Copy or create the project files from templates/article-project/PROJECT_STRUCTURE.md.

Fill these first:

• project.md
• source-map.md
• status.md
• decision-log.md
• 00-intake/initial-outline-v1.0.md

3. Prepare For Outline Review

The first operational stage is outline-review-prep.

Material processing is a subtask of outline review preparation. It exists because context windows are limited, not because the article has not entered writing.

For each source, decide the processing method from the source type:

• 思想考古报告 or already coherent report: preserve mostly intact or lightly annotate.
• long discussion: compress around article-relevant claims while preserving unused possibilities.
• past article: extract relevant arguments, examples, concepts, and style constraints.
• metadata or writing protocol: preserve as direct constraints.

Always keep source paths in source-map.md.

4. Review Rounds

A review round starts only when the user names the reviewer or reviewers.

Each reviewer gets:

02-outline-review/round-NN/reviewers/<reviewer-id>/session.md
02-outline-review/round-NN/reviewers/<reviewer-id>/report.md

The review brief may be prepared by the controller session, but the report must come from the real reviewer sub-session.

5. User Decision Gate

After review, stop and wait for the user.

The user may provide:

• reflection;
• accepted and rejected review points;
• direction for lead writer repair;
• instruction to run another review;
• instruction to draft a specific part.

Record these in decision-log.md and the relevant stage folder.

6. Outline Repair

Lead writer repair starts only after the user gives a repair instruction.

Versioning:

• Web initial outline is 1.0.
• First repaired outline starts at 2.0.
• Major later revisions use 3.0, 4.0, and so on.
• Small local adjustments use 3.1, 3.2, and so on.

Review reports do not create outline versions by themselves.

7. Drafting

Do not generate a full article unless the user explicitly asks for that exact action.

Default drafting is section-level or chapter-level. Preserve the complete writer session and the resulting draft.

If the writer introduces new cases outside source materials, mark them in draft-notes.md or the session record.

8. Publication Boundary

Writing Workbench may keep a local full draft for revision.

The publication copy and release metadata are maintained by the user in knowledge-vault, normally under sayings/.

Record the intended or final knowledge-vault target path in publish/knowledge-vault-target.md.