From 6d0b5d28a55812f2211f6ecb68e70cf3137b5dff Mon Sep 17 00:00:00 2001 From: wantsong Date: Fri, 19 Jun 2026 08:03:39 +0800 Subject: [PATCH] Document round automation protocol --- AGENTS.md | 5 + PROJECTS.md | 5 + README.md | 9 +- docs/DATA_CONTRACT.md | 41 +++ docs/DECISIONS.md | 24 +- docs/FILE_TAXONOMY.md | 5 +- docs/HANDOFF_TEMPLATE.md | 18 +- docs/PROJECT_BRIEF.md | 14 + docs/ROUND_AUTOMATION_PROTOCOL.md | 255 ++++++++++++++++++ docs/WORKFLOW.md | 32 ++- .../qpi/CASE_PREPROCESSING_WORKFLOW.md | 3 +- knowledge_assets/10_本地CCRA评审机制说明.md | 49 ++-- local_ccra_reviews/README.md | 38 ++- ...话交接文档_Round自动化规则调整_2026-06-19.md | 188 +++++++++++++ reports/README.md | 9 + .../lifecycle-status-guard-scan.json | 49 ++++ .../lifecycle-status-guard-scan.md | 50 ++++ 17 files changed, 764 insertions(+), 30 deletions(-) create mode 100644 docs/ROUND_AUTOMATION_PROTOCOL.md create mode 100644 reports/Codex新会话交接文档_Round自动化规则调整_2026-06-19.md create mode 100644 reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.json create mode 100644 reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.md diff --git a/AGENTS.md b/AGENTS.md index 96f4440..ec1b87c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -220,6 +220,7 @@ At minimum, keep these files consistent: - `docs/PROJECT_BRIEF.md` - `docs/DATA_CONTRACT.md` - `docs/WORKFLOW.md` +- `docs/ROUND_AUTOMATION_PROTOCOL.md` when Round Conductor behavior changes - `docs/DECISIONS.md` - `PROJECTS.md` - `local_ccra_reviews/README.md` when Local CCRA review process changes @@ -245,6 +246,10 @@ C:\Users\wangq\.agents\skills Local CCRA review runs belong in `local_ccra_reviews/`, but the `ccra-local-reviewer` Agent Spec, review rubric, Runtime Spec, invocation protocol, session-continuation contract, and companion capability classification belong in `ccpe-system`. +Round Conductor automation belongs in this repository only as a product-local file protocol and execution workflow. It may orchestrate Local CCRA passes, write Chinese `findings-confirmation.md`, and implement Owner-accepted repairs, but it must not replace Owner decision, Web CCRA review, or lifecycle authority. + +Do not repair Local CCRA findings before `owner-decision.md` records `accept_for_codex_fix`. + Do not create a `skills-vault` request for Local CCRA companion automation until CCPE or the project owner classifies the operation as reusable deterministic automation. If a missing capability blocks model extraction: diff --git a/PROJECTS.md b/PROJECTS.md index 907f1b5..c17fbd2 100644 --- a/PROJECTS.md +++ b/PROJECTS.md @@ -23,6 +23,7 @@ This repository owns: - Application implementation when the project later adopts frameworks such as CrewAI, LangGraph, or a server runtime - Project-specific requirements, handoffs, validation reports, and decision records - Local CCRA review run records under `local_ccra_reviews/` +- Project-local Round Conductor process records, Owner decisions, and applied repair loops for this product This repository does not own canonical expert-agent specifications, reusable automation Skill source, or upstream source archives. @@ -77,6 +78,8 @@ Do not store canonical CCPE artifacts in this repository. Store the request here For Local CCRA, this repository stores only review run inputs, runtime session metadata, local review reports, Owner decisions, and action registers. The `ccra-local-reviewer` Agent Spec and Runtime protocol belong in `ccpe-system`. +For Round Conductor automation, this repository owns the product-specific file protocol in `docs/ROUND_AUTOMATION_PROTOCOL.md`, round charters under `reports/`, `findings-confirmation.md`, Owner decisions, accepted repairs, validation outputs, and Web bundle assembly. CCPE still owns reviewer/runtime governance and lifecycle authority rules. + ### skills-vault Requests Use: @@ -100,6 +103,8 @@ Do not store reusable automation Skill source in this repository. Store the requ For Local CCRA companion automation, route the capability through `requirements/ccpe/` first when it is unclear whether the need is Agent-specific, Runtime-specific, product-local, or reusable. Create a `skills-vault` request only after the operation has been abstracted as deterministic, reusable automation. +Do not create a `skills-vault` request merely because Round Conductor automation exists. Extract a reusable Skill only after repeated use shows a deterministic, cross-project operation. + ## Model Extraction Work Mode Model extraction is a duplex workflow: diff --git a/README.md b/README.md index 7382b85..29f36fd 100644 --- a/README.md +++ b/README.md @@ -177,11 +177,14 @@ Use the installed `bundle-zip` Skill for review bundle raw zips. Do not hand-rol Local CCRA first-pass reviews are recorded under `local_ccra_reviews///`. 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. +Round Conductor rules for Round 05 and later trial use are documented in `docs/ROUND_AUTOMATION_PROTOCOL.md`. The protocol allows Codex to automate Local CCRA orchestration and Chinese findings confirmation, then repair only findings recorded by Owner as `accept_for_codex_fix`. + ## 13. Next Steps 1. Round 03 is closed after the Round 03.2a CCRA / GPT pass decision. 2. Keep QPI and Intellectual Archaeology at `draft / B / pending` until Owner / CCRA review accepts stronger status. 3. Round 04.1 is closed after GPT review acceptance and closeout documentation. The closeout records `R04-BI-022` as an accepted collateral depth-limited QPI override and adds it to regression. -4. The next round discussion should start from Owner / Web CCRA planning; do not treat Round 04.1 closure as a model lifecycle upgrade or as a predefined Round 05 scope. -5. Defer any third-model expansion until the current QPI selector and case layer are accepted. -6. Route missing reusable extraction, inspection, or stability-scoring tools to `requirements/skills-vault/` or `requirements/ccpe/` instead of improvising local platform features. +4. Round 05 should start from Owner / Web CCRA planning, then use `docs/ROUND_AUTOMATION_PROTOCOL.md` for the project-local Round Conductor flow. +5. Do not treat Round 04.1 closure as a model lifecycle upgrade or as a predefined Round 05 scope. +6. Defer any third-model expansion until the current QPI selector and case layer are accepted. +7. Route missing reusable extraction, inspection, or stability-scoring tools to `requirements/skills-vault/` or `requirements/ccpe/` instead of improvising local platform features. diff --git a/docs/DATA_CONTRACT.md b/docs/DATA_CONTRACT.md index c12742f..c4f8445 100644 --- a/docs/DATA_CONTRACT.md +++ b/docs/DATA_CONTRACT.md @@ -167,6 +167,7 @@ Each local pass should contain: - `04_LOCAL_CCRA_REVIEW_REPORT.md` - `next-review-requirements.md` - `returned-output.md` +- `findings-confirmation.md` - `owner-decision.md` `review-metadata.json`, `review-file-manifest.json`, and helper JSON outputs are machine-readable process records. @@ -186,6 +187,46 @@ For Local CCRA v0.1.2 and later, `review-metadata.json` or `agent-invocation-pac `returned-output.md` should include the compact Owner-facing summary defined by CCPE v0.1.2, including evidence limitations for the four fields above. +`findings-confirmation.md` is a Chinese Owner-facing decision aid written by the Codex main session after Local CCRA outputs exist. It should extract only core confirmation items, proposed decision states, repair scope, impact, and evidence paths. It must not replace the full Local CCRA report or invent findings that are not grounded in `04_LOCAL_CCRA_REVIEW_REPORT.md`, `next-review-requirements.md`, or `returned-output.md`. + +Allowed decision states in `findings-confirmation.md` and `owner-decision.md` are: + +- `accept_for_codex_fix` +- `reject` +- `defer_to_future_round` +- `escalate_to_web_ccra` +- `owner_clarification_required` +- `accept_as_known_limit` + +Codex may implement only findings recorded as `accept_for_codex_fix` in `owner-decision.md`. + 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. + +## 11. Round Conductor Process Records + +Round automation process records are not model assets. + +Round charters and conductor summaries should live under `reports/` and should reference the relevant Local CCRA pass directories rather than copying reviewer outputs wholesale. + +Recommended round charter filename: + +```text +reports/RoundNN_round_conductor_charter_YYYY-MM-DD.md +``` + +Round Conductor records may describe: + +- public round label; +- Owner / Web CCRA guidance source; +- in-scope files or asset areas; +- non-goals; +- Local CCRA pass paths; +- Owner decision gates; +- accepted repair items; +- deferred or escalated items; +- validation and before/after behavior evidence; +- Web bundle readiness. + +Round Conductor records must not override canonical project files. If a finding changes model state, selector behavior, regression cases, model cards, or evidence records, that change must be applied to the canonical file and validated there. diff --git a/docs/DECISIONS.md b/docs/DECISIONS.md index 68988bc..2687846 100644 --- a/docs/DECISIONS.md +++ b/docs/DECISIONS.md @@ -172,7 +172,7 @@ Reason: Round 03.1 fixed QPI default over-selection, but GPT review found that explicit Intellectual Archaeology refusal phrases such as `先不要思想考古` could still lose to positive IA signals and QPI-completed bonuses. -A user instruction that names a model and refuses it should not be represented as a normal score penalty. It must hard-exclude that model unless a later owner-approved rule defines an explicit reversal phrase. +A user instruction that names a model and refuses it should not be represented as a normal score penalty. It must hard-exclude that model unless a later Owner-confirmed rule defines an explicit reversal phrase. The current Round 03.2 implementation keeps this scoped: @@ -342,3 +342,25 @@ Decision: - 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. + +## Decision 022: Add a project-local Round Conductor protocol before Round 05 + +Status: Owner-agreed for Round 05 trial + +Reason: + +The project needs to reduce manual review-loop labor before scaling from two model assets to a much larger model library. + +Local CCRA v0.1.2 is ready for formal local first review with conditions, but the Local CCRA reviewer contract intentionally does not define full Round-level automation or authorize repairs. + +Decision: + +- Add `docs/ROUND_AUTOMATION_PROTOCOL.md` as the project-local Round Conductor protocol. +- Use Round automation v0.1 for Local CCRA orchestration, helper execution, real child-session submission, and Chinese `findings-confirmation.md` extraction. +- Use Round automation v0.2 after Owner decision to let Codex repair only findings marked `accept_for_codex_fix`. +- Require `owner-decision.md` before any repair starts. +- Keep `ccra-local-reviewer` read-only; the main Codex session remains the implementer after Owner decision. +- Do not create a generic reusable Skill yet. Reusable automation should be extracted only after repeated project use proves a deterministic cross-project operation. +- Keep formal Web CCRA bundle rules unchanged: exclude `04_LOCAL_CCRA_REVIEW_REPORT.md` by default and include it only when Owner explicitly asks Web CCRA to review local findings. + +The initial Round 05 use should validate whether the protocol reduces transfer work without weakening Owner / Web CCRA authority boundaries. diff --git a/docs/FILE_TAXONOMY.md b/docs/FILE_TAXONOMY.md index 5428999..523be2e 100644 --- a/docs/FILE_TAXONOMY.md +++ b/docs/FILE_TAXONOMY.md @@ -22,7 +22,7 @@ Every meaningful file should fit one of four classes: | --- | --- | --- | --- | | Canonical source of truth | Files that define model/library behavior or reviewed content | Keep and version | `models/*.model.json`, `cards/*.md`, `sources/*.json`, `tests/*.regression.json`, `selector/*.json`, `schemas/*.json`, operative `docs/*.md` | | Generated / derived | Files rebuilt or checked from canonical assets | Keep when useful, rebuild at handoff/release | `models/model_index.json`, `cards/card_index.md`, `reports/validation_report.md`, `reports/index_rebuild_report.md`, `reports/model_card_sync_report_v0.2.md`, `reports/selector_regression_report_v0.2.md` | -| Review archive | Per-round evidence for Owner / CCRA / GPT review | Keep by round, do not treat as runtime truth | `ccra_review_bundle/round-*`, `local_ccra_reviews/round-*`, `reports/Codex*.md`, `reports/GPT*.md`, `reports/model_case_preprocessing/*` | +| Review archive | Per-round evidence for Owner / CCRA / GPT review | Keep by round, do not treat as runtime truth | `ccra_review_bundle/round-*`, `local_ccra_reviews/round-*`, `reports/Codex*.md`, `reports/GPT*.md`, `reports/Round*_round_conductor_*.md`, `reports/model_case_preprocessing/*` | | Temporary / local runtime | Caches or local command byproducts | Do not commit | `__pycache__/`, `*.pyc`, temporary extraction folders, ad hoc local scratch files | ## 3. Canonical Source Of Truth @@ -92,6 +92,7 @@ Examples: - `local_ccra_reviews/round-*/` - `reports/Codex*.md` - `reports/GPT*.md` +- `reports/Round*_round_conductor_*.md` - `reports/model_case_preprocessing/*` Rules: @@ -103,6 +104,8 @@ Rules: - Do not flatten zip contents, because duplicate filenames such as `README.md` can collide. - `knowledge_assets/` is excluded from review zips by default because the Owner manually syncs stable knowledge assets into GPT knowledge storage. - `local_ccra_reviews/` records local first-pass review runs and is not copied into Web CCRA bundles by default. +- `findings-confirmation.md` inside a Local CCRA run is a Chinese Owner decision aid and does not replace the full review report. +- Round Conductor reports under `reports/` are process records and do not override canonical model, selector, evidence, or regression files. - `04_LOCAL_CCRA_REVIEW_REPORT.md` is excluded from Web CCRA bundles by default unless the Owner explicitly asks to include it. ## 6. Temporary / Local Runtime Files diff --git a/docs/HANDOFF_TEMPLATE.md b/docs/HANDOFF_TEMPLATE.md index 228aa3b..47a4ae7 100644 --- a/docs/HANDOFF_TEMPLATE.md +++ b/docs/HANDOFF_TEMPLATE.md @@ -45,11 +45,27 @@ Task: - Local CCRA report: - Owner decision: - Returned output: +- Findings confirmation: - Helper outputs: - Accepted actions: - Deferred or escalated findings: -## 11. Suggested Next Tasks +## 11. Round Conductor Status + +- Public round: +- Round charter: +- Current local pass: +- Findings awaiting Owner decision: +- Items accepted for Codex repair: +- Items rejected: +- Items deferred: +- Items escalated to Web CCRA: +- Validation / routing diff evidence: +- Stop condition status: +- Web CCRA bundle path: +- Local CCRA report included in Web bundle?: + +## 12. Suggested Next Tasks 1. 2. diff --git a/docs/PROJECT_BRIEF.md b/docs/PROJECT_BRIEF.md index 648b35c..530f44f 100644 --- a/docs/PROJECT_BRIEF.md +++ b/docs/PROJECT_BRIEF.md @@ -77,3 +77,17 @@ First-version constraints: - 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`. + +## 8. Round Conductor Trial + +The project may use the Round Conductor protocol in `docs/ROUND_AUTOMATION_PROTOCOL.md` for Round 05 and later trial runs. + +The Round Conductor is the main Codex session acting as a project-local orchestrator. It may prepare round charters, run Local CCRA passes, extract Chinese findings confirmation items, and implement Owner-accepted repairs. + +Constraints: + +- Owner / Web CCRA defines the public round goal before the conductor starts. +- Codex must write `findings-confirmation.md` before asking Owner to decide Local CCRA findings. +- Codex may repair only findings recorded in `owner-decision.md` as `accept_for_codex_fix`. +- The protocol does not create a generic Skill or move reviewer governance into this repository. +- Web CCRA remains the formal review lane for key product and lifecycle gates. diff --git a/docs/ROUND_AUTOMATION_PROTOCOL.md b/docs/ROUND_AUTOMATION_PROTOCOL.md new file mode 100644 index 0000000..9e236c1 --- /dev/null +++ b/docs/ROUND_AUTOMATION_PROTOCOL.md @@ -0,0 +1,255 @@ +# Round Automation Protocol + +version: 0.1 + +last_updated: 2026-06-19 + +status: Round 05 trial protocol + +## 1. Purpose + +This document defines the project-local Round Conductor protocol for reducing manual work around Local CCRA review loops. + +It does not define the `ccra-local-reviewer` Agent, CCPE Agent Runtime, or reusable automation Skills. + +The goal is to automate low-value file handling, validation, review submission, pass tracking, and Web bundle preparation while keeping Owner judgment at the required gates. + +## 2. Scope + +Round automation v0.1 covers local review orchestration: + +```text +Owner / Web CCRA defines a public round goal +-> Codex creates a round charter and local review pass +-> Codex prepares context, helper outputs, invocation packet, and prompts +-> Codex invokes the real Local CCRA child review session +-> Local CCRA writes review and planning outputs +-> Codex extracts Chinese Owner-facing confirmation items +-> Owner decides which findings are accepted, rejected, deferred, or escalated +``` + +Round automation v0.2 extends the loop after Owner decision: + +```text +Owner accepts findings for Codex repair +-> Codex applies only accepted fixes +-> Codex runs validation and before/after checks +-> Codex opens the next local pass when needed +-> loop stops by explicit stopping conditions +-> Codex prepares the formal Web CCRA bundle when Owner requests it +``` + +## 3. Roles + +### Owner / Web CCRA + +Owner and Web CCRA define the public round goal, non-goals, and product judgment questions. + +Owner decides: + +- whether a finding is accepted for Codex repair; +- whether a finding is rejected; +- whether a finding is deferred to a later round; +- whether a finding needs Web CCRA escalation; +- whether the local loop is complete enough for formal Web review; +- whether a Local CCRA report should be included in a Web upload package. + +### Codex Main Session + +The main Codex session is the Round Conductor. + +It may: + +- create round-charter and local-pass files; +- run deterministic helper Skills and project validation; +- invoke a real child Local CCRA session; +- summarize Local CCRA findings into Chinese confirmation items; +- implement Owner-accepted fixes; +- run post-fix validation and behavior comparisons; +- prepare a Web CCRA bundle after Owner direction. + +It must not: + +- treat Local CCRA output as Owner approval; +- repair findings before Owner decision; +- expand round scope without confirmation; +- upgrade model lifecycle status; +- replace Web CCRA review at key product gates. + +### Local CCRA Child Session + +The Local CCRA child session is the reviewer. + +It is read-only with respect to product files and writes review outputs into the local review run directory. + +## 4. Round Charter + +Before starting a public round, Codex should create or update a round charter in `reports/` when the Owner / Web CCRA guidance is concrete enough to execute. + +Recommended filename: + +```text +reports/Round05_round_conductor_charter_YYYY-MM-DD.md +``` + +The charter should include: + +- public round label; +- source of Owner / Web CCRA guidance; +- round goal; +- explicit non-goals; +- in-scope files or asset areas; +- required validation; +- expected Local CCRA pass path; +- stopping conditions; +- open product questions. + +The charter is a process record. It is not a model asset and does not override canonical model JSON, model cards, selector rules, or regression cases. + +## 5. Local Pass File Contract + +Each Local CCRA pass follows the existing path rule: + +```text +local_ccra_reviews/// +``` + +In addition to the existing Local CCRA files, each formal automated pass should contain: + +```text +findings-confirmation.md +``` + +`findings-confirmation.md` is written by the Codex main session after reading: + +- `04_LOCAL_CCRA_REVIEW_REPORT.md` +- `next-review-requirements.md` +- `returned-output.md` + +It is not a replacement for the full review report. + +## 6. Findings Confirmation Format + +`findings-confirmation.md` must be written in Chinese and should extract only the core Owner decision items. + +Each item should use this shape: + +```text +### F-001: <中文短标题> + +- 核心确认事项： +- Local CCRA 建议： +- Codex 建议处理： +- 建议决策：accept_for_codex_fix | reject | defer_to_future_round | escalate_to_web_ccra | owner_clarification_required | accept_as_known_limit +- 若接受，Codex 可改范围： +- 若不接受，影响： +- 证据路径： +- 需要 Owner 回答： +``` + +Rules: + +- Do not copy the whole Local CCRA report. +- Do not hide uncertainty; if the report is unclear, mark `owner_clarification_required`. +- Preserve the distinction between Local CCRA recommendation and Codex implementation recommendation. +- Include enough evidence paths for the Owner to open the original report when needed. +- Use plain Chinese decision language, not long audit prose. + +## 7. Owner Decision Gate + +Codex may not start repair for a Local CCRA finding until `owner-decision.md` records the Owner decision. + +Allowed decision states: + +```text +accept_for_codex_fix +reject +defer_to_future_round +escalate_to_web_ccra +owner_clarification_required +accept_as_known_limit +``` + +Codex may only implement findings marked `accept_for_codex_fix`. + +For all other states, Codex should preserve the item in the next handoff or Web bundle questions when relevant. + +## 8. Repair Loop + +After Owner decision, Codex may enter the v0.2 repair loop. + +Allowed repair behavior: + +- modify only files in the confirmed round scope; +- keep model JSON, cards, selector rules, regression cases, and reports synchronized; +- run index checks, model validation, selector checks, routing before/after comparisons, and whitespace checks as applicable; +- document every change in the round conductor status or handoff report; +- open the next local pass when validation or Local CCRA requirements call for it. + +Forbidden repair behavior: + +- adding a third model; +- adding an LLM selector, RAG system, database, frontend, backend, user system, or platform service; +- upgrading lifecycle or stability status based only on Local CCRA; +- modifying Local CCRA reviewer outputs; +- treating dry-run gates as executed validation; +- treating helper warnings as automatic blockers without triage. + +## 9. Stopping Conditions + +The local loop should stop when one of these is true: + +- Local CCRA reports no current-scope blocker or major finding, and remaining findings are rejected, deferred, escalated, or accepted as known limits by Owner. +- The current pass identifies only Web CCRA or product judgment questions. +- Owner decides the round is ready for Web review. +- Owner decides to pause the round. +- The loop reaches three local passes for the same public round without clearing the same blocking class. + +If the three-pass limit is reached, Codex should summarize the repeated blocker and ask Owner whether to continue, defer, or escalate. + +## 10. Web Bundle Preparation + +After the local loop stops and Owner requests Web review, Codex prepares the formal Web CCRA bundle under: + +```text +ccra_review_bundle/round-NN_YYYY-MM-DD_topic/ +``` + +The Web bundle should summarize: + +- public round goal; +- changes made in the public round and local passes; +- validation and routing-diff evidence; +- unresolved Owner / Web CCRA questions; +- explicit non-goals and deferred items. + +By default, do not include `04_LOCAL_CCRA_REVIEW_REPORT.md` in the Web bundle. + +Include a Local CCRA report only when Owner explicitly asks Web CCRA to review local findings. + +## 11. Supplier Boundary + +This protocol is project-local. + +Route future needs as follows: + +- CCPE: reviewer contract, runtime invocation, session continuation, review rubric, lifecycle authority, stopping-condition governance. +- skills-vault: only deterministic, reusable automation extracted from repeated project use. +- this repository: product-specific round state, local pass records, Owner decisions, applied fixes, validation outputs, and Web bundle assembly. + +Do not create a reusable Skill merely because this protocol exists. Extract only after repeated use proves a deterministic cross-project operation. + +## 12. Round 05 Startup Checklist + +At the start of Round 05, the new Codex session should: + +1. Read `AGENTS.md`. +2. Read `reports/Codex新会话交接文档_LocalCCRA自动化讨论上下文_2026-06-19.md`. +3. Read this protocol. +4. Read `local_ccra_reviews/README.md`. +5. Read `knowledge_assets/10_本地CCRA评审机制说明.md`. +6. Create the Round 05 charter from Owner / Web CCRA guidance. +7. Confirm the first Local CCRA pass path. +8. Prepare helper policy fields for v0.1.2. +9. Run the Local CCRA pass through a real child session. +10. Produce `findings-confirmation.md` before asking Owner to decide findings. diff --git a/docs/WORKFLOW.md b/docs/WORKFLOW.md index bdef148..8f0100a 100644 --- a/docs/WORKFLOW.md +++ b/docs/WORKFLOW.md @@ -120,10 +120,11 @@ Workflow: 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/`. +11. Codex writes `findings-confirmation.md` in Chinese, extracting the core Owner decision items from the Local CCRA report and planning output. +12. Owner records accepted, rejected, deferred, escalated, known-limit, or clarification-needed findings in `owner-decision.md`. +13. Codex executes only Owner-accepted actions in the main project session. +14. A follow-up Local CCRA review uses the next local pass label, such as `02/`. +15. After Local CCRA and Owner acceptance, Codex creates the formal Web CCRA bundle under `ccra_review_bundle/round-NN_YYYY-MM-DD_topic/`. Rules: @@ -134,12 +135,35 @@ Rules: - 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. +- `findings-confirmation.md` is an Owner-facing Chinese extraction aid, not a replacement for `04_LOCAL_CCRA_REVIEW_REPORT.md`. +- Codex must not repair a Local CCRA finding until the Owner decision is recorded in `owner-decision.md`. - 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. - Full Round-level automation is a separate workflow/orchestrator design topic, not part of the Local CCRA reviewer contract. - `skills-vault` receives a request only after CCPE or the owner decides that a companion operation is reusable deterministic automation. +## 5.3 Round Conductor Workflow + +For the project-local Round Conductor protocol, see `docs/ROUND_AUTOMATION_PROTOCOL.md`. + +Round automation v0.1 automates Local CCRA orchestration, file preparation, helper execution, real child-session review submission, and Chinese findings confirmation. + +Round automation v0.2 additionally permits Codex to enter a repair loop after Owner decision, but only for findings marked `accept_for_codex_fix`. + +Round Conductor rules: + +1. Owner / Web CCRA defines the public round goal before Codex starts the round. +2. Codex records the public round goal, non-goals, validation expectations, and stopping conditions in a round charter under `reports/`. +3. Codex prepares and runs each Local CCRA pass under `local_ccra_reviews///`. +4. Codex writes `findings-confirmation.md` before asking for Owner decision. +5. Owner records decisions in `owner-decision.md`. +6. Codex repairs only `accept_for_codex_fix` items. +7. Codex runs validation and before/after behavior checks appropriate to the change. +8. Codex starts another local pass only when accepted fixes or Local CCRA requirements justify it. +9. Codex stops the local loop when the stopping conditions in `docs/ROUND_AUTOMATION_PROTOCOL.md` are met. +10. Codex prepares the formal Web CCRA bundle only after Owner requests Web review. + ## 6. Supplier Request Workflow When this repository needs a capability owned by a neighboring repository: diff --git a/docs/model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md b/docs/model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md index ad7460a..9393aeb 100644 --- a/docs/model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md +++ b/docs/model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md @@ -157,7 +157,7 @@ Do not: - create a third model; - summarize the whole source instead of extracting cases; - quote long source passages; -- pretend draft cases are owner-approved. +- pretend draft cases have Owner confirmation. ## 7. Promotion Path @@ -172,4 +172,3 @@ raw source ``` Only owner-reviewed cases may become machine-readable calibration or regression assets. - diff --git a/knowledge_assets/10_本地CCRA评审机制说明.md b/knowledge_assets/10_本地CCRA评审机制说明.md index 9a8a052..d640700 100644 --- a/knowledge_assets/10_本地CCRA评审机制说明.md +++ b/knowledge_assets/10_本地CCRA评审机制说明.md @@ -1,6 +1,6 @@ # 本地 CCRA 评审机制说明 -version: 0.3 +version: 0.4 last_updated: 2026-06-19 @@ -87,6 +87,7 @@ helper-outputs/ next-review-requirements.md returned-output.md 05_WEB_LOCAL_CCRA_COMPARISON.md +findings-confirmation.md owner-decision.md ``` @@ -102,6 +103,7 @@ owner-decision.md - `next-review-requirements.md`：同一子会话第二回合产出的下一轮评审要求与提交资料规划。 - `returned-output.md`：子会话返回内容或报告路径记录。 - `05_WEB_LOCAL_CCRA_COMPARISON.md`：可选的主会话比较笔记，用于把 Local CCRA 输出与 Web CCRA / GPT 反馈对照后调优。 +- `findings-confirmation.md`：主会话用中文摘录 Local CCRA findings 的核心确认事项，供 Owner 快速决策。 - `owner-decision.md`：Owner 对 findings 的接受、拒绝、延后或升级判断。 ## 6. 运行流程 @@ -116,6 +118,7 @@ Owner 决定需要本地评审 -> Codex 调起 CCPE Agent Runtime 子会话并记录 child_session_id -> review_turn: ccra-local-reviewer 只读评审资料并写本地评审报告 -> planning_turn: 同一 child_session_id 继续，写下一轮评审要求与提交资料规划 +-> Codex 主会话写 findings-confirmation.md，提取中文核心确认事项 -> Owner 写 decision -> Codex 根据 accepted findings 修复 -> 必要时进入下一次本地评审 @@ -214,30 +217,42 @@ Local CCRA 的 companion automation 不直接提交给 `skills-vault`。应先 ## 10. 自动化边界 -当前 Local CCRA 机制只定义本地初审的 reviewer/runtime 使用方式，不定义完整轮次自动化。 +Local CCRA 机制只定义本地初审的 reviewer/runtime 使用方式，不把 `ccra-local-reviewer` 变成执行者。 -完整 Round 级自动化，例如： +项目侧可以另行定义 Round Conductor 协议来减少人工搬运和重复操作。当前协议见： + +```text +docs/ROUND_AUTOMATION_PROTOCOL.md +``` + +Round Conductor v0.1 范围： ```text Owner/Web 确定 Round N 规划 --> 项目自动执行 Round N 工作 --> 自动提交 Local CCRA 初审 --> 自动修复 N.1 / N.2 / N.x --> 自动汇总本地变化并构造 Web CCRA 正式评审包 +-> Codex 创建 round charter 和 Local CCRA pass +-> Codex 准备上下文、helper 输出、调用包和提示词 +-> Codex 调起真实 Local CCRA 子会话 +-> Local CCRA 输出 review_turn / planning_turn +-> Codex 写 findings-confirmation.md，摘录中文核心确认事项 +-> Owner 写 owner-decision.md ``` -属于后续的 workflow / orchestrator 设计问题，应另开会话或另写需求讨论。 +Round Conductor v0.2 范围： -原因是这会涉及： +```text +Owner 接受 findings +-> Codex 只处理 accept_for_codex_fix 项 +-> Codex 运行验证和 before/after 行为检查 +-> 必要时进入下一次本地评审 pass +-> 满足停止条件后准备正式 Web CCRA bundle +``` -- Owner 参与点； -- 自动修复边界； -- Local CCRA findings 的接受 / 拒绝 / 延后协议； -- 多次本地评审的停止条件； -- 正式 Web bundle 的生成策略； -- 是否需要项目侧 runtime、CCPE runtime 或 skills-vault deterministic helper。 +这仍然不是无人值守自动修复。必须保留： -这些内容不应混入 `ccra-local-reviewer` 本体定义。 +- Round 目标和非目标的 Owner / Web CCRA 确认； +- findings 的 Owner decision gate； +- 生命周期升级、模型范围扩大、第三模型扩展、Web bundle 是否包含 Local CCRA report 的人工判断； +- Web CCRA 对关键产品节点的正式评审。 ## 11. 非目标 @@ -250,7 +265,7 @@ Local CCRA 不做： - model card 修改； - regression case 修改； - review bundle 创建； -- Round 级自动化编排； +- Round Conductor 的 Owner decision 或修复授权； - 第三模型扩展； - LLM selector、RAG、数据库、前端、后端或平台化功能。 diff --git a/local_ccra_reviews/README.md b/local_ccra_reviews/README.md index 87f0493..6ee8388 100644 --- a/local_ccra_reviews/README.md +++ b/local_ccra_reviews/README.md @@ -87,6 +87,7 @@ helper-outputs/ next-review-requirements.md returned-output.md 05_WEB_LOCAL_CCRA_COMPARISON.md +findings-confirmation.md owner-decision.md ``` @@ -105,7 +106,8 @@ File roles: - `next-review-requirements.md`: same-child-session planning output that defines the next review's required materials, evidence, and open Owner/Web decisions. - `returned-output.md`: the raw returned output from the child reviewer, or a pointer to the report if the report is the returned output. - `05_WEB_LOCAL_CCRA_COMPARISON.md`: optional main-session comparison between Local CCRA output and Web CCRA / GPT feedback for pilot tuning. -- `owner-decision.md`: accepted, rejected, deferred, or escalated findings. +- `findings-confirmation.md`: Chinese Owner-facing extraction of core findings requiring decision before Codex repair. +- `owner-decision.md`: Owner decision states for findings, such as `accept_for_codex_fix`, `reject`, `defer_to_future_round`, or `escalate_to_web_ccra`. ## 5. Runtime Rules @@ -118,6 +120,8 @@ When the owner asks for Local CCRA review: 5. `review_turn`: `ccra-local-reviewer` writes `04_LOCAL_CCRA_REVIEW_REPORT.md`. 6. `planning_turn`: the same child session continues from the first-turn report and writes `next-review-requirements.md` when next-round planning is requested. 7. `ccra-local-reviewer` does not modify product files, selector rules, model cards, regression cases, review bundles, or Owner decisions. +8. The main Codex session writes `findings-confirmation.md` in Chinese before asking Owner to decide findings. +9. Codex does not repair a finding until Owner records the decision in `owner-decision.md`. The default formal pattern is two turns in the same child session: @@ -151,6 +155,7 @@ Owner requests Local CCRA review -> invoke CCPE Agent Runtime child session -> review_turn writes LOCAL_CCRA_REVIEW_REPORT -> planning_turn writes next-review-requirements when needed +-> Codex writes findings-confirmation.md in Chinese -> Owner records decision -> Codex executes accepted actions -> next local review pass uses the next pass label if needed @@ -172,6 +177,36 @@ lifecycle_scan_scope: current_review_bundle | changed_files | knowledge_assets | `returned-output.md` should preserve a compact Owner-facing summary, including final action recommendation, blocking status, required next action, output paths, and evidence limitations. +`findings-confirmation.md` should preserve the Owner decision surface in Chinese. Each item should include: + +- core confirmation question; +- Local CCRA recommendation; +- Codex implementation recommendation; +- proposed decision state; +- allowed repair scope if accepted; +- impact if not accepted; +- evidence paths; +- exact Owner question when clarification is required. + +Allowed decision states are: + +```text +accept_for_codex_fix +reject +defer_to_future_round +escalate_to_web_ccra +owner_clarification_required +accept_as_known_limit +``` + +Only `accept_for_codex_fix` authorizes Codex to modify project files for that finding. + +For the broader Round Conductor protocol, see: + +```text +docs/ROUND_AUTOMATION_PROTOCOL.md +``` + ## 7. Relationship To Web CCRA Bundles `ccra_review_bundle/` remains the formal Web CCRA / GPT upload archive. @@ -197,5 +232,6 @@ Local CCRA review must not: - Add LLM selector, RAG, database, frontend, backend, user system, or platform behavior. - Turn `ccra-local-reviewer` into an implementer. - Implement full Round-level automation or autonomous multi-pass repair loops. +- Start repair before Owner decision. - Store canonical CCPE artifacts in this repository. - Store reusable Skill source in this repository. diff --git a/reports/Codex新会话交接文档_Round自动化规则调整_2026-06-19.md b/reports/Codex新会话交接文档_Round自动化规则调整_2026-06-19.md new file mode 100644 index 0000000..4f3d801 --- /dev/null +++ b/reports/Codex新会话交接文档_Round自动化规则调整_2026-06-19.md @@ -0,0 +1,188 @@ +# Codex 新会话交接文档：Round 自动化规则调整 + +Date: 2026-06-19 + +## 1. 本文档目的 + +本文档用于下一次 Codex 新会话进入 Round 05 和 Local CCRA 正式处理流程。 + +本次会话没有启动 Round 05 内容工作，也没有运行正式 Local CCRA review。 + +本次只完成 Round 自动化 v0.1 + v0.2 的项目侧文件协议调整。 + +## 2. Owner 已确认的共识 + +Owner 同意： + +- 先做 v0.1 + v0.2 的文件协议设计，不急着写通用 Skill。 +- Round 自动化 v0.1 不只做本地评审编排；在 Owner 确认 findings 后，允许 Codex 自动进入 5.1 修复。 +- 修复前必须有一次 Owner decision gate。 +- Codex 需要把 Local CCRA findings 摘录成中文核心确认事项，供 Owner 快速确认；Owner 不清楚时再自行打开完整评审报告和规划意见。 + +## 3. 新增核心规则文件 + +新增： + +```text +docs/ROUND_AUTOMATION_PROTOCOL.md +``` + +该文件定义项目本地 Round Conductor 协议。 + +重点： + +- v0.1：自动化 Local CCRA 编排、上下文准备、helper 输出、真实子会话递交、中文 findings 确认。 +- v0.2：Owner decision 后，Codex 只处理 `accept_for_codex_fix` 项，并进入下一次本地 review pass。 +- 不创建通用 Skill。 +- 不把 `ccra-local-reviewer` 变成执行者。 +- 不替代 Owner / Web CCRA / 生命周期权限。 + +## 4. 新增 Local CCRA pass 文件 + +正式自动化 pass 应新增： + +```text +findings-confirmation.md +``` + +该文件由主 Codex 会话在 Local CCRA 输出后编写，必须用中文摘录核心确认事项。 + +推荐条目格式： + +```text +### F-001: <中文短标题> + +- 核心确认事项： +- Local CCRA 建议： +- Codex 建议处理： +- 建议决策：accept_for_codex_fix | reject | defer_to_future_round | escalate_to_web_ccra | owner_clarification_required | accept_as_known_limit +- 若接受，Codex 可改范围： +- 若不接受，影响： +- 证据路径： +- 需要 Owner 回答： +``` + +`findings-confirmation.md` 不是完整评审报告替代品。它只负责把 Owner 需要确认的事项压缩出来。 + +## 5. Owner Decision Gate + +Codex 不得在 `owner-decision.md` 之前修复 Local CCRA findings。 + +允许的状态： + +```text +accept_for_codex_fix +reject +defer_to_future_round +escalate_to_web_ccra +owner_clarification_required +accept_as_known_limit +``` + +只有 `accept_for_codex_fix` 授权 Codex 修改项目文件。 + +## 6. 已同步的规则文件 + +本次同步了： + +```text +AGENTS.md +README.md +PROJECTS.md +docs/PROJECT_BRIEF.md +docs/WORKFLOW.md +docs/DATA_CONTRACT.md +docs/DECISIONS.md +docs/FILE_TAXONOMY.md +docs/HANDOFF_TEMPLATE.md +local_ccra_reviews/README.md +knowledge_assets/10_本地CCRA评审机制说明.md +reports/README.md +``` + +同时修正两个旧状态用语： + +```text +docs/DECISIONS.md +docs/model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md +``` + +修正原因：lifecycle scan 对旧 `owner-approved` 表述报 blocker。已改成不声称批准状态的表述。 + +## 7. 验证结果 + +已运行： + +```powershell +python scripts\rebuild_indexes.py --check +python scripts\validate_model_library.py +git diff --check +conda run -n skills-vault python C:\Users\wangq\.agents\skills\lifecycle-status-guard-scan\scripts\lifecycle_status_guard_scan.py --scan-root docs --config local_ccra_reviews\round-04\pilot-02\lifecycle-guard-config.yaml --output-dir reports\round_automation_lifecycle_status_guard_scan_2026-06-19 +``` + +结果： + +- index check passed +- validation passed +- staged-independent whitespace check passed; only Windows LF-to-CRLF warnings +- lifecycle status guard scan passed + +Lifecycle scan report： + +```text +reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.md +``` + +## 8. Round 05 新会话启动顺序 + +下一次新会话进入 Round 05 时，建议先读： + +1. `AGENTS.md` +2. `reports/Codex新会话交接文档_LocalCCRA自动化讨论上下文_2026-06-19.md` +3. `reports/Codex新会话交接文档_Round自动化规则调整_2026-06-19.md` +4. `docs/ROUND_AUTOMATION_PROTOCOL.md` +5. `local_ccra_reviews/README.md` +6. `knowledge_assets/10_本地CCRA评审机制说明.md` +7. Owner / Web CCRA 提供的 Round 05 规划或指导 + +## 9. Round 05 第一动作 + +拿到 Owner / Web CCRA 的 Round 05 指导后，Codex 应先创建或更新 Round 05 charter： + +```text +reports/Round05_round_conductor_charter_YYYY-MM-DD.md +``` + +charter 至少写明： + +- public round label +- guidance source +- round goal +- explicit non-goals +- in-scope files or asset areas +- required validation +- expected Local CCRA pass path +- stopping conditions +- open product questions + +然后再进入 Round 05 执行和 Local CCRA pass。 + +## 10. 当前未做事项 + +本次未做： + +- 未启动 Round 05。 +- 未创建 Round 05 charter。 +- 未创建 `local_ccra_reviews/round-05/...`。 +- 未调用 Local CCRA 子会话。 +- 未实现 Round Conductor 脚本。 +- 未创建 skills-vault 请求。 +- 未创建 CCPE 新需求。 + +## 11. 下一步建议 + +1. Owner / Web CCRA 给出 Round 05 目标和指导。 +2. Codex 按 `docs/ROUND_AUTOMATION_PROTOCOL.md` 创建 Round 05 charter。 +3. Codex 执行 Round 05 工作并准备 Local CCRA pass 01。 +4. Local CCRA 输出后，Codex 写 `findings-confirmation.md`，只问 Owner 需要确认的中文核心事项。 +5. Owner decision 后，Codex 只修复 `accept_for_codex_fix` 项，并进入下一次 local pass 或 Web bundle 准备。 diff --git a/reports/README.md b/reports/README.md index c3df928..944ac49 100644 --- a/reports/README.md +++ b/reports/README.md @@ -21,5 +21,14 @@ Current reports: - `Codex新会话交接文档_Round04.1关闭与Round05准备_2026-06-18.md` - `Codex_本地CCRA规划落地_2026-06-19.md` - `Codex新会话交接文档_LocalCCRA自动化讨论上下文_2026-06-19.md` +- `Codex新会话交接文档_Round自动化规则调整_2026-06-19.md` +- `round_automation_lifecycle_status_guard_scan_2026-06-19/` + +Round Conductor charters and summaries may use filenames such as: + +```text +Round05_round_conductor_charter_YYYY-MM-DD.md +Round05_round_conductor_status_YYYY-MM-DD.md +``` Reports should separate verified facts, assumptions, unresolved questions, and suggested next tasks. diff --git a/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.json b/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.json new file mode 100644 index 0000000..674f908 --- /dev/null +++ b/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.json @@ -0,0 +1,49 @@ +{ + "scan_root": "C:\\Users\\wangq\\Documents\\Codex\\work-projects\\the-mindscape-of-bro-tsong\\docs", + "config_path": "C:\\Users\\wangq\\Documents\\Codex\\work-projects\\the-mindscape-of-bro-tsong\\local_ccra_reviews\\round-04\\pilot-02\\lifecycle-guard-config.yaml", + "files_scanned": [ + "CHATGPT_HANDOFF_RULES.md", + "CONTENT_STABILIZATION_PROTOCOL.md", + "DATA_CONTRACT.md", + "DECISIONS.md", + "FILE_TAXONOMY.md", + "GPT_PLAN_LOCALIZATION_PROTOCOL.md", + "HANDOFF_TEMPLATE.md", + "INDEX_MAINTENANCE_PROTOCOL.md", + "INTELLECTUAL_ARCHAEOLOGY_DEPTH_GATE.md", + "KNOWLEDGE_ASSET_RULES.md", + "MODEL_CARD_CONTRACT.md", + "model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md", + "model_case_preprocessing/qpi/README.md", + "model_case_preprocessing/README.md", + "MODEL_EXTRACTION_RULES.md", + "MODEL_EXTRACTION_WORKFLOW.md", + "NON_GOALS.md", + "PROJECT_BRIEF.md", + "QPI_CONTEXTUAL_ROUTING_RULES.md", + "ROUND_AUTOMATION_PROTOCOL.md", + "superpowers/plans/2026-06-16-model-extraction-contract-and-workflow.md", + "superpowers/plans/2026-06-16-project-initialization.md", + "superpowers/plans/2026-06-17-contract-hardening-selector-calibration.md", + "superpowers/plans/2026-06-18-round04-1-selector-rule-patch.md", + "superpowers/plans/2026-06-18-round04-blind-routing-evaluation.md", + "WORKFLOW.md" + ], + "possible_overclaims": [], + "field_level_findings": [], + "phrase_level_findings": [], + "missing_evidence_markers": [], + "warnings": [], + "blocking_errors": [], + "observations": [], + "machine_readable_summary": { + "status": "PASS", + "files_scanned_count": 26, + "field_finding_count": 0, + "phrase_finding_count": 0, + "missing_evidence_count": 0, + "warning_count": 0, + "blocking_count": 0, + "observation_count": 0 + } +} \ No newline at end of file diff --git a/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.md b/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.md new file mode 100644 index 0000000..bd471fc --- /dev/null +++ b/reports/round_automation_lifecycle_status_guard_scan_2026-06-19/lifecycle-status-guard-scan.md @@ -0,0 +1,50 @@ +# Lifecycle Status Guard Scan + +## Summary + +- Status: `PASS` +- Files scanned: 26 +- Blocking findings: 0 +- Warnings: 0 +- Evidence-present observations: 0 + +## Blocking Findings + +- None + +## Warnings + +- None + +## Observations + +- None + +## Files Scanned + +- `CHATGPT_HANDOFF_RULES.md` +- `CONTENT_STABILIZATION_PROTOCOL.md` +- `DATA_CONTRACT.md` +- `DECISIONS.md` +- `FILE_TAXONOMY.md` +- `GPT_PLAN_LOCALIZATION_PROTOCOL.md` +- `HANDOFF_TEMPLATE.md` +- `INDEX_MAINTENANCE_PROTOCOL.md` +- `INTELLECTUAL_ARCHAEOLOGY_DEPTH_GATE.md` +- `KNOWLEDGE_ASSET_RULES.md` +- `MODEL_CARD_CONTRACT.md` +- `model_case_preprocessing/qpi/CASE_PREPROCESSING_WORKFLOW.md` +- `model_case_preprocessing/qpi/README.md` +- `model_case_preprocessing/README.md` +- `MODEL_EXTRACTION_RULES.md` +- `MODEL_EXTRACTION_WORKFLOW.md` +- `NON_GOALS.md` +- `PROJECT_BRIEF.md` +- `QPI_CONTEXTUAL_ROUTING_RULES.md` +- `ROUND_AUTOMATION_PROTOCOL.md` +- `superpowers/plans/2026-06-16-model-extraction-contract-and-workflow.md` +- `superpowers/plans/2026-06-16-project-initialization.md` +- `superpowers/plans/2026-06-17-contract-hardening-selector-calibration.md` +- `superpowers/plans/2026-06-18-round04-1-selector-rule-patch.md` +- `superpowers/plans/2026-06-18-round04-blind-routing-evaluation.md` +- `WORKFLOW.md`