# Review Questions For GPT

## 1. Round-Level Judgment

Please return:

1. pass / revise / block judgment;
2. required corrections, grouped by file;
3. any regression cases that should be added, removed, or downgraded to calibration;
4. any schema, naming, or bundle-structure risk;
5. confirmation that QPI remains a routing model and not a full solution system.

## 2. Framework And Contract Questions

1. Are the QPI v0.3 contextual routing fields the right required runtime output layer?
2. Do `classification_scope`, `is_provisional`, `context_sufficiency`, and `missing_context` sufficiently prevent false high-confidence QPI classification?
3. Are `intra_frame_mixed` and `inter_viewpoint_divergence` separated correctly?
4. Is the Issue-as-governance-load rule acceptable?
5. Are selector hard no-call signals too broad or too narrow?
6. Does the IA heavy-depth gate sufficiently prevent IA from being selected for ordinary QPI cases?

## 3. Case Promotion Questions

1. Are the 62 owner-reviewed QPI case digests faithful to the owner/GPT review decisions?
2. Are the selected 23 new organizational QPI regression cases the right subset, or are there missing high-value regression traps?
3. Are any cases over-promoted into regression when digest/calibration would be enough?
4. Are `classification` and `dominant_scarcity` decisions coherent across similar patterns?
5. Are `intra_frame_mixed` and `inter_viewpoint_divergence` separated consistently in the promoted case layer?
6. Do umbrella / synthesis / subcase / boundary-case markers help reviewability, or do they overcomplicate the QPI case layer?
7. Does the no-call calibration remain narrow and safe?

## 4. Specific High-Risk Decisions To Audit

- `year-end-review-international-college` case 002:
  - `classification: mixed`
  - `dominant_scarcity: path_resource`
  - includes a paired simple-logistics no-call trap.

- `year-end-review-research-office` case 006:
  - `classification: problem`
  - `dominant_scarcity: path_resource`
  - `governance_risk: medium`
  - intentionally lower than similar international-college capacity governance case.

- `year-end-review-research-office` case 002:
  - changed from `inter_viewpoint_divergence` to `intra_frame_mixed`.

- `year-end-review-international-college` case 006:
  - promoted from pricing Problem to trust-system Issue.
  - APTC remains only an owner note, not a new model.

- `year-end-review-research-office` case 001:
  - marked as umbrella case for research identity simulation.

## 5. Required Non-Goal Check

Confirm that the updated framework and case layer still do not imply:

- a third model;
- stable upgrade;
- LLM selector;
- full answer system;
- legal/tax/personnel decision engine;
- RAG / vector database / frontend / backend platform.
