the-mindscape-of-bro-tsong/requirements/ccpe/2026-06-19-ccra-local-revie...

6.4 KiB

CCPE Request: Local CCRA Reviewer Agent Runtime

Date: 2026-06-19

Client repository:

C:\Users\wangq\Documents\Codex\work-projects\the-mindscape-of-bro-tsong

Requested supplier repository:

C:\Users\wangq\Documents\Codex\ccpe-system

1. Product Context

The Mindscape of Bro Tsong is building a file-first cognitive model library MVP.

The project already produces CCRA / GPT review bundles under:

ccra_review_bundle/

The owner wants to reduce manual transfer work by adding a first-pass Local CCRA review loop inside the project. Local CCRA review should use a real CCPE Agent Runtime child session, not main-session roleplay.

The first version serves only this repository.

2. Needed Capability

Provide a ccra-local-reviewer capability that can be invoked from this project through CCPE Agent Runtime.

The capability must include:

  • Agent Spec for ccra-local-reviewer.
  • Runtime Spec or invocation protocol for creating and continuing a child review session.
  • File-first input and output contract for local review run directories.
  • Review report template.
  • Findings classification rubric.
  • Lifecycle and scope guard rules.
  • Guidance for whether companion automation stays CCPE-owned or should be routed to skills-vault.

3. Why This Belongs In CCPE

This request is primarily about expert-agent role definition, review governance, invocation protocol, runtime session continuation, and model lifecycle gate judgment.

Those are CCPE responsibilities.

This repository should only store product-side review runs and supplier requests. It should not become the canonical source for the CCRA Agent definition or runtime protocol.

4. Current Blocked Task

The project can document local_ccra_reviews/ now, but it cannot run official Local CCRA review until CCPE supplies the Agent Spec and Runtime interface.

Concrete blocked action:

Owner asks main Codex session to run Local CCRA review
-> main session creates local_ccra_reviews/<round>/<nn>/
-> main session invokes CCPE Agent Runtime
-> child session writes local review report

The final runtime invocation command or tool contract is intentionally not defined in this repository.

5. Input Files And Source Paths

Relevant project-side paths:

README.md
AGENTS.md
PROJECTS.md
docs/WORKFLOW.md
docs/DECISIONS.md
docs/DATA_CONTRACT.md
docs/HANDOFF_TEMPLATE.md
knowledge_assets/
ccra_review_bundle/
local_ccra_reviews/README.md

Relevant upstream CCRA source material:

C:\Users\wangq\Documents\Codex\knowledge-vault\prompts\GPT\认知科学产品规划架构师\认知科学产品规划架构师.md
C:\Users\wangq\Documents\Codex\knowledge-vault\prompts\GPT\认知科学产品规划架构师\
C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\强哥的思想宇宙\讨论\2026-06-18产品交流-GPT.md
C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\强哥的思想宇宙\讨论\Local-Agent\0.1本地的CCRA放在哪儿.md

Reference implementation pattern:

C:\Users\wangq\Documents\Codex\knowledge-vault\skills\knowledge-processing\viewpoint-discussion-distillation

This reference is for the existence of prior CCPE Runtime invocation and session-continuation patterns. Do not copy it into this repository.

6. Expected Output Artifacts

CCPE should produce or register:

  1. ccra-local-reviewer Agent Spec.
  2. CCPE Agent Runtime invocation protocol for this Agent.
  3. Session persistence contract covering child session id, continuation state, and resume behavior.
  4. File-first review run contract compatible with:
local_ccra_reviews/<public-round>/<local-pass>/
  1. Local CCRA report template.
  2. Findings classification rubric, including at least:
blocker
major
minor
calibration
defer
  1. Capability routing decision for companion automation:
  • keep as Agent-specific CCPE runtime support;
  • implement locally in this product repository;
  • or abstract as reusable deterministic automation and route to skills-vault.

7. Required Review Behavior

ccra-local-reviewer must:

  • Run in a child session or equivalent isolated runtime context.
  • Read primary evidence from files, not from main-session summaries.
  • Prioritize review bundle files, reports, tests, selector rules, regression cases, and diffs before Codex explanations.
  • Output review findings, risks, evidence references, and recommended next actions.
  • Identify non-target behavior changes.
  • Identify engineering-pass versus product-judgment gaps.
  • Identify lifecycle overclaims.
  • Preserve the distinction between Local CCRA first review, Owner decision, and Web CCRA final review.

8. Prohibited Behavior

ccra-local-reviewer must not:

  • Modify project files.
  • Edit selector rules.
  • Edit model cards.
  • Edit model JSON.
  • Edit regression cases.
  • Create review bundles.
  • Upgrade model lifecycle status.
  • Add a third model.
  • Introduce LLM selector, RAG, database, frontend, backend, user system, or platform behavior.
  • Treat its own output as Owner approval.
  • Treat its own output as Web CCRA approval.

9. Companion Capability Candidates

The following needs were discovered while planning Local CCRA. They should not be sent directly to skills-vault from this repository yet. CCPE should first classify them.

Candidates:

  • Routing behavior diff audit after selector changes.
  • Review bundle completeness audit.
  • Lifecycle status guard scan.
  • Round initialization context builder.
  • Regression and validation gate runner.

Classification options:

  1. Agent-specific support inside ccra-local-reviewer Runtime.
  2. Product-local deterministic helper.
  3. Reusable deterministic Skill request to skills-vault.

If a candidate becomes a skills-vault request, it should be named by its reusable operation rather than by this project-specific review context.

10. Human Gate

Owner approval is required before:

  • Treating Local CCRA findings as accepted work.
  • Copying accepted materials into a formal Web CCRA review bundle.
  • Including 04_LOCAL_CCRA_REVIEW_REPORT.md in any Web CCRA upload package.
  • Upgrading model lifecycle status.
  • Routing any companion capability to skills-vault.

11. Urgency And Dependency

Urgency: high for future review-loop efficiency, but not blocking current model library validation.

Dependency:

  • Local review run folders can be documented now.
  • Official Local CCRA execution waits for CCPE Agent Spec and Runtime interface.