wantsong
/
writing-workbench
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
writing-workbench/ccpe/invocation-policy.md

2.1 KiB
Raw Blame History

Writing Workbench CCPE Invocation Policy

This is the root-level CCPE invocation policy for writing-workbench.

No article project owns a special CCPE participant registry. Article projects only own their run records under their own audit/ directories. Participant identity, canonical artifact binding, and default invocation rules live here.

External Interface

Use this single CCPE external entrypoint:

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

Before invoking any CCPE participant:

  1. Read C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md.
  2. Follow that interface to the consumer setup contract.
  3. Read only the protocol, Runtime, Agent, Lite, or Skill files required for the current task.
  4. Resolve the participant through ccpe/agent-registry.yaml.
  5. Create a project run directory under projects/<project>/audit/<participant-display-name>/rS.R/.
  6. Write run-specific agent-invocation-packet.md.
  7. Write run-specific prompt-to-send.md so the participant loads the canonical artifact before task context.
  8. Launch a real participant carrier.
  9. Save returned-output.md only after the real participant returns.

If the canonical artifact is missing or unreadable, stop with:

blocked_missing_canonical_artifact

If a real participant cannot be launched, stop with:

blocked_waiting_for_participant_output

Default Roles

  • han-yu: default lead writer for outline repair.
  • zhang-liao: default reviewer.
  • giant-cognition: default reviewer.
  • cognitive-imaging: default reviewer, display alias 显影.

Acceptance Rule

A participant output is formal only when all of these are true:

  • ccpe/agent-registry.yaml binds the participant to a canonical artifact.
  • The canonical artifact was readable or pasted before task context.
  • agent-invocation-packet.md exists for the project run.
  • A real participant carrier was launched and recorded.
  • returned-output.md was saved after the participant returned.
  • Metadata says simulation_only: false.

Packet-only and prompt-only states are not execution evidence. The controller session must not write a formal reviewer or lead-writer result.