# Capability Spec: Viewpoint Discussion Distillation

## 1. Purpose

Convert a long viewpoint discussion into a durable Knowledge Vault material package without losing source traceability.

## 2. Inputs

```text
- source document path
- source type
- source primary language
- known boundary rule
- intended use
- output workspace path
- optional seed topics
- optional forbidden merges
- optional downstream intent
```

## 3. Outputs

```text
- README.md
- 00-source-map.md
- 01-topic-map.md
- 02-material-routing-log.md
- 03-run-notes.md
- topics/
- audits/
- model-mining/
- handoff/
- invocations/
```

## 4. Operating Principle

First preserve, then structure.

The source material layer must remain separate from the structured viewpoint layer. Topic documents may reorganize ideas, but must keep source block ids and enough original material to support later reuse.

For discussion sources that fit a high-context participant, first get a whole-source gestalt alignment before segmentation. The global portrait prevents chunk-first workers from flattening tools, layers, cases, action tracks, and model upgrades into false peer topics.

Step 0 determines downstream mode:

```text
coherent -> structure-first mode with biased workers
mixed -> macro-topic split mode
fragmented -> flat-topic discovery mode with minimally biased workers
```

The Step 0 output must be checked by the user. It may repeat multiple times under human correction before it becomes the structure lens for workers.

Human confirmation artifacts must primarily use the source primary language unless the user explicitly requests another language.

## 5. Human Gates

```text
Setup checks: workspace path, source block convention, source-primary language, and invocation carrier.

Gate 1: Confirm Step 0 gestalt alignment, macro-topic split, or recorded exception.
Gate 2: Confirm candidate topic-map / topic hierarchy before topic expansion.
Gate 3: Confirm topic docs / extracted material usefulness before downstream handoff, source-disposable claims, or repair decisions.
Gate 4: Confirm downstream routing only when the downstream target, scope, or receiving workbench is not already covered by prior user instruction.
```

Do not add a human gate merely to ask whether the workflow may enter the next mechanical stage. A human gate is required only when the user must answer substantive questions: hierarchy, scope, downstream boundary, usefulness, repair strategy, source-disposable status, or handoff target.

After Gate 2 confirms the topic hierarchy and expansion boundary, material routing may proceed as the mechanical implementation of that confirmed structure. Create `02-material-routing-log.md` without a separate "start material routing?" prompt unless new unresolved decisions appear.

## 6. Acceptance Criteria

```text
- every source block has a routing status
- every formal participant output has a valid record
- no topic document relies only on summary
- low-confidence routing remains visible
- source-disposable claims are blocked until coverage audit
- downstream work is optional and user-confirmed
```