knowledge-vault/skills/knowledge-processing/viewpoint-discussion-distillation/ccpe-sync-request-2026-06-06-whole-source-gestalt.md

# CCPE Sync Request: Whole-Source Gestalt Alignment

## 1. Background

Knowledge Vault discovered a structural weakness in the current `viewpoint-discussion-distillation` flow.

The previous flow was too `chunk-first / worker-first`:

```text
source registration -> segmentation -> worker topic extraction -> synthesis -> routing
```

This works for loose, very long, multi-topic material, but it is risky for coherent discussion drafts under the high-context limit. Range workers see local evidence and can lose the global shape. The failure mode is that tools, layers, cases, action tracks, and model-upgrade relations get flattened into peer topics.

## 2. Required Runtime Change

Upgrade the Runtime to a 9-step operational flow by adding Step 0. Step 0 should be treated as a human-confirmed alignment loop, not as a one-shot summary:

```text
0. Whole-Source Gestalt Alignment
1. Segmentation
2. Worker Topic Extraction
3. Topic Graph Synthesis
4. Human Structure Confirmation
5. Material Routing
6. Topic Docs / Material Extraction
7. Coverage / Distortion Audit
8. Downstream Task Routing
```

Knowledge Vault still needs source registration before this operational flow so it can create the workspace, source map, run notes, and invocation records. If CCPE keeps source registration inside the canonical Runtime, the practical order should be:

```text
registration -> Step 0 whole-source gestalt -> segmentation -> worker passes
```

## 3. New Participant Needed

Add a canonical participant:

```text
participant_id: whole-source-gestalt-reviewer
participant_type: high_context_participant
runtime: viewpoint-discussion-distillation
invocation_mode: real sub-session only
main_session_may_simulate: false
```

The main session must not perform this pass itself. It prepares the invocation packet, records the returned output, and uses it as orientation for downstream segmentation and worker extraction.

The participant output must be inspected by the user before it becomes a binding worker lens. If the user corrects the global structure, the Runtime should support another Step 0 pass or an explicit human-correction record before segmentation.

## 4. Output Contract

The participant output should include:

```text
- participant identity and invocation metadata
- source document path and source version note
- coherence judgment: coherent / mixed / fragmented
- coherence rationale and split recommendation if mixed or fragmented
- recommended downstream mode: structure-first / macro-topic split / flat-discovery
- 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 / confirmed / needs revision / rejected
```

This output is not a final topic map, material routing log, or coverage audit. It is an upstream global orientation layer.

## 5. Worker Rule Change

Worker behavior depends on Step 0 coherence judgment.

For coherent sources, worker participants should no longer discover the global structure from zero. They should work under the confirmed global portrait.

They should:

```text
- receive the accepted gestalt summary in their thread-start packet
- extract local evidence, refinements, contradictions, and exceptions
- explicitly mark any challenge to the global portrait
- cite local source ranges for every challenge
```

For fragmented sources, worker participants should remain minimally biased and continue flat topic discovery. For mixed sources, the Runtime should split macro-topics before worker extraction.

## 6. Topic Docs / Material Extraction Confirmation

Add a second human confirmation gate after Topic Docs / Material Extraction:

```text
gate_id: topic_docs_human_confirmation
required_before:
  - coverage completion claims
  - downstream handoff
  - model mining
  - writing handoff
purpose:
  - confirm that extracted materials are useful enough for downstream automation
  - decide whether another extraction pass is needed
  - record user corrections before downstream work
```

For coherent sources where Step 0 is confirmed, this gate can replace the old topic-granularity pause. The user reviews the actual extracted content rather than only reviewing candidate topic labels.

## 7. Worker/Sub-Session Rule For Extraction

CCPE should make explicit that source analysis, splitting, routing, and material extraction should be performed by worker/sub-session participants when they require reading substantial source material.

Main session responsibilities:

```text
- create invocation packets
- preserve run notes and source maps
- collect returned outputs
- integrate indexes
- perform bounded verification
- record human confirmations
```

Worker/sub-session responsibilities:

```text
- full-source gestalt alignment
- source-range extraction
- topic-doc material extraction
- quote-level evidence pack generation
- local contradiction or distortion checks
```

## 8. Knowledge Vault Side Already Updated

Knowledge Vault updated these public capability files:

```text
skills/context-management-policy.md
skills/knowledge-processing/viewpoint-discussion-distillation/runbook.md
skills/knowledge-processing/viewpoint-discussion-distillation/context-strategy.md
skills/knowledge-processing/viewpoint-discussion-distillation/invocation-contract.md
skills/knowledge-processing/viewpoint-discussion-distillation/participant-registry.md
skills/knowledge-processing/viewpoint-discussion-distillation/ccpe-runtime-alignment.md
```

CCPE should synchronize the canonical Runtime, participant registry, and any agent/skill specs needed to make `whole-source-gestalt-reviewer` invocable as a real participant.