975 lines
30 KiB
Markdown
975 lines
30 KiB
Markdown
---
|
||
artifact_type: ccpe-runtime
|
||
name: article-outline-development
|
||
runtime_id: article-outline-development
|
||
author: CCPE System
|
||
version: 0.1.0
|
||
created: 2026-06-04
|
||
updated: 2026-06-04
|
||
status: draft
|
||
runtime_type: interactive-runtime
|
||
target_platform: Codex / Claude Code / OpenClaw / manual workflow
|
||
based_on: CCPE System
|
||
related_agents:
|
||
- article-context-architect
|
||
- han-yu-main-writer
|
||
- zhang-liao
|
||
- cognitive-imaging
|
||
- giant-cognition
|
||
related_skills:
|
||
- candidate: context-pack-builder
|
||
- candidate: review-synthesis
|
||
- candidate: repair-request-builder
|
||
related_protocols:
|
||
- agent-invocation-packet
|
||
related_models:
|
||
- cognitive-imaging
|
||
- giant-cognition
|
||
---
|
||
|
||
# Article Outline Development Runtime
|
||
|
||
## 1. Runtime Overview
|
||
|
||
### 1.1 Purpose
|
||
|
||
定义深度创作流程中“观点素材进入韩愈立意与提纲生成，再进入提纲评审”的标准交互式运行协议。Runtime 管理观点素材压缩拆分、韩愈立意调用、用户立意确认、韩愈提纲调用、上下文包构建、评审员分发、独立会话记录、评审报告归档、意见综合、修复请求生成和用户决策门。
|
||
|
||
### 1.2 Runtime Type
|
||
|
||
```text
|
||
interactive-runtime
|
||
```
|
||
|
||
### 1.3 Operating Mode
|
||
|
||
```text
|
||
hybrid-mode
|
||
```
|
||
|
||
### 1.4 Success Criteria
|
||
|
||
- 用户可以从观点素材文件启动写作流程，而不手工压缩、拆分和传递全部材料。
|
||
- 韩愈在输出立意和提纲前，已经获得经过压缩拆分的相关素材包。
|
||
- 用户可以从一份初稿提纲启动评审，而不手工复制全部材料。
|
||
- Runtime 可以明确区分“自己执行的调度工作”和“必须调用 canonical agent 的角色工作”。
|
||
- 所有被调用角色都有 invocation packet 或 invocation record。
|
||
- 每个评审员获得足够但不过量的上下文。
|
||
- 每个评审会话独立保存 `session.md` 和 `report.md`。
|
||
- Runtime 不模拟韩愈、张辽、认知显影、巨人认知或 Article Context Architect 的正式输出。
|
||
- Orchestrator 或用户可以只读 report 完成综合。
|
||
- 评审冲突被转化为用户可裁决的问题。
|
||
- 修复请求能交给韩愈执行下一版提纲修复。
|
||
- 每轮结束后可以清楚判断：下一轮、确认终稿、暂停、补充材料。
|
||
|
||
### 1.5 Non-Goals
|
||
|
||
- 不管理灵感记录。
|
||
- 不替用户完成观点判断，但可以管理“用户已放入观点素材后，请韩愈看立意和切入”的标准写作入口。
|
||
- 不覆盖正文写作、正文评审、附录、Metadata、审判庭或建模委员会。
|
||
- 不取代用户对文章立意和提纲终稿的确认。
|
||
- 不自动重写韩愈或评审员的专家内核。
|
||
|
||
## 2. Participants
|
||
|
||
### 2.1 Human Role
|
||
|
||
用户是最终导演、编辑和决策门，负责：
|
||
|
||
- 指定当前文章项目。
|
||
- 指定当前提纲版本。
|
||
- 指定本轮评审员。
|
||
- 确认材料范围。
|
||
- 确认上下文包可分发。
|
||
- 决定采纳、拒绝、保留或延后哪些评审意见。
|
||
- 决定是否进入下一轮评审或确认 `outline-final.md`。
|
||
|
||
### 2.2 Agents
|
||
|
||
```text
|
||
- agent_id: article-context-architect
|
||
role: 上下文架构助手
|
||
responsibility: 构建 source digest、outline-aligned context pack、shared context pack 和 per-reviewer dispatch pack。
|
||
invocation_condition: 每轮评审启动前，或提纲/材料发生显著变化时。
|
||
|
||
- agent_id: han-yu-main-writer
|
||
role: 散文主笔
|
||
responsibility: 基于用户讨论生成初稿提纲，并根据 repair-request 修复提纲。
|
||
invocation_condition: 用户需要生成或修复提纲时。
|
||
|
||
- agent_id: zhang-liao
|
||
role: 红队与建设性苏格拉底评审
|
||
responsibility: 检查提纲的战略风险、论证薄弱点、反对意见和修复路径。
|
||
invocation_condition: 用户指定其参与本轮评审时。
|
||
|
||
- agent_id: cognitive-imaging
|
||
role: 认知显影评审
|
||
responsibility: 显影提纲中的概念结构、认知遮蔽、论证显影不足和读者理解障碍。
|
||
invocation_condition: 用户指定其参与本轮评审时。
|
||
|
||
- agent_id: giant-cognition
|
||
role: 巨人认知评审
|
||
responsibility: 检查提纲的尺度、宏观结构、跨层连接和认知跨度。
|
||
invocation_condition: 用户指定其参与本轮评审时。
|
||
```
|
||
|
||
### 2.3 Skills
|
||
|
||
```text
|
||
- skill_id: candidate/context-pack-builder
|
||
purpose: 将稳定的上下文构建步骤抽成 Skill。
|
||
invocation_condition: v0 试跑后确认步骤稳定。
|
||
|
||
- skill_id: candidate/review-synthesis
|
||
purpose: 综合多个评审报告。
|
||
invocation_condition: 多轮试跑后确认综合规则稳定。
|
||
|
||
- skill_id: candidate/repair-request-builder
|
||
purpose: 把评审综合转为主笔修复请求。
|
||
invocation_condition: 修复请求格式稳定后。
|
||
```
|
||
|
||
### 2.4 Tools
|
||
|
||
```text
|
||
- tool_name: filesystem-read
|
||
purpose: 读取 writing-workbench 项目文件、source-map 指向材料和评审报告。
|
||
permission: 只读用户指定项目和材料。
|
||
|
||
- tool_name: filesystem-write
|
||
purpose: 写入本轮 Runtime 输出文件。
|
||
permission: 仅写入当前 article project 目录；覆盖需确认。
|
||
```
|
||
|
||
## 3. Context Layer
|
||
|
||
### 3.1 Input Contract
|
||
|
||
Runtime 从以下状态启动：
|
||
|
||
```text
|
||
- 用户已在 writing-workbench 创建 article project。
|
||
- project.md、source-map.md、status.md 至少存在。
|
||
- 用户已放入观点素材文件，并在 source-map.md 标明来源或 src mapping。
|
||
- 用户发起任务：写文章，观点在哪儿，让韩愈看立意和切入。
|
||
- 用户确认韩愈输出的立意后，再请求韩愈输出提纲。
|
||
- 用户指定或确认本轮评审员。
|
||
```
|
||
|
||
### 3.2 Required Context
|
||
|
||
- 当前项目路径。
|
||
- source-map。
|
||
- 当前阶段目标：立意 / 提纲生成 / 提纲评审 / 提纲修复。
|
||
- 当前阶段可用材料范围。
|
||
- 如果已有立意：当前文章立意或 creative brief。
|
||
- 如果已有主笔会话：主笔提纲生成过程的 report 或 session。
|
||
- 如果进入评审：本轮评审目标。
|
||
|
||
### 3.3 Optional Context
|
||
|
||
- 过往文章全文。
|
||
- Deep Research 报告。
|
||
- 知识库讨论记录。
|
||
- 系列文章定位。
|
||
- 用户对读者可见性和内部材料的说明。
|
||
|
||
### 3.4 Shared Context
|
||
|
||
所有评审员默认共享：
|
||
|
||
- review-brief.md
|
||
- 当前提纲。
|
||
- shared-outline-context-pack.md
|
||
- 用户指定的评审目标和输出格式。
|
||
|
||
评审员专属上下文放在其目录下的 `dispatch-pack.md`。
|
||
|
||
`dispatch-pack.md` 不能默认等同于完整 agent 启动包。Runtime 必须额外生成 `agent-invocation-packet.md` 来说明如何启动 canonical CCPE agent；当参与者在 Gemini/GPT/Claude 等外部平台运行且无法读取本地 canonical prompt/spec 时，还必须生成 `prompt-to-send.md`。
|
||
|
||
该规则适用于所有被调用角色：
|
||
|
||
```text
|
||
- article-context-architect
|
||
- han-yu-main-writer
|
||
- zhang-liao
|
||
- cognitive-imaging
|
||
- giant-cognition
|
||
```
|
||
|
||
### 3.5 Source Policy
|
||
|
||
- `knowledge-vault` 保持原始材料权威位置。
|
||
- `writing-workbench` 项目保存 source-map、digest、context pack、session 和 report。
|
||
- Runtime 不默认复制原文全文。
|
||
- 用户明确指定的材料优先于模型回忆。
|
||
- 内部资料不得自动变成公开引用。
|
||
|
||
## 4. Authority Layer
|
||
|
||
### 4.1 Autonomous Actions
|
||
|
||
- 创建本轮评审目录。
|
||
- 草拟 review-brief。
|
||
- 调用 Article Context Architect 生成上下文包草案。
|
||
- 为评审员准备 dispatch pack 草案。
|
||
- 根据 report.md 汇总评审意见。
|
||
- 生成 synthesis 和 repair-request 草案。
|
||
|
||
### 4.2 Actions Requiring Confirmation
|
||
|
||
- 启动评审分发。
|
||
- 覆盖已有轮次文件。
|
||
- 修改提纲版本命名。
|
||
- 改变材料范围。
|
||
- 确认某条评审意见为采纳或拒绝。
|
||
- 确认 outline-final。
|
||
- 修改 writing-workbench 模板。
|
||
|
||
### 4.3 Forbidden Actions
|
||
|
||
- 删除原始材料或会话记录。
|
||
- 在没有用户确认时自动进入下一阶段。
|
||
- 合并评审员会话导致来源不可追溯。
|
||
- 将评审员意见改写成用户意见。
|
||
- 以自动化替代用户的立意裁决。
|
||
|
||
### 4.4 Human Decision Gates
|
||
|
||
```text
|
||
Gate 1:
|
||
- Trigger: Runtime 启动。
|
||
- Human decision required: 确认项目路径、提纲版本、评审员、材料范围。
|
||
- Possible outcomes: 启动 / 补材料 / 暂停。
|
||
|
||
Gate 2:
|
||
- Trigger: 上下文包和 dispatch pack 草案完成。
|
||
- Human decision required: 是否批准分发给评审员。
|
||
- Possible outcomes: 分发 / 修改上下文 / 缩小材料 / 扩充材料。
|
||
|
||
Gate 3:
|
||
- Trigger: 所有 report.md 收齐并完成 synthesis。
|
||
- Human decision required: 采纳、拒绝、保留或延后哪些意见。
|
||
- Possible outcomes: 生成 repair-request / 补评审 / 暂停。
|
||
|
||
Gate 4:
|
||
- Trigger: 韩愈根据 repair-request 输出新版提纲。
|
||
- Human decision required: 是否进入下一轮评审或确认终稿。
|
||
- Possible outcomes: 下一轮 / outline-final / 回到主笔讨论 / 暂停。
|
||
```
|
||
|
||
### 4.5 Risk Levels
|
||
|
||
```text
|
||
Low: 创建新轮次目录、生成草案、读取已授权项目文件。
|
||
Medium: 压缩材料、裁剪 dispatch pack、综合评审意见。
|
||
High: 改变提纲结构、改变材料用途、确认采纳/拒绝意见。
|
||
Critical: 删除材料、覆盖终稿、自动发布或进入后续大流程。
|
||
```
|
||
|
||
## 5. Workflow Layer
|
||
|
||
### 5.1 Runtime Stages
|
||
|
||
```text
|
||
Stage 1:
|
||
- Purpose: 启动标准写作入口。
|
||
- Actor: Human + Runtime
|
||
- Input: project path, source-map, viewpoint material scope
|
||
- Output: runtime-entry.md and material intake status
|
||
- Human gate: required
|
||
|
||
Stage 2:
|
||
- Purpose: 压缩拆分观点素材，生成韩愈立意输入包。
|
||
- Actor: Article Context Architect
|
||
- Input: source-map, viewpoint materials, project brief if any
|
||
- Output: context manifest, source digests, premise-context-pack.md, article-context-architect invocation record
|
||
- Human gate: required before Han Yu positioning invocation
|
||
|
||
Stage 3:
|
||
- Purpose: 韩愈看立意和切入。
|
||
- Actor: Han Yu
|
||
- Input: premise-context-pack.md, project.md, source-map.md, user instruction
|
||
- Output: han-yu positioning dispatch-pack.md, agent-invocation-packet.md, prompt-to-send.md when needed, positioning proposal
|
||
- Human gate: required for positioning confirmation
|
||
|
||
Stage 4:
|
||
- Purpose: 韩愈基于确认立意输出初稿提纲。
|
||
- Actor: Han Yu
|
||
- Input: confirmed positioning, premise-context-pack.md, source digests, project brief
|
||
- Output: han-yu outline dispatch-pack.md, agent-invocation-packet.md, prompt-to-send.md when needed, outline-v1.md
|
||
- Human gate: required before outline review
|
||
|
||
Stage 5:
|
||
- Purpose: 构建提纲对齐上下文。
|
||
- Actor: Article Context Architect
|
||
- Input: source-map, current outline, confirmed positioning, selected materials, source digests
|
||
- Output: outline-aligned context pack, shared-outline-context-pack.md, updated invocation record
|
||
- Human gate: required before dispatch
|
||
|
||
Stage 6:
|
||
- Purpose: 准备评审员分发包。
|
||
- Actor: Runtime + Article Context Architect
|
||
- Input: shared context, reviewer roles, review goals
|
||
- Output: per-reviewer dispatch-pack.md, agent-invocation-packet.md, and prompt-to-send.md when needed
|
||
- Human gate: required before reviewer sessions
|
||
|
||
Stage 7:
|
||
- Purpose: 独立评审。
|
||
- Actor: Selected reviewers
|
||
- Input: review-brief, current outline, shared context, dispatch pack
|
||
- Output: session.md and report.md for each reviewer
|
||
- Human gate: optional during reviewer dialogue
|
||
|
||
Stage 8:
|
||
- Purpose: 综合评审。
|
||
- Actor: Runtime / Orchestrator
|
||
- Input: reviewer report.md files
|
||
- Output: synthesis.md
|
||
- Human gate: required for adoption decisions
|
||
|
||
Stage 9:
|
||
- Purpose: 生成主笔修复请求。
|
||
- Actor: Runtime / Orchestrator
|
||
- Input: synthesis and user decisions
|
||
- Output: repair-request.md
|
||
- Human gate: required before sending to Han Yu
|
||
|
||
Stage 10:
|
||
- Purpose: 主笔修复提纲。
|
||
- Actor: Han Yu
|
||
- Input: current outline and repair-request
|
||
- Output: han-yu dispatch-pack.md, han-yu agent-invocation-packet.md, prompt-to-send.md when needed, next outline version
|
||
- Human gate: required to continue, finalize, or pause
|
||
```
|
||
|
||
### 5.2 Main Workflow
|
||
|
||
```text
|
||
1. 用户指定 article project、观点素材位置或 source-map 和材料范围。
|
||
2. Runtime 为 Article Context Architect 生成 agent-invocation-packet.md；如果当前环境不能真正执行该 agent，则生成 prompt-to-send.md 并停止等待。
|
||
3. Article Context Architect 压缩拆分观点素材，生成 source digests 和 premise-context-pack.md。
|
||
4. Runtime 为韩愈生成 positioning dispatch-pack.md、agent-invocation-packet.md 和必要时的 prompt-to-send.md。
|
||
5. 韩愈输出立意和切入 proposal，保存 session.md 和 report.md。
|
||
6. 用户审核并确认、修改或驳回立意。
|
||
7. Runtime 基于确认立意为韩愈生成 outline dispatch-pack.md、agent-invocation-packet.md 和必要时的 prompt-to-send.md。
|
||
8. 韩愈输出 outline-v1.md。
|
||
9. Runtime 创建或确认 02-outline/review-rounds/round-XX/。
|
||
10. Runtime 草拟 review-brief.md。
|
||
11. Article Context Architect 基于确认立意和 outline-v1.md 生成 outline-aligned context pack。
|
||
12. Runtime 生成各评审员 dispatch-pack.md 和 agent-invocation-packet.md。
|
||
13. 如果任一 participant 在外部平台运行，Runtime 生成对应的 prompt-to-send.md。
|
||
14. 用户确认上下文包可分发。
|
||
15. 各评审员在独立会话中评审，保存 session.md 和 report.md。
|
||
16. Runtime 汇总 report.md，生成 synthesis.md。
|
||
17. 用户对评审意见做采纳决策。
|
||
18. Runtime 根据用户决策生成 repair-request.md。
|
||
19. Runtime 为韩愈生成 repair dispatch-pack.md、agent-invocation-packet.md 和必要时的 prompt-to-send.md。
|
||
20. 韩愈根据 repair-request 修复提纲，输出下一版 outline。
|
||
21. 用户决定进入下一轮、确认 outline-final 或暂停。
|
||
```
|
||
|
||
### 5.3 Branch Logic
|
||
|
||
- 如果用户只指定部分评审员，只创建对应目录。
|
||
- 如果用户补充新素材，必须先判断补充素材影响范围：立意、提纲、评审、修复、正文。然后增量更新 source digest 和相关 context pack，再继续当前阶段。
|
||
- 如果材料不足，停在 Stage 2 请求补充。
|
||
- 如果当前环境不能真正执行 Article Context Architect，则只生成其 prompt-to-send.md，不得模拟完成 source digest 或 outline-aligned context pack。
|
||
- 如果当前环境不能真正执行韩愈，则只生成韩愈 prompt-to-send.md，不得模拟立意、提纲或修复结果。
|
||
- 如果某个评审员需要多轮交流，继续写入该评审员 `session.md`，但 `report.md` 只保存本轮最终意见。
|
||
- 如果当前环境不能真正执行某个评审员，则只生成该评审员 prompt-to-send.md，不得模拟正式 report.md。
|
||
- 如果评审意见互相冲突，synthesis 不消除冲突，而是列为用户决策项。
|
||
- 如果提纲修复后变动较小，下一轮可复用上一轮 source digest，只更新 outline-aligned pack。
|
||
- 如果提纲修复后结构大改，重新生成 outline-aligned pack。
|
||
- 如果当前环境不能真正执行韩愈，则只生成韩愈 prompt-to-send.md，不得模拟下一版 outline。
|
||
|
||
### 5.4 Loop Rules
|
||
|
||
每轮评审递增：
|
||
|
||
```text
|
||
round-01
|
||
round-02
|
||
round-03
|
||
```
|
||
|
||
循环只在用户确认后继续。默认最大轮数不硬编码，由用户根据提纲质量决定。
|
||
|
||
### 5.5 Stop Conditions
|
||
|
||
- 用户确认 `outline-final.md`。
|
||
- 用户暂停项目。
|
||
- 材料或立意不足以继续。
|
||
- 上下文包无法在当前工具/平台限制下可靠构建，需要改用更大上下文平台或分批压缩。
|
||
- 任何必须由 canonical agent 完成的环节无法被真实调用，且尚未生成可投递的 prompt-to-send.md。
|
||
|
||
### 5.6 Escalation Conditions
|
||
|
||
- 评审员对文章立意提出根本性否定。
|
||
- 当前提纲与 creative brief 冲突。
|
||
- source-map 中关键材料不可读。
|
||
- 用户指定材料和评审员实际所需上下文严重不匹配。
|
||
- Runtime 需要修改 writing-workbench 模板或项目结构。
|
||
|
||
## 6. State Layer
|
||
|
||
### 6.1 Working State
|
||
|
||
- current_outline_version
|
||
- current_positioning_version
|
||
- current_review_round
|
||
- material_digest_version
|
||
- selected_reviewers
|
||
- material_scope
|
||
- context_pack_status
|
||
- reviewer_report_status
|
||
- user_adoption_decisions
|
||
- next_action
|
||
|
||
### 6.2 Persistent State
|
||
|
||
保存在 writing-workbench article project 内：
|
||
|
||
```text
|
||
project.md
|
||
source-map.md
|
||
status.md
|
||
context/context-manifest.md
|
||
context/source-digests/
|
||
context/premise/
|
||
context/outline-aligned/
|
||
01-positioning/
|
||
02-outline/outlines/
|
||
02-outline/main-writer-sessions/
|
||
02-outline/review-rounds/
|
||
```
|
||
|
||
### 6.3 Decision Log
|
||
|
||
每轮至少记录：
|
||
|
||
- 为什么启动本轮评审。
|
||
- 哪些观点素材进入了立意前压缩。
|
||
- 韩愈立意是否由用户确认。
|
||
- 哪个提纲版本来自韩愈真实调用。
|
||
- 本轮评审员是谁。
|
||
- 使用了哪些材料。
|
||
- 上下文包是否被用户确认。
|
||
- 哪些意见被采纳、拒绝、保留、延后。
|
||
- 是否进入下一轮或终稿确认。
|
||
|
||
### 6.4 Artifact Log
|
||
|
||
典型轮次文件：
|
||
|
||
```text
|
||
02-outline/review-rounds/round-01/
|
||
review-brief.md
|
||
shared-outline-context-pack.md
|
||
article-context-architect/
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
zhang-liao/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
cognitive-imaging/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
giant-cognition/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
han-yu/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
synthesis.md
|
||
repair-request.md
|
||
```
|
||
|
||
观点到提纲标准入口的典型文件：
|
||
|
||
```text
|
||
context/
|
||
context-manifest.md
|
||
source-digests/
|
||
premise/
|
||
premise-context-pack.md
|
||
|
||
01-positioning/
|
||
han-yu/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
positioning-final.md
|
||
|
||
02-outline/
|
||
main-writer-sessions/
|
||
han-yu/
|
||
outline-generation/
|
||
dispatch-pack.md
|
||
agent-invocation-packet.md
|
||
prompt-to-send.md
|
||
session.md
|
||
report.md
|
||
outlines/
|
||
outline-v1.md
|
||
```
|
||
|
||
### 6.5 Resume Rules
|
||
|
||
恢复 Runtime 时按顺序读取：
|
||
|
||
```text
|
||
1. project.md
|
||
2. status.md
|
||
3. source-map.md
|
||
4. context/context-manifest.md
|
||
5. current outline file
|
||
6. current round review-brief.md
|
||
7. existing report.md files
|
||
```
|
||
|
||
如果这些文件和聊天上下文冲突，以文件为准，再请求用户确认。
|
||
|
||
## 7. Collaboration Layer
|
||
|
||
### 7.0 Session Topology
|
||
|
||
The runtime should use file-based coordination instead of a single all-purpose chat window.
|
||
|
||
```text
|
||
Main Session:
|
||
owner: Runtime Operator / Article Production Orchestrator
|
||
purpose: project control, file routing, decision gates, status updates, synthesis, repair-request drafting
|
||
reads: project.md, source-map.md, status.md, context manifest, report.md files
|
||
writes: runtime-entry.md, review-brief.md, synthesis.md, repair-request.md, status recommendations
|
||
must_not: simulate canonical agent outputs
|
||
|
||
Context Subsession:
|
||
owner: Article Context Architect
|
||
purpose: source digest, premise-context-pack, outline-generation context, outline-aligned context, supplemental material refresh
|
||
persistence: may continue across stages while material architecture remains stable
|
||
restart_condition: context window pressure, hallucination signs, large new source batch, major change in article direction
|
||
|
||
Main Writer Subsession:
|
||
owner: Han Yu
|
||
purpose: positioning, outline generation, outline repair
|
||
persistence: should normally stay continuous through positioning and outline rounds
|
||
restart_condition: user requests restart, context drift, hallucination signs, major style/role reset needed
|
||
|
||
Reviewer Subsessions:
|
||
Zhang Liao:
|
||
persistence: should usually stay continuous across rounds because follow-up dialogue often affects repair direction
|
||
report_policy: report.md plus session.md; dialogue after report may become supplemental review material
|
||
|
||
Cognitive Imaging:
|
||
persistence: may stay continuous across rounds, but default use is report-only unless user continues dialogue
|
||
report_policy: report.md is the formal input to synthesis
|
||
|
||
Giant Cognition:
|
||
persistence: may stay continuous across rounds, but default use is report-only unless user continues dialogue
|
||
report_policy: report.md is the formal input to synthesis
|
||
```
|
||
|
||
CCPE artifacts are not chat sessions:
|
||
|
||
```text
|
||
article-outline-development.runtime.md = operating protocol for the main session.
|
||
article-context-architect.agent.md = canonical spec for the context subsession.
|
||
agent-invocation-packet.protocol.md = launch and handoff protocol for all participant sessions.
|
||
article-outline-development-runtime-creation-brief.md = design rationale and acceptance criteria.
|
||
```
|
||
|
||
When context is large, keep the main session thin. It should read structured reports and manifests, not all raw source material or full participant transcripts.
|
||
|
||
### 7.1 Handoff Protocol
|
||
|
||
每次 handoff 必须包含：
|
||
|
||
- 当前提纲版本。
|
||
- 本轮目标。
|
||
- 必要上下文包。
|
||
- 输出文件路径。
|
||
- 不允许越界处理的事项。
|
||
|
||
### 7.1.1 Universal Agent Invocation Protocol
|
||
|
||
每个被调用角色目录必须有 `agent-invocation-packet.md` 或等价 `invocation-record.md`。它用于区分“给 orchestrator 看的任务索引”和“真正启动 canonical CCPE agent 的完整包”。
|
||
|
||
Detailed standalone protocol:
|
||
|
||
```text
|
||
workbench/upgraded/agent-invocation-packet.protocol.md
|
||
```
|
||
|
||
```md
|
||
# Agent Invocation Packet: {participant_id}
|
||
|
||
## 1. Invocation Identity
|
||
|
||
- project_id:
|
||
- review_round:
|
||
- participant_id:
|
||
- target_agent_name:
|
||
- canonical_agent_artifact_path:
|
||
- canonical_agent_artifact_type: lite_prompt | agent_spec | native_agent
|
||
- canonical_agent_version:
|
||
- invocation_mode: full_prompt_paste | prompt_path_reference | native_agent_id
|
||
- packet_type: orchestrator_index | agent_startup_packet
|
||
|
||
## 2. Canonical Artifact Handling
|
||
|
||
- prompt_source:
|
||
- should_paste_full_prompt: yes/no
|
||
- prompt_to_send_path:
|
||
- role_integrity_requirement:
|
||
|
||
## 3. This Round's Task
|
||
|
||
## 4. Input Files
|
||
|
||
## 5. Context Files
|
||
|
||
## 6. Output Contract
|
||
|
||
## 7. Continuity Policy
|
||
|
||
## 8. Session Logging
|
||
|
||
## 9. Forbidden Actions
|
||
```
|
||
|
||
Default canonical artifact paths for v0:
|
||
|
||
```text
|
||
article-context-architect: workbench/upgraded/article-context-architect.agent.md
|
||
han-yu-main-writer: agents/lite/han-yu.prompt.md
|
||
zhang-liao: agents/lite/zhang-liao.prompt.md
|
||
cognitive-imaging: agents/lite/cognitive-imaging-practitioner.prompt.md
|
||
giant-cognition: agents/lite/giant-cognition.prompt.md
|
||
```
|
||
|
||
Invocation modes:
|
||
|
||
```text
|
||
full_prompt_paste:
|
||
Use when the participant runs in an external platform that cannot read local CCPE files.
|
||
Runtime must generate prompt-to-send.md containing the canonical prompt/spec, this round's task, context pack, and output contract.
|
||
|
||
prompt_path_reference:
|
||
Use when the executing agent can read local files and can load the canonical prompt/spec by path.
|
||
Runtime may reference the prompt path but must still provide task, input files, output contract, and continuity policy.
|
||
|
||
native_agent_id:
|
||
Use only when a platform has a registered agent with the same canonical role and version.
|
||
Runtime must still provide task, context, output contract, and session logging requirements.
|
||
```
|
||
|
||
### 7.1.2 No Simulation Rule
|
||
|
||
Runtime operator 可以调度、整理文件、生成任务包、综合真实 `report.md`，但不得冒充任一 canonical agent 产出正式结果。
|
||
|
||
```text
|
||
Must not simulate:
|
||
- Article Context Architect 的正式 source digest / outline-aligned context pack
|
||
- Han Yu 的下一版提纲
|
||
- Zhang Liao 的评审报告
|
||
- Cognitive Imaging 的评审报告
|
||
- Giant Cognition 的评审报告
|
||
```
|
||
|
||
如果当前环境不能真实调用某个 participant，Runtime 必须：
|
||
|
||
```text
|
||
1. 生成 agent-invocation-packet.md。
|
||
2. 生成 prompt-to-send.md。
|
||
3. 在 status.md 或 synthesis.md 中标记 blocked_waiting_for_external_agent_output。
|
||
4. 停止在该 participant 的正式输出之前。
|
||
```
|
||
|
||
任何未真实调用 canonical agent 的输出必须标记：
|
||
|
||
```text
|
||
simulation-only
|
||
excluded-from-synthesis
|
||
not-a-formal-report
|
||
```
|
||
|
||
### 7.2 Role Differentiation
|
||
|
||
- 韩愈负责写作与提纲修复。
|
||
- Article Context Architect 负责上下文准备。
|
||
- 张辽负责红队风险和建设性追问。
|
||
- 认知显影负责概念显影和认知结构问题。
|
||
- 巨人认知负责尺度、结构和宏观认知跨度。
|
||
- 用户负责最终裁决。
|
||
|
||
### 7.3 Conflict Resolution
|
||
|
||
Runtime 不强行统一评审意见。它将冲突分为：
|
||
|
||
```text
|
||
- direct contradiction
|
||
- different priority
|
||
- different risk tolerance
|
||
- different article ideal
|
||
- context insufficiency
|
||
```
|
||
|
||
然后交给用户决定。
|
||
|
||
### 7.4 Synthesis Rules
|
||
|
||
`synthesis.md` 应包含：
|
||
|
||
- 共识问题。
|
||
- 单一评审员强烈问题。
|
||
- 互相冲突的问题。
|
||
- 对文章立意的影响。
|
||
- 对提纲结构的影响。
|
||
- 需要韩愈修复的事项。
|
||
- 需要用户裁决的事项。
|
||
|
||
## 8. Output Layer
|
||
|
||
### 8.1 Runtime Outputs
|
||
|
||
- review-brief.md
|
||
- premise-context-pack.md
|
||
- han-yu positioning dispatch-pack.md
|
||
- han-yu positioning agent-invocation-packet.md
|
||
- han-yu positioning prompt-to-send.md when invocation_mode = full_prompt_paste
|
||
- positioning-final.md
|
||
- han-yu outline dispatch-pack.md
|
||
- han-yu outline agent-invocation-packet.md
|
||
- han-yu outline prompt-to-send.md when invocation_mode = full_prompt_paste
|
||
- outline-v1.md
|
||
- shared-outline-context-pack.md
|
||
- article-context-architect agent-invocation-packet.md
|
||
- article-context-architect prompt-to-send.md when invocation_mode = full_prompt_paste
|
||
- per-reviewer dispatch-pack.md
|
||
- per-reviewer agent-invocation-packet.md
|
||
- per-reviewer prompt-to-send.md when invocation_mode = full_prompt_paste
|
||
- per-reviewer session.md
|
||
- per-reviewer report.md
|
||
- synthesis.md
|
||
- repair-request.md
|
||
- han-yu dispatch-pack.md for outline repair
|
||
- han-yu agent-invocation-packet.md
|
||
- han-yu prompt-to-send.md when invocation_mode = full_prompt_paste
|
||
- next outline version or outline-final recommendation
|
||
|
||
### 8.2 Intermediate Outputs
|
||
|
||
- context-manifest.md
|
||
- source digest files
|
||
- outline-aligned context pack
|
||
- context quality check
|
||
- adoption decision notes
|
||
|
||
### 8.3 Output Format
|
||
|
||
```md
|
||
# Article Outline Review Round Report
|
||
|
||
## 1. Run Summary
|
||
|
||
## 2. Input Files
|
||
|
||
## 3. Reviewers
|
||
|
||
## 4. Context Packs
|
||
|
||
## 5. Reviewer Findings
|
||
|
||
## 6. Synthesis
|
||
|
||
## 7. User Decisions
|
||
|
||
## 8. Repair Request
|
||
|
||
## 9. Next Action
|
||
|
||
## 10. Archive Notes
|
||
```
|
||
|
||
### 8.4 Archival Rules
|
||
|
||
- `session.md` 保存讨论过程，不作为默认综合输入。
|
||
- `report.md` 保存评审员最终可读结论，是综合输入。
|
||
- 每轮文件不覆盖，新增 round。
|
||
- `outline-final.md` 只在用户确认后生成或更新。
|
||
|
||
## 9. Evaluation Layer
|
||
|
||
### 9.1 Validation Checklist
|
||
|
||
```text
|
||
Objective fulfilled?
|
||
Runtime starts from existing draft outline?
|
||
Runtime can also start from viewpoint materials?
|
||
Viewpoint materials compressed before Han Yu positioning?
|
||
Supplemental materials trigger incremental context refresh?
|
||
Runtime operator did not simulate canonical agents?
|
||
Each invoked participant has invocation packet or invocation record?
|
||
External participants have prompt-to-send.md?
|
||
Review round directory clear?
|
||
Context pack generated?
|
||
Context size controlled?
|
||
Reader-visible and internal sources separated?
|
||
Reviewer sessions isolated?
|
||
Reports collected?
|
||
Synthesis preserves disagreement?
|
||
Human gates respected?
|
||
Repair request actionable for Han Yu?
|
||
Next action clear?
|
||
```
|
||
|
||
### 9.2 Quality Rubric
|
||
|
||
- Context Fitness: 上下文足够支撑评审。
|
||
- Context Economy: 没有不必要地塞入全文。
|
||
- Role Separation: 主笔、上下文助手、评审员、用户职责清楚。
|
||
- Traceability: 评审意见可以追溯到提纲、上下文和 report。
|
||
- Human-in-the-loop: 决策门真实存在，不被自动化吞掉。
|
||
- Iteration Clarity: 下一轮如何继续明确。
|
||
|
||
### 9.3 Failure Modes
|
||
|
||
- 只传提纲不传材料，导致评审浅表化。
|
||
- 上下文包过大，回到单智能体大 prompt 模式。
|
||
- 上下文包过度摘要，评审无法看到关键支撑。
|
||
- 评审员会话混在一起，无法复盘。
|
||
- synthesis 抹平冲突，导致用户看不到真正分歧。
|
||
- repair-request 太抽象，韩愈无法执行。
|
||
|
||
### 9.4 Recovery Rules
|
||
|
||
- 上下文不足：回到 Stage 2 补 source digest 或 outline alignment。
|
||
- 评审报告不可用：要求对应评审员重写 report.md，不重跑其他评审。
|
||
- synthesis 不可用：重做 synthesis，不修改原始 report。
|
||
- repair-request 不可用：基于用户采纳决策重写 repair-request。
|
||
- 轮次混乱：以 `status.md` 和 round 目录为准恢复。
|
||
|
||
## 10. Runtime Environment
|
||
|
||
### 10.1 Platform
|
||
|
||
Codex 为首选运行环境。其他平台通过 Markdown 文件手工或半自动交接。
|
||
|
||
### 10.2 File Access
|
||
|
||
允许读取：
|
||
|
||
```text
|
||
- 当前 writing-workbench article project
|
||
- source-map 指向且用户确认的材料
|
||
- CCPE System 中相关 Agent / Runtime 草案
|
||
```
|
||
|
||
允许写入：
|
||
|
||
```text
|
||
- 当前 writing-workbench article project 内的本轮输出文件
|
||
```
|
||
|
||
### 10.3 Tool Access
|
||
|
||
文件读写工具即可。v0 不需要外部网络检索。
|
||
|
||
### 10.4 Network Access
|
||
|
||
默认不需要。若评审员在外部平台运行，由用户或调度者手工复制 dispatch pack 和 report。
|
||
|
||
### 10.5 Logging
|
||
|
||
所有关键步骤写入 `status.md` 或本轮 `synthesis.md` 的 Archive Notes。
|
||
|
||
### 10.6 Versioning
|
||
|
||
- Runtime 草案版本由 CCPE System 管理。
|
||
- 文章项目内轮次版本由 `round-XX` 和 `outline-vX.md` 管理。
|
||
|
||
## 11. Automation Boundary
|
||
|
||
### 11.1 Allowed Automation
|
||
|
||
```text
|
||
- 创建本轮目录草案。
|
||
- 生成上下文包草案。
|
||
- 生成 dispatch pack 草案。
|
||
- 汇总 report.md 中明确内容。
|
||
- 生成 repair-request 草案。
|
||
```
|
||
|
||
### 11.2 Requires Confirmation
|
||
|
||
```text
|
||
- 分发给评审员。
|
||
- 覆盖已有文件。
|
||
- 改变材料范围。
|
||
- 确认采纳意见。
|
||
- 确认 outline-final。
|
||
- 修改 writing-workbench 模板。
|
||
```
|
||
|
||
### 11.3 Forbidden Automation
|
||
|
||
```text
|
||
- 删除材料。
|
||
- 自动发布。
|
||
- 自动进入正文写作阶段。
|
||
- 自动替用户做立意裁决。
|
||
- 自动把内部材料变成公开引用。
|
||
```
|
||
|
||
## 12. Deployment Notes
|
||
|
||
### 12.1 Codex
|
||
|
||
Codex 可以作为 Runtime operator：读取项目文件、生成上下文包、创建轮次文件、综合 report，并向用户请求决策。
|
||
|
||
### 12.2 Claude Code
|
||
|
||
Claude Code 可按相同文件协议运行，但需明确工作目录和可写路径。
|
||
|
||
### 12.3 OpenClaw
|
||
|
||
OpenClaw 可将该 Runtime 拆为多 Agent 任务队列，但仍需保留用户决策门。
|
||
|
||
### 12.4 Manual Operation
|
||
|
||
用户可手工使用：
|
||
|
||
1. 创建 round 目录。
|
||
2. 准备 shared context 和 dispatch pack。
|
||
3. 分别发给评审员。
|
||
4. 将评审过程保存为 session.md。
|
||
5. 将最终意见保存为 report.md。
|
||
6. 汇总 synthesis。
|
||
7. 写 repair-request 给韩愈。
|
||
|
||
## 13. Version Notes
|
||
|
||
```text
|
||
v0.1:
|
||
- Initial draft.
|
||
- Runtime begins from an existing draft outline.
|
||
- Scope limited to outline review loop before drafting.
|
||
```
|