63 lines
1.4 KiB
Markdown
63 lines
1.4 KiB
Markdown
# Local CCRA Milestone Protocol
|
|
|
|
status: draft_milestone_lane
|
|
date: 2026-06-20
|
|
|
|
## Purpose
|
|
|
|
Local CCRA remains available as a milestone review lane.
|
|
|
|
It must not become a default round factory.
|
|
|
|
## Review Triggers
|
|
|
|
Use Local CCRA only at milestone boundaries, such as:
|
|
|
|
- project boundary ready;
|
|
- first end-to-end runtime sample complete;
|
|
- before adding the third or fourth model/lens;
|
|
- before converting repeated runtime outputs into governed model assets;
|
|
- before asking Web CCRA for formal acceptance.
|
|
|
|
## Non-Triggers
|
|
|
|
Do not start Local CCRA for:
|
|
|
|
- every prompt edit;
|
|
- small model note changes;
|
|
- routing wording changes;
|
|
- registry field additions;
|
|
- minor documentation cleanup.
|
|
|
|
## Review Package Shape
|
|
|
|
When a milestone review is explicitly started later, use a local-only directory such as:
|
|
|
|
```text
|
|
local-ccra-reviews/milestone-XX/01/
|
|
```
|
|
|
|
Expected files:
|
|
|
|
- `review-brief.md`;
|
|
- `file-manifest.md`;
|
|
- `prompt-to-send.md`;
|
|
- `LOCAL_CCRA_REVIEW_REPORT.md`;
|
|
- `returned-output.md`;
|
|
- `owner-decision.md`.
|
|
|
|
Optional only when needed:
|
|
|
|
- `helper-outputs/`;
|
|
- `next-review-requirements.md`.
|
|
|
|
## Authority
|
|
|
|
Local CCRA can identify findings and recommend repairs. It does not authorize repairs by itself.
|
|
|
|
Repairs require an owner decision. Web CCRA remains the strategic alignment and final-acceptance lane for major project direction.
|
|
|
|
## M0-M1 Boundary
|
|
|
|
M0-M1 defines this protocol only. It does not create a review directory or run a review.
|