3.0 KiB

Raw Blame History

Invocation Contract

1. Minimum Runtime Input

runtime_id: viewpoint-discussion-distillation
source_document_path:
source_type:
round_boundary_rule:
intended_use: viewpoint-development
output_workspace_path:
lossless_requirement: true
allow_topic_overlap: true
writing_handoff_required: optional
model_mining_required: optional
no_simulation_requirement: true
human_confirmation_required_before:
  - accepting_whole_source_gestalt_as_worker_lens
  - final_topic_map
  - material_routing
  - accepting_topic_docs_for_downstream_use
  - source_disposable_claim
  - writing_workbench_handoff
  - downstream_task_routing
whole_source_gestalt_required_when:
  - source_is_coherent
  - source_fits_high_context_participant
whole_source_gestalt_exception_requires_record: true

2. Run Directory Contract

{workspace}/
  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/

3. Invocation Directory Contract

invocations/
  whole-source-gestalt-reviewer/
  conversation-segmentation/
  topic-discovery-router/
  evidence-routing-and-topic-doc-builder/
  lossless-coverage-auditor/

Subdirectories may be split by range:

conversation-segmentation/R01/
conversation-segmentation/R02/

4. Whole-Source Gestalt Output Contract

whole-source-gestalt-reviewer/returned-output.md must include:

- 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 orientation and constraint material. It is not a substitute for source block indexing, evidence routing, or coverage audit. It becomes a worker structure lens only after human confirmation.

5. Topic Docs Human Confirmation Contract

After topic docs and material extraction are generated, record:

topic_docs_human_confirmation.md

It must include:

- confirmation status: confirmed / needs revision / rejected
- reviewed topic docs or material index
- whether extracted materials are useful for downstream work
- whether another extraction pass is required
- whether downstream handoff may proceed
- user corrections, if any

6. Blocked State

Use this state when the run cannot accept a participant output:

blocked_waiting_for_participant_output

Record the reason in 03-run-notes.md or the relevant invocation directory.

3.0 KiB Raw Blame History