# Signal-to-Noise Checklist

Use this checklist during Phase 1 of the Self-Review SOP.

## Verdict Counts

- [ ] Count Block verdicts: ___
- [ ] Count Flag verdicts: ___
- [ ] Count Pass verdicts: ___
- [ ] Count Ack verdicts: ___
- [ ] Total claims: ___

## Actionability Ratio

Formula: `(Block + Flag) / Total`

- [ ] Calculate ratio: ___
- [ ] Compare to threshold (0.30): PASS / FAIL

## Top Claim Types

List the 5 most frequent claim types:

| Rank | Claim Type | Count | Classification |
|------|------------|-------|----------------|
| 1 | | | Signal / Noise |
| 2 | | | Signal / Noise |
| 3 | | | Signal / Noise |
| 4 | | | Signal / Noise |
| 5 | | | Signal / Noise |

## Signal Classification Criteria

A claim is **Signal** if it helps answer:
- "What do I need to fix before commit?" (Developer)
- "What's the risk posture?" (Auditor)
- "What context should my agent see?" (ADK User)
- "Are we testing the right things?" (SDET)

A claim is **Noise** if:
- It describes build metadata (Cargo.toml version, package name)
- It extracts from test fixtures or mock data
- It duplicates information available elsewhere
- It has no actionable remediation
- It would never block a commit or change a decision

## Noise Source Analysis

For each noise claim type, identify:

| Claim Type | Source Pattern | Noise Cause |
|------------|----------------|-------------|
| | Files: | Reason: |
| | Files: | Reason: |
| | Files: | Reason: |

## Common Noise Patterns

- [ ] Build/package metadata (Cargo.toml, package.json)
- [ ] Test fixtures and mock data
- [ ] Documentation examples
- [ ] Generated code
- [ ] Vendored dependencies
- [ ] Configuration defaults that are correct

## Noise Volume Assessment

- High noise directories: ___
- High noise file patterns: ___
- High noise extractors: ___

## Outcome

- [ ] Actionability ratio meets threshold (>= 0.30)
- [ ] Top noise sources identified
- [ ] Suppression strategy selected (see Decision Point 2)