Sync local CCRA runtime 0.1.2 contract
This commit is contained in:
parent
ab59e3ce48
commit
e798cd2923
|
|
@ -175,7 +175,7 @@ Files intended for GPT / CCRA upload inside a review bundle should include the r
|
|||
|
||||
Use the installed `bundle-zip` Skill for review bundle raw zips. Do not hand-roll source-relative zip creation with PowerShell `Compress-Archive` when directory paths matter.
|
||||
|
||||
Local CCRA first-pass reviews are recorded under `local_ccra_reviews/<public-round>/<local-pass>/`. They run through a real CCPE Agent Runtime child session and normally use the same-child `review_turn` plus `planning_turn` pattern. Local CCRA output is formal local first review, but it does not replace Owner or Web CCRA judgment. Formal Web CCRA bundles do not include the local review report by default.
|
||||
Local CCRA first-pass reviews are recorded under `local_ccra_reviews/<public-round>/<local-pass>/`. They run through a real CCPE Agent Runtime child session and normally use the same-child `review_turn` plus `planning_turn` pattern. Local CCRA v0.1.2 requires explicit helper/runtime policies for bundle audit profile, gate execution mode, routing diff policy, and lifecycle scan scope. Local CCRA output is formal local first review, but it does not replace Owner or Web CCRA judgment. Formal Web CCRA bundles do not include the local review report by default.
|
||||
|
||||
## 13. Next Steps
|
||||
|
||||
|
|
|
|||
|
|
@ -177,6 +177,15 @@ Markdown files in the run directory are human-readable process records.
|
|||
|
||||
`next-review-requirements.md` is the same-child `planning_turn` output and should not be treated as Owner approval or proof that a patch worked.
|
||||
|
||||
For Local CCRA v0.1.2 and later, `review-metadata.json` or `agent-invocation-packet.md` must declare:
|
||||
|
||||
- `bundle_audit_profile`: `ccra_mindscape_review_bundle`, `generic`, or `not_applicable`.
|
||||
- `gate_execution_mode`: `dry_run`, `run`, `owner_waived`, or `not_applicable`.
|
||||
- `routing_diff_policy`: `required`, `skipped_no_after_evidence`, `manual_equivalent_required`, or `not_applicable`.
|
||||
- `lifecycle_scan_scope`: `current_review_bundle`, `changed_files`, `knowledge_assets`, `model_library_state`, or `whole_repo`.
|
||||
|
||||
`returned-output.md` should include the compact Owner-facing summary defined by CCPE v0.1.2, including evidence limitations for the four fields above.
|
||||
|
||||
Local CCRA review records must not become source of truth for model status, selector behavior, regression cases, or source evidence. Accepted actions must be applied back to the canonical project files and validated there.
|
||||
|
||||
Formal Web CCRA upload bundles exclude the Local CCRA report by default unless the owner explicitly asks to include it.
|
||||
|
|
|
|||
|
|
@ -314,3 +314,31 @@ Patch 2 should focus on:
|
|||
- Mandatory routing behavior diff when before/after patch evidence exists.
|
||||
- Scoped lifecycle/status scan and triage.
|
||||
- Short Owner-facing `returned-output.md` summary.
|
||||
|
||||
## Decision 021: Adopt Local CCRA v0.1.2 helper/runtime policy contract
|
||||
|
||||
Status: Accepted
|
||||
|
||||
Reason:
|
||||
|
||||
CCPE completed Patch 2 and advanced `ccra-local-reviewer` / `ccra-local-review` to v0.1.2.
|
||||
|
||||
Patch 2 did not change the core reviewer behavior accepted after `pilot-02`:
|
||||
|
||||
- issue mechanism diagnosis;
|
||||
- patch scope judgment;
|
||||
- same-child `review_turn` and `planning_turn`;
|
||||
- mandatory `knowledge_assets/` knowledge base;
|
||||
- Owner / Web CCRA / lifecycle authority boundaries.
|
||||
|
||||
It hardens the local runtime contract around helper reliability and return shape.
|
||||
|
||||
Decision:
|
||||
|
||||
- Future Local CCRA runs should follow CCPE v0.1.2.
|
||||
- `review-metadata.json` or `agent-invocation-packet.md` should declare `bundle_audit_profile`, `gate_execution_mode`, `routing_diff_policy`, and `lifecycle_scan_scope`.
|
||||
- `returned-output.md` should contain the compact Owner-facing summary expected by v0.1.2.
|
||||
- A third historical pilot is not required for this patch because the core reviewer behavior did not change.
|
||||
- The next Owner / Web CCRA-defined Local CCRA run should serve as live validation for v0.1.2.
|
||||
|
||||
The historical `pilot-01` and `pilot-02` records remain unchanged because they preserve the actual v0.1.1-era test evidence.
|
||||
|
|
|
|||
|
|
@ -74,5 +74,6 @@ First-version constraints:
|
|||
- Local CCRA review runs are stored under `local_ccra_reviews/`.
|
||||
- The reviewer runs through CCPE Agent Runtime in a real child review session.
|
||||
- Formal local review normally uses the same-child `review_turn` plus `planning_turn` pattern.
|
||||
- v0.1.2 requires explicit helper/runtime policies for bundle audit profile, gate execution mode, routing diff policy, and lifecycle scan scope.
|
||||
- Local CCRA output is formal local first review, but it does not replace Owner or Web CCRA judgment.
|
||||
- The `ccra-local-reviewer` Agent Spec and Runtime protocol belong in `ccpe-system`.
|
||||
|
|
|
|||
|
|
@ -113,16 +113,17 @@ Workflow:
|
|||
1. Owner decides whether the public round needs Local CCRA review.
|
||||
2. Codex creates the next numbered local review run directory.
|
||||
3. Codex writes `run-notes.md`, `review-metadata.json`, `gate-manifest.yaml`, and `lifecycle-guard-config.yaml`.
|
||||
4. Codex runs `review-context-builder` and applicable helper Skills, recording skipped helpers in `run-notes.md`.
|
||||
5. Codex writes `agent-invocation-packet.md`, `prompt-to-send.md`, and `turn-prompts/`.
|
||||
6. Codex invokes CCPE Agent Runtime / Codex child thread as `ccra-local-reviewer`.
|
||||
7. The runtime child session id or carrier id is recorded in `run-notes.md`.
|
||||
8. `review_turn` writes `04_LOCAL_CCRA_REVIEW_REPORT.md` and `returned-output.md`.
|
||||
9. `planning_turn` continues the same child session and writes `next-review-requirements.md` when next-review planning is needed.
|
||||
10. Owner records accepted, rejected, deferred, or escalated findings in `owner-decision.md`.
|
||||
11. Codex executes accepted actions in the main project session.
|
||||
12. A follow-up Local CCRA review uses the next local pass label, such as `02/`.
|
||||
13. After Local CCRA and Owner acceptance, Codex creates the formal Web CCRA bundle under `ccra_review_bundle/round-NN_YYYY-MM-DD_topic/`.
|
||||
4. Codex declares Local CCRA v0.1.2 helper policies: `bundle_audit_profile`, `gate_execution_mode`, `routing_diff_policy`, and `lifecycle_scan_scope`.
|
||||
5. Codex runs `review-context-builder` and applicable helper Skills, recording skipped helpers in `run-notes.md`.
|
||||
6. Codex writes `agent-invocation-packet.md`, `prompt-to-send.md`, and `turn-prompts/`.
|
||||
7. Codex invokes CCPE Agent Runtime / Codex child thread as `ccra-local-reviewer`.
|
||||
8. The runtime child session id or carrier id is recorded in `run-notes.md`.
|
||||
9. `review_turn` writes `04_LOCAL_CCRA_REVIEW_REPORT.md` and `returned-output.md`.
|
||||
10. `planning_turn` continues the same child session and writes `next-review-requirements.md` when next-review planning is needed.
|
||||
11. Owner records accepted, rejected, deferred, or escalated findings in `owner-decision.md`.
|
||||
12. Codex executes accepted actions in the main project session.
|
||||
13. A follow-up Local CCRA review uses the next local pass label, such as `02/`.
|
||||
14. After Local CCRA and Owner acceptance, Codex creates the formal Web CCRA bundle under `ccra_review_bundle/round-NN_YYYY-MM-DD_topic/`.
|
||||
|
||||
Rules:
|
||||
|
||||
|
|
@ -131,6 +132,8 @@ Rules:
|
|||
- Review inputs and outputs should be exchanged through local files, not chat summaries.
|
||||
- Runtime child session id and continuation state belong in `run-notes.md` and `agent-invocation-packet.md`.
|
||||
- The default formal pattern is same-child `review_turn` followed by `planning_turn`.
|
||||
- Patch or post-patch review material requires `routing_diff_policy: required` or a manually documented equivalent table.
|
||||
- `gate_execution_mode: dry_run` cannot support validation pass claims.
|
||||
- Formal Web CCRA bundles exclude `04_LOCAL_CCRA_REVIEW_REPORT.md` by default.
|
||||
- Include the local report in Web CCRA upload packages only when the owner explicitly asks for Web CCRA to review local findings.
|
||||
- CCPE owns the Agent Spec, Runtime Spec, invocation protocol, review rubric, and companion-capability classification.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# 本地 CCRA 评审机制说明
|
||||
|
||||
version: 0.2
|
||||
version: 0.3
|
||||
|
||||
last_updated: 2026-06-19
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ Owner 决定需要本地评审
|
|||
|
||||
## 7. 正式使用条件
|
||||
|
||||
基于 Round 04 `pilot-02` 的三方对比，Local CCRA v0.1.1 可以作为本项目正式本地初审使用，但带条件：
|
||||
基于 Round 04 `pilot-02` 的三方对比和 CCPE Patch 2 更新，Local CCRA v0.1.2 可以作为本项目正式本地初审使用，但带条件：
|
||||
|
||||
- 必须真实调起子会话，不允许主会话角色扮演。
|
||||
- 必须记录并复用 `child_session_id`。
|
||||
|
|
@ -151,9 +151,25 @@ Owner 决定需要本地评审
|
|||
- 当评审对象包含补丁或 post-patch 证据时，必须要求 before / after 行为对比。
|
||||
- Local CCRA 不能替代 Owner decision、Web CCRA final review 或模型生命周期升级判断。
|
||||
|
||||
Patch 2 属于硬化需求，不是进入下一轮本地初审的前置门槛。它主要改善 helper profile、gate runner 策略、routing diff 强制化、lifecycle scan 范围和短摘要输出。
|
||||
v0.1.2 已把 Patch 2 硬化项纳入 CCPE runtime 合同。每次运行应明确记录：
|
||||
|
||||
如果 Patch 2 不改变机制诊断、补丁范围判断、同子会话延续、强制知识库或权限边界，则不需要第三次历史试运行。可以在下一次 Owner / Web CCRA 已确定目标的真实本地初审中验证。
|
||||
```text
|
||||
bundle_audit_profile: ccra_mindscape_review_bundle | generic | not_applicable
|
||||
gate_execution_mode: dry_run | run | owner_waived | not_applicable
|
||||
routing_diff_policy: required | skipped_no_after_evidence | manual_equivalent_required | not_applicable
|
||||
lifecycle_scan_scope: current_review_bundle | changed_files | knowledge_assets | model_library_state | whole_repo
|
||||
```
|
||||
|
||||
这些字段通常写入 `review-metadata.json` 和 `agent-invocation-packet.md`，并在 `returned-output.md` 中摘要返回。
|
||||
|
||||
字段含义：
|
||||
|
||||
- `bundle_audit_profile`：优先使用 `ccra_mindscape_review_bundle`；若 helper 只能使用 generic profile，必须标注 profile mismatch，不能自动判定 bundle 失败。
|
||||
- `gate_execution_mode`：`dry_run` 只能证明 gate 声明可读，不能支持 pass claim；真正验收需要 `run` 或 Owner 记录 `owner_waived`。
|
||||
- `routing_diff_policy`：如果评审对象包含 patch 或 before / after 证据，必须有 routing diff 或手工等价表；初始无后验评审可记录为 `skipped_no_after_evidence`。
|
||||
- `lifecycle_scan_scope`：whole repo 是广域审计模式，不应默认成为当前评审 blocker；发现项必须做 current-scope triage。
|
||||
|
||||
CCPE Patch 2 没有改变机制诊断、补丁范围判断、同子会话延续、强制知识库或权限边界，因此不需要第三次历史试运行。可以在下一次 Owner / Web CCRA 已确定目标的真实本地初审中验证 v0.1.2。
|
||||
|
||||
## 8. 与 Web CCRA Bundle 的关系
|
||||
|
||||
|
|
|
|||
|
|
@ -159,7 +159,18 @@ Owner requests Local CCRA review
|
|||
|
||||
Major public rounds normally should receive Local CCRA review after Owner / Web CCRA define the round goal. Patch rounds such as `round-03.2a` are optional and owner-directed.
|
||||
|
||||
After `pilot-02`, Local CCRA v0.1.1 is usable as the formal local first-review lane with conditions. CCPE Patch 2 remains a non-blocking hardening request for helper profile, gate execution policy, routing diff requirements, lifecycle scan scope, and short returned summaries.
|
||||
After `pilot-02` and CCPE Patch 2, Local CCRA v0.1.2 is usable as the formal local first-review lane with conditions.
|
||||
|
||||
For v0.1.2, every new run should declare these helper/runtime policy fields in `review-metadata.json` or `agent-invocation-packet.md`:
|
||||
|
||||
```text
|
||||
bundle_audit_profile: ccra_mindscape_review_bundle | generic | not_applicable
|
||||
gate_execution_mode: dry_run | run | owner_waived | not_applicable
|
||||
routing_diff_policy: required | skipped_no_after_evidence | manual_equivalent_required | not_applicable
|
||||
lifecycle_scan_scope: current_review_bundle | changed_files | knowledge_assets | model_library_state | whole_repo
|
||||
```
|
||||
|
||||
`returned-output.md` should preserve a compact Owner-facing summary, including final action recommendation, blocking status, required next action, output paths, and evidence limitations.
|
||||
|
||||
## 7. Relationship To Web CCRA Bundles
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Date: 2026-06-19
|
|||
|
||||
本次工作已从项目侧结构规划推进到历史试运行验证。
|
||||
|
||||
Local CCRA v0.1.1 已通过 Round 04 `pilot-02` 的两回合历史试运行，可作为本项目正式本地初审使用，但不替代 Owner / Web CCRA。
|
||||
Local CCRA v0.1.2 已在 CCPE 完成 Patch 2 硬化，可作为本项目正式本地初审使用，但不替代 Owner / Web CCRA。
|
||||
|
||||
本次仍不新增 selector、模型、RAG、前端、后端或完整 Round 级自动化平台。
|
||||
|
||||
|
|
@ -34,7 +34,8 @@ Local CCRA v0.1.1 已通过 Round 04 `pilot-02` 的两回合历史试运行，
|
|||
7. CCPE 完成 Patch 1 后，完成 `pilot-02` 两回合试运行。
|
||||
8. 完成 Web baseline / pilot-01 / pilot-02 三方对比。
|
||||
9. 新增 Patch 2 非阻塞硬化需求单。
|
||||
10. 更新本地机制知识资产到 v0.2。
|
||||
10. CCPE 完成 Patch 2 后，同步本地环境说明到 v0.1.2。
|
||||
11. 更新本地机制知识资产到 v0.3。
|
||||
|
||||
## 4. 关键文件路径
|
||||
|
||||
|
|
@ -112,24 +113,24 @@ Do not include 04_LOCAL_CCRA_REVIEW_REPORT.md unless Owner explicitly asks.
|
|||
|
||||
## 7. Current Local CCRA Runtime Status
|
||||
|
||||
- CCPE has supplied Patch 1-level `ccra-local-reviewer` / `ccra-local-review` behavior.
|
||||
- CCPE has supplied Patch 2-level `ccra-local-reviewer` / `ccra-local-review` behavior, version `0.1.2`.
|
||||
- `pilot-02` verified real child-session invocation and same-child `review_turn` + `planning_turn`.
|
||||
- `pilot-02` child session id: `019edcde-24be-7593-99b2-5cf014467340`.
|
||||
- `review_turn` duration: 512317 ms.
|
||||
- `planning_turn` duration: 342925 ms.
|
||||
- Readiness: `ready_for_formal_local_first_review_with_conditions`.
|
||||
|
||||
Remaining hardening needs are captured in:
|
||||
Patch 2 request was captured in:
|
||||
|
||||
```text
|
||||
requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime-patch2.md
|
||||
```
|
||||
|
||||
Patch 2 is non-blocking if Patch 1 behavior remains intact.
|
||||
CCPE completed that hardening without changing the core reviewer behavior. Future runs should declare `bundle_audit_profile`, `gate_execution_mode`, `routing_diff_policy`, and `lifecycle_scan_scope`.
|
||||
|
||||
## 8. Needs Product / CCPE Judgment
|
||||
|
||||
- CCPE should process Patch 2 hardening: bundle audit profile, gate runner execution policy, routing diff requirement, lifecycle scan scope, and short returned summary.
|
||||
- CCPE v0.1.2 should be used for future Local CCRA runs.
|
||||
- Owner must decide per round whether Local CCRA review is required.
|
||||
- Owner must decide whether any Local CCRA report should be included in a Web CCRA upload package.
|
||||
- Owner / Web CCRA still need to define the next round's work before this project starts that round.
|
||||
|
|
@ -157,7 +158,7 @@ The first `--check` run reported drift because `models/model_index.json.last_upd
|
|||
|
||||
## 10. Suggested Next Tasks
|
||||
|
||||
1. Send `requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime-patch2.md` to `ccpe-system`.
|
||||
2. Sync `knowledge_assets/10_本地CCRA评审机制说明.md` v0.2 to the Web CCRA / GPT knowledge side.
|
||||
1. Sync `knowledge_assets/10_本地CCRA评审机制说明.md` v0.3 to the Web CCRA / GPT knowledge side.
|
||||
2. Use CCPE v0.1.2 for the next Owner / Web CCRA-defined Local CCRA run.
|
||||
3. Do not run a third historical pilot unless CCPE changes mechanism diagnosis, patch scope judgment, same-child continuation, mandatory knowledge-base use, or authority boundaries.
|
||||
4. Discuss full Round-level automation in a new conversation, because it is a workflow/orchestrator topic rather than a Local CCRA reviewer patch.
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
|
||||
Date: 2026-06-19
|
||||
|
||||
Status: implemented upstream in `ccpe-system` as `ccra-local-reviewer` / `ccra-local-review` v0.1.2.
|
||||
|
||||
Client repository:
|
||||
|
||||
```text
|
||||
|
|
|
|||
Loading…
Reference in New Issue