Cognitive-OS-Wantsong/requirements/ccpe/2026-06-20-m2-cognitive-runtime-prompt-contracts.md

CCPE Request: M2 Cognitive Runtime Prompt Contracts

Date: 2026-06-20

Client repository:

C:\Users\wangq\Documents\Codex\work-projects\Cognitive-OS-Wantsong

Requested supplier repository:

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

1. Product Context

Cognitive-OS-Wantsong is a new product-runtime repository for a lightweight cognitive-processing flow.

The product repo currently owns M0-M1 boundary docs, QPI and Intellectual Archaeology model cards, and the model registry.

The next planned phase is M2, but the GPT-authored M2 plan proposed prompt files without separating:

• product-local runtime adapters;
• canonical Prompt Cards;
• Agent Specs;
• Runtime Specs;
• model-call protocols;
• evaluation rubrics;
• Local CCRA review protocol.

This request asks CCPE to own the canonical contract layer before the product repo creates any canonical-looking prompt assets.

2. Needed Capability

CCPE should define the canonical prompt/runtime contract set for the Cognitive-OS M2 runtime.

Needed canonical artifacts:

1. Prompt Card contract for Intake / Value Assessment.
2. Prompt Card contract for QPI routing.
3. Prompt Card contract for Lens Orchestration.
4. Prompt Card contract for Intellectual Archaeology runner.
5. Prompt Card contract for Synthesis and Calibration.
6. Prompt Card contract for Reader Translation.
7. Prompt Card contract for Feedback and Asset Decision.
8. Runtime Spec for chaining these cards in a manual or semi-automated run.
9. Model-call protocol describing how product-local adapters may invoke or reference canonical prompt contracts.
10. Evaluation rubric for judging internal trace and reader-facing output quality.
11. Boundary rule for when Local CCRA can review the milestone.

3. Why This Belongs In CCPE

This work defines canonical prompt authority, runtime protocol, evaluation rubric, and review criteria.

Those are CCPE responsibilities. The product repo should only hold product-local adapters, sample runs, local output formats, and supplier requests.

4. Current Blocked Task

The product repo should not create canonical prompt files for M2 until the CCPE contract exists.

Allowed interim product work:

• document prompt authority boundaries;
• create product-local draft adapters only with explicit adapter frontmatter;
• run a minimal manual sample only after adapter status is unambiguous.

Blocked canonical work:

prompts/intake-value-assessor.md
prompts/qpi-router.md
prompts/lens-orchestrator.md
prompts/intellectual-archaeology-runner.md
prompts/synthesis-engine.md
prompts/reader-translation-engine.md
prompts/calibration-checker.md

These filenames may exist later only as product-local adapters unless CCPE explicitly supplies canonical placement rules.

5. Input Files And Source Paths

Product repo files:

README.md
AGENTS.md
PROJECTS.md
docs/PROJECT_BRIEF.md
docs/COGNITIVE_WORKFLOW_V0.md
docs/MODEL_MANAGEMENT_V0.md
docs/MODEL_ORCHESTRATION_V0.md
docs/READER_TRANSLATION_LAYER_V0.md
docs/LOCAL_CCRA_MILESTONE_PROTOCOL.md
docs/ASSET_MIGRATION_POLICY.md
docs/DECISIONS.md
models/qpi.md
models/intellectual-archaeology.md
models/model-registry.json

Planning/source references:

C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\强哥的思想宇宙\Cognitive-OS-Wantsong项目总计划 v0.1.md
C:\Users\wangq\Documents\Codex\work-projects\the-mindscape-of-bro-tsong\PROJECTS.md
C:\Users\wangq\Documents\Codex\work-projects\the-mindscape-of-bro-tsong\requirements\

6. Expected Output Artifacts

CCPE should provide or register:

• canonical Prompt Card templates or concrete cards for the seven M2 runtime steps;
• a Runtime Spec for manual chaining and later automation;
• model-call protocol covering model registry lookup, primary/support role limits, and reader translation handoff;
• evaluation rubric for:
  • QPI routing quality;
  • Intellectual Archaeology depth quality;
  • synthesis/calibration quality;
  • reader translation quality;
  • evidence/action-boundary quality;
• Local CCRA milestone-readiness criteria for after the first minimal manual sample.

7. Required Human Gate

Owner approval is required before:

• treating any product-local adapter as canonical;
• copying any CCPE-supplied artifact into this product repo;
• starting Local CCRA;
• expanding beyond QPI and Intellectual Archaeology;
• turning M2 output into stable model governance.

8. Prohibited Behavior

CCPE output should not require this product repo to:

• store canonical Prompt Cards as local truth;
• create a full selector;
• create a full regression suite;
• start Local CCRA before a minimal manual sample;
• recreate old review-bundle or Round Conductor workflows;
• use lite suffixes for model filenames or model IDs.

9. Urgency And Dependency

Urgency: high before M2 prompt work.

Dependency:

• M2a boundary correction can complete immediately in this product repo.
• M2b product-local adapter work can proceed only if adapter authority is clearly marked.
• Canonical prompt/runtime authority waits for CCPE.