# Content Stabilization Protocol

## Principle

Engineering contract PASS is not content stability.

The validation scripts prove that the model library can be parsed, indexed, and checked. They do not prove that a model is semantically correct, sufficiently evidenced, regression-stable, or safe for broad product use.

## Stabilization Gates

A model cannot move beyond `draft` without these review gates:

1. Evidence review.
2. Content review.
3. Regression review.
4. Selector review.
5. Owner / CCRA review.

Each gate must leave a file-backed result under `reports/` or a structured status entry.

## Current Model Rule

For this round:

| Model ID | Status | Stability | Regression Status |
| --- | --- | --- | --- |
| `qpi` | draft | B | pending |
| `intellectual_archaeology` | draft | B | pending |

Do not upgrade either model to stable.

## Current Non-Goals

This round must not:

- Add a third model.
- Connect a full question-answering system.
- Introduce an LLM selector.
- Introduce a vector database.
- Build frontend or backend product surfaces.
- Change `stability_level` from B to A.
- Change `regression_status` from pending to passed.
- Change `status` from draft to stable.

## Draft-Callable Meaning

`draft-callable` is a review conclusion, not a model JSON status value in v0.2.

It means:

- The model remains `status: draft`.
- The model has enough structure for controlled review calls.
- Evidence coverage, regression coverage, selector false-positive protection, and content risks are visible.
- The model still requires Owner / CCRA judgment before any stronger state.

## Required v0.2 Evidence Types

Field support must be classified as:

- `direct_source`: directly supported by source text.
- `derived_from_source`: reasonably inferred from source text.
- `product_decision`: product or selector rule.
- `red_team_inference`: misuse, boundary, or failure inference.
- `owner_decision`: Owner / CCRA judgment.

## Required v0.2 Coverage Status

Each required model field must be marked as:

- `supported`
- `partially_supported`
- `derived`
- `unsupported`
- `needs_owner_review`

## Required Review Status Fields

Content review reports should track:

- `engineering_contract_status`
- `content_review_status`
- `evidence_review_status`
- `regression_review_status`
- `selector_review_status`
