knowledge-vault/discussions/viewpoint-development/2026-06-12-复杂度放置门/invocations/whole-source-gestalt-reviewer/agent-invocation-packet.md

Agent Invocation Packet: whole-source-gestalt-reviewer

1. Invocation Identity

• project_id: knowledge-vault
• workflow: viewpoint-discussion-distillation
• stage: Step 0 whole-source gestalt alignment
• run_id: 2026-06-12-复杂度放置门
• participant_id: whole-source-gestalt-reviewer
• target_participant_name: Whole-Source Gestalt Reviewer
• participant_type: high_context_participant
• canonical_artifact_path: C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\whole-source-gestalt-reviewer.agent.md
• canonical_artifact_version: unknown_current
• invocation_mode: codex_thread_participant
• packet_type: formal_runtime_participant_invocation

2. Canonical Artifact Handling

• should_paste_full_prompt_or_spec: no; canonical artifact path is provided and the task contract is summarized in prompt-to-send
• prompt_to_send_path: C:\Users\wangq\Documents\Codex\knowledge-vault\discussions\viewpoint-development\2026-06-12-复杂度放置门\invocations\whole-source-gestalt-reviewer\prompt-to-send.md
• role_integrity_requirement: preserve Step 0 whole-source gestalt reviewer role
• allowed_wrapper_instructions: repository path, output path, boundary rule, user structural prior, forbidden actions, return contract
• forbidden_role_changes: do not become topic router, topic doc writer, segmentation worker, product designer, article writer, or implementation planner
• no_simulation_requirement: true

3. Invocation Carrier

• carrier_type: codex_thread_participant
• thread_id: 019eb88c-4bab-7b21-9ab1-f14e07db46a1
• agent_id:
• persistent_required: true
• resume_or_followup_method: send follow-up prompt to the same Codex child thread
• execution_status: returned_output_available_pending_human_confirmation
• strict_invocation_required: true
• simulation_only: false

Language policy status:

source_primary_language: zh-CN
output_language_policy: mirror_source_primary_language
human_confirmation_artifact: true
gate_id_if_applicable: Gate 0 / Step 0 human review
language_policy_status: pending
repair_required: unknown_until_return

Returned output status:

returned_output_path: C:\Users\wangq\Documents\Codex\knowledge-vault\discussions\viewpoint-development\2026-06-12-复杂度放置门\invocations\whole-source-gestalt-reviewer\returned-output.md
returned_output_available: true
human_confirmation_status: pending
accepted_as_worker_lens: false

4. Current Task

Read the full source document as a whole and return a Step 0 structural alignment report.

The report must help the user decide:

- whether the source is coherent, mixed, or fragmented
- whether the five rounds should be treated as one unified development arc or split into macro-topics
- how to interpret the relation between deep creative workflow and AI development methodology
- whether downstream mode should be structure-first, macro-topic split, or flat-discovery
- whether later topics should be organized as a tree, a flat list, or a mixed graph
- what worker lenses and distortion guardrails should be carried into segmentation and extraction

5. Input Files

C:\Users\wangq\Documents\Codex\knowledge-vault\diary\2026\2026-06\2026-06-12.md

6. Context Files

C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation\README.md
C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation\runbook.md
C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation\context-strategy.md
C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation\invocation-contract.md
C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation\participant-registry.md
C:\Users\wangq\Documents\Codex\knowledge-vault\discussions\viewpoint-development\2026-06-12-复杂度放置门\00-source-map.md

7. Embedded Inputs

Round boundary rule:

Use only numeric Markdown H1 headings matching ^#\s+\d+\s*$ as discussion round boundaries.
Ignore non-numeric H1 headings inside a numeric round.
Inside each numeric round, ## GPT marks the start of the GPT response.

Source size:

196795 bytes, 5079 lines, 5 numeric H1 rounds.

User structural prior:

深度创作流程就是我在践行我的 AI 开发方法论。

8. Output Contract

Write the returned output to:

C:\Users\wangq\Documents\Codex\knowledge-vault\discussions\viewpoint-development\2026-06-12-复杂度放置门\invocations\whole-source-gestalt-reviewer\returned-output.md

The output must include:

- participant identity and invocation metadata
- source document path and source version note
- source primary language and output language policy
- coherence judgment: coherent / mixed / fragmented
- judgment on unified-main-axis versus macro-topic split
- explicit treatment of the user's structural prior
- recommended downstream mode: structure-first / macro-topic split / flat-discovery
- recommendation on topic organization: tree / flat / mixed graph, with rationale
- global topic portrait
- main structure or candidate layers
- core tensions and governing questions
- model-evolution line
- parent/child/tool/case/action-layer distinctions
- chunk-first distortion risks
- segmentation guidance for downstream workers
- worker lens recommendation: required / partial / omitted
- confidence notes and unresolved structure questions
- human confirmation status: pending

9. Continuity Policy

The same child thread must be used for user corrections or follow-up alignment before the Step 0 output becomes a worker lens.

10. Session Logging

The main session will record:

- child thread id
- send status
- return status
- returned-output path
- follow-up correction prompts, if any

11. Forbidden Actions

The participant must not:

- modify the source file
- create final 01-topic-map.md
- create 02-material-routing-log.md
- write topic documents
- perform evidence routing
- perform material-unit extraction
- claim coverage audit completion
- create writing-workbench handoff
- treat the Step 0 report as final topic authority

12. Runtime Acceptance Rule

This output is accepted only if it is produced by the recorded Codex child thread or another real persistent participant and saved to the return path with participant metadata.

Human confirmation is required before downstream segmentation or worker extraction.