# Quality Gaps / Scrutiny Errata — Overcome Fitness

**Date:** 2026-08-03  
**Scope:** Post-lock scrutiny on Layer 1a GBP snapshot + derived threats  
**Status:** Documented; re-observe required before record is production-usable

## Critical (must re-observe or compute)

| Issue | Fix applied this pass? | Remaining action |
|-------|------------------------|------------------|
| PRIMARY_CATEGORY multi-value + typo | Flagged invalid in inventory | Re-observe single canonical primary + additional list |
| PLACE_ID marked Not observed while in MAPS_URL | **Computed** from URL | None for this field |
| Second feature ID in MAPS_URL ignored | **Logged as related-listing lead** | Verify on Maps |
| OPEN_NOW without datetime+TZ | Flagged | Re-observe with SNAPSHOT_DATETIME + TZ |
| REVIEW_RESPONSES Yes without detail | Flagged inconsistent | Re-observe N of 5 + recency |

## High

| Issue | Fix applied this pass? | Remaining action |
|-------|------------------------|------------------|
| CLAIMED_STATUS Unknown vs signals | **Set Likely Claimed — inferred (2 signals)** | Owner confirm for Tier 1 |
| Services vs category mismatch not threat | **T-012 added** | Confirm on re-observe |

## Structural (schema v1.2)

- Vocabulary: prefer `NOT_PRESENT` vs `NOT_OBSERVED`
- Action-button row must be complete set when any button observed
- Posts: `POSTS_SECTION_PRESENT` + `POST_COUNT`
- `OBSERVATION_SURFACE` required (desktop Maps / mobile / knowledge panel)
- Address: observed string + canonical NAP
- Phone: full digits or NOT_OBSERVED (no partial mask)
- Rules: completeness precondition; severity separate from verification_tier
- Rules log: rule ID, version, inputs, values, output

## Minimum before record is usable

1. Re-observe with surface + datetime+TZ  
2. Canonical primary + additional categories  
3. Full action-button row + review-response detail  
4. Re-run rules with completeness preconditions