Scribe layers beyond NAP and why owners care

Base Core 3, provider extras, provider stacks (Apple vs Google).
This commit is contained in:
porbot
2026-09-15 19:26:53 +00:00
parent 12901e5d5d
commit f752e8d0ae
5 changed files with 66 additions and 0 deletions
+2
View File
@@ -13,4 +13,6 @@ Running definitions for industry terms used in geolocal.io planning.
| **Core 3** | The common US min-bar listing set: GBP, Apple Business Connect, Bing Places. Genre/market adds (Yelp, Facebook, TripAdvisor, vertical dirs) are separate. |
| **Discovery foundation** | Owner-facing name for tier 1: Core listings + NAP/hours/category/contact consistency (internally: “2017”). |
| **AI readiness** | Owner-facing name for tier 2: known-for / recommendability scorecard and structured presence when ready (internally: “2027”). |
| **Apple Stack** | Owner-facing name for Apple Business brand/place-card capabilities above NAP: Brand logo/Style Guide, cover into Maps + Wallet/Pay, Showcases, Actions, Insights — a unified brand OS, not just a Maps pin. |
| **Listings pack** | Per-provider capability model (what GBP / Apple / Bing can hold above NAP). Distinct from **genre pack** (what a salon vs bakery must prove). |