# Prompt Authority Boundary

status: draft_m2_boundary_correction
date: 2026-06-20

## Purpose

M2 must not directly implement the GPT-authored prompt plan as canonical prompts in this repository.

The M2 correction is to separate product-local runtime work from CCPE-owned canonical prompt and runtime authority.

## Authority Split

| Surface | Owner | This repository may store | This repository must not store |
| --- | --- | --- | --- |
| Product runtime | `Cognitive-OS-Wantsong` | product-local adapters, manual run records, sample inputs/outputs, product workflow notes, product output formats | canonical CCPE prompt cards, Agent Specs, Runtime Specs, CCRA reviewer specs |
| Canonical prompt/runtime authority | `ccpe-system` | supplier requests under `requirements/ccpe/` | copied canonical artifacts treated as local truth |
| Deterministic automation | `skills-vault` | supplier requests under `requirements/skills-vault/` | reusable Skill source, generic validators, reusable CLIs |

## Product Repository Scope

This repository owns:

- product-specific runtime adapters;
- sample run inputs and outputs;
- manual run records;
- product-specific workflow glue;
- local output formats for internal trace and reader-facing explanation;
- product-side requests to CCPE and skills-vault.

This repository does not own:

- canonical Prompt Cards;
- Agent Specs;
- Runtime Specs;
- model-call protocols;
- evaluation rubrics;
- Local CCRA canonical review protocol;
- reusable deterministic automation tools.

## M2 Prompt Rule

Do not create canonical prompt files in this repository.

If `prompts/` must be created later, every file must be a product-local draft adapter and include this frontmatter:

```yaml
---
authority: product_local_adapter
status: draft
canonical_source: pending_ccpe
not_canonical_ccpe_prompt: true
---
```

Adapter files may reference pending CCPE contracts but cannot claim canonical status.

## Routing Rule

When M2 needs canonical prompt/spec/rubric/protocol authority, write a CCPE request under:

```text
requirements/ccpe/
```

When M2 needs reusable deterministic automation, write a skills-vault request under:

```text
requirements/skills-vault/
```

Do not solve supplier-owned capabilities locally unless the owner explicitly changes the boundary.

## Forbidden During M2a

M2a must not:

- create canonical prompts;
- create `ccra_review_bundle/`;
- start Local CCRA;
- import old prompt packs from the previous project;
- implement a full selector;
- implement reusable validators locally;
- expand the model set.

## Revised M2a Plan

Goal: correct M2 authority boundaries before any prompt/runtime skeleton work.

Deliverables:

- `docs/PROMPT_AUTHORITY_BOUNDARY.md`;
- M2 boundary decisions in `docs/DECISIONS.md`;
- CCPE request for cognitive runtime prompt contracts;
- skills-vault request for deterministic adapter/run manifest tooling if needed;
- request-channel READMEs.

Acceptance:

- no `prompts/` directory is required;
- no canonical CCPE artifact is copied into this repository;
- any missing canonical prompt/spec is represented as a supplier request;
- any reusable deterministic tool is represented as a supplier request.

## Revised M2b Plan

Goal: create only product-local runtime material after M2a boundaries are accepted.

Allowed M2b work:

1. Create product-local draft adapters only if the owner confirms adapter work should start before CCPE supplies canonical Prompt Cards.
2. Use the mandatory adapter frontmatter from this document.
3. Define product-local run input/output shapes for:
   - intake/value assessment;
   - QPI;
   - lens orchestration;
   - Intellectual Archaeology;
   - synthesis/calibration;
   - reader translation;
   - feedback/asset decision.
4. Run one minimal manual sample only after adapters and run format are clearly product-local.
5. Record the run as product evidence, not as review evidence.

M2b must still not start Local CCRA. Local CCRA waits until boundary correction and one minimal manual sample are complete.