53 lines
1.3 KiB
Markdown
53 lines
1.3 KiB
Markdown
# Invocation Policy
|
|
|
|
## Formal Output Requires Real Invocation
|
|
|
|
Formal output includes:
|
|
|
|
- reviewer report;
|
|
- lead writer outline repair;
|
|
- lead writer draft;
|
|
- specialist analysis used for a user decision.
|
|
|
|
Formal output must come from a real sub-session, thread, tool invocation, or explicitly approved external execution path.
|
|
|
|
## Controller May Do
|
|
|
|
The controller session may:
|
|
|
|
- prepare context packs;
|
|
- create review briefs;
|
|
- route source files;
|
|
- launch or coordinate sub-sessions;
|
|
- summarize returned formal outputs;
|
|
- update project records;
|
|
- ask the user for decisions.
|
|
|
|
## Controller Must Not Do
|
|
|
|
The controller session must not:
|
|
|
|
- impersonate a reviewer or lead writer;
|
|
- create a formal report without real invocation;
|
|
- treat a prompt draft as an executed report;
|
|
- advance the project after its own recommendation;
|
|
- hide uncertainty about missing capability.
|
|
|
|
## Missing Capability
|
|
|
|
If a required agent, skill, or runtime is unavailable:
|
|
|
|
1. Create a supplier ticket in `requirements/ccpe/` or `requirements/skills-vault/`.
|
|
2. Set project state to `blocked_waiting_capability`.
|
|
3. Stop until the user confirms the capability is ready.
|
|
|
|
## Simulation
|
|
|
|
Simulation is allowed only for planning and must be labeled:
|
|
|
|
```yaml
|
|
simulation_only: true
|
|
formal_output: false
|
|
excluded_from_synthesis: true
|
|
```
|