Ty_Tech/geolocal-io
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Scribe layers beyond NAP and why owners care

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
docs/strategy/BUSINESS_PLAN.md
+10
View File
@@ -124,6 +124,16 @@ Three layers (not one giant schema): **A** universal Discovery foundation → **
Deep example packs: [`docs/product/genre-packs/salon.md`](../product/genre-packs/salon.md), [`docs/product/genre-packs/bakery.md`](../product/genre-packs/bakery.md). Index: [`docs/product/genre-packs.md`](../product/genre-packs.md).
### Layers beyond NAP (working direction — essence)
See [`LAYERS-BEYOND-NAP.md`](./LAYERS-BEYOND-NAP.md).
1. **Shared listing basics (Core 3)** — category, hours, website, description, service-area mode
2. **Provider listing extras** — GBP services/posts/actions/attrs; Apple Good to Know / hours types; Bing thinner
3. **Provider stacks** — Apple Stack (brand → Maps+Wallet/Pay, Showcases, Actions); Google = rich but fragmented listing + adjacent products
**Why owners care:** NAP = findable; extras = know what you do; stacks/actions = chosen and acted on.
### Validation gate (working direction — essence)
Anyone using GeoLocal tools must pass a **business-representation check** first (e.g. prove control of a contact channel tied to that business). Mechanism details and free/silver/gold allotments stay open until COGS is real — only the gate itself is directional essence so far.