4.0 KiB

Raw Blame History

CCPE Runtime Alignment

0. External Interface And Local Placement

Recorded investigation: 2026-06-20.

The current single external CCPE interface is:

C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md

Consumer projects must start there, then follow it to:

C:\Users\wangq\Documents\Codex\ccpe-system\runtimes\hybrid\ccpe-agent-consumer-setup.md

For this Knowledge Vault Runtime capability, the local consumer path remains:

skills/knowledge-processing/viewpoint-discussion-distillation/

Do not create a root ccpe/ folder for this Runtime integration. This repository already uses skills/ as the vault-side Runtime operating layer, with run-specific records under the related discussions/.../invocations/ work directory.

The local manifest for this Runtime integration is:

skills/knowledge-processing/viewpoint-discussion-distillation/runtime-manifest.yaml

1. Canonical CCPE References

C:\Users\wangq\Documents\Codex\ccpe-system\runtimes\hybrid\viewpoint-discussion-distillation.runtime.md
C:\Users\wangq\Documents\Codex\ccpe-system\runtimes\hybrid\agent-invocation-packet.protocol.md
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\whole-source-gestalt-reviewer.agent.md
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\topic-discovery-router.agent.md
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\topic-graph-synthesizer.agent.md
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\lossless-coverage-auditor.agent.md
C:\Users\wangq\Documents\Codex\ccpe-system\skills\workflow\conversation-segmentation.skill.md
C:\Users\wangq\Documents\Codex\ccpe-system\skills\workflow\evidence-routing-and-topic-doc-builder.skill.md

Sync status:

core_sync_status: completed_by_ccpe_batches_1_to_3
confirmed_on: 2026-06-07
remaining_ccpe_batch_4: handoff / creation brief / sync response documentation only
blocking_for_knowledge_validation: false

CCPE has now provided:

- Runtime v0.2 with strict invocation, Gate 0, Gate 3, Gate 6, and invocation-validity audit.
- Agent Invocation Packet Protocol v0.3.0 with carrier metadata, persistent carrier rule, returned-output format, packet-only invalidity, and human-review language fields.
- whole-source-gestalt-reviewer Agent.
- topic-graph-synthesizer Agent.
- updated topic-discovery-router, conversation-segmentation, evidence-routing-and-topic-doc-builder, and lossless-coverage-auditor.
- source_primary_language / output_language_policy rules for all human-confirmation artifacts.

Knowledge validation may proceed against those canonical artifacts.

2. Responsibility Split

CCPE System:
  Defines canonical behavior, roles, participant specs, and runtime protocol.

Knowledge Vault:
  Defines local workspace layout, context control, invocation records, run handoffs, and acceptance policy.

Writing Workbench:
  Receives a writing-intake packet only after user confirmation.

3. If CCPE Is Insufficient

If a canonical artifact is missing, ambiguous, or not specific enough to run a participant, stop the current stage and record:

blocked_waiting_for_participant_output

Do not fill the missing gap by writing a simulated Agent report.

4. Third-Round Validation Boundary

The next formal Knowledge-side validation should use:

source_document_path: diary/2026/2026-06/2026-06-05.md
recommended_workspace: discussions/viewpoint-development/2026-06-05-失望性情感隔离3
mode: fresh third-round validation
allowed_prior_context:
  - updated Knowledge Vault Skill rules
  - updated CCPE Runtime / Protocol / Agent / Skill specs
disallowed_prior_context:
  - first-round formal outputs as production inputs
  - second-round topic docs or material extraction as production inputs
  - second-round user-confirmed model relations unless explicitly supplied by the user in the new session

The third-round workspace has not been created by this alignment update. It should be created by the new validation session during source registration / preflight.

4.0 KiB Raw Blame History