43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
# Requirements
|
|
|
|
This directory stores outbound supplier requests from CCPE System to neighboring repositories.
|
|
|
|
Use this directory when a CCPE Agent, Runtime, Committee, Skill, or Integration Registration needs a capability that CCPE should not implement directly.
|
|
|
|
## Current Supplier Channels
|
|
|
|
```text
|
|
requirements/
|
|
└── skills-vault/
|
|
```
|
|
|
|
## Ownership Rule
|
|
|
|
CCPE owns the architecture, role contracts, runtime protocols, rubrics, and integration registrations.
|
|
|
|
Neighboring repositories own implementation surfaces:
|
|
|
|
```text
|
|
skills-vault:
|
|
deterministic automation Skill source, scripts, tests, fixtures, install notes
|
|
|
|
project repositories:
|
|
project-specific runbooks, execution records, returned outputs, decision logs
|
|
|
|
development application repositories:
|
|
framework adapters, deployed runtime, service state, monitoring, operations
|
|
```
|
|
|
|
Do not place automation Skill source code in this directory. Place one Markdown request per needed capability.
|
|
|
|
## Request Lifecycle
|
|
|
|
```text
|
|
draft request
|
|
-> user confirms routing
|
|
-> supplier repository implements capability
|
|
-> CCPE registers the implemented capability only when a CCPE artifact depends on it
|
|
```
|
|
|
|
If a supplier capability is not yet implemented, CCPE artifacts may reference it as a planned integration, but must not claim it is available.
|