# Codex 本地 CCRA 规划落地摘要

Date: 2026-06-19

## 1. 当前阶段

项目仍处于 `model_library_mvp`。

本次工作已从项目侧结构规划推进到历史试运行验证。

Local CCRA v0.1.2 已在 CCPE 完成 Patch 2 硬化，可作为本项目正式本地初审使用，但不替代 Owner / Web CCRA。

本次仍不新增 selector、模型、RAG、前端、后端或完整 Round 级自动化平台。

## 2. 本轮目标

把已确认的 Local CCRA 规划转成当前仓库内可执行的文件规则：

- 第一版只服务 `the-mindscape-of-bro-tsong`。
- Local CCRA 是正式本地初审，但不替代 Owner / Web CCRA 关键节点判断。
- 本地评审必须通过真实 CCPE Agent Runtime 子会话，不做主会话模拟。
- 本地评审按公共 round 版本加内部 pass 编号归档。
- skills / companion automation 需求先交给 CCPE 分类，再决定是否转给 `skills-vault`。
- 正式 Web CCRA 包默认不包含 Local CCRA review report。

## 3. 已完成内容

1. 新增 `local_ccra_reviews/` 运行区说明。
2. 新增 CCPE 需求单，请求 `ccra-local-reviewer` Agent Spec、Runtime invocation protocol、session continuation contract 和 companion capability classification。
3. 更新项目边界、工作流、数据契约、文件身份、决策日志、项目简报和 handoff 模板。
4. 新增长期知识资产，说明项目侧 Local CCRA 机制。
5. 运行索引与验证命令。
6. 完成 `pilot-01` 与 Web baseline 的对比，识别 Patch 1 需求。
7. CCPE 完成 Patch 1 后，完成 `pilot-02` 两回合试运行。
8. 完成 Web baseline / pilot-01 / pilot-02 三方对比。
9. 新增 Patch 2 非阻塞硬化需求单。
10. CCPE 完成 Patch 2 后，同步本地环境说明到 v0.1.2。
11. 更新本地机制知识资产到 v0.3。

## 4. 关键文件路径

- `local_ccra_reviews/README.md`
- `requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime.md`
- `requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime-patch1.md`
- `requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime-patch2.md`
- `knowledge_assets/10_本地CCRA评审机制说明.md`
- `local_ccra_reviews/round-04/pilot-01/04_LOCAL_CCRA_REVIEW_REPORT.md`
- `local_ccra_reviews/round-04/pilot-01/05_WEB_LOCAL_CCRA_COMPARISON.md`
- `local_ccra_reviews/round-04/pilot-02/04_LOCAL_CCRA_REVIEW_REPORT.md`
- `local_ccra_reviews/round-04/pilot-02/next-review-requirements.md`
- `local_ccra_reviews/round-04/pilot-02/05_WEB_LOCAL_CCRA_COMPARISON.md`
- `docs/WORKFLOW.md`
- `docs/DECISIONS.md`
- `docs/DATA_CONTRACT.md`
- `docs/FILE_TAXONOMY.md`
- `docs/HANDOFF_TEMPLATE.md`
- `PROJECTS.md`
- `README.md`
- `AGENTS.md`

## 5. 关键规则

Local CCRA run path:

```text
local_ccra_reviews/<public-round>/<local-pass>/
```

Example:

```text
local_ccra_reviews/round-05_selector-calibration-policy/01/
local_ccra_reviews/round-05_selector-calibration-policy/02/
```

Run directory contract:

```text
run-notes.md
review-metadata.json
gate-manifest.yaml
lifecycle-guard-config.yaml
agent-invocation-packet.md
prompt-to-send.md
turn-prompts/
review-context.md
review-file-manifest.json
helper-outputs/
04_LOCAL_CCRA_REVIEW_REPORT.md
next-review-requirements.md
returned-output.md
owner-decision.md
```

Formal Web CCRA bundle path remains:

```text
ccra_review_bundle/round-NN_YYYY-MM-DD_topic/
```

Default Web CCRA upload behavior:

```text
Do not include 04_LOCAL_CCRA_REVIEW_REPORT.md unless Owner explicitly asks.
```

## 6. Assumptions Made

- CCPE will later provide the Runtime interface documentation and invocation contract.
- This repository should not define Runtime command details before CCPE supplies them.
- Local CCRA companion tooling should not be sent directly to `skills-vault` until CCPE or Owner classifies the capability as reusable deterministic automation.
- The new knowledge asset documents project-side workflow only, not the canonical Agent definition.

## 7. Current Local CCRA Runtime Status

- 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`.

Patch 2 request was captured in:

```text
requirements/ccpe/2026-06-19-ccra-local-reviewer-runtime-patch2.md
```

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 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.
- Full Round-level automation should be discussed separately as workflow/orchestrator design.

## 9. Validation Results

Commands run:

```powershell
python scripts\rebuild_indexes.py --write
python scripts\rebuild_indexes.py --check
python scripts\validate_model_library.py
```

Results:

- `rebuild_indexes.py --write`: PASS; refreshed `models/model_index.json` generated date and `cards/card_index.md` consistency.
- `rebuild_indexes.py --check`: PASS.
- `validate_model_library.py`: PASS.

Note:

The first `--check` run reported drift because `models/model_index.json.last_updated` was still `2026-06-18` while the generator uses the current date. Model entries and counts were not the source of drift. Running `--write` reconciled the generated index.

## 10. Suggested Next Tasks

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.