5.1 KiB
Prompt To Send: whole-source-gestalt-reviewer
You are the whole-source-gestalt-reviewer participant for a Knowledge Vault viewpoint-discussion-distillation run.
This is a formal Step 0 participant invocation. Do not simulate another agent. Do not write as the main session.
Canonical Role
Canonical artifact:
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\whole-source-gestalt-reviewer.agent.md
If readable, use it as the binding role specification. If not readable, follow the contract below and explicitly record the artifact access limitation in the returned output.
Source
Read this full source document:
C:\Users\wangq\Documents\Codex\knowledge-vault\diary\2026\2026-06\2026-06-12.md
Source metadata:
source_type: five-round ChatGPT discussion draft
source_size_bytes: 196795
source_line_count: 5079
source_sha256: 1ECF344824AF1D5DA3F1AB19C092460D41F6726D764ABD0345D7CF8AB66E53F3
source_version_note: file last modified 2026-06-12 04:59:16 local time
source_primary_language: zh-CN
output_language_policy: mirror_source_primary_language
Boundary Rule
Use only numeric Markdown H1 headings matching ^#\s+\d+\s*$ as discussion round boundaries.
Inside each numeric round:
# N -> before ## GPT: user input / source material for round N
## GPT -> before next numeric # N+1: GPT response for round N
Ignore non-numeric H1 headings as round boundaries. They are intra-round content. Known intra-round H1 headings include:
# 评审环节改造：信息材料抽取初稿
# 素材提炼改造：信息材料抽取初稿
# 降维输出的工作流
# **HiFi Agent Studio**
Registered round ranges:
| range_id | start_line | gpt_start_line | end_line |
|---|---|---|---|
| R01 | 1 | 843 | 1020 |
| R02 | 1021 | 1192 | 1909 |
| R03 | 1910 | 1962 | 2638 |
| R04 | 2639 | 2904 | 4013 |
| R05 | 4014 | 4027 | 5079 |
User Structural Prior
The user supplied this interpretation before Step 0:
深度创作流程就是我在践行我的 AI 开发方法论。
Do not prematurely split the source into two peer macro-topics named "deep creative workflow" and "AI development methodology." First test the unified hypothesis:
The deep creative workflow is a practical enactment / lived case / operating sample of the user's AI development methodology.
You may still recommend a macro split if the source evidence requires it, but you must explicitly explain why the unified hypothesis is insufficient.
Task
Read the full source as a whole and produce a Step 0 gestalt alignment report before any segmentation, topic routing, topic docs, material extraction, or downstream handoff.
The report should help the user decide:
- whether the source is coherent, mixed, or fragmented
- whether the five rounds should stay under one unified main axis or split into macro-topics
- how deep creative workflow relates to AI development methodology
- whether downstream mode should be structure-first, macro-topic split, or flat-discovery
- whether later topic organization should be tree-shaped, flat, or a mixed graph
- what worker lens and distortion guardrails should be carried into downstream segmentation and extraction
Required Output File
Write your returned output to:
C:\Users\wangq\Documents\Codex\knowledge-vault\discussions\viewpoint-development\2026-06-12-复杂度放置门\invocations\whole-source-gestalt-reviewer\returned-output.md
Required Output Structure
Your returned-output.md must include:
1. Participant identity and invocation metadata
2. Source document path and source version note
3. Source primary language and output language policy
4. Coherence judgment: coherent / mixed / fragmented
5. Unified-main-axis versus macro-topic split judgment
6. Treatment of the user's structural prior
7. Recommended downstream mode: structure-first / macro-topic split / flat-discovery
8. Topic organization recommendation: tree / flat / mixed graph
9. Global topic portrait
10. Main structure or candidate layers
11. Core tensions and governing questions
12. Model-evolution line
13. Parent / child / tool / case / action-layer distinctions
14. Chunk-first distortion risks
15. Segmentation guidance for downstream workers
16. Worker lens recommendation: required / partial / omitted
17. Confidence notes and unresolved structure questions
18. Human confirmation status: pending
Write the explanatory content primarily in Chinese. Technical identifiers, file paths, and protocol field names may remain English.
Forbidden Actions
Do not:
- modify the source
- create or finalize 01-topic-map.md
- create 02-material-routing-log.md
- write topic documents
- perform evidence routing
- extract material units
- claim coverage audit completion
- create writing-workbench handoff
- treat this Step 0 report as final topic authority
Return Message
After writing the file, reply briefly with:
- output path
- coherence judgment
- unified-main-axis versus macro-topic split recommendation
- recommended downstream mode
- topic organization recommendation
- unresolved questions requiring user confirmation