128 lines
3.3 KiB
Markdown
128 lines
3.3 KiB
Markdown
# Knowledge Vault Invocation Policy
|
|
|
|
## 1. Purpose
|
|
|
|
This policy defines how Knowledge Vault invokes reusable capabilities, CCPE participants, local scripts, and external agents.
|
|
|
|
It is a vault-side operating rule. CCPE defines canonical participants; this file defines how this repository accepts or rejects participant outputs during real knowledge-processing work.
|
|
|
|
## 2. Scope
|
|
|
|
Use this policy when a Knowledge Vault workflow invokes:
|
|
|
|
```text
|
|
- CCPE Agent
|
|
- CCPE Skill
|
|
- CCPE Runtime node
|
|
- native platform agent
|
|
- external GPT / Gemini / Claude / manual participant
|
|
- local script or code-based processor
|
|
```
|
|
|
|
## 3. Run-Specific Records
|
|
|
|
Run-specific invocation records belong in the work item directory, not in `skills/`.
|
|
|
|
Example:
|
|
|
|
```text
|
|
discussions/viewpoint-development/{date}-{topic}/
|
|
invocations/
|
|
{participant-id}/
|
|
agent-invocation-packet.md
|
|
prompt-to-send.md
|
|
returned-output.md
|
|
skill-execution-record.md
|
|
run-log.md
|
|
```
|
|
|
|
The public `skills/templates/` directory only stores templates.
|
|
|
|
## 4. No-Simulation Rule
|
|
|
|
The main session may:
|
|
|
|
```text
|
|
- create directories and templates
|
|
- prepare invocation packets
|
|
- prepare prompt-to-send files
|
|
- execute local skills when the procedure is explicit
|
|
- run scripts and record their inputs and outputs
|
|
- collect real participant outputs
|
|
- synthesize results that are backed by records
|
|
- ask the user for decisions
|
|
```
|
|
|
|
The main session must not:
|
|
|
|
```text
|
|
- write a formal Agent output as if a canonical Agent produced it
|
|
- write a Skill result without a skill-execution-record
|
|
- treat a convenience summary as a participant report
|
|
- accept an external participant result without source metadata
|
|
- proceed when CCPE rules are insufficient to launch the participant safely
|
|
```
|
|
|
|
If a required participant cannot be truly invoked, mark the stage:
|
|
|
|
```text
|
|
blocked_waiting_for_participant_output
|
|
```
|
|
|
|
## 5. Acceptance Rule
|
|
|
|
A participant output may be accepted only when at least one condition is true:
|
|
|
|
```text
|
|
- a completed participant startup packet returned a real output
|
|
- a prompt-to-send file was executed externally and the returned output was saved
|
|
- a local Skill execution record identifies procedure, inputs, outputs, and validation
|
|
- a local script record identifies command, inputs, outputs, and validation
|
|
- the user explicitly labels material as simulation-only and it is excluded from formal synthesis
|
|
```
|
|
|
|
## 6. Insufficient Rule Handling
|
|
|
|
If CCPE provides an Agent, Skill, Runtime, or protocol that is not specific enough to run safely, Knowledge Vault must pause before formal processing.
|
|
|
|
Record:
|
|
|
|
```text
|
|
- missing rule or unclear boundary
|
|
- affected participant
|
|
- blocked output files
|
|
- proposed clarification needed
|
|
- user decision required
|
|
```
|
|
|
|
## 7. External Participant Metadata
|
|
|
|
Returned external outputs must record:
|
|
|
|
```text
|
|
- participant name
|
|
- platform or tool
|
|
- date
|
|
- prompt-to-send path
|
|
- source input range
|
|
- returned output path
|
|
- operator note, if manually pasted back
|
|
```
|
|
|
|
## 8. Local Script Or Code-Based Capability
|
|
|
|
Some Knowledge Vault capabilities may be implemented as scripts rather than CCPE participants.
|
|
|
|
The run record must include:
|
|
|
|
```text
|
|
- script path
|
|
- command or entrypoint
|
|
- input files
|
|
- output files
|
|
- validation checks
|
|
- known limitations
|
|
```
|
|
|
|
Script output is not an Agent judgment. It must be labeled as deterministic or tool-assisted processing.
|