Normalize GMB→GBP terminology in Overcome Fitness threat register
This commit is contained in:
@@ -28,7 +28,7 @@ No speculation. No invented gaps. No solution language.
|
||||
- **Data Recency:** 2026-08-02
|
||||
- **Estimated Severity:** Major
|
||||
- **Verification Tier:** Tier 2
|
||||
- **Notes / Context:** Whether a booking tool exists behind the scenes is unknown without owner confirmation. GMB booking state remains separately unresolved.
|
||||
- **Notes / Context:** Whether a booking tool exists behind the scenes is unknown without owner confirmation. GBP booking state remains separately unresolved.
|
||||
- **Human Decision:** Pending
|
||||
|
||||
### Threat ID: T-003
|
||||
@@ -82,7 +82,7 @@ No speculation. No invented gaps. No solution language.
|
||||
- **Human Decision:** Pending
|
||||
|
||||
### Threat ID: T-008
|
||||
- **Title:** Second related GMB listing observed (Overcome Power Cycle)
|
||||
- **Title:** Second related GBP listing observed (Overcome Power Cycle)
|
||||
- **Signal Source:** Google Maps / directory observations
|
||||
- **Evidence Snippet:** Prior audit noted a separate related listing at the same building (different suite) under Overcome Power Cycle.
|
||||
- **Data Recency:** 2025-08
|
||||
@@ -116,7 +116,7 @@ No speculation. No invented gaps. No solution language.
|
||||
- Tier 1 (Verified): 0
|
||||
- Tier 2 (Indicative): 10
|
||||
- Current as of 2026-08-02: T-001, T-002, T-005, T-007 (and partial support for T-003/T-004 via live links)
|
||||
- Still open / higher uncertainty: GMB completeness (affects T-002/T-008 context), deeper social metrics
|
||||
- Still open / higher uncertainty: GBP completeness (affects T-002/T-008 context), deeper social metrics
|
||||
|
||||
## Human Review Gate
|
||||
- [x] Fresh public checks completed for key website paths and FB search label (2026-08-02)
|
||||
@@ -128,6 +128,6 @@ No speculation. No invented gaps. No solution language.
|
||||
- [ ] Human has recorded a decision on each entry
|
||||
- [ ] No invented or speculative threats remain
|
||||
|
||||
Once this gate is signed off (and GMB gap is either resolved or explicitly accepted as blocker), the Threat Register may be **Locked**.
|
||||
Once this gate is signed off (and GBP gap is either resolved or explicitly accepted as blocker), the Threat Register may be **Locked**.
|
||||
|
||||
**Reviewer sign-off:** _________________ Date: _________
|
||||
|
||||
Reference in New Issue
Block a user