knowledge-vault/skills/knowledge-processing/viewpoint-discussion-distil.../runbook.md

117 lines
4.1 KiB
Markdown

# Runbook: Viewpoint Discussion Distillation
## 1. Before Creating A Work Directory
```text
1. Read Knowledge Vault README and VAULT rules.
2. Read this capability folder.
3. Read CCPE runtime handoff and invocation protocol.
4. Confirm target work directory with the user.
5. Confirm whether the source is likely under the high-context whole-source limit.
6. Confirm whether the first pass stops after source registration or proceeds to whole-source gestalt.
```
## 2. First Pass: Source Registration
```text
1. Create the confirmed work directory.
2. Create required subdirectories.
3. Write README.md.
4. Write 00-source-map.md with source metadata and round boundaries.
5. Write 03-run-notes.md with decisions and gates.
6. Create invocation records for the whole-source gestalt reviewer when applicable.
7. Stop at the agreed confirmation point.
```
## 3. Step 0: Whole-Source Gestalt Pass
Use this pass before segmentation when the source is one coherent discussion and can fit inside a high-context participant.
```text
1. Prepare a whole-source-gestalt-reviewer invocation packet.
2. Invoke a real high-context participant in a sub-session; the main session must not perform this pass itself.
3. The participant reads the full source and first judges topic coherence.
4. If the source is coherent, output a global topic portrait, main structure, core tensions, model-evolution line, and hierarchy risks.
5. If the source is not coherent, output a split recommendation before any topic extraction.
6. Save returned-output.md with source metadata and participant metadata.
7. Write or update 03-run-notes.md with the accepted gestalt output path.
8. Stop if no real participant output is available.
```
Acceptance condition:
```text
Segmentation and worker topic extraction may proceed only after the run has either:
- an accepted whole-source gestalt output; or
- a recorded exception explaining why the source cannot or should not receive a whole-source pass.
```
## 4. Segmentation Pass
```text
1. Create worker thread-start packets by source range.
2. Include the accepted whole-source gestalt summary and hierarchy cautions in each worker packet.
3. Execute or dispatch conversation-segmentation.
4. Write skill-execution-record.md for local execution.
5. Collect source block indexes and worker return packets.
6. Create a continuation handoff before topic discovery.
```
## 5. Topic Discovery Pass
```text
1. Prepare topic-discovery-router invocation packet.
2. Provide the whole-source gestalt output as binding context, not as a final topic map.
3. Instruct workers to supplement and challenge the global portrait with local evidence, not rediscover the whole structure from zero.
4. Prepare prompt-to-send.md if the participant is external.
5. Stop if real invocation is unavailable.
6. Save returned output with metadata.
7. Draft 01-topic-map.md from accepted returned output.
8. Pause for user confirmation.
```
## 6. Topic Graph Synthesis And Human Confirmation
```text
1. Convert flat topic candidates into a topic hierarchy or graph.
2. Preserve distinctions among parent topic, subtopic, tool, layer, case, action track, and model upgrade.
3. Compare the synthesized hierarchy against the whole-source gestalt output.
4. Record unresolved hierarchy risks before routing.
5. Pause for user confirmation before material routing.
```
## 7. Routing And Topic Docs
```text
1. Confirm topic-map.
2. Execute evidence-routing-and-topic-doc-builder by range or topic group.
3. Write 02-material-routing-log.md.
4. Generate topic docs with source material layer and source index.
5. Do not declare completion until coverage audit is accepted.
```
## 8. Audit
```text
1. Prepare lossless-coverage-auditor invocation packet.
2. Save real returned output.
3. Write audits/coverage-audit.md and audits/distortion-risk-log.md.
4. Repair missing or distorted routing.
5. Ask user before any source-disposable claim.
```
## 9. Downstream Handoff
Create downstream packets only after user confirmation.
Possible downstream tracks:
```text
- writing-workbench
- CCPE model or participant work
- engineering project
- scale or rubric extraction
- todo extraction
- continued research
```