---
artifact_type: ccpe-skill
name: CCRA Findings Classification
skill_id: ccra-findings-classification
author: CCPE System
version: 0.1.0
created: 2026-06-19
updated: 2026-06-19
status: draft
skill_type: evaluation
target_platform: Codex / platform-neutral Markdown
related_models:
  - qpi-front-routing-boundary
related_agents:
  - ccra-local-reviewer
related_runtimes:
  - ccra-local-review
based_on: CCPE System
---

# CCRA Findings Classification

## 1. Purpose

Provide a reusable classification method for CCRA-style review findings.

This Skill is an evaluation method, not script-backed automation.

## 2. Skill Type

```text
evaluation
```

## 3. Trigger Conditions

Use when:

```text
Local CCRA writes a review report
a review finding needs severity
a finding affects Web final review readiness
a finding affects lifecycle or round closure
a finding should be accepted, deferred, or routed to calibration
```

## 4. Input Contract

```yaml
finding_text:
evidence_references:
review_scope:
round_goal:
claimed_status:
affected_files:
downstream_decision:
```

## 5. Output Contract

```yaml
classification: blocker | major | minor | calibration | defer
reason:
blocks_web_final_review: true | false
blocks_lifecycle_change: true | false
owner_decision_required: true | false
recommended_action:
```

## 6. Classification Definitions

### 6.1 blocker

Use when a finding invalidates the review, blocks round closure, blocks Web final review, or creates unacceptable lifecycle / scope risk.

Examples:

```text
missing required evidence
invalid child-session invocation
review relies on main-session roleplay
engineering pass treated as lifecycle approval
selector behavior changed beyond target without documentation
model status upgraded without Owner / CCRA authority
```

### 6.2 major

Use when a finding does not invalidate the whole review but materially weakens the round outcome or requires local tuning before Web final review.

Examples:

```text
important regression evidence is incomplete
review bundle omits a significant report
round goal is partially drifted
non-target behavior change is documented but not evaluated
```

### 6.3 minor

Use when a finding is real but does not block local tuning, round understanding, or Web final review readiness.

Examples:

```text
minor manifest mismatch
non-blocking report naming issue
small documentation gap that does not affect judgment
```

### 6.4 calibration

Use when the finding should improve future policy, selector behavior, examples, regression cases, or review standards rather than trigger immediate patching in the current round.

Examples:

```text
ambiguous routing policy boundary
case useful for future calibration
review behavior difference that needs policy discussion
```

### 6.5 defer

Use when the finding is valid but outside the current round's scope or should be handled after Owner/Web CCRA planning.

Examples:

```text
third-model idea
future product-system feature
non-urgent UX or platform concern
large architecture expansion
```

## 7. Procedure

```text
1. Identify the round goal and current review scope.
2. Identify the evidence supporting the finding.
3. Ask whether the finding invalidates review authenticity or required evidence.
4. Ask whether the finding blocks Web final review or lifecycle change.
5. Ask whether the finding is current-round work or future calibration.
6. Assign the lowest severity that accurately preserves downstream risk.
7. Record owner decision requirement.
```

## 8. Branch Logic

```text
If invocation authenticity is invalid:
  classify as blocker.

If lifecycle promotion lacks required authority:
  classify as blocker.

If issue concerns future policy but current round can proceed:
  classify as calibration.

If issue is true but outside current scope:
  classify as defer.
```

## 9. Stop Conditions

Stop when classification, rationale, downstream blocking status, and recommended action are recorded.

## 10. Failure Handling

If evidence is insufficient, classify the finding based on the risk of the missing evidence. Missing evidence that affects review validity should be `blocker`.

## 11. Validation Checklist

```text
Round goal considered?
Evidence cited?
Classification selected from allowed set?
Owner decision requirement recorded?
Web final review blocking status recorded?
Lifecycle blocking status recorded?
Calibration vs immediate patch distinguished?
```

## 12. Related Runtime Usage

Used by:

```text
runtimes/hybrid/ccra-local-review.runtime.md
```

## 13. Version Notes

```text
v0.1.0:
- Initial CCRA findings classification method.
```