761 lines
34 KiB
Markdown
761 lines
34 KiB
Markdown
---
|
|
artifact_type: ccpe-runtime
|
|
name: viewpoint-discussion-distillation-runtime
|
|
runtime_id: viewpoint-discussion-distillation
|
|
author: CCPE System
|
|
version: 0.2
|
|
created: 2026-06-06
|
|
updated: 2026-06-07
|
|
status: draft
|
|
runtime_type: hybrid-runtime
|
|
target_platform: Codex / Claude Code / OpenClaw / platform-neutral Markdown
|
|
based_on: CCPE System
|
|
related_agents:
|
|
- whole-source-gestalt-reviewer
|
|
- topic-discovery-router
|
|
- topic-graph-synthesizer
|
|
- lossless-coverage-auditor
|
|
related_skills:
|
|
- conversation-segmentation
|
|
- evidence-routing-and-topic-doc-builder
|
|
related_models:
|
|
- candidate: lossless-viewpoint-distillation
|
|
related_protocols:
|
|
- agent-invocation-packet
|
|
---
|
|
|
|
# Viewpoint Discussion Distillation Runtime
|
|
|
|
## 1. Runtime Overview
|
|
|
|
### 1.1 Purpose
|
|
|
|
This Runtime turns a long viewpoint-development discussion into a durable Knowledge Vault material package. It preserves source material through traceable source block IDs, establishes a whole-source structural lens before local worker extraction when feasible, synthesizes a confirmed topic graph, routes material into topic documents, audits source coverage and invocation validity, and optionally prepares downstream task packets.
|
|
|
|
### 1.2 Runtime Type
|
|
|
|
```text
|
|
hybrid-runtime
|
|
```
|
|
|
|
### 1.3 Operating Mode
|
|
|
|
```text
|
|
hybrid-mode
|
|
```
|
|
|
|
### 1.4 Depth vs Automation Orientation
|
|
|
|
```text
|
|
Hybrid:
|
|
- depth-oriented: whole-source gestalt alignment, topic graph synthesis, hierarchy repair, downstream judgment
|
|
- automation-supported: registration, segmentation, source block ID assignment, material-unit extraction, routing-log construction, audit matrix construction
|
|
```
|
|
|
|
### 1.5 Success Criteria
|
|
|
|
```text
|
|
- The source document is registered without modifying the source file.
|
|
- Coherent sources under the feasible high-context limit receive a Whole-Source Gestalt Alignment before segmentation and worker extraction.
|
|
- Gate 0 records human confirmation, correction, rejection, or revision request for the gestalt lens before it becomes binding worker context.
|
|
- Source segmentation remains non-interpretive and traceable.
|
|
- Topic-discovery workers validate, enrich, localize, or challenge the confirmed gestalt lens instead of rediscovering the whole structure from zero.
|
|
- Topic graph synthesis is a formal participant boundary before material routing.
|
|
- Hierarchy Repair / Structure Confirmation is accepted before `02-material-routing-log.md` or `topics/*.md` are generated.
|
|
- Topic documents contain source material layers and material-unit extraction records, not only summaries.
|
|
- Gate 6 records whether topic docs and extracted material are useful enough for downstream automation.
|
|
- Coverage audit checks both source preservation and invocation validity before any completion or downstream-readiness claim.
|
|
- Every formal Agent or Skill output is backed by an invocation packet plus returned output, prompt-to-send returned output, or Skill execution record.
|
|
```
|
|
|
|
### 1.6 Non-Goals
|
|
|
|
```text
|
|
- Do not write the article.
|
|
- Do not start a writing-workbench project automatically.
|
|
- Do not build the downstream system automatically.
|
|
- Do not promote candidate models into canonical Model Cards without user confirmation.
|
|
- Do not delete, move, overwrite, or mark the original source disposable without explicit user approval after audit.
|
|
- Do not route material before topic graph / hierarchy acceptance.
|
|
- Do not simulate canonical participant output.
|
|
```
|
|
|
|
## 2. Participants
|
|
|
|
### 2.1 Human Role
|
|
|
|
The human user owns source boundary acceptance, gestalt lens confirmation, topic graph repair, topic document usefulness acceptance, downstream task routing, model promotion, source disposability, and final acceptance.
|
|
|
|
### 2.2 Agents
|
|
|
|
```text
|
|
- agent_id: whole-source-gestalt-reviewer
|
|
role: high-context structural alignment participant
|
|
responsibility: read the full source when feasible, judge coherence, identify global topic portrait, candidate layers, model-evolution line, core tensions, hierarchy risks, and segmentation guidance
|
|
invocation_condition: after source registration and before segmentation for coherent or potentially coherent sources under the feasible high-context limit
|
|
required_invocation_record: invocations/whole-source-gestalt-reviewer/agent-invocation-packet.md
|
|
required_return_record: invocations/whole-source-gestalt-reviewer/returned-output.md
|
|
persistent_required: true when user correction, revision, or follow-up may be needed
|
|
|
|
- agent_id: topic-discovery-router
|
|
role: lens-guided local topic extraction and challenge agent
|
|
responsibility: validate, enrich, localize, and challenge the confirmed gestalt lens using source blocks or excerpt packs; identify local exceptions and downstream task candidates
|
|
invocation_condition: after segmentation and Gate 0 confirmation, or in flat-discovery mode when Step 0 marks source as fragmented
|
|
required_invocation_record: invocations/topic-discovery-router/agent-invocation-packet.md
|
|
required_return_record: invocations/topic-discovery-router/returned-output.md
|
|
|
|
- agent_id: topic-graph-synthesizer
|
|
role: formal topic graph synthesis participant
|
|
responsibility: synthesize confirmed Step 0 lens, worker returns, user corrections, local challenges, merge/split candidates, parent-child relations, and model/tool/action/example distinctions into a topic graph draft
|
|
invocation_condition: after topic-discovery worker outputs are returned and before material routing
|
|
required_invocation_record: invocations/topic-graph-synthesizer/agent-invocation-packet.md
|
|
required_return_record: invocations/topic-graph-synthesizer/returned-output.md
|
|
|
|
- agent_id: lossless-coverage-auditor
|
|
role: preservation, distortion, and invocation-validity audit agent
|
|
responsibility: check source block coverage, source material layers, material-unit traceability, distortion risk, downstream readiness, carrier metadata, returned outputs, and Skill execution records
|
|
invocation_condition: after topic docs / material extraction and Gate 6 readiness review, and after any major topic document optimization
|
|
required_invocation_record: invocations/lossless-coverage-auditor/agent-invocation-packet.md
|
|
required_return_record: invocations/lossless-coverage-auditor/returned-output.md
|
|
```
|
|
|
|
### 2.3 Skills
|
|
|
|
```text
|
|
- skill_id: conversation-segmentation
|
|
purpose: split long discussions into stable source blocks without interpreting topics
|
|
invocation_condition: after source registration and, when present, after Gate 0 confirmation of the gestalt lens
|
|
required_execution_record: invocations/conversation-segmentation/skill-execution-record.md when executed locally
|
|
|
|
- skill_id: evidence-routing-and-topic-doc-builder
|
|
purpose: generate material-unit extraction records, routing logs, and topic documents with source material layers
|
|
invocation_condition: only after topic graph / hierarchy is confirmed or repaired
|
|
required_execution_record: invocations/evidence-routing-and-topic-doc-builder/skill-execution-record.md when executed locally
|
|
```
|
|
|
|
### 2.4 Tools
|
|
|
|
```text
|
|
- tool_name: filesystem
|
|
purpose: read source documents and write Knowledge Vault workbench outputs
|
|
permission: read specified source; write only confirmed output workspace
|
|
```
|
|
|
|
## 3. Context Layer
|
|
|
|
### 3.1 Input Contract
|
|
|
|
```yaml
|
|
runtime_id: viewpoint-discussion-distillation
|
|
source_document_path: path to diary or discussion markdown
|
|
source_type: diary | discussion | multi-platform-transcript | research-discussion
|
|
round_boundary_rule: markdown-h1 | user-defined | inferred
|
|
intended_use: viewpoint-development
|
|
output_workspace_path: confirmed Knowledge Vault workspace path
|
|
source_primary_language: inferred | user-provided language label
|
|
human_review_output_language: mirror_source_primary_language
|
|
lossless_requirement: true
|
|
allow_topic_overlap: true
|
|
downstream_routing_required: optional
|
|
strict_invocation_required: true
|
|
whole_source_gestalt_required: conditional
|
|
```
|
|
|
|
### 3.2 Required Context
|
|
|
|
```text
|
|
- Source document path.
|
|
- Output workspace path.
|
|
- Boundary rule or permission to infer boundaries.
|
|
- User confirmation that this run is for viewpoint development, not direct article writing.
|
|
- Invocation carrier policy for every substantive participant.
|
|
- Source excerpt context packs for any judgment Agent that must classify topics, not only locator text.
|
|
```
|
|
|
|
### 3.3 Optional Context
|
|
|
|
```text
|
|
- Seed topics.
|
|
- Forbidden merges.
|
|
- Known downstream task types.
|
|
- Related research files.
|
|
- Existing model or system names that should be preserved.
|
|
- Prior human corrections to topic graph or hierarchy.
|
|
```
|
|
|
|
### 3.4 Shared Context
|
|
|
|
```text
|
|
- README.md
|
|
- 00-source-map.md
|
|
- 00-whole-source-gestalt.md or invocations/whole-source-gestalt-reviewer/returned-output.md
|
|
- 01-topic-map.md
|
|
- 02-material-routing-log.md
|
|
- 03-run-notes.md
|
|
- material-unit extraction records
|
|
- topic documents
|
|
- audit reports
|
|
- participant invocation records
|
|
```
|
|
|
|
### 3.5 Source Policy
|
|
|
|
The source document is user-provided source. It remains authoritative. Runtime outputs must distinguish source excerpts, interpretations, routing decisions, structured summaries, candidate models, downstream task recommendations, participant outputs, and main-session integration notes.
|
|
|
|
Human-confirmation artifacts must use the primary language of the source material as their dominant language. This applies to Step 0 gestalt output, worker returned outputs when reviewed by the user, Topic Graph Synthesis / Gate 3 hierarchy materials, Hierarchy Repair records, Gate 6 topic-doc review materials, audit reports, and downstream routing decisions. English may remain in protocol field names, slugs, participant IDs, file paths, and secondary aliases, but it must not become the dominant language of human-review content unless the user explicitly requests it.
|
|
|
|
## 4. Authority Layer
|
|
|
|
### 4.1 Autonomous Actions
|
|
|
|
```text
|
|
- Read the specified source document only as required for registration or formally recorded Skill execution.
|
|
- Create source-map shells, run notes, invocation packets, prompt-to-send files, and draft handoff records in the confirmed workspace.
|
|
- Assign provisional source block IDs through the segmentation Skill.
|
|
- Mark low-confidence topics, routing decisions, and invocation gaps.
|
|
- Integrate real returned outputs without inventing participant judgments.
|
|
```
|
|
|
|
### 4.2 Actions Requiring Confirmation
|
|
|
|
```text
|
|
- Create a new Knowledge Vault directory if the target path was not previously confirmed.
|
|
- Bind the Step 0 gestalt lens as worker context.
|
|
- Finalize or repair the topic graph.
|
|
- Start material routing and topic document generation.
|
|
- Accept topic docs and extracted material as useful enough for downstream automation.
|
|
- Drop, merge, or archive a topic.
|
|
- Mark source material as disposable or superseded.
|
|
- Start downstream writing, CCPE, engineering, scale, model update, or todo work.
|
|
- Update canonical Model Index or workspace templates.
|
|
- Accept any formal participant output without complete invocation evidence.
|
|
```
|
|
|
|
### 4.3 Forbidden Actions
|
|
|
|
```text
|
|
- Delete or overwrite the original source.
|
|
- Replace source material layers with summaries.
|
|
- Hide unresolved questions inside polished conclusions.
|
|
- Treat all downstream candidates as article ideas.
|
|
- Treat all interesting claims as models.
|
|
- Generate `02-material-routing-log.md` or `topics/*.md` before topic graph / hierarchy acceptance.
|
|
- Use one-shot Step 0 output as a valid formal persistent-alignment record when user correction requires follow-up and the carrier cannot resume.
|
|
- Simulate the gestalt reviewer, topic router, topic graph synthesizer, coverage auditor, segmentation Skill, or topic-doc builder and label the output as formal participant output.
|
|
```
|
|
|
|
### 4.4 Human Decision Gates
|
|
|
|
```text
|
|
Gate Preflight:
|
|
- Trigger: target workspace and source registration are proposed.
|
|
- Human decision required: confirm output directory and source handling.
|
|
- Possible outcomes: proceed / change path / stop.
|
|
|
|
Gate 0:
|
|
- Trigger: Whole-Source Gestalt Alignment output is returned.
|
|
- Human decision required: confirm, correct, reject, or request revision of the gestalt lens, including whether the output language is usable for human review.
|
|
- Possible outcomes: bind lens for workers / record human correction / rerun Step 0 / switch to macro-topic split / switch to flat-discovery mode / stop.
|
|
|
|
Gate 3:
|
|
- Trigger: Topic graph synthesis or hierarchy repair draft is returned.
|
|
- Human decision required: approve, merge, split, rename, demote tool/case/action-layer topics, or defer hierarchy decisions, including whether the topic graph language is usable for human review.
|
|
- Possible outcomes: route material / run hierarchy repair / rerun synthesis / stop.
|
|
|
|
Gate 6:
|
|
- Trigger: Topic docs, material-unit extraction records, and routing log are available.
|
|
- Human decision required: decide whether extracted materials are useful enough for downstream automation, including whether review sections use the source primary language.
|
|
- Possible outcomes: proceed to audit / request another extraction pass / repair topic docs / stop.
|
|
|
|
Gate Audit:
|
|
- Trigger: coverage, distortion, or invocation-validity audit finds gaps.
|
|
- Human decision required: choose repair strategy, including whether the audit report is readable in the source primary language.
|
|
- Possible outcomes: reroute / repair topic docs / produce missing participant record / keep as unresolved / accept risk where allowed / stop.
|
|
|
|
Gate Downstream:
|
|
- Trigger: audited topic package is ready for downstream routing.
|
|
- Human decision required: choose downstream route.
|
|
- Possible outcomes: archive-only / writing packet / CCPE packet / engineering packet / model update / scale extraction / todo extraction / continued research.
|
|
|
|
Gate Invocation Block:
|
|
- Trigger: any canonical participant cannot be truly invoked or locally executed with a record.
|
|
- Human decision required: provide real output, approve manual handoff, or explicitly request simulation-only output.
|
|
- Possible outcomes: wait for participant output / generate prompt-to-send.md / stop / create simulation-only material excluded from synthesis.
|
|
```
|
|
|
|
### 4.5 Risk Levels
|
|
|
|
```text
|
|
Low: creating draft maps, packets, and logs in confirmed workspace.
|
|
Medium: merging topics or duplicating source blocks across topics.
|
|
High: binding a global lens as worker context or preparing downstream task packets.
|
|
Critical: declaring coverage complete, deleting source, changing canonical models, starting downstream projects without confirmation, or accepting simulated participant work as formal output.
|
|
```
|
|
|
|
## 5. Workflow Layer
|
|
|
|
### 5.1 Runtime Stages
|
|
|
|
```text
|
|
Preflight:
|
|
- Purpose: source registration
|
|
- Actor: runtime operator
|
|
- Input: user-confirmed source path and output workspace
|
|
- Output: 00-source-map.md shell, 03-run-notes.md, invocation directory structure
|
|
- Human gate: Gate Preflight
|
|
- Invocation rule: this is orchestration, not participant judgment
|
|
|
|
Step 0:
|
|
- Purpose: Whole-Source Gestalt Alignment
|
|
- Actor: whole-source-gestalt-reviewer agent
|
|
- Input: full source when feasible; otherwise 2-3 quasi-global source packs; source_primary_language; output_language_policy
|
|
- Output: output language policy, coherence judgment, downstream mode, global topic portrait, candidate layers, core tensions, model-evolution line, parent/child/tool/case/action-layer distinctions, chunk-first distortion risks, segmentation guidance, unresolved structure questions
|
|
- Language rule: human-review sections must primarily use the source material's primary language
|
|
- Human gate: Gate 0
|
|
- Invocation record: invocations/whole-source-gestalt-reviewer/agent-invocation-packet.md plus returned-output.md
|
|
|
|
Step 1:
|
|
- Purpose: conversation segmentation
|
|
- Actor: conversation-segmentation skill
|
|
- Input: source document, boundary rule, output workspace, accepted_gestalt_lens_path when present
|
|
- Output: source block inventory in 00-source-map.md
|
|
- Human gate: only if boundary inference is ambiguous
|
|
- Invocation record: invocations/conversation-segmentation/skill-execution-record.md or prompt-to-send.md returned output
|
|
|
|
Step 2:
|
|
- Purpose: lens-guided worker topic extraction
|
|
- Actor: topic-discovery-router agent or equivalent worker participants
|
|
- Input: confirmed Step 0 lens, source block inventory, source excerpt context packs, user corrections
|
|
- Output: local topic evidence, refinements, contradictions, exceptions, source-cited challenges, downstream candidates
|
|
- Language rule: if returned output may be reviewed by the user or quoted into Gate 3, human-review sections must primarily use the source material's primary language
|
|
- Human gate: only for severe contradiction or missing context
|
|
- Invocation record: invocations/topic-discovery-router/agent-invocation-packet.md plus returned-output.md for each formal worker
|
|
|
|
Step 3:
|
|
- Purpose: topic graph synthesis
|
|
- Actor: topic-graph-synthesizer agent
|
|
- Input: confirmed Step 0 lens, worker returned outputs, user corrections, local exceptions and challenges
|
|
- Output: 01-topic-map.md as topic graph draft with hierarchy, parent-child relations, cross-links, merge/split candidates, model/tool/action/example distinctions, and unresolved hierarchy risks
|
|
- Language rule: Gate 3 human-review sections must primarily use the source material's primary language
|
|
- Human gate: Gate 3
|
|
- Invocation record: invocations/topic-graph-synthesizer/agent-invocation-packet.md plus returned-output.md
|
|
|
|
Step 3R:
|
|
- Purpose: Hierarchy Repair Pass
|
|
- Actor: topic-graph-synthesizer agent, runtime operator integration, or user-directed repair record
|
|
- Trigger: human rejects or amends parent-child relations, model/tool/layer distinctions, or global topic graph
|
|
- Output: revised 01-topic-map.md and 03-run-notes.md entry recording accepted, rejected, and repaired relationships
|
|
- Human gate: Gate 3 must pass before Step 4
|
|
- Hard rule: do not generate `02-material-routing-log.md` or `topics/*.md` until this pass is accepted or explicitly not needed
|
|
|
|
Step 4:
|
|
- Purpose: evidence routing, topic docs, and material-unit extraction
|
|
- Actor: evidence-routing-and-topic-doc-builder skill or worker/sub-session participants
|
|
- Input: confirmed topic graph, source blocks, accessible source document, output workspace
|
|
- Output: material-unit extraction records, 02-material-routing-log.md, topics/*.md
|
|
- Language rule: Gate 6 review sections, topic titles, source interpretation, open questions, and downstream candidate descriptions should primarily use the source material's primary language
|
|
- Human gate: Gate 6
|
|
- Invocation record: invocations/evidence-routing-and-topic-doc-builder/skill-execution-record.md or prompt-to-send.md returned output
|
|
|
|
Step 5:
|
|
- Purpose: coverage, distortion, and invocation-validity audit
|
|
- Actor: lossless-coverage-auditor agent
|
|
- Input: source map, accepted gestalt lens, topic graph, routing log, material-unit records, topic docs, participant invocation records
|
|
- Output: audits/coverage-audit.md, audits/distortion-risk-log.md, audits/invocation-validity-audit.md
|
|
- Language rule: audit findings and human decision sections must primarily use the source material's primary language
|
|
- Human gate: Gate Audit
|
|
- Invocation record: invocations/lossless-coverage-auditor/agent-invocation-packet.md plus returned-output.md
|
|
|
|
Step 6:
|
|
- Purpose: downstream task routing
|
|
- Actor: runtime operator with returned participant outputs as evidence
|
|
- Input: audited topic package
|
|
- Output: handoff/downstream-task-routing.md and optional specialized packets
|
|
- Human gate: Gate Downstream
|
|
- Invocation rule: downstream routing must not claim router or auditor approval unless those outputs exist as real participant records
|
|
```
|
|
|
|
### 5.2 Main Workflow
|
|
|
|
```text
|
|
1. Register source and proposed workspace.
|
|
2. Decide whether Whole-Source Gestalt Alignment is required.
|
|
3. Invoke whole-source-gestalt-reviewer when required and save returned-output.md.
|
|
4. Ask user to confirm, correct, reject, or revise the Step 0 lens.
|
|
5. Segment the discussion into stable source blocks without interpreting topics.
|
|
6. Run topic-discovery workers under the confirmed lens for coherent sources; use macro-topic split for mixed sources; use flat-discovery mode only for fragmented sources.
|
|
7. Invoke topic-graph-synthesizer to produce 01-topic-map.md as a topic graph draft.
|
|
8. Ask user to confirm or repair the topic graph / hierarchy.
|
|
9. Route material and build topic docs only after hierarchy acceptance.
|
|
10. Ask user to confirm topic docs and extracted materials before downstream automation.
|
|
11. Audit coverage, traceability, distortion risk, and invocation validity.
|
|
12. Repair gaps or low-confidence routing.
|
|
13. Generate downstream-task-routing only if user wants task分流.
|
|
14. Stop with a run report and clear next action.
|
|
15. Do not accept any formal participant output unless the invocation evidence is present.
|
|
```
|
|
|
|
### 5.3 Branch Logic
|
|
|
|
```text
|
|
- If source is coherent and under the feasible high-context limit, run Step 0 before segmentation and worker extraction.
|
|
- If source is mixed, Step 0 recommends macro-topic split before ordinary worker extraction.
|
|
- If source is fragmented, workers may perform minimally biased flat discovery.
|
|
- If full source is too long for one high-context participant, split into 2-3 quasi-global source packs, run gestalt workers, synthesize a global gestalt report, then proceed.
|
|
- If the Step 0 carrier is one-shot and cannot handle human correction, treat its output as reference analysis, not a valid formal persistent-alignment record.
|
|
- If topic-discovery-router cannot read the source directly as a real participant, build source excerpt context packs before invocation.
|
|
- If a worker challenges the gestalt lens, require source block IDs or source ranges.
|
|
- If a source block belongs to multiple topics, record primary and secondary routing.
|
|
- If material is immature, route to continued-research rather than writing or build execution.
|
|
- If material defines a reusable model, mark model-update or candidate-model, but do not promote it.
|
|
- If material defines a system or engineering task, route to downstream-task-routing, not writing-intake.
|
|
```
|
|
|
|
### 5.4 Loop Rules
|
|
|
|
```text
|
|
- Repeat Step 0 only when the user rejects the gestalt lens or the source coherence mode changes.
|
|
- Repeat topic graph synthesis when worker challenges or user corrections alter hierarchy.
|
|
- Repeat hierarchy repair until Gate 3 passes or the user stops the run.
|
|
- Repeat material extraction when Gate 6 finds topic docs not useful enough for downstream automation.
|
|
- Repeat audit after repairs that change source routing, topic docs, material-unit records, or invocation evidence.
|
|
```
|
|
|
|
### 5.5 Stop Conditions
|
|
|
|
```text
|
|
- User pauses at a decision gate.
|
|
- Step 0 requires a real participant and none can be invoked.
|
|
- Topic graph is too unstable for document generation.
|
|
- Hierarchy Repair / Structure Confirmation has not passed.
|
|
- A required participant cannot be truly invoked or locally executed with a record.
|
|
- Topic-discovery-router has only locator text and no source content or source excerpt context pack.
|
|
- Evidence-routing-and-topic-doc-builder lacks confirmed topic graph or recoverable source blocks.
|
|
- Coverage audit has unresolved high-risk gaps.
|
|
- Invocation-validity audit finds missing carrier metadata, missing returned-output.md, missing prompt-to-send return, or missing Skill execution record for formal outputs.
|
|
- Final run report is written after accepted audit and optional downstream routing.
|
|
```
|
|
|
|
### 5.6 Escalation Conditions
|
|
|
|
Escalate when source boundaries are unclear, topic names flatten user terminology, global lens conflicts with strong local evidence, downstream routes imply external project creation, source material cannot be preserved without exceeding available context, or invocation evidence is incomplete.
|
|
|
|
## 6. State Layer
|
|
|
|
### 6.1 Working State
|
|
|
|
```text
|
|
- source registration status
|
|
- gestalt lens status
|
|
- coherence mode
|
|
- source block inventory
|
|
- worker extraction returns
|
|
- topic graph
|
|
- hierarchy repair queue
|
|
- material-unit records
|
|
- routing decisions
|
|
- low-confidence queue
|
|
- audit findings
|
|
- downstream task candidates
|
|
- participant invocation records
|
|
- carrier metadata
|
|
```
|
|
|
|
### 6.2 Persistent State
|
|
|
|
Persistent state lives in Knowledge Vault files, not hidden chat memory.
|
|
|
|
### 6.3 Decision Log
|
|
|
|
Record workspace confirmations, Gate 0 decisions, topic-map confirmations, hierarchy repairs, merge/split decisions, Gate 6 decisions, audit repairs, source disposability decisions, and downstream routing decisions in `03-run-notes.md`.
|
|
|
|
### 6.4 Artifact Log
|
|
|
|
Maintain generated file list in `handoff/ccpe-runtime-run-report.md`.
|
|
|
|
### 6.5 Resume Rules
|
|
|
|
Resume by reading `README.md`, `00-source-map.md`, accepted gestalt output, `01-topic-map.md`, `02-material-routing-log.md` if it exists, `03-run-notes.md`, material-unit records, latest audit files, and invocation records from the workspace.
|
|
|
|
## 7. Collaboration Layer
|
|
|
|
### 7.1 Handoff Protocol
|
|
|
|
Each stage hands off explicit files. No participant should rely on unrecorded chat state.
|
|
|
|
Every participant handoff must follow `runtimes/hybrid/agent-invocation-packet.protocol.md`.
|
|
|
|
### 7.2 Role Differentiation
|
|
|
|
```text
|
|
- Runtime operator: orchestrates, prepares packets, records decisions, integrates returned outputs, and stops at blocked states.
|
|
- Whole-Source Gestalt Reviewer: reads the whole source when feasible and proposes global structural orientation.
|
|
- Topic Discovery Router / workers: extract local evidence, refinements, contradictions, and exceptions under the confirmed lens.
|
|
- Topic Graph Synthesizer: synthesizes returned worker outputs and user corrections into a topic graph.
|
|
- Evidence Routing and Topic Doc Builder: produces material-unit records, routing log, and topic docs after hierarchy acceptance.
|
|
- Lossless Coverage Auditor: checks source preservation, distortion risk, downstream readiness, and invocation validity.
|
|
```
|
|
|
|
### 7.3 Conflict Resolution
|
|
|
|
When participants disagree, preserve source evidence, mark the conflict, and ask the user before finalizing. User corrections override agent classifications. Source evidence overrides memory or assumptions.
|
|
|
|
### 7.4 Synthesis Rules
|
|
|
|
Synthesis must keep source material, interpretation, participant output, main-session integration, and downstream recommendation separate. Main-session synthesis is allowed only as mechanical integration over returned outputs and must be labeled as integration, not participant judgment.
|
|
|
|
## 8. Output Layer
|
|
|
|
### 8.1 Runtime Outputs
|
|
|
|
```text
|
|
- Knowledge viewpoint-development workspace.
|
|
- Accepted whole-source gestalt lens.
|
|
- Confirmed topic graph.
|
|
- Material-unit extraction records.
|
|
- Audited topic documents.
|
|
- Coverage, distortion, and invocation-validity audit.
|
|
- Downstream task routing file.
|
|
- Optional specialized packets.
|
|
```
|
|
|
|
### 8.2 Intermediate Outputs
|
|
|
|
```text
|
|
- source-map
|
|
- whole-source gestalt returned output
|
|
- worker dispatch packs
|
|
- worker returned outputs
|
|
- topic-map / topic graph
|
|
- hierarchy repair record
|
|
- routing-log
|
|
- run-notes
|
|
- low-confidence queue
|
|
- invocation records
|
|
```
|
|
|
|
### 8.3 Output Format
|
|
|
|
```md
|
|
# CCPE Runtime Run Report
|
|
|
|
## 1. Run Summary
|
|
|
|
## 2. Source Files
|
|
|
|
## 3. Invocation Records
|
|
|
|
## 4. Generated Artifacts
|
|
|
|
## 5. Human Decisions
|
|
|
|
## 6. Topic Graph Status
|
|
|
|
## 7. Material Extraction Status
|
|
|
|
## 8. Audit Result
|
|
|
|
## 9. Downstream Task Routing
|
|
|
|
## 10. Open Questions
|
|
|
|
## 11. Resume Instructions
|
|
```
|
|
|
|
### 8.4 Archival Rules
|
|
|
|
Store all source-derived outputs under the confirmed Knowledge Vault viewpoint-development workspace. Do not store source-derived topic documents in `ccpe-system`.
|
|
|
|
## 9. Evaluation Layer
|
|
|
|
### 9.1 Validation Checklist
|
|
|
|
```text
|
|
Objective fulfilled?
|
|
Source file preserved?
|
|
Preflight registration complete?
|
|
Step 0 required or explicitly waived by coherence mode?
|
|
Step 0 returned output present when required?
|
|
Step 0 human-review language mirrors source primary language?
|
|
All Gate-facing human-review artifacts mirror source primary language?
|
|
Gate 0 human confirmation recorded?
|
|
Source blocks assigned?
|
|
Workers received confirmed lens when source is coherent?
|
|
Worker challenges cite source IDs or ranges?
|
|
Topic graph synthesizer returned output present?
|
|
Topic graph / hierarchy confirmed or repaired?
|
|
No material routing before hierarchy acceptance?
|
|
Material-unit extraction records present?
|
|
Topic docs include source material layer?
|
|
Gate 6 confirmation recorded?
|
|
Routing log complete?
|
|
Coverage audit complete?
|
|
Invocation-validity audit complete?
|
|
Distortion risks marked?
|
|
Simulation-only material excluded from formal synthesis?
|
|
Human gates respected?
|
|
Downstream routing optional and confirmed?
|
|
```
|
|
|
|
### 9.2 Quality Rubric
|
|
|
|
```text
|
|
- Source fidelity
|
|
- Whole-source coherence judgment
|
|
- Topic boundary clarity
|
|
- Dynamic classification quality
|
|
- Hierarchy accuracy
|
|
- Model/tool/action/example distinction
|
|
- Traceability
|
|
- Material-unit usability
|
|
- Downstream routing precision
|
|
- Human-in-the-loop discipline
|
|
- Invocation validity
|
|
- Knowledge Vault fit
|
|
- Reusability for future discussions
|
|
```
|
|
|
|
### 9.3 Failure Modes
|
|
|
|
```text
|
|
- Chunk-first workers flatten tools, layers, cases, and model-upgrade relationships into peer topics.
|
|
- Summary compression replaces source preservation.
|
|
- Step 0 becomes a one-shot summary rather than a persistent alignment loop.
|
|
- Main session absorbs the full source and pretends to be the formal gestalt participant.
|
|
- Topic map becomes a rigid taxonomy too early.
|
|
- Material routing starts before hierarchy acceptance.
|
|
- Topic docs lack material-unit records or source material layers.
|
|
- Article routing dominates non-writing tasks.
|
|
- Coverage gaps are hidden.
|
|
- Invocation gaps are ignored because topic docs look polished.
|
|
- Unresolved questions are mixed with confirmed facts.
|
|
- Source block IDs are unstable across passes.
|
|
```
|
|
|
|
### 9.4 Recovery Rules
|
|
|
|
```text
|
|
- If Step 0 fails, rerun it with a valid carrier or switch modes with human approval.
|
|
- If topic graph fails, return to topic graph synthesis or hierarchy repair.
|
|
- If material routing begins too early, stop, mark affected outputs invalid, repair hierarchy, and regenerate routing.
|
|
- If topic docs fail Gate 6, repeat extraction or repair topic docs before audit.
|
|
- If audit fails, return to routing, extraction, topic docs, or invocation evidence repair.
|
|
- If invocation validity fails, collect missing returned output / Skill execution record or mark affected material simulation-only and exclude it.
|
|
- If source preservation fails, restore from the original source and rebuild affected topic documents.
|
|
```
|
|
|
|
### 9.5 Regression Checks
|
|
|
|
```text
|
|
1. Orchestrator tries to write topic docs directly.
|
|
Expected: blocked, simulation-only, or rejected from formal synthesis.
|
|
|
|
2. Step 0 is run by a one-shot agent, then user corrects the structure.
|
|
Expected: invalid formal Step 0 unless the same carrier can continue.
|
|
|
|
3. Topic-discovery workers ignore confirmed Step 0 and rediscover flat peer topics.
|
|
Expected: audit flags hierarchy drift.
|
|
|
|
4. Evidence-routing-and-topic-doc-builder output lacks source material layer, material-unit records, or source block IDs.
|
|
Expected: rejected.
|
|
|
|
5. Lossless coverage audit sees a polished topic package but no returned-output / skill-execution-record.
|
|
Expected: invocation validity failure.
|
|
```
|
|
|
|
## 10. Runtime Environment
|
|
|
|
### 10.1 Platform
|
|
|
|
Codex first; platform-neutral Markdown for portability.
|
|
|
|
### 10.2 File Access
|
|
|
|
Read the user-confirmed source file only for registration, explicit local Skill execution, or formally invoked participant context preparation. Write only within the confirmed Knowledge Vault output workspace.
|
|
|
|
### 10.3 Tool Access
|
|
|
|
Filesystem tools are sufficient for v0.2. External web access is not part of this Runtime unless the user explicitly adds research sources.
|
|
|
|
### 10.4 Network Access
|
|
|
|
Not required.
|
|
|
|
### 10.5 Logging
|
|
|
|
Log decisions, generated artifacts, unresolved questions, carrier metadata, returned outputs, Skill execution records, and audit findings in workspace files.
|
|
|
|
### 10.6 Versioning
|
|
|
|
Use `runtime_version: 0.2` in run reports. Update this spec before changing output contracts.
|
|
|
|
## 11. Automation Boundary
|
|
|
|
### 11.1 Allowed Automation
|
|
|
|
```text
|
|
- source registration scaffolding
|
|
- invocation packet generation
|
|
- segmentation
|
|
- source block ID assignment
|
|
- worker dispatch pack preparation
|
|
- draft topic graph integration from returned outputs
|
|
- material-unit extraction when executed as a recorded Skill or real worker output
|
|
- draft routing after hierarchy acceptance
|
|
- draft topic document generation after hierarchy acceptance
|
|
- audit checklist execution
|
|
```
|
|
|
|
### 11.2 Requires Confirmation
|
|
|
|
```text
|
|
- binding the Step 0 lens
|
|
- final topic graph / hierarchy
|
|
- downstream packet generation
|
|
- source disposability claim
|
|
- canonical model or project updates
|
|
- accepting participant outputs with incomplete invocation evidence
|
|
```
|
|
|
|
### 11.3 Forbidden Automation
|
|
|
|
```text
|
|
- source deletion
|
|
- summary-only replacement
|
|
- automatic article project creation
|
|
- automatic engineering project creation
|
|
- automatic Model Card promotion
|
|
- material routing before hierarchy acceptance
|
|
- simulated canonical participant output accepted as formal result
|
|
```
|
|
|
|
## 12. Deployment Notes
|
|
|
|
### 12.1 Codex
|
|
|
|
Use from a Knowledge Vault session after reading local governance and handoff docs. Keep CCPE specs referenced by path. The main session is an orchestrator, not a substitute participant.
|
|
|
|
### 12.2 Claude Code
|
|
|
|
Use the same file contracts. Require explicit approval before file writes outside the confirmed workspace.
|
|
|
|
### 12.3 OpenClaw
|
|
|
|
Use as a staged workflow with visible decision gates and file-based resume points.
|
|
|
|
### 12.4 Manual Operation
|
|
|
|
The user can run the workflow manually by creating the same source-map, gestalt return, topic-map, routing-log, topic docs, audit files, invocation records, and downstream-task-routing file.
|
|
|
|
## 13. Version Notes
|
|
|
|
```text
|
|
v0.2:
|
|
- Refactored Runtime from chunk-first discovery to gestalt-first topic graph workflow.
|
|
- Added Preflight registration, Step 0 Whole-Source Gestalt Alignment, Gate 0, Topic Graph Synthesis, Hierarchy Repair, Gate 6, material-unit extraction records, and invocation-validity audit.
|
|
- Made strict invocation the default for production, tests, audits, and downstream handoffs.
|
|
|
|
v0.1:
|
|
- Initial draft for Knowledge Vault viewpoint-development use.
|
|
```
|