# Guidance Pack And Compliance Matrix

## 1. Input Guidance

Round 03 implements two connected Owner/GPT requirements:

1. harden the model-library framework without expanding product scope;
2. after owner-provided QPI case data became available, process those cases into auditable QPI digest, calibration, and regression assets.

The same non-goals apply across both parts:

- do not add a third model;
- do not upgrade stable;
- do not build a full answer system;
- do not introduce an LLM selector;
- do not introduce database, vector database, RAG, frontend, backend service, user accounts, or platform features.

## 2. Compliance Matrix

| Requirement | Status | Evidence |
| --- | --- | --- |
| Per-round CCRA bundle directory | Done | `ccra_review_bundle/round-02_...`, `round-03_...` |
| Preserve second-round bundle | Done | Existing second-round files live under `round-02_2026-06-16_second-audit/` |
| Add `structured_output_contract` to schema properties | Done | `schemas/model_card.schema.json` |
| Do not make QPI/IA fields global top-level required | Done | Schema allows object; validator performs model-specific checks |
| QPI required runtime fields | Done | `models/qpi.model.json`, `scripts/validate_model_library.py` |
| IA required runtime fields | Done | `models/intellectual_archaeology.model.json`, `scripts/validate_model_library.py` |
| Fix QPI report missing `classification` | Done | `reports/content_review_report_v0.2.md` |
| Add QPI contextual routing rules | Done | `docs/QPI_CONTEXTUAL_ROUTING_RULES.md` |
| Add IA depth gate rules | Done | `docs/INTELLECTUAL_ARCHAEOLOGY_DEPTH_GATE.md` |
| Make selector rules executable source | Done | `selector/selector_rules.json`, `scripts/run_selector_demo.py` |
| Hard no-call gate | Done | `selector/selector_rules.json`, `scripts/run_selector_demo.py` |
| Keep models `draft / B / pending` | Done | `models/model_index.json` |
| Process owner-reviewed QPI case drafts | Done | `reports/model_case_preprocessing/qpi/round-01/*.cases.md` |
| Promote case digests | Done | `selector/qpi_case_digests.json`, 62 cases |
| Promote selector calibration inputs | Done | `selector/selector_calibration_inputs.json`, 83 inputs |
| Promote selected regression cases | Done | `tests/qpi.regression.json`, 46 total QPI regression cases |
| Keep APTC as context note, not a model | Done | International-college case guidance and no third-model policy |

## 3. QPI Contract Delta

New or hardened QPI output fields include:

- `classification_scope`
- `is_provisional`
- `subject_position`
- `scenario_context`
- `responsibility_scope`
- `context_sufficiency`
- `missing_context`
- `expectation_reality_gap`
- `success_criteria_stability`
- `hard_feedback_availability`
- `governance_load`
- `dynamic_stage`
- `possible_trajectory`
- `classification_by_viewpoint`
- `frame_shift_risk` as a documented risk concept through `misclassification_risk`

Required runtime fields enforced by validator:

- `classification_scope`
- `is_provisional`
- `subject_position`
- `scenario_context`
- `responsibility_scope`
- `context_sufficiency`
- `missing_context`
- `problem_owner`
- `problem_source`
- `time_scale`
- `scarcity_profile`
- `dominant_scarcity`
- `classification`
- `classification_confidence`
- `evidence_gap`
- `misclassification_risk`
- `recommended_next_step`
- `next_model_candidates`

## 4. Selector Delta

`selector/selector_rules.json` now contains:

- hard no-call signals;
- explicit analysis override phrases;
- complexity signals;
- QPI gate signals;
- IA heavy-depth signals;
- scoring weights;
- per-model base scores and trigger lists.

`scripts/run_selector_demo.py` reads that file at runtime.

## 5. QPI Case Promotion Delta

The owner-reviewed QPI case layer adds a second kind of evidence for review:

- Markdown case files preserve owner review decisions and human-readable reasoning;
- `selector/qpi_case_digests.json` stores compact auditable case summaries;
- `selector/selector_calibration_inputs.json` gives the rule-based selector concrete QPI examples and no-call traps;
- `tests/qpi.regression.json` stores selected high-value regression cases for boundary, misuse, and false-positive prevention.

Not every owner-reviewed case was promoted into regression. Regression was reserved for cases that protect model boundaries, selector behavior, or high-risk Q/P/I/mixed/no-call distinctions.

## 6. Known Limits

- QPI and Intellectual Archaeology remain draft assets.
- The selector is still rule-based and local; passing regression is not evidence of stable behavior in the wild.
- Case digests are owner-reviewed processing artifacts, not raw legal, personnel, financial, or operational findings.
- `frame_shift_risk` can become a separate required field later if Owner/CCRA wants a stricter contract, but this round keeps it under `misclassification_risk`.

